<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://www.w3.org/Bugs/Public/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4"
          urlbase="https://www.w3.org/Bugs/Public/"
          
          maintainer="sysbot+bugzilla@w3.org"
>

    <bug>
          <bug_id>29759</bug_id>
          
          <creation_ts>2016-07-29 09:20:10 +0000</creation_ts>
          <short_desc>[QT3TS] fn-parse-json-923, 924</short_desc>
          <delta_ts>2016-07-29 12:57:50 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>XPath / XQuery / XSLT</product>
          <component>XQuery 3 &amp; XPath 3 Test Suite</component>
          <version>Candidate Recommendation</version>
          <rep_platform>PC</rep_platform>
          <op_sys>Windows NT</op_sys>
          <bug_status>CLOSED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Tim Mills">tim</reporter>
          <assigned_to name="O&apos;Neil Delpratt">oneil</assigned_to>
          <cc>mike</cc>
          
          <qa_contact name="Mailing list for public feedback on specs from XSL and XML Query WGs">public-qt-comments</qa_contact>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>127072</commentid>
    <comment_count>0</comment_count>
    <who name="Tim Mills">tim</who>
    <bug_when>2016-07-29 09:20:10 +0000</bug_when>
    <thetext>The expected result   

&lt;assert-eq&gt;&apos;&amp;#xFFFD;&apos;&lt;/assert-eq&gt;

is wrong - it should be

&lt;assert-eq&gt;[&apos;&amp;#xFFFD;&apos;]&lt;/assert-eq&gt;

  &lt;test&gt;parse-json(&apos;[&quot;\u0000&quot;]&apos;, map{&apos;escape&apos;:false()})&lt;/test&gt;
      &lt;result&gt;
         &lt;any-of&gt;
            &lt;assert-eq&gt;&apos;&amp;#xFFFD;&apos;&lt;/assert-eq&gt;
            &lt;error code=&quot;FOJS0001&quot;/&gt;
         &lt;/any-of&gt;</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>127076</commentid>
    <comment_count>1</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2016-07-29 10:00:23 +0000</bug_when>
    <thetext>Actually I think the result is valid, probably by accident, because

[&apos;a&apos;] eq &apos;a&apos;

is true. A better test would be to use deep-equal.

But looking at the tests, I don&apos;t see any justification in the expected result FOJS0001. I don&apos;t think an error result is conformant for either of these two tests.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>127079</commentid>
    <comment_count>2</comment_count>
    <who name="Tim Mills">tim</who>
    <bug_when>2016-07-29 10:14:55 +0000</bug_when>
    <thetext>I&apos;ve no idea where &quot;FOJS0001&quot; came from either.

We were failing the test

[&apos;a&apos;] eq &apos;a&apos;

because our test suite harness deliberately tries to avoid using our implementation to test itself and I hadn&apos;t updated it to take account of atomization here.

I&apos;ll switch it to assert-deep-eq and remove the FOJS0001.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>127085</commentid>
    <comment_count>3</comment_count>
    <who name="Tim Mills">tim</who>
    <bug_when>2016-07-29 12:57:37 +0000</bug_when>
    <thetext>Now fixed.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>