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

[Bug 24494] New: No clear mention when something is not guaranteed streamable

From: <bugzilla@jessica.w3.org>
Date: Wed, 05 Feb 2014 01:35:19 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-24494-523@http.www.w3.org/Bugs/Public/>

            Bug ID: 24494
           Summary: No clear mention when something is not guaranteed
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          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

Under the preambule of 19, the third paragraph before 19.1, we use the
following text:

"The values of these properties for a top-level construct such as the body of a
template rule determine whether the construct is streamable."

But in the text prior to this paragraph, there is no mention of a property that
deems a construct not streamable. Looking further down at 19.7, The Sweep of a
Construct, we neither find this, which originally left me confused.

There is probably a reason for this, i.e. a construct itself can be
free-ranging, but applied to a grounded construct, it is still streamable, as
in doc('x')/y/preceding::node().

I think it is worthwhile to say precisely what is required to make an
instruction that introduced streamability (xsl:stream, xsl:mode, xsl:merge)
guaranteed streamable. This information is already available by going to these
instructions (if you add templates to the list), but I think a summary under
Guaranteed Streamability, or right under section 19 would proof worthwhile.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 5 February 2014 01:35:22 UTC

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