W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2016

[Bug 29698] [XSLT30] Streamable merging does not require streamability checking anymore

From: <bugzilla@jessica.w3.org>
Date: Sat, 18 Jun 2016 13:03:13 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29698-523-pwkxnbd5tn@http.www.w3.org/Bugs/Public/>

--- 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:

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.

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:

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.

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.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 18 June 2016 13:03:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:01 UTC