- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Mon, 10 Nov 2014 16:51:13 -0500
- To: public-ldp-wg@w3.org
- Message-ID: <54613351.2070409@openlinksw.com>
On 11/10/14 4:02 PM, Ashok Malhotra wrote: > Hi Kingsley: > Could you give an example of how a query using a Link header > would look like? > All the best, Ashok Ashok, Henry has covered this already, all I am hinting here is that a "Link:" request header route is going to be more feasible than getting a new verb added to HTTP. Basically, via a Link: headers in the request, one can indicate the nature of the request using RDF Language i.e., look at Link: as just another notation for representing relations using RDF Language (which is distinct for any specific notation). Ultimately, all I see is a slot for SPARQL payloads, everything else (in my eyes) is a SPARQL redo adventure, for all the wrong reasons. SPARQL is extremely powerful and useful, especially the SPARQL 1.1 edition. Combine that with WebID-TLS and ACLs and you have everything we need ++. Kingsley > > On 11/10/2014 2:04 PM, Kingsley Idehen wrote: >> On 11/10/14 1:43 PM, Ashok Malhotra wrote: >>> So, yes, a QUERY verb would be preferable. >>> How difficult would this to get through? >>> We could ask Mark Nottingham. >>> All the best, Ashok >> >> He will more than likely direct you back to a Link: relation. >> >> Note, you can use Link: headers in HTTP requests too :) >> >> >> [1] >> http://lists.w3.org/Archives/Public/public-webpayments/2014Jul/0112.html >> . >> [2] https://github.com/mnot/I-D/issues/61 . >> > > > > -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog 1: http://kidehen.blogspot.com Personal Weblog 2: 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 Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Monday, 10 November 2014 21:51:36 UTC