This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The expression in orderDecl-2.xq: (<a>1</a>) union (<b>2</b>) results in the nodes <a>1</a> and <b>2</b> in document order, since there is a 'ordering ordered' declaration. But that since the "document order" in this case is implementation defined, the result is still indeterminate. (I searched for previous bugs with union or orderDecl, but didn't find one.)
Per: I am not sure that I agree with with you. From the Query specs "Ordering mode affects the behavior of path expressions that include a "/" or "//" operator or an axis step; union, intersect, ..." Why will it still indeterminate? Carmelo
The ordering mode specifies that the result of union is in document order. That is not indeterminate. However, document order itself is indeterminate (or implementation dependent) in this case, the since the constructed element nodes do not share a common ancestor.
Per: Correct. Submitted a second set of expect results. Please close the bug if in agreement and able to verify. Thanks, Carmelo
I can't really "verify" the fix it until I get the next version of the testsuite, or at least a patch. But I might as well close it anyway.