W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2015

[Bug 28476] [SER 3.1]JSON serialization: escaping strings

From: <bugzilla@jessica.w3.org>
Date: Mon, 13 Apr 2015 14:38:59 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28476-523-tUHvIbVAHV@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28476

Josh Spiegel <josh.spiegel@oracle.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |josh.spiegel@oracle.com

--- Comment #5 from Josh Spiegel <josh.spiegel@oracle.com> ---
Serialization-json-42 and Serialization-json-57 allow the serialization error
(SESU0007) since implementations are not required to support US-ASCII.  See
section 9.1.3:

"The encoding parameter identifies the encoding that the JSON output method
MUST use to convert sequences of characters to sequences of bytes. Serializers
are REQUIRED to support values of UTF-8 and UTF-16. A serialization error
[err:SESU0007] occurs if the serializer does not support the encoding specified
by the encoding parameter."

These tests also allow the character to be escaped.  From Section 4, bullet 3.
e:
"Escape according to the rules of the XML, HTML, or JSON output method, ...
where JSON requires escaping, and any characters that cannot be represented in
the selected encoding."

By the way, I raised the same concern as you about strings (see bug 27330).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 13 April 2015 14:39:05 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 14:39:06 UTC