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 28290 - [XP3.1] 2.4.1 Document Order defining
Summary: [XP3.1] 2.4.1 Document Order defining
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XPath 3.1 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Linux
: P2 minor
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-03-23 00:49 UTC by Patrick Durusau
Modified: 2015-07-10 22:39 UTC (History)
1 user (show)

See Also:


Attachments

Description Patrick Durusau 2015-03-23 00:49:07 UTC
2.4.1 Document Order

"An ordering called document order is defined among all the nodes accessible during processing of a given expression, which may consist of one or more trees (documents or fragments). Document order is defined in [XQuery and XPath Data Model (XDM) 3.1], and its definition is repeated here for convenience. Document order is a total ordering, although the relative order of some nodes is implementation-dependent. [Definition: Informally, document order is the order in which nodes appear in the XML serialization of a document.] "

Correct link for XDM: http://www.w3.org/TR/xpath-datamodel-31/#document-order 2.4 Document Order

BTW, the definition in XDM reads: 

"[Definition: A document order is defined among all the nodes accessible during a given query or transformation. Document order is a total ordering, although the relative order of some nodes is implementation-dependent. Informally, document order is the order in which nodes appear in the XML serialization of a document.]" 

Compare: 

 [Definition: Informally, document order is the order in which nodes appear in the XML serialization of a document.] "

I would simply insert the reference and/or quote the relevant definition rather than attempting to recast it.

[Will this make parsers faint and strong users curse? No but it is symptomatic.]
Comment 1 Jonathan Robie 2015-07-10 22:39:20 UTC
I fixed the reference, but did not eliminate the duplicate description, which has been there for a very long time.