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

[Bug 29392] [xslt 3.0] Serialization Feature and the fn:serialize() function

From: <bugzilla@jessica.w3.org>
Date: Fri, 19 Feb 2016 14:32:12 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29392-523-KNR7UNp0u1@http.www.w3.org/Bugs/Public/>

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
             Status|RESOLVED                    |CLOSED

--- Comment #3 from Michael Kay <mike@saxonica.com> ---
I interpreted our decisions as follows, by adding the text:

Note: A processor that does not claim conformance with the serialization
<rfc2119>may</rfc2119> offer alternative serialization capabilities, and these
<rfc2119>may</rfc2119> make use of the serialization parameters defined on
<elcode>xsl:output</elcode> and/or <elcode>xsl:result-document</elcode>.</p>

If the processor claims conformance with the serialization feature then it
<rfc2119>must</rfc2119> fully implement the <xfunction>serialize</xfunction>
function defined in <bibref ref="xpath-functions-30"/> or <bibref
ref="xpath-functions-31"/> as appropriate, and <rfc2119>must not</rfc2119>
raise error FODC0010 as the result of such a call.

If the processor does not claim conformance with the serialization feature,
then it <rfc2119>may</rfc2119> raise error FODC0010 in respect of some or all
calls on the <xfunction>serialize</xfunction> function; it <rfc2119>must
not</rfc2119> return a result from a call on this function unless the result is
conformant with the specification, given the parameters actually supplied.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 19 February 2016 14:32:15 UTC

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