- From: <bugzilla@jessica.w3.org>
- Date: Mon, 15 Feb 2016 11:23:06 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29392
Michael Kay <mike@saxonica.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Michael Kay <mike@saxonica.com> ---
Noted that F+O already states:
If the host language makes serialization an optional feature and the
implementation does not support serialization, then a dynamic error
[err:FODC0010] is raised.
There was discussion about "cherry-picking" - are implementations allowed to
offer partial support for serialization, e.g. some methods but not others, some
serialization params but not others, or fn:serialize() without external
serialization. (MK's view - they will do so whether we allow it or not).
PROPOSAL (for XSLT - the section on Conformance / Serialization Feature):
If the Serialization Feature is not available and fn:serialize() is called with
values for serialization parameters that are not supported, then a processor
MUST raise error FODC0010
(and add notes to say what this means - a processor might reject all calls on
fn:serialize, or it might support only selected options.)
This proposal was accepted.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 15 February 2016 11:23:09 UTC