W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2015

[Bug 28540] [FO30] [FO31] defaults for serialization parameters with fn:serialize not defined

From: <bugzilla@jessica.w3.org>
Date: Tue, 05 May 2015 23:25:05 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28540-523-M7yaBLlu20@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28540

Josh Spiegel <josh.spiegel@oracle.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |josh.spiegel@oracle.com

--- Comment #4 from Josh Spiegel <josh.spiegel@oracle.com> ---
I do not want the change proposed in comment 3.  It is too late to mandate
defaults for these parameters since fn:serialize is already part of a w3c
recommendation:
http://www.w3.org/TR/xpath-functions-30/#func-serialize

Adding specific defaults would force implementations to make
backwards-incompatible changes when they adopt 3.1 and thus violates
requirement 2.2.1:

  "XQuery 3.1 MUST be backward compatible with [XQuery 3.0]."
  http://www.w3.org/TR/xquery-31-requirements/#backward-compatibility

For example, an XQuery implementation is currently allowed to select a default
for omit-xml-declaration in the static context (Appendix C.1) and for
fn:serialize.  An implementation may have reasonably selected "yes" as the
default in both cases.  For this implementation, the change proposed in comment
3 would:

(1) Cause fn:serialize to return different results in 3.1
(2) Create an undesirable inconsistency between the default behavior of
fn:serialize and the default behavior when serializing the result of a query

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 5 May 2015 23:25:06 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 5 May 2015 23:25:07 UTC