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

[Bug 25335] New: [xslt 3.0] Streamed merging

From: <bugzilla@jessica.w3.org>
Date: Sun, 13 Apr 2014 08:56:54 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-25335-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25335

            Bug ID: 25335
           Summary: [xslt 3.0] Streamed merging
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: mike@saxonica.com
        QA Contact: public-qt-comments@w3.org

There are two specific problems with section 15.4 on streamable merging:

(a) We say the xsl:merge-source/@select attribute must be striding, but in
several of the examples it is grounded

(b) We place no constraints on the use of the current-merge-group() function
within the xsl:merge-action (or within the merge keys).

I think these problems are not superficial. The concepts of sweep and posture
have been developed with the idea in mind that there is only one streamable
document and that it is the document containing the context item. Generalizing
this to multiple input documents is non-trivial.

I currently feel that the right answer is to insist that
xsl:merge-source/@select is grounded (e.g. by using copy-of() or snapshot()),
in which case we do not need to place any constraints on xsl:merge-action or
the use of current-merge-group().

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 13 April 2014 08:56:59 UTC

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