29934 2016-10-11 19:32:58 +0000 fn-parse-json-110 expects wrong result 2016-10-21 10:08:20 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 3 & XPath 3 Test Suite Candidate Recommendation PC All RESOLVED FIXED P2 normal --- 1 josh.spiegel oneil andrew_coleman mike public-qt-comments oldest_to_newest 127742 0 josh.spiegel 2016-10-11 19:32:58 +0000 <test-case name="fn-parse-json-110" xmlns="http://www.w3.org/2010/09/qt-fots-catalog"> <created by="Michael Kay" on="2016-09-29"/> <test><![CDATA[parse-json('{"'||codepoints-to-string((10, 37))||'":"x", "\n%":"y"}', map{'escape':true(), 'duplicates':'reject'})]]></test> <result> <error code="FOJS0003"/> </result> </test-case> The input to parse-json is not a valid JSON text. From RFC7159: <quote> All Unicode characters may be placed within the quotation marks, except for the characters that must be escaped: quotation mark, reverse solidus, and the control characters (U+0000 through U+001F). </quote> Therefore, passing a naked control character should raise FOJS0001. 127892 1 andrew_coleman 2016-10-21 07:20:13 +0000 The WG agreed the following resolution: ACTION A-657-15: O'Neil to fix the tests mentioned in this bug report, fn-parse-json-110, bug 29934 127897 2 mike 2016-10-21 10:08:20 +0000 I have split the test into two, one testing for duplicates with the original intent, and one testing that raw control characters are rejected.