6994 2009-06-03 13:54:00 +0000 distinct-duration-equal-2 presumes a certain order 2009-10-14 12:37:50 +0000 1 1 1 Unclassified XML Query Test Suite XML Query Test Suite 1.0.2 PC Linux RESOLVED FIXED P2 normal --- 1 bogdanb+w3c+bugzilla frans.englich public-qt-comments oldest_to_newest 25444 0 bogdanb+w3c+bugzilla 2009-06-03 13:54:00 +0000 Hello! Test distinct-duration-equal-2 runs the query “fn:distinct-values((xs:yearMonthDuration('P1Y'), xs:dayTimeDuration('P365D')))” and expects the result “<doc>P1Y P365D</doc>”. However, http://www.w3.org/TR/2007/REC-xpath-functions-20070123/#func-distinct-values says that “[t]he order in which the sequence of values is returned is ·implementation dependent·.” Unless I'm missing something, this means that “<doc>P365D P1Y</doc>” is also a valid result, and should be added to the expected results list. Similar considerations apply to K-SeqDistinctValuesFunc-6, which expects that “deep-equal( distinct-values( ("1", 1, 2, 1, 1, 3, 1, 1, 3,  xs:anyURI("example.com/"), xs:anyURI("example.com/") ) ), ("1", 1, 2, 3, xs:anyURI("example.com/"))    )” should return true, even though distinct-values may reorder elements. Also, I think ns-queries-results-q1 also has this problem, but I'm not that far in implementation to be sure. 25447 1 andrew.eisenberg 2009-06-03 21:29:36 +0000 I agree with the issue that you have raised, and have added the additional expected result that you suggested for distinct-duration-equal-2. Frans, I believe that K-SeqDistinctValuesFunc-6 should be changed as well. 28336 2 frans.englich 2009-10-14 12:37:50 +0000 Fixed in CVS.