- From: <bugzilla@jessica.w3.org>
- Date: Wed, 05 Feb 2014 01:08:07 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24492
Bug ID: 24492
Summary: Options when streamable construct is not guaranteed
streamable
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 definition of Guaranteed Streamable we give three options what a
processor MUST do when a declared streamable construct is not guaranteed
streamable:
a) Signal a static error
b) Process the stylesheet as if it were a non-streaming processor
c) Process the stylesheet with streaming if it is able to do so, or signal a
static error if it is not able to do so.
For (b) and (c), I think it is appropriate that we specify that the processor
must signal a warning (which can be switched off). Otherwise, we end up with
stylesheets that are not guaranteed streamable and users never knowing they are
not guaranteed streamable, hence undermining the meaning of guaranteed
streamability.
Also, we don't specify a default option if the user does not specify a specific
option. I think the default option should be to signal a static error and at
user option, this can be changed.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 5 February 2014 01:08:08 UTC