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

Re: [Serial] I18N WG last call comments

From: Henry Zongaro <zongaro@ca.ibm.com>
Date: Tue, 13 Apr 2004 10:59:23 -0400
To: w3c-i18n-ig@w3.org, duerst@w3.org
Cc: public-qt-comments@w3.org
Message-ID: <OFFBF8989B.DD0E6AAF-ON85256E74.006FEF4E-85256E75.005255F7@ca.ibm.com>


     In [1], Martin Duerst 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.

> [17] Section 4.2 (XML output method, encoding): "When outputting a 
>    character in the data model, the implementation is free to represent
>    it using any character sequence that will be normalized to a newline
>    character by an XML parser,...": This should probably says that
>    for interoperability, it is better to avoid x85 and x2028.

     In [2], Michael Kay responded:

> I don't see a specific need to say that: if you're generating XML 1.0
> then you need to avoid these characters and if you're generating XML 1.1
> then you don't. This seems to be covered by the statement as written.

     Thanks to Martin and the I18N Working Group for this comment.

     The XSL and XQuery Working Groups discussed the comment, and agreed 
with Michael Kay that the statement regarding the representation of 
newline characters in the serialized document was correct as written, and 
that no change is required.

     May I ask the I18N Working Group to confirm that this response is 


Henry [On behalf of the XSL and XQuery Working Groups.]
Henry Zongaro      Xalan development
IBM SWS Toronto Lab   T/L 969-6044;  Phone +1 905 413-6044
Received on Tuesday, 13 April 2004 10:59:59 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:19 UTC