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: Fri, 08 May 2015 15:22:30 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28540-523-axCGNEUz4O@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28540

--- Comment #6 from Josh Spiegel <josh.spiegel@oracle.com> ---
I checked 4 implementations from different companies:

   3 evaluate fn:serialize(<e/>) as "<e/>"

   1 evaluates fn:serialize(<e/>) as "<?xml version="1.0"
encoding="UTF-8"?><e/>"

By forcing the default value of "omit-xml-declaration", it will cause a
backwards compatibility issue for somebody.  This is just one example.

----

Consider this expression:

   (1, 2, 3)

Serializing the result as XML in 1.0 would produce the string:

   "1 2 3"

Consider this 3.0 expression:

   fn:serialize((1, 2, 3))

The least surprising behavior is that it evaluates to the same string.  Under
Mike's proposal, in XQuery 3.1 it would not.  

Forcing the defaults for fn:serialize will create inconsistencies like this. 
In general, I want the defaults I use in the static context and in XQJ to be
the same as the defaults I use for fn:serialize().

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 8 May 2015 15:22:34 UTC

This archive was generated by hypermail 2.3.1 : Friday, 8 May 2015 15:22:35 UTC