This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 29738 - [XSLT30] (editorial) We shouldn't use the term "streamable stylesheet" in the spec
Summary: [XSLT30] (editorial) We shouldn't use the term "streamable stylesheet" in the...
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: P2 editorial
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-18 13:20 UTC by Abel Braaksma
Modified: 2016-10-06 18:42 UTC (History)
0 users

See Also:


Attachments

Description Abel Braaksma 2016-07-18 13:20:58 UTC
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".
Comment 1 Michael Kay 2016-07-20 19:29:29 UTC
I have changed this to

Other changes introduced to facilitate the writing of streamable transformations
                     include:

I don't actually think the change is essential. This isn't a term of art; it's purely an ordinary noun (stylesheet or transformation) accomapanied by an ordinary adjective (streamable = capable of being streamed).