W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > October to December 2009

Re: HTTP Update : graph naming

From: Paul Gearon <gearon@ieee.org>
Date: Tue, 10 Nov 2009 13:46:15 -0500
Message-ID: <a25ac1f0911101046h5d4c566fw9d08ea5453326708@mail.gmail.com>
To: Steve Harris <steve.harris@garlik.com>
Cc: Andy Seaborne <andy.seaborne@talis.com>, RDF Data Access Working Group <public-rdf-dawg@w3.org>
On Tue, Nov 10, 2009 at 1:25 PM, Steve Harris <steve.harris@garlik.com> wrote:
> On 10 Nov 2009, at 12:45, Andy Seaborne wrote:
<snip/>
>> 2/ Extreme URIs.
>>
>> For the non-query string form, corner case URIs can be difficult or
>> ambiguous.  URI scheme names may appear in URIs as legitimate character
>> strings so looking for a ":" is not always safe enough.
>>
>> Some (unusual URIs - but this is a spec) cases: one level of encoding
>> removed for clarity.
>>
>> # Two encoded http: in URI
>> http://service/graphs/http://other/abc/http://yetanother/xyz
>
> We do exactly one URI decode pass, remove the "known" prefix and the rest is
> the graph URI.
>
> However, I'm not especially advocating the /path/$(uri-encoded-uri)
> approach, we'd be happy with
> /path/?graph=$(uri-encoded-uri) also.

I prefer the /path/?graph=$(uri-encoded-uri) approach. We use it
because we use a servlet engine for hosting our SPARQL endpoint, and
this approach is the easiest to fit in.

Regards,
Paul Gearon
Received on Tuesday, 10 November 2009 18:46:55 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:40 GMT