This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
FS 4.8.4 states "the static semantics of a FLWORExpr expression with an OrderByClause is equivalent to the static semantics of an equivalent FLWORExpr in which the OrderByClause is replaced by a call to the gt comparison over the corresponding OrderSpec expression(s)". Which I think means the following use cases should fail static type checking as they contains sequences on the lines indicated. xmp-queries-results-q7 order by $b/title xmp-queries-results-q12 order by $a/last, $a/first rdb-queries-results-q2 order by $i/itemno rdb-queries-results-q10 order by $highbid/itemno rdb-queries-results-q13 rdb-queries-results-q16 order by $u/userid rdb-queries-results-q16 let $descr := $i/description/text() order by $descr
Last one should be: rdb-queries-results-q18 let $descr := $i/description/text() order by $descr
I see, your point, but not sure how to tackle it.
Adding exactly-one(...) should work. I can't think of any more elegant solution which will type-check.
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 returned within two weeks, status will be changed to CLOSED. Thanks for reporting!
Thanks. Most of them are fixed, but there are still problems with: rdb-queries-results-q2: order by $i/itemno Also, there are the same problems (which I failed to include in my original report) for rdb-queries-results-q1: order by $i/itemno similarly, while the problem reported in rdf-queries-results-q18, there is a similar problem in the line: order by $u/name
Specific static typing tests have been added to CVS