- From: Peter Ansell <ansell.peter@gmail.com>
- Date: Thu, 17 Nov 2011 08:36:07 +1000
- 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 UTC