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 29463 - [XSLT30] A little too much prejudice in the algorithm of on-empty/on-non-empty
Summary: [XSLT30] A little too much prejudice in the algorithm of on-empty/on-non-empty
Status: CLOSED INVALID
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-15 14:42 UTC by Abel Braaksma
Modified: 2016-10-06 18:42 UTC (History)
0 users

See Also:

Attachments

Description Abel Braaksma 2016-02-15 14:42:35 UTC 
Under 8.4.4 we write a suggested algorithm, starting with "The algorithm is as follows:". This then continues with "The nodes in the sequence constructor are evaluated in document order.". 

At this stage we do not know yet that the sequence constructor will only create nodes. I think this should better read "The items in the....".
Comment 1 Michael Kay 2016-02-15 22:02:23 UTC 
We have just explained that a sequence constructor consists of instructions, literal result elements, and text nodes. All of these are nodes. Everything in a sequence constructor is a node. We aren't talking about the result of the sequence constructor, we are talking about its constituents/operands.