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: Wed, 28 Apr 2004 11:57:56 -0400
To: Martin Duerst <duerst@w3.org>, w3c-i18n-ig@w3.org
Cc: public-qt-comments@w3.org
Message-ID: <OF5965255D.1BBB7C9B-ON85256E78.006C1DC7-85256E84.0057B31A@ca.ibm.com>

Hello,

     In [1], Martin Duerst submitted the following comment on the Last 
Call Working Draft of XSLT 2.0 and XQuery 1.0 Serialization:

> [15] Section 4, "To anticipate the proposed changes to end-of-line
>    handling in XML 1.1, implementations may also output the characters
>    x85 and x2028 as character references. This will not affect the way
>    they are interpreted by an XML 1.0 parser.": XML 1.1 is now a REC,
>    so this is no longer anticipated. See
>    http://www.w3.org/TR/2004/REC-xml11-20040204/#sec-line-ends

     Thanks to Martin and the working group for this comment.

     The XSL and XML Query Working Groups discussed the comment, and 
agreed that the Serialization specification should be amended so that it 
no longer refers to XML 1.1 as if it were not yet a recommendation. 
Furthermore, the working groups decided that the handling of x85 and x2028 
should be such that they can be successfully processed by either an XML 
1.0 or an XML 1.1 processor without being normalized to a line-feed 
character, even if the value of the version parameter is 1.0.  Following 
are the changes required to implement that change:

Replace the paragraph after the bulleted list in Section 4 with the 
following:

<<
A consequence of this rule is that certain whitespace characters must be
output as character references, to ensure that they survive the round
trip through serialization and parsing. Specifically, CR, NEL and LINE
SEPARATOR characters in text nodes must be output respectively as &#xD;,
&#x85;, and &#x2028;, or their equivalents; while CR, NL, TAB, NEL and
LINE SEPARATOR characters in attribute nodes must be output respectively
as &#xD;, &#xA;, &#x9;, &#x85;, and &#x2028;, or their equivalents
>>

And replace the note following the bulleted list with the following note:

<<
Note:  XML 1.0 did not permit processors to normalize NEL or LINE
SEPARATOR characters to a LINE FEED character.  However, if a document
entity that specifies version 1.1 invokes an external general parsed
entity with no TextDecl or a TextDecl that specifies a version of 1.0,
the external parsed entity is processed according to the rules of XML
1.1.  For this reason, NEL and LINE SEPARATOR characters in text and
attribute nodes must always be escaped using character references or
CDATA sections, regardless of the value of the version parameter.
>>

     May I ask the working group to confirm that this response is 
acceptable to it?

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
------------------------------------------------------------------
Henry Zongaro      Xalan development
IBM SWS Toronto Lab   T/L 969-6044;  Phone +1 905 413-6044
mailto:zongaro@ca.ibm.com
Received on Wednesday, 28 April 2004 11:58:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:14:33 GMT