W3C home > Mailing lists > Public > public-rdf-dawg-comments@w3.org > November 2011

Re: SPARQL 1.1 Service Description comment

From: Peter Ansell <ansell.peter@gmail.com>
Date: Thu, 17 Nov 2011 08:36:07 +1000
Message-ID: <CAGYFOCT9SyrfPBK2jcv4M+DKDaH0D4ihAYaVXMaNv4MV-fgr8A@mail.gmail.com>
To: Toby Inkster <tai@g5n.co.uk>
Cc: public-rdf-dawg-comments@w3.org
One solution could be to change the GRAPH URIs and advertise the new
ones in the Service Description (which you could embed using RDFa or
return RDF based on Content Negotiation).

You have already equated three things with the one URI, ie, the Wiki
page, the SPARQL endpoint, and the Graph URI. You may have to
sacrifice one or two of them to save the system if you want to support
SD.

Cheers,

Peter

On 17 November 2011 08:07, Toby Inkster <tai@g5n.co.uk> wrote:
> I've been working on a DataWiki recently. This is basically a wiki
> where each page is not a traditional document, but an RDF graph.
>
> Rather than having a single endpoint for querying, each graph URI is
> its own endpoint. So to query this graph:
>
>        http://example.com/mydata
>
> You'd send the query like this:
>
>        http://example.com/mydata?query=SELECT...
>
> Apparently to comply with SD, I'd need to add the SD to every request
> for <http://example.com/mydata>. But as <http://example.com/mydata> is
> the graph URI, I don't want to pollute GET requests to it with SD
> triples.
>
> Ideally I'd like to only return the SD in return to a request using the
> HTTP "OPTIONS" method, and not "GET".
>
> --
> Toby A Inkster
> <mailto:mail@tobyinkster.co.uk>
> <http://tobyinkster.co.uk>
>
>
>
Received on Wednesday, 16 November 2011 22:36:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 16 November 2011 22:36:48 GMT