W3C home > Mailing lists > Public > public-rdf-wg@w3.org > February 2012

status of ACTION-143: %nn is *NOT* unescaped while parsing

From: Eric Prud'hommeaux <eric@w3.org>
Date: Wed, 15 Feb 2012 11:03:06 -0500
To: public-rdf-wg@w3.org
Message-ID: <20120215160305.GA11289@w3.org>
I added this note:
[[ Note
The <PERCENT> terminal matches %-encoding sequences. These sequences are not decoded during processing; a term written as <http://a.example/%66oo\-bar> in Turtle designates the RDF IRI http://a.example/%66oo-bar.
]]
but haven't been able to push 'cause of
[[
eric@eric-ubu:~/WWW/t/rdf$ hg push
pushing to http://dvcs.w3.org/hg/rdf/
searching for changes
abort: HTTP Error 405: push requires POST request
]]

I note that the normative text:
[[
Turtle strings and IRIs can use \-escape sequences to represent Unicode code points.
…
Escape sequence 	Unicode code point
'\u' hex hex hex hex 	A Unicode codepoint in the range U+0 to U+FFFF inclusive corresponding to the encoded hexadecimal value.
'\U' hex hex hex hex hex hex hex hex 	A Unicode codepoint in the range U+10000 to U+10FFFF inclusive corresponding to the encoded hexadecimal value.
'\t' 			U+0009
'\n' 			U+000A
'\r' 			U+000D
'\"' (inside string) 	U+0022
'\\' 			U+005C
]]
does not include all of the places \-escapes can appear (e.g. localnames) or the various kinds of escaping. The former issue can be addressed by adding "and localnames":
[[
Turtle strings, IRIs and local names can use \-escape sequences to represent Unicode code points.
]]
but I'm working on a more wholistic proposal.
-- 
-ericP
Received on Wednesday, 15 February 2012 16:03:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:02:03 UTC