- From: <bugzilla@jessica.w3.org>
- Date: Tue, 25 Oct 2016 11:30:42 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29928 --- Comment #3 from Michael Kay <mike@saxonica.com> --- I have updated the non-normative error descriptions in appendix A.2 as follows: <error class="JS" code="0001" label="JSON syntax error." type="dynamic"> <p diff="add" at="A">Raised by functions such as <code>fn:json-doc</code>, <code>fn:parse-json</code> <phrase diff="add" at="D">or <code>fn:json-to-xml</code></phrase> if the string supplied as input does not conform to the JSON grammar (optionally with implementation-defined extensions).</p></error> <error class="JS" code="0003" label="JSON duplicate keys." type="dynamic"><p diff="add" at="A">Raised by functions such as <code>map:merge</code>, <code>fn:json-doc</code>, <code>fn:parse-json</code> <phrase diff="add" at="D">or <code>fn:json-to-xml</code></phrase> if the input contains duplicate keys, when the chosen policy is to reject duplicates.</p></error> <error class="JS" code="0004" label="JSON: not schema-aware." type="dynamic"><p diff="add" at="D">Raised by <code>fn:json-to-xml</code> if validation is requested when the processor does not support schema validation or typed nodes.</p></error> <error class="JS" code="0005" label="Invalid options." type="dynamic"><p diff="add" at="D">Raised by functions such as <code>map:merge</code>, <code>fn:parse-json</code>, and <code>fn:xml-to-json</code> if the <code>$options</code> map contains an invalid entry.</p></error> <error class="JS" code="0006" label="Invalid XML representation of JSON." type="dynamic"><p diff="add" at="D">Raised by <code>fn:xml-to-json</code> if the XML input does not conform to the rules for the XML representation of JSON.</p></error> <error class="JS" code="0007" label="Bad JSON escape sequence." type="dynamic"><p diff="add" at="D">Raised by <code>fn:xml-to-json</code> if the XML input uses the attribute<code>escaped="true"</code> or <code>escaped-key="true"</code>, and the corresponding string or key contains an invalid JSON escape sequence.</p></error> -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 25 October 2016 11:30:50 UTC