- From: <bugzilla@jessica.w3.org>
- Date: Mon, 13 Apr 2015 16:21:58 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28479 --- Comment #2 from Michael Kay <mike@saxonica.com> --- OK, I wasn't looking at section 4. If that's the case, then the paragraph in section 11 (Character maps) Character mapping is applied to the characters that actually appear in a text or attribute node in the instance of the data model, before any other serialization operations such as escaping or Unicode Normalization are applied. is misleading, because (a) "the instance of the data model" seems to be saying "the input to the serializer" rather than "the output of sequence normalization", and (b) any other serialization operations" is too broad. The way the spec was written for XML/HTML, it was clear that character maps did NOT apply to markup generated during the "Markup Generation" phase. I think it is desirable that this principle should also apply for JSON; but it's not at all clear under the current spec whether it does; and indeed the inclusion of "strings" in the input to the character expansion phase muddies the water for the traditional XML/HTML methods as well. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 13 April 2015 16:22:01 UTC