W3C home > Mailing lists > Public > public-qt-comments@w3.org > October 2004

Re: [Serial] I18N WG last call comments [16]

From: Martin Duerst <duerst@w3.org>
Date: Tue, 26 Oct 2004 15:13:41 +0900
Message-Id: <6.0.0.20.2.20041026145808.05178e08@localhost>
To: Henry Zongaro <zongaro@ca.ibm.com>
Cc: w3c-i18n-ig@w3.org, public-qt-comments@w3.org

Hello Henry,

The I18N WG (Core TF) has looked at your reply. We are not satisfied
with your answer.

On a procedural point, we would like to point out that moving the defaults
elsewhere makes them very difficult to check, and risks that agreements
between WGs are forgotten. In particular, it is not sufficient to just
close a comment on the specification it is made; it should be transferred
to the other specification(s) where it now applies.

On the actual issue, our main concern is to make sure that defaults
are actually specified appropriately.
In XQuery, the default seems to be 'implementation-defined':
    http://www.w3.org/TR/2004/WD-xquery-20040723/#id-xq-serialization-parameters
We are not at all convinced that this will lead to the necessary
degree of interoperability.
For XSLT, there is no new public WD. A pointer to or explanation
of the current solution for this issue for XSLT would be appreciated.
Without having a look at it, we cannot assess whether we are satisfied
with the resolution to our comment.

We would also like to mention that while there may be specific considerations
for each specification, using the same defaults where possible will make
things easier for users, and will lead to better overall interoperability.

Regards,    Martin.

At 03:59 04/09/22, Henry Zongaro wrote:
 >
 >Martin,
 >
 >     In [1], you submitted the following comment on the Last Call Working
 >Draft of XSLT 2.0 and XQuery 1.0 Serialization on behalf of the I18N
 >Working Group:
 >
 ><<
 >[16] Section 4.2 (XML output method, encoding): "If no encoding parameter
 >   is specified, then the processor must use either UTF-8 or UTF-16.":
 >   It may be desirable to further narrow this to UTF-8 for higher
 >   predictability. On the other hand, this should not say
 >   "If no encoding parameter is specified", but "If no encoding
 >   is specified (either with an encoding parameter or externally)"
 >   to allow e.g. specification of encoding with an option.
 >>>
 >
 >     Thanks to you and the working group for this comment.  The XSL and
 >XML Query Working Groups discussed your comment.
 >
 >     Regarding the first point: in response to other Last Call comments,
 >Serialization no longer specifies default values for parameters.  This is
 >reflected in the 23 July Working Draft of Serialization.[2]  XSLT and
 >XQuery now specify how the value of the encoding parameter is determined
 >in all circumstances, so no change to the Serialization specification is
 >required in response to that part of the comment.
 >
 >     Regarding the second point:  again, all the serialization parameters
 >are fully determined by whatever mechanisms are provided by the host
 >specification.  Beyond that, serialization has implementation-dependent
 >and implementation-defined aspects, so it should be clear that not all of
 >a serializer's behaviour is governed by the settings of the parameters.
 >The working groups feel no change to the Serialization specification is
 >required in this regard.
 >
 >     May I ask you to confirm that this response is acceptable to the I18N
 >Working Group?
 >
 >Thanks,
 >
 >Henry [On behalf of the XSL and XML Query Working Groups]
 >[1]
 >http://lists.w3.org/Archives/Public/public-qt-comments/2004Feb/0362.html
 >[2]
 >http://www.w3.org/TR/2004/WD-xslt-xquery-serialization-20040723/#serparam
 >------------------------------------------------------------------
 >Henry Zongaro      Xalan development
 >IBM SWS Toronto Lab   T/L 969-6044;  Phone +1 905 413-6044
 >mailto:zongaro@ca.ibm.com 
Received on Tuesday, 26 October 2004 06:15:34 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 23:39:56 UTC