- From: <bugzilla@jessica.w3.org>
- Date: Tue, 15 Apr 2014 15:14:56 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25350 Bug ID: 25350 Summary: Incorrect sweep of xsl:for-each in operand usage example Product: XPath / XQuery / XSLT Version: Last Call drafts Hardware: All OS: All Status: NEW Severity: normal Priority: P2 Component: XSLT 3.0 Assignee: mike@saxonica.com Reporter: eugene.fotin@gmail.com QA Contact: public-qt-comments@w3.org 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". -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 15 April 2014 15:14:58 UTC