- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 08 Feb 2007 18:27:54 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4310 Summary: fn-subsequence-mix-args-009, 011, 022 not aligned with latest spec Product: XML Query Test Suite Version: 1.0.2 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: XML Query Test Suite AssignedTo: andrew.eisenberg@us.ibm.com ReportedBy: frans.englich@telia.com QAContact: public-qt-comments@w3.org I'm questioning the baselines of: fn-subsequence-mix-args-009 fn-subsequence-mix-args-011 fn-subsequence-mix-args-022 For instance, 009's query is: fn:subsequence( ("a", xs:float("INF"), "b", "c"),-2,3) and expects the empty sequence as output. Contrasting the arguments to 15.1.10 fn:subsequence: "If $startingLoc is zero or negative, the subsequence includes items from the beginning of the $sourceSeq." Since startingLoc is -2, we begin from the very beginning of the sequence. Therefore, I conclude that the return sequence should be: a INF b. I (hopefully correctly) remember that fn:subsequence were described with a rather complex algorithm that involved arithmetics between the length/position arguments, and apparently subsequence have changed here(although I don't recall when). Maybe the tests should be aligned with the latest spec? If one reads the summary in isolation, "Returns the contiguous sequence of items in the value of $sourceSeq beginning at the position indicated by the value of $startingLoc and continuing for the number of items indicated by the value of $length." the baseline makes more sense, but in my opinion the Notes is rather clear. Frans
Received on Thursday, 8 February 2007 18:27:59 UTC