- From: Axel Polleres <axel.polleres@deri.org>
- Date: Tue, 20 Apr 2010 14:42:17 +0100
- To: Chimezie Ogbuji <ogbujic@ccf.org>
- Cc: "Andy Seaborne" <andy.seaborne@talis.com>, "SPARQL Working Group" <public-rdf-dawg@w3.org>
May be a stupid question... " This is equivalent to the following SPARQL query: CONSTRUCT { ?s ?p ?o } WHERE { GRAPH <graph_uri> { ?s ?p ?o } } " It seems that in [1] just this part of the equation is questionable, yes? could this be resolved by just saying: "This may be viewed equivalent to the following SPARQL query: CONSTRUCT { ?s ?p ?o } WHERE { GRAPH <graph_uri> { ?s ?p ?o } } posed to a SPARQL endpoint which had any Web retrievable RDF graph in it's <a href="referencetodefinition of Graph store in Update 1.1">Graph store</a>. " 1. http://www.w3.org/2009/sparql/docs/http-rdf-update/#http-get On 19 Apr 2010, at 22:33, Chimezie Ogbuji wrote: > Comments below: > > On 4/19/10 5:40 AM, "Andy Seaborne" <andy.seaborne@talis.com> wrote: > >> However, section 5.4 of HTTP Update [1] says, > >>> The HTTP GET method SHOULD be used to retrieve a graph representation of the > >>> networked RDF knowledge identified by the Request-URI. > >>> > >>> This is equivalent to the following SPARQL query: > >>> > >>> CONSTRUCT { ?s ?p ?o } WHERE { GRAPH<graph_uri> { ?s ?p ?o } } > > > > I'm a bit confused here as to the intent in SPARQL HTTP Update: the > > section "Graph Identification" just talks graph identification, with two > > forms, direct and indirect. It does not talk about graph stores > > Taking a look at the informal definition of a Graph Store from the SPARQL > Update editor's draft: > > [[[ > A Graph Store is a repository of RDF graphs managed by a single service. > Like an RDF Dataset <http://www.w3.org/TR/rdf-sparql-query/#sparqlDataset> > operated on by SPARQL, a Graph Store contains one unnamed graph and zero or > more named graphs. Unlike an RDF dataset, named graphs can be added to or > deleted from a graph store. A Graph Store need not be authoritative for the > graphs it contains. > ]]] > > It looks like this can be re-used verbatim - i.e., the idea of a Graph Store > seems to work as is for both protocols. There is a reference to a formal > definition later in the document that I cannot find. > > > or RDF > > datasets > > I could probably just substitute the common 'Graph store' term for ever > reference to 'dataset' in the HTTP update specification. > > > nor define terminology for the first part of an indirect > > identification: > > > > http://host/thing?graph=http://www.example.org/other/graph > > Beyond re-using the graph store term, what other terminology did you have in > mind? The indirect identification portion describes what determines the > 'request URI' of the operation, but otherwise, the mechanism is the same. > > > Elsewhere in the doc itself, there is indirect reference to graph stores > > and RDF datasets through the use of SPARQL Update illustrations as above. > > -- Chime > > > > > Andy > > > > > > > =================================== > > P Please consider the environment before printing this e-mail > > Cleveland Clinic is ranked one of the top hospitals > in America by U.S.News & World Report (2009). > Visit us online at http://www.clevelandclinic.org for > a complete listing of our services, staff and > locations. > > > Confidentiality Note: This message is intended for use > only by the individual or entity to which it is addressed > and may contain information that is privileged, > confidential, and exempt from disclosure under applicable > law. If the reader of this message is not the intended > recipient or the employee or agent responsible for > delivering the message to the intended recipient, you are > hereby notified that any dissemination, distribution or > copying of this communication is strictly prohibited. If > you have received this communication in error, please > contact the sender immediately and destroy the material in > its entirety, whether electronic or hard copy. Thank you. > >
Received on Tuesday, 20 April 2010 13:43:09 UTC