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

[Bug 29805] New: [XSLT30] Allow xsl:source-document/@use-accumulators to be present when streamable=no

From: <bugzilla@jessica.w3.org>
Date: Fri, 02 Sep 2016 16:47:55 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29805-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29805

            Bug ID: 29805
           Summary: [XSLT30] Allow xsl:source-document/@use-accumulators
                    to be present when streamable=no
           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
https://lists.w3.org/Archives/Public/public-xsl-wg/2016Sep/0003.html.)

Following up on yesterday's telcon discussion, I changed my mind on my
standpoint and would like to propose that we lift the requirement that
xsl:source-document/@use-accumulators cannot be used together with
xsl:source-document/@streamable=no.

I would expect the semantics to behave as if

<xsl:source-document href="x.html" streamable="no" use-accumulators="a b">
   <!--sequence constructor-->
</xsl:source-document>

is equivalent to:

<xsl:source-document href="x.html" streamable="yes" use-accumulators="a b">
   <xsl:variable name="source" select="copy-of(.)" />
   <xsl:for-each select="$source">
      <!--sequence constructor-->
   </xsl:for-each>
</xsl:source-document>

This would work, because fn:copy-of on a streamed document copies its
accumulators and disallows the use of any other accumulator. For non-streaming
processors, it works because they are required to enforce the rule on copying
and using applicable accumulators.

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

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