- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Mon, 09 Jan 2012 07:41:55 -0500
- To: WebID XG <public-xg-webid@w3.org>
- Message-ID: <4F0AE093.5020208@openlinksw.com>
All, Please note: http://tools.ietf.org/html/rfc6415 . This is an important note is about: a method for locating host metadata as well as information about individual resources controlled by a given host. This is another approach that reduces the nuanced laced tedium associated with publishing Linked Data. Basically, there is a dedicated metadata resource that includes information the aids user agents re. understanding URIs (via templates) as provided by a particular host of resources. Re. Linked Data deployment think of this as the 3rd option alongside: 1. hash URIs -- carries implicit Name/Address disambiguation courtesy of fragment identifier semantics 2. slash URIs -- requiring explicit HTTP message exchange based Name/Address disambiguation 3. host metadata -- a dedicated resource that basically handles URI role comprehension en route to Name/Address disambiguation. You can't deliver or effectively exploit Linked Data solutions without properly understanding Name/Address disambiguation. -- 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 12:42:27 UTC