ISSUE-123: PN_CHARS_BASE permits up to U+EFFFF but RFC-3987 stops at U+EFFFD
localName chars
PN_CHARS_BASE permits up to U+EFFFF but RFC-3987 stops at U+EFFFD
- State:
- CLOSED
- Product:
- RDF Turtle
- Raised by:
- Eric Prud'hommeaux
- Opened on:
- 2013-03-24
- Description:
- 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? - Related Actions Items:
- No related actions
- Related emails:
- Re: RDF-ISSUE-123 (localName chars): PN_CHARS_BASE permits up to U+EFFFF but RFC-3987 stops at U+EFFFD [RDF Turtle] (from gregg@greggkellogg.net on 2013-03-25)
- Re: RDF-ISSUE-123 (localName chars): PN_CHARS_BASE permits up to U+EFFFF but RFC-3987 stops at U+EFFFD [RDF Turtle] (from eric@w3.org on 2013-03-24)
- Re: RDF-ISSUE-123 (localName chars): PN_CHARS_BASE permits up to U+EFFFF but RFC-3987 stops at U+EFFFD [RDF Turtle] (from gregg@greggkellogg.net on 2013-03-24)
- 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@epimorphics.com on 2013-03-24)
- RDF-ISSUE-123 (localName chars): PN_CHARS_BASE permits up to U+EFFFF but RFC-3987 stops at U+EFFFD [RDF Turtle] (from sysbot+tracker@w3.org on 2013-03-24)
Related notes:
As discussed here, I'm satisfied with the resolution. It could perhaps go in the errata, but the fact that we already normatively reference RFC-3987 makes the meaning unambiguous.
http://lists.w3.org/Archives/Public/public-rdf-comments/2013Mar/0032.html
Display change log
