- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Sun, 24 Nov 2013 15:29:50 -0500
- To: public-ldp-wg@w3.org
- Message-ID: <529261BE.50100@openlinksw.com>
On 11/24/13 6:12 AM, Henry Story wrote: > On 23 Nov 2013, at 23:59, Ashok Malhotra<ashok.malhotra@oracle.com> wrote: > >> >If we are brainstorming, then why not consider a URI scheme >> >where LDPC-URI#n retrieves the nth member of the container? > That cannot be implemented in HTTP. A #n URI cannot be passed over HTTP. > Requests in HTTP MUST remove the fragment identifier, before making a request. > > Henry > The following [1][2][3] hopefully illustrate Henry's point above re., HTTP URI based denotation (naming). [1] http://bit.ly/17RQQXX -- name resolution protocols and their effect on the notion of data source names (dsns) [2] http://bit.ly/WAJGCp -- Linked Data in a single slide [3] http://bit.ly/15tk1Au -- HTTP URI duality, implicit indirection, and sense. -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter Profile: https://twitter.com/kidehen Google+ Profile: https://plus.google.com/+KingsleyIdehen/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Sunday, 24 November 2013 20:30:12 UTC