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

[Bug 29804] New: [XSLT30] Drop the restriction of @use-accumulators to be allowed only when @streamable=yes is present: XTSE3195

From: <bugzilla@jessica.w3.org>
Date: Fri, 02 Sep 2016 16:47:45 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29804-523@http.www.w3.org/Bugs/Public/>

            Bug ID: 29804
           Summary: [XSLT30] Drop the restriction of @use-accumulators to
                    be allowed only when @streamable=yes is present:
           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 raised this bug following the discussion thread in

In light of yesterday's discussion at the telcon, it was briefly mentioned that
the presence of one attribute being dependent on the presence of another
attribute is unfortunate.

For the same reasons we introduced xsl:source-document (i.e. to flip the
streamable attribute painlessly), I propose we lift the following restriction
(section 15.3) on xsl:merge-source:

"[ERR XTSE3195] If the for-each-item is present then the for-each-stream and
use-accumulators attributes must both be absent. If the use-accumulators
attribute is present then the for-each-stream attribute must be present. If the
for-each-stream attribute is present then the for-each-item attribute must be
absent. If the for-each-stream attribute is present, the only permitted value
(and the default value) of the streamable attribute is yes."

- allow streamable="no" and the presence of for-each-stream, in which case it
simply returns a document, much like a non-streaming processor would in this

- allow the presence of use-accumulators whether or not for-each-stream is
present. It would restrict the applicability of accumulators.

- retain that for-each-item and for-each-stream are mutually exclusive.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 2 September 2016 16:47:58 UTC

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