- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 03 Jun 2009 13:54:01 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6994 Summary: distinct-duration-equal-2 presumes a certain order Product: XML Query Test Suite Version: 1.0.2 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: XML Query Test Suite AssignedTo: andrew.eisenberg@us.ibm.com ReportedBy: bogdanb+w3c+bugzilla@gmail.com QAContact: public-qt-comments@w3.org 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. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 3 June 2009 13:54:08 UTC