- From: <bugzilla@jessica.w3.org>
- Date: Fri, 08 May 2015 17:24:42 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28540 --- Comment #8 from Josh Spiegel <josh.spiegel@oracle.com> --- I don't see why the specifications would treat the serialization defaults in the static context any differently than the defaults for fn:serialize. The reality is that they both impact the predictability of an implementation. I think it is more important that the default serialization behavior is consistent within an implementation than it is that serialization behaves consistently across implementations. Making changes to the specifications that cause implementations to ship with compatibility configuration switches would be unfortunate. It puts the burden on existing users to discover and set the switch or makes the implementation non-conformant by default. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 8 May 2015 17:24:44 UTC