- From: <nobody@w3.org>
- Date: Mon, 27 Jul 2015 19:44:20 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28996
Bug ID: 28996
Summary: json-doc-021 and json-to-xml-021 should expect \f
instead of \u000C
Product: XPath / XQuery / XSLT
Version: Candidate Recommendation
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: XQuery 3 & XPath 3 Test Suite
Assignee: oneil@saxonica.com
Reporter: josh.spiegel@oracle.com
QA Contact: public-qt-comments@w3.org
Target Milestone: ---
Group: XSLXQuery_WG
json-doc-021:
<test-case name="json-doc-021">
<description>Character invalid in XML 1.0 in a string and a key: escape
true</description>
...
<test><![CDATA[
fn:json-doc('http://www.w3.org/qt3/json/mapUnescape10-json',
map{'escape':true()})
]]></test>
<result>
<assert-deep-eq>map{"a":"\u000C", "\u0007":"bell"}</assert-deep-eq>
</result>
</test-case>
mapUnescape10-json
{
"a":"\u000C",
"\u0007":"bell"
}
>From section 17.5.1 parse-json, when 'escape' is true:
"Special characters in the JSON input are represented using JSON escape
sequences in the result. This applies whether or not the relevant characters
were represented using JSON escape sequences in the input. The characters that
are considered "special" for this purpose are all codepoints in the range x00
to x1F or x7F to x9F, .... Such characters are represented using a
two-character escape sequence where available (for example, \t) or a
six-character escape sequence otherwise (for example \uDEAD)."
The expected result should be:
<assert-deep-eq>map{"a":"\f", "\u0007":"bell"}</assert-deep-eq>
json-to-xml-021 also needs to be updated.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 27 July 2015 19:44:22 UTC