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

[Bug 24109] [xslt 3.0] streamability of xsl:variable when atomised

From: <bugzilla@jessica.w3.org>
Date: Thu, 06 Mar 2014 14:00:55 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-24109-523-weFNeM0eKM@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24109

Abel Braaksma <abel.braaksma@xs4all.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CLOSED                      |REOPENED
                 CC|                            |abel.braaksma@xs4all.nl
         Resolution|FIXED                       |---

--- Comment #3 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
I am reopening this, because it seems the change introduced a new bug.

Under 19.8.4.39, under the rules, list item 2.b., the usage of the seqtor
operand has changed from navigation (previous draft) to absorption (current
internal draft).

This would allow the following to be streamable (sequence has usage
transmission, seqtor usage absorption):

<xsl:variable name="x">
    <xsl:sequence select="foo">
</xsl:variable>

but it isn't streamable, because the variable would hold a reference to a
streamed node.

Unless I misunderstand the change, I think the proper usage here is navigation,
and not absorption.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 6 March 2014 14:01:06 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:55 UTC