W3C home > Mailing lists > Public > public-rdf-dawg-comments@w3.org > June 2012

RE: Direct Graph Identification

From: Philip Fennell <Philip.Fennell@marklogic.com>
Date: Tue, 5 Jun 2012 22:47:02 -0700
To: "public-rdf-dawg-comments@w3.org" <public-rdf-dawg-comments@w3.org>
Message-ID: <D20C296D14127D4EBD176AD949D8A75A2056EAE017@EXCHG-BE.marklogic.com>
Chime,

> We would be grateful if you would acknowledge that your comments have
> been answered by sending a reply to this mailing list.

Yes it does. Thank you.


Regards

Philip

-----Original Message-----
From: Chimezie Ogbuji [mailto:chimezie@gmail.com] 
Sent: Tuesday, June 05, 2012 1:39 PM
To: Philip Fennell; public-rdf-dawg-comments@w3.org
Subject: Re: Direct Graph Identification

Philip,

Yes, this is correct, assuming

   http://example.com/rdf-graphs

Identifies a Graph Store managed by an HTTP service that is an
implementation of this protocol and

   http://example.com/rdf-graphs/employees

is the graph IRI associated with an RDF graph within that Graph Store

We would be grateful if you would acknowledge that your comments have
been answered by sending a reply to this mailing list.

Regards,

Chime Ogbuji, on behalf of the SPARQL WG.

On Mon, 23 Jan 2012 at 06:14,  Philip Fennell wrote:
> I've had a quick look in the archive but have not found anything the immediately answers my questions, which is:
> I'm not sure I understand the distinction between Direct Graph Identification and Indirect Graph Identification that uses the graph request parameter to identify a named
> graph.

> With respect to Direct Graph Identification (section 4.1 of the SPARQL 1.1 Graph Store HTTP Protocol) can I deduce from the following statements:

> 'Per [RFC2616]<http://www.w3.org/TR/sparql11-http-rdf-update/>, the most common usage of a Request-URI is to identify a resource on an origin server or gateway. In our
> example, the corresponding request URI (http://example.com/rdf-graphs/employees) is meant to identify RDF triples on the example.com server that describe employees. In
> addition, the request specifies the GET method, which means that a representation of these triples should be returned. In this case, the preferred representation format is
> application/rdf+xml

> In this way, the server would route operations on a named graph in an Graph Store via its Graph IRI. However, in using a URI in this way, we are not directly identifying an
> RDF graph but rather the RDF graph content that is represented by an RDF document, which is a serialization of that graph. Intuitively, the set of interpetations that satisfy
> [RDF-MT]<http://www.w3.org/TR/sparql11-http-rdf-update/> the RDF graph that the RDF document is a serialization of can be thought of as this RDF graph content.'

> that by using 'Direct Graph Identification', the graph content that you would be addressing with:
> <http://example.com/rdf-graphs/employees>
> is a 'Named Graph' and an equivalent request would be, for example:
> <http://example.com/rdf-graphs?graph= http%3A%2F%2Fexample.com%2Frdf-graphs%2Femployees>
Received on Wednesday, 6 June 2012 05:47:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 6 June 2012 05:47:29 GMT