- From: <bugzilla@jessica.w3.org>
- Date: Sat, 18 Jun 2016 13:03:13 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29698 --- Comment #1 from Abel Braaksma <abel.braaksma@xs4all.nl> --- Oops, not entirely correct. The xsl:merge-source/@select expression is bound to certain rules to be guaranteed streamable: <quote> 3. The expression in the select attribute of that xsl:merge-source element, assessed with a context posture of striding and a context item type of U{document-node()}, has striding or grounded posture and motionless or consuming sweep. </quote> And there are a few other rules in there as well. The snapshot-effect applies to xsl:merge-action, not the select-expression. So, perhaps we should change the 19.10 mention something as follows: <quote> Specifying streamable="yes" either explicitly or implicitly (through the for-each-stream attribute) on xsl:merge-source declares that the selection of merge items on that source is streamable. Note: This does not impose rules on the child instructions of xsl:merge, in particular, xsl:merge-action can contain free-ranging or roaming constructs. This is a result of an implicit call to the fn:snapshot function as described in section 15.4 Streamable Merging. </quote> -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Saturday, 18 June 2016 13:03:16 UTC