Re: Service or graph store naming.

On Tue, Feb 8, 2011 at 11:14 AM, Andy Seaborne
<andy.seaborne@epimorphics.com> wrote:
> ..snip...
> If I can read the document so that:
>
> http://example.com/rdf-graphs/ is a graph store
> http://example.com/rdf-graphs/service is a service on the graph store
>
> then my confusion about service or graph store is addressed.

Ok.  I've made all the changes suggested below into the editor's draft
and I've added an example (for consistency) for the 'POST to the graph
store scenario' in 5.4 HTTP POST:

-------------------------

So, given the following request and response:

    GET /rdf-graphs/service HTTP/1.1
    Host: example.com
    Accept: application/rdf+xml

    HTTP/1.1 200 OK
    Date: .. some date ..
    Server: ... etc ...
    Last-Modified: .. some date ..
    Etag: ".. etc .."
    Content-Length: .. length of service description document ..
    Connection: close

    @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
    @prefix sd: <http://www.w3.org/ns/sparql-service-description#> .

    <> a sd:Service;
       sd:defaultDatasetDescription  <http://www.example.com/rdf-graphs> .
    <http://www.example.com/rdf-graphs> a sd:Dataset
    ..snip..

Then the following are equivalent:

POST /rdf-graphs HTTP/1.1
    Host: example.com
    Accept: application/rdf+xml
    ... RDF payload ...

    CREATE GRAPH <new_uri>
    INSERT DATA { GRAPH <new_uri> {.. RDF payload .. } }

--------------------------------------

I also updated the diagrams to reflect new terminology (forgot to do this)

-- Chime

Received on Tuesday, 8 February 2011 21:37:16 UTC