- From: David Booth <david@dbooth.org>
- Date: Tue, 04 Jun 2013 17:26:22 -0400
- To: Alexandre Bertails <bertails@w3.org>
- CC: Henry Story <henry.story@bblfish.net>, Mark Baker <mark@zepheira.com>, Kingsley Idehen <kidehen@openlinksw.com>, "public-ldp@w3.org" <public-ldp@w3.org>
On 06/04/2013 04:14 PM, Alexandre Bertails wrote: > On 06/04/2013 03:13 PM, Henry Story wrote: >> >> On 4 Jun 2013, at 20:21, Alexandre Bertails <bertails@w3.org> wrote: [ . . . ] >>> At most, RDF is HTTP friendly. For example, that's why SPARQL does not >>> operate on datasets living on the web (the dataset is behind the >>> service), and you need to interact with the resources through the >>> service, whether they are HTTP URIs or not. >> >> I am not familiar enough with SPARQL, so I'll leave that be. >> I am familiar with HTTP though, and that is more important >> and more widely used. > > Where -- other than in LDP -- have you seen people defining how to > interact with RDF using HTTP? The SPARQL Graph Store Protocol defines a standard way to manage and interact with a collection of RDF graphs: http://www.w3.org/TR/sparql11-http-rdf-update/ David
Received on Tuesday, 4 June 2013 21:26:54 UTC