Aldo Bucchi wrote:
Hello,
The question is not wether the URIQA should be https or not, sorry.
The question is actually:
Is there automatic redirection from http to https?
This is an old question lurking in the LOD mailing lists, I would like
to know what others think and what the best practices are.
Is there a sameAs created implicitly?
This is a tricky issue.
This what you see re. ODS once the Identity VAD has been installed and
instance endpoints configured.
http://myopenlink.net/ods should be working this way right now re.
FOAF+SSL (note the padlock on the home page which is the key indicator).
Also remember, you can make re-write rules do whatever you want (within
reason), so conditional redirection is always there to be exploited.
Generally, the workflow is:
1. Authenticate securely with a Web ID (Personal URI bound to an X.509
cert.)
2. Use data access policies (rules which can exist in RDF using N3 or
other representation formats) to control access to resources by the
authenticated Web ID (the protected resources have "https" based URIs.
The only issue we have right now is that the policy aspect (which is a
bizarre back to the future thing for us since our UDA products have
possessed data access rules books 1993) isn't completely implemented for
high level use. We basically, are a month or less away from completion.
Kingsley
Thanks,
A
On Fri, Aug 7, 2009 at 3:42 PM, Aldo Bucchi<aldo.buc...@gmail.com> wrote:
Hello,
Imagine Virtuoso sitting as the front door to the ( group of ) Linked
Data Space( s ) of a corporation.
We would like URIs to be permanent and valid throughout the web, so it
makes sense to assign a URIQA in the public realm.
http://data.company.com/
So I can have URIs like so
http://data.company.com/person/ssn/xxxx
Of course, this is not necessarily "open" to the rest of the world.
Then, the access partitioning is achieved via ACLs and other means
underneath. Which leads me to the following question.
Once the user agent is authenticated, it should issue requests via
HTTPS. But this changes the URIs ( http --> https ).
Can this be achieved using some transparent redirection?
So that my URIs remain HTTP but the actual dereferencing takes place
using HTTPS?
Or should I just go for https://data.company.com/ as URIQA?
I see no problem in doing that ( the roundtrip is not significant in
relative terms ).
Thanks,
A
--
Aldo Bucchi
skype:aldo.bucchi
http://www.univrz.com/
http://aldobucchi.com/
PRIVILEGED AND CONFIDENTIAL INFORMATION
This message is only for the use of the individual or entity to which it is
addressed and may contain information that is privileged and confidential. If
you are not the intended recipient, please do not distribute or copy this
communication, by e-mail or otherwise. Instead, please notify us immediately by
return e-mail.
--
Regards,
Kingsley Idehen Weblog: http://www.openlinksw.com/blog/~kidehen
President & CEO
OpenLink Software Web: http://www.openlinksw.com
