<?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>19634</bug_id>
          
          <creation_ts>2012-10-19 13:53:49 +0000</creation_ts>
          <short_desc>[XSLT 3.0] deep-equal2() function</short_desc>
          <delta_ts>2013-02-16 12:29:42 +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>XSLT 3.0</component>
          <version>Last Call drafts</version>
          <rep_platform>PC</rep_platform>
          <op_sys>All</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="Michael Kay">mike</reporter>
          <assigned_to name="Michael Kay">mike</assigned_to>
          
          
          <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>76686</commentid>
    <comment_count>0</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2012-10-19 13:53:49 +0000</bug_when>
    <thetext>At some stage before we finally go to press, we need to decide what to do about the deep-equal2() function, which is currently in the XSLT 3.0 specification as a description of how we expect deep-equal to be enhanced to cater for maps.

I think the best approach is to drop the separate function name, and say instead something along the lines of &quot;the fn:deep-equal function described is F+O 3.0 is modified to handle maps as follows:&quot;</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>82969</commentid>
    <comment_count>1</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2013-02-12 10:30:56 +0000</bug_when>
    <thetext>The WG accepts the proposal as suggested, editor to implement.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>82971</commentid>
    <comment_count>2</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2013-02-12 10:39:55 +0000</bug_when>
    <thetext>We noted also that the proposal to remove collations from maps impacts the deep-equal() comparison of maps; we should compare the keys in the two maps using codepoint collation and rely on the assumption that the application has normalized the keys to take account of the comparison semantics of the required collation.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>83219</commentid>
    <comment_count>3</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2013-02-16 12:29:42 +0000</bug_when>
    <thetext>Changes applied (draft N)</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>