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 http://www.w3.org/TR/xquery/#id-unordered-expressions the ordering mode ``unordered'' changes the order of most XQuery constructs returning a sequence of nodes (path steps, union, except, and intersect) to an implementation dependent order. The only other XQuery expressions, that also return a sequence of nodes, are the two functions fn:id (http://www.w3.org/TR/xpath-functions/#func-id)and fn:idref (http://www.w3.org/TR/xpath-functions/#func-idref). In the current version they return their result always in document order. I would, however, expect their result to be in an implementation dependent order, whenever the ordering mode is ``unordered'', as well.
Jan, On 01 Feb 2006 the Query working group agreed that unordered mode should affect the result of fn:id and fn:idref. This change will affect XQuery but not XPath, since XPath does not have an unordered mode. The change will be reflected in the next version of the XQuery specification. If you find this resolution acceptable, please mark the Bugzilla comment closed (if we do not hear from you, we will mark it closed at the end of Feb. 2006). Regards, Don Chamberlin (for the Query working group)