- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Sun, 25 Mar 2012 18:02:00 -0400
- CC: www-tag@w3.org, "public-lod@w3.org" <public-lod@w3.org>
- Message-ID: <4F6F95D8.4070700@openlinksw.com>
On 3/25/12 5:51 PM, Kingsley Idehen wrote: >> > > With regards to (ISSUE-57, performance and deployment of discovery) > i.e., reducing the challenges that 303 redirection posses to some > systems, you have the following items which are already covered in > section 4.1 of your doc [1]: > > 200 OK > Link: <http://example.com/uri-documentation>; rel="describedby" > > 303 See Other > Location: http://example.com/uri-documentation> > > Either of the above introduce heuristics that existing Linked Data > compliant user agents can choose to implement. > > In the specific case of "Link:" you have the added benefit of a > heuristic that works for Web developers that are interested in > structured data and even high-fidelity linked data modulo anything to > do with R-D-F. Basically, those that don't have any interested in > processing HTTP response metadata simply have the option to process > identical <link/> relations in the <head/> section of (X)HTML resources. > > Links: > > 1. http://www.w3.org/2001/tag/doc/uddp-20120229/ -- Understanding URI > Hosting Practice as Support for URI Documentation Discovery . *Typo fixed edition* With regards to (ISSUE-57, performance and deployment of discovery) i.e., reducing the challenges that 303 redirection posses to some systems, you have the following items which are already covered in section 4.1 of your doc [1]: 200 OK Link: <http://example.com/uri-documentation>; rel="describedby" 303 See Other Location: http://example.com/uri-documentation> Either of the above introduce heuristics that existing Linked Data compliant user agents can choose to implement. In the specific case of "Link:" you have the added benefit of a heuristic that works for Web developers that are interested in structured data and even high-fidelity linked data modulo anything to do with R-D-F. Basically, those that don't have any *interest* in processing HTTP response metadata simply have the option to process identical <link/> relations in the <head/> section of (X)HTML resources. Links: 1. http://www.w3.org/2001/tag/doc/uddp-20120229/ -- Understanding URI Hosting Practice as Support for URI Documentation Discovery . -- 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 Sunday, 25 March 2012 22:02:44 UTC