- From: <bugzilla@jessica.w3.org>
- Date: Fri, 29 May 2015 10:00:59 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28663 Michael Kay <mike@saxonica.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |public-qt-comments@w3.org Flags| |needinfo?(public-qt-comment | |s@w3.org) --- Comment #1 from Michael Kay <mike@saxonica.com> --- I'm finding the rules quite hard to decipher, and I think we can achieve greater clarity by refactoring them as follows: (1) If the attribute escaped="true" is present for a string value, or escaped-key="true" for a key value, then: (1.a) any valid JSON escape sequence present in the string is copied unchanged to the output, (1.b) any invalid JSON escape sequence results in a dynamic error [err:FOJS0007]. (1.c) any unescaped occurrence of quotation mark, backspace, form-feed, newline, carriage return, or tab is replaced by \", \b, \f, \n, \r, or \t respectively, (1.d) any other codepoint in the range 1-31 or 127-159 is replaced by an escape in the form \uHHHH where HHHH is the upper-case hexadecimal representation of the codepoint value. (2) Otherwise (that is, in the absence of the attribute escaped="true" for a string value, or escaped-key="true" for a key value): (2.a) any occurrence of backslash (\) is replaced by \\ (2.b) any occurrence of quotation mark, backspace, form-feed, newline, carriage return, or tab is replaced by \", \b, \f, \n, \r, or \t respectively, (2.c) any other codepoint in the range 1-31 or 127-159 is replaced by an escape in the form \uHHHH where HHHH is the upper-case hexadecimal representation of the codepoint value. I agree that we should allow lower-case A-F in an escape sequence. At one time I was under the impression JSON did not allow this, but this was because I overlooked an obscure clause in RFC4234 whose effect is that the ABNF "A"|"B"|"C" doesn't mean what you think it does. -- You are receiving this mail because: You are the QA Contact for the bug. You are on the CC list for the bug.
Received on Friday, 29 May 2015 10:01:01 UTC