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

[Bug 29738] New: [XSLT30] (editorial) We shouldn't use the term "streamable stylesheet" in the spec

From: <bugzilla@jessica.w3.org>
Date: Mon, 18 Jul 2016 13:20:58 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29738-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29738

            Bug ID: 29738
           Summary: [XSLT30] (editorial) We shouldn't use the term
                    "streamable stylesheet" in the spec
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: editorial
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

This bug is *editorial*.

I happened upon only one occurrence of this, and even though it is in a
non-normative section, I think we should not use this term, as a stylesheet as
a whole is never "streamable" by the way we use the term "streamable".

We might even add a Note explaining that stylesheets as a whole are not
streamable, but I'm agnostic to that.

The occurrence is in J.1. Changes in this Specification, item 4:

"Other changes introduced to facilitate the writing of streamable stylesheets
include:"

A suggested rewrite could be:

"Other changes introduced to facilitate the writing of stylesheets that can
process streamed documents include:"

Or use the term "guaranteed streamable constructs".

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 18 July 2016 13:21:15 UTC

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