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 25350 - Incorrect sweep of xsl:for-each in the effect of operand usage example
Summary: Incorrect sweep of xsl:for-each in the effect of operand usage example
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Last Call drafts
Hardware: All All
: 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: 2014-04-15 15:14 UTC by Eugene Fotin
Modified: 2014-08-02 18:07 UTC (History)
1 user (show)

See Also:


Attachments

Description Eugene Fotin 2014-04-15 15:14:56 UTC
The sweep of xsl:for-each instruction in the second example (http://marker.to/MrekZv) in "19.4.1 Examples showing the Effect of Operand Usage" (http://www.w3.org/TR/xslt-30/#operand-usage-examples) should be consuming.
According to http://www.w3.org/TR/xslt-30/#streamability-xsl-for-each, sweep of xsl:for-each for this case is widest sweep of the select expression "*/emp" (consuming) and the seqtor "<xsl:sequence select="."/>" (motionless), which is consuming.

Also it is not very clear from the step 9 that "striding and consuming" (currently: striding and motionless) is not allowed as a result of xsl:stream's seqtor.
It might be better if it links to streamability of xsl:stream under 18.1:
"The xsl:stream instruction is guaranteed-streamable if the contained sequence constructor is grounded".
Comment 1 Michael Kay 2014-05-15 14:28:31 UTC
Thanks for reporting this, I have fixed the example editorially as suggested.