W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2014

[Bug 26328] [XSLT30] Streamable and non-streamable accumulators in grounded postures

From: <bugzilla@jessica.w3.org>
Date: Thu, 31 Jul 2014 13:09:01 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-26328-523-KyMUMq3GKl@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26328

--- Comment #1 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
The WG discussed this at F2F Hursley 30 July 2014.

The WG concluded that there were some issues that needed resolving, but not
necessarily as mentioned in this bug entry.

> 1) calling a streamable accumulator when a streamed node, not 
> copied, is the context node (first call above).

This is allowed, but limited inside the focus-setting construct of xsl:stream
and xsl:template. The WG agreed that it would be beneficial to expand this to
xsl:for-each, xsl:iterate, xsl:for-each-group.

> 2) calling a streamable accumulator when a copy of a streamed 
> node is the context node (inside the for-each above).
> 3) calling a streamable accumulator when a copy of a streamed 
> node is the context node and the construct is inside a declaration 
> that is outside the scope of streamability analysis (the last matching 
> template above).

Both are not allowed, the rules stipulate that the context node must be equal
to a streamed node of the focus setting container (which is xsl:template or
xsl:stream only, atm). A copy of a node is never the same as the context node. 

> 4) calling a non-streamable accumulator when a copy of a streamed 
> node is the context node (inside the for-each above)

Uncertain (question: is it possible to let a non-streamable accumulator operate
on a temporary tree?)

> 5) calling a non-streamable accumulator when a copy of a 
> streamed node is the context node and the construct is inside 
> a declaration that is outside the scope of streamability 
> analysis (the last matching template above).

Same as above: unclear atm.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 31 July 2014 13:09:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:47 UTC