Re: s/URI/IRI/ in http://www.w3.org/TR/sparql11-http-rdf-update/#indirect-graph-identification

* Jeremy Carroll <jeremy@topquadrant.com> [2011-02-16 15:03-0800]
> 
> Hi Chime
> 
> we are just having a discussion about % decoding etc.
> 
> Suggested modification to text:
> 
> Old text:
> [[
> SHOULD invoke the indicated operation on the RDF knowledge
> identified by the URI embedded in the query component where the URI
> is the result of percent-decoding the value associated with the
> /graph/ key.
> ]]
> 
> Suggested text:
> [[
> SHOULD invoke the indicated operation on the RDF knowledge
> identified by the IRI embedded in the query component where the IRI
> is the result of percent-decoding the value associated with the
> /graph/ key.
> ]]

+1
and BTW, I wouldn't use RDF's URI-reference; the def'n I've been using for IRI is:

<a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference">RDF URI-reference</a> as subsequently <a href="http://www.w3.org/TR/rdf-sparql-query/#docTerminology¹">restricted by SPARQL</a>

I think further wordsmithing is in order.

The IRI lineage is a but funny. RDF mandates the %-encoding of any non-ASCII. It preceeded 2397 so it professed a compatibility instead with XML Namespace IRIs (which includes the small non-ASCII range [\xA0-\xEFFFD], as well as ' '). Somehow, the RDF world seemed to move as one from "<%E6%A4%8D%E7%89%A9#%E5%90%8D>" to "<怍物#名>". SPARQL declares its IRIs to "correspond" to RDF URI References and provides a grammar which excludes ' ', but copies XML's Name production. At any rate, the world seems to have agreed to IRIs, so let's breath a sigh of relief and perpetuate this boon to I18N.

¹ of course, you're probably already in lockstep with SPARQL11 so you needed ref 1.0 .
-- 
-ericP

Received on Thursday, 17 February 2011 04:09:22 UTC