Re: RDF-ISSUE-123 (localName chars): PN_CHARS_BASE permits up to U+EFFFF but RFC-3987 stops at U+EFFFD [RDF Turtle] from Andy Seaborne on 2013-03-24 (public-rdf-wg@w3.org from March 2013)

From: Andy Seaborne <andy.seaborne@epimorphics.com>
Date: Sun, 24 Mar 2013 11:26:46 +0000
To: public-rdf-wg@w3.org
Message-ID: <514EE2F6.7060201@epimorphics.com>

On 24/03/13 05:40, RDF Working Group Issue Tracker wrote:
> RDF-ISSUE-123 (localName chars): PN_CHARS_BASE permits up to U+EFFFF but RFC-3987 stops at U+EFFFD [RDF Turtle]
>
> http://www.w3.org/2011/rdf-wg/track/issues/123
>
> Raised by: Eric Prud'hommeaux
> On product: RDF Turtle
>
> Gregg Kellogg pointed out in http://www.w3.org/mid/49EB390E-BCA6-401B-98EC-F4DD6A44AD0B@greggkellogg.net that Turtle's localNames overrun RFC-3987 iri by two characters. These two Unicode characters are reserved for process-internal use and thusly don't make sense in a global identification scheme.
>
> Should we shave PN_CHARS_BASE down to [#x10000-#xEFFFF]? If this is a bug fix, can we do that without another LC?
>
>
>

I prefer Gregg's solution of making the the IRIs in tests legal by RFC 
3987.  The grammar may be wider - it is anyway because we don't include 
an RFC 3986/3987 parser (or scheme specific rules).

 Andy

Received on Sunday, 24 March 2013 11:27:17 UTC