- From: <bugzilla@jessica.w3.org>
- Date: Mon, 13 Apr 2015 13:37:54 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28476 --- Comment #4 from Michael Kay <mike@saxonica.com> --- I now see that section 4 clause 3(e) provides additional material on JSON escaping, and contradicts section 9.1.3 by saying that escaping IS applied to characters that cannot be represented in the chosen encoding. However section 4 clause 3 is still a little vague as to what strings it applies to. It starts: "Character expansion is concerned with the representation of characters appearing in text and attribute nodes and strings in the sequence. ". Normally I would interpret this as "instances of xs:string appearing as items in the sequence to be serialized". But the intended meaning is clearly more general than this: JSON escaping needs to be applied to anything that appears as a string in the output, whether or not it started life as a "string in the sequence". For example it applies to strings within arrays or maps; to values of type untypedAtomic or anyURI or QName; and to the strings that result from serializing nodes. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 13 April 2015 13:38:01 UTC