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

[Bug 24543] New: Supplying a streamable initial context item on a non-streamable initial mode

From: <bugzilla@jessica.w3.org>
Date: Wed, 05 Feb 2014 23:24:54 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-24543-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24543

            Bug ID: 24543
           Summary: Supplying a streamable initial context item on a
                    non-streamable initial mode
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: minor
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org

Under 6.6.3 Streamable Templates
(http://www.w3.org/TR/xslt-30/#streamable-templates), the fifth paragraph
(right before the Note), we write:

"Alternatively, streamed processing may be initiated by invoking the
transformation with an initial mode declared as streamable, while supplying the
initial context item (in an implementation-defined way) as a streamed
document."

It occurred to me that we never mention the reverse. What happens when the
initial context item is provided in a streaming way, and the initial mode is
not streamable?

I think the answer should be: it is implementation defined. Not sure we should
do something here, but it is clearly an error case if the stylesheet expects to
be non-streaming, but receives a streaming node.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 5 February 2014 23:24:57 UTC

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