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.
