- From: <bugzilla@jessica.w3.org>
- Date: Tue, 02 Dec 2014 17:45:59 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27478
C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com> ---
The joint WGs discussed this bug today. JSON (as defined by RFC 7159) doesn't
require escaping of characters other than " and \ but on consideration the WGs
agreed that it's probably useful to escape other characters which might
otherwise frequently be corrupted in transmission over some channels.
The rules in serialization will be aligned with the json-to-xml function of
XSLT [1], which says that in addition to escaping \,
any occurrence of quotation mark, backspace, form-feed, newline,
carriage return, or tab is replaced by \", \b, \f, \n, \r, or \t
respectively, and any other codepoint in the range 1-31 or 127-159 is
replaced by an escape in the form \uHHHH where HHHH is the hexadecimal
representation of the codepoint value.
[1] http://www.w3.org/TR/xslt-30/#func-xml-to-json
We believe this resolves the issues, so we are marking this Bugzilla entry
RESOLVED.
Christian, if you would review this resolution and indicate your agreement by
changing the bug status to CLOSED (or your dissent by RE-OPENING it), it would
be helpful. If we don't hear from you in the next two weeks, we will assume
that you are content with the resolution of the issue.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 2 December 2014 17:46:05 UTC