This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28862 - [XP30] and [XP31] ordering mode (under simple map operator) is undefined
Summary: [XP30] and [XP31] ordering mode (under simple map operator) is undefined
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XPath 3.1 (show other bugs)
Version: Member-only Editors Drafts
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Jonathan Robie
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-28 22:58 UTC by Abel Braaksma
Modified: 2015-07-14 16:15 UTC (History)
1 user (show)

See Also:


Attachments

Description Abel Braaksma 2015-06-28 22:58:04 UTC
Under 3.15 (XP31) and 3.14 (XP30) Simple Map Operator (!) the spec for both editions says:

<quote>
If ordering mode is ordered, the returned sequence preserves the orderings within and among the subsequences generated by the evaluations of E2; otherwise the order of the returned sequence is implementation-dependent.
</quote>

I can't find "ordering mode", "order mode" or similar terms defined anywhere else in the spec. What definition or statement does it refer to and/or what defines whether the ordering mode is ordered or not for the selection in the expression?

Filed under XP31 so that it gets on the agenda, but applies equally to both XP30 and XP31.
Comment 1 Jonathan Robie 2015-07-14 15:50:40 UTC
I will remove this text from XPath 3.1.

Ordering mode is defined only for XQuery:

[Definition: Ordering mode. Ordering mode, which has the value ordered or unordered, affects the ordering of the result sequence returned by certain expressions, as discussed in 3.14 Ordered and Unordered Expressions.]

Section 3.14 also appears only in XQuery.
Comment 2 Michael Kay 2015-07-14 16:08:07 UTC
Rather than removing the text, you should retain the part that applies:

the returned sequence preserves the orderings within and among the subsequences generated by the evaluations of E2
Comment 3 Jonathan Robie 2015-07-14 16:15:21 UTC
(In reply to Michael Kay from comment #2)
> Rather than removing the text, you should retain the part that applies:
> 
> the returned sequence preserves the orderings within and among the
> subsequences generated by the evaluations of E2

Done.