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

Re: [Serial] I18N WG last call comments

From: François Yergeau <francois@yergeau.com>
Date: Mon, 14 Jun 2004 21:28:11 -0400
To: Henry Zongaro <zongaro@ca.ibm.com>
Cc: w3c-i18n-ig@w3.org, public-qt-comments@w3.org
Message-id: <40CE50AB.2010702@yergeau.com>

Henry Zongaro a écrit :
>      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.
> 
> 
>>[4] This only defines serialization into bytes. In some contexts
>>   (e.g. Databases, in-program,...), serialization into a stream
>>   of characters is also important. The spec should specify how
>>   this is done.
> 
> 
>      Thanks to Martin and the I18N Working Group for this comment.
> 
>      The XSL and XQuery Working Groups discussed the comment.  The working 
> groups noted that there is an analogy in parsing XML documents.  XML 1.0 
> and XML 1.1 parsed entities are defined as sequences of character code 
> points, each in some encoding.  Though it is common practice to parse XML 
> documents that have already been decoded into a sequence of characters, 
> the XML 1.0 and XML 1.1 Recommendations do not describe the actions of an 
> XML processor in those terms.
> 
>      Based on this analogy, the working groups decided that it was not 
> appropriate for Serialization to specify normatively how to serialize into 
> a stream of characters.  The working groups did decide to add a note to 
> Section 3 of Serialization indicating that a processor could provide an 
> option that would permit the fourth phase of serialization (Encoding) to 
> be skipped.

We are not really satisfied with this resolution and would like to 
request further clarification.  In particular, conformance when one is 
actually serializing to characters instead of bytes is not clear at all 
to us.  Allowing this but not normatively is very strange, one is left 
to wonder what would be the conformance status of an implementation that 
*only* serializes to characters (because that's all that is required in 
a given context).

> [1] 
> http://lists.w3.org/Archives/Public/public-qt-comments/2004Feb/0362.html

Regards,

-- 
François Yergeau
Received on Monday, 14 June 2004 21:30:32 GMT

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