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

[Bug 24492] Options when streamable construct is not guaranteed streamable

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

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
In general we have avoided being prescriptive about warnings, and in the few
cases where we have specified that processors must give a warning (for example,
when running a 1.0 stylesheet under a 2.0 processor), it has not been a
success: users lobbied hard for an option to suppress this warning, and I
eventually provided an option to suppress it, although it's not clear that the
spec allows me to do so.

There are also some environments (e.g. XSLT in the browser) where providing a
warning is difficult to achieve. 

And one can satisfy the letter of the requirement without satisfying its spirit
by writing the warning to some system log file that no-one ever looks at.

I think in general it's best to leave implementors to decide when warnings are
appropriate.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 5 February 2014 10:27:40 UTC

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