- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Mon, 09 Jan 2012 13:21:35 -0500
- To: public-xg-webid@w3.org
- Message-ID: <4F0B302F.1060600@openlinksw.com>
On 1/9/12 1:10 PM, Henry Story wrote: > Well what does the SIA point to? A URN perhaps? Why? It holds an Address. A URL. A URI functioning as a Data Source Name with one level of indirection as opposed to > 1 level of indirection (which is what you get with an HTTP URI based Name). > Otherwise how do you solve the problem of the "luxury of URIs"? By disambiguating Name and Address in the certificate. The SAN holds the Name. and sIA the Address. This is simply for situations where the subject of the cert. can't place a full fidelity Linked Data URI in SAN. > And if it is a URL then why is that not just the place of a WebID then? Because you will ultimately quibble about its complexity. Let's close here, as I need to get stuff implemented, and my team needs my attention. You'll see the end product, as per usual via our implementation. -- 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 Monday, 9 January 2012 18:24:33 UTC