This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In the latest update, we get fn:exactly-one called with a sequence containing zero or more than one item in emptyorderdecl-2 emptyorderdecl-3 emptyorderdecl-10 emptyorderdecl-11 emptyorderdecl-14 emptyorderdecl-15 emptyorderdecl-18 emptyorderdecl-19 emptyorderdecl-22 emptyorderdecl-24 ForExprType049
Yes, I get the same problem. The change that was made to these files is clearly incorrect.
A fix has been attempted in CVS, XQTS_current.zip is updated. If the resolution is satisfactory, feel free to change status to closed. Otherwise reopen this report. If no feedback is given within two weeks, status will be set to closed.
Thanks. The emptyorderdecl-* tests are fixed, but there is still an exactly-one in the ForExprType049 which is causing problems
How would you like ForExprType049 to be, exactly? Like this? for $test as xs:decimal in data(zero-or-one($input-context/root/InterleaveType/*)) return $test (See http://www.w3.org/Bugs/Public/show_bug.cgi?id=4046 for a discussion of what previously was considered problematic with this test.)
for $test as xs:decimal in data($input-context/root/InterleaveType/*) return $test should be fine. The problem wasn't with the quantifier, but with knowing $test was xs:decimal rather than xs:untypedAtomic, which we fixed by rewriting the "declare variable $input-context external" with a "as document-node(schema-element(root))" so it gets the schema types.