Suggestion on URLs for triple pattern fragments

Hi Ruben,
 
In the draft section 4.2.1 you have proposed that constant IRI should be "the
text value of the IRI, e.g., http://example.org/bar".

I was thinking that it might be good to stick with existing conventions like the
N-Triples encoded RDF value syntax (as used by Sesame) that expect the IRI to be
enclosed in angle brackets, e.g., <http://example.org/bar>.

Furthermore this could enable the use of CURIE syntax in triple pattern
fragments URLs.

Based on the example with URI template
http://example.org/dataset?s={subject}&p={predicate}&o={object} a client could
make requests like:

http://example.org/dataset?s=%3Chttp%3A%2F%2Fexample.org%2Fbar%3E
http://example.org/dataset?p=rdf%3Atype
http://example.org/dataset?p=rdf%3Atype&o=foaf%3APerson

A server would somehow need to advertise which namespace prefixes it supports.
One could even define a minimal set of prefixes that an implementation must
support as part of the standard.

I think adding support for CURIE syntax would help make it a lot easier to hack
together the URL for a fragment and make them more human readable.

Regards,

John Walker
Principal Consultant & co-founder
Semaku B.V.
SFJ 4.009, Torenallee 20, 5617 BC Eindhoven
Mobile: +31 6 475 22030
Email: john.walker@semaku.com
Skype: jaw111

KvK: 58031405
BTW: NL852842156B01
IBAN: NL94 INGB 0008 3219 95

Received on Friday, 25 July 2014 09:10:49 UTC