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

[Bug 29499] New: [XSLT30] Global xsl:variable/xsl:param not in streamability rules

From: <bugzilla@jessica.w3.org>
Date: Mon, 22 Feb 2016 12:48:10 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29499-523@http.www.w3.org/Bugs/Public/>

            Bug ID: 29499
           Summary: [XSLT30] Global xsl:variable/xsl:param not in
                    streamability rules
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

I'm not sure, but I couldn't find it. We have section " Streamability
of xsl:variable" which deals with the *instruction* xsl:variable, but not with
the declaration.

I vaguely remember we have had discussions concluding that a global variable
declared with xsl:param and xsl:variable is allowed to access a streamable
global context item (either because the stylesheet is executed with a default
mode set to a streamable mode or the xsl:global-context-item is set to
streamable), but only if motionless and grounded.

If we do have these rules in place, I wonder where they went. If we don't I
think we should add them.

The same seems true for xsl:key.

As an aside, I wouldn't oppose to — in fact, I'd welcome — a section under "19
Streaming" that is called something like "Classifying declarations" and point
from there to the relevant section in the rest of the prose, and any
declaration not yet in the prose and that is not allowed to access the global
context item could be mentioned there (currently, a back-reference is placed in
the opening section of section "19 Streaming", while this helps, it could be
more prominent with its own section).

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 22 February 2016 12:48:14 UTC

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