- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Tue, 09 Oct 2012 14:28:01 -0400
- To: public-xg-webid@w3.org
- Message-ID: <50746CB1.6040309@openlinksw.com>
On 10/9/12 1:58 PM, Henry Story wrote: > I opened this issue now: > https://www.w3.org/2005/Incubator/webid/track/issues/64 > > Please come up with some text, and help along. It's a difficult issue. > > We need text for > > a- what happens when a redirect moves from http to https (security section) > b- how to resolve urls in remote documents that were reached by redirects > c- whether the WebID itself changes if redirected??? > d- a note on reasonable numbers of redirects to follow and pointer to http spec > > > I am not sure I have an answer for c. If the WebID changes, and there's no inference in play (e.g., owl:sameAS), it has to be invalid. That's the nature of the underlying semantics of this identity verification protocol. > > Henry -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Tuesday, 9 October 2012 18:28:24 UTC