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

Re: [Serial] I18N WG last call comments [first comment 12] (qt-2004Feb0362-07)

From: Henry Zongaro <zongaro@ca.ibm.com>
Date: Wed, 1 Sep 2004 09:55:51 -0400
To: duerst@w3.org
Cc: public-qt-comments@w3.org, w3c-i18n-ig@w3.org
Message-ID: <OF842878D6.BECEF908-ON85256F01.007E3165-85256F02.004C82AA@ca.ibm.com>

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:

<<
[12] [Should be "10". HZ]
   Section 3, 'escape-uri-attributes' (and other places in this spec):
   RFC 2396, section 2.4.1, only specifies how to escape a string of
   bytes in an URI, and cannot directly be applied to a string of
   (Unicode) characters. In accordance with the IRI draft and many
   other W3C specifications, this must be specified to use UTF-8
   first and then use RFC 2396, section 2.4.1 (%-escaping).
>>

     Thanks to you and the working group for this comment.  The XSL and 
XML Query Working Groups discussed the comment, and noted that Section 
16.1 of XSLT 1.0 [2] relied upon Appendix B.2.1 of HTML 4.0 [3] for the 
normative definition of URI escaping.  The working groups also noted that 
some specifications have duplicated the description of URI escaping, while 
still others have relied on diverse references for the normative 
definition of the URI escaping algorithm.  In particular, the working 
groups noted that Section 3.2.17 of the PER of XML Schema:  Datatypes 2nd 
ed. [4] refers to Section 5.4 of XML Linking Language [5] for the 
normative definition of URI escaping.

     The working groups decided to follow the lead of the XML Schema 
Working Group, and adopted the following changes:

. In Section 6 of Serialization, sixth bullet, change
<<
escape non-ASCII characters in URI attribute values using the method 
recommended in Section 2.4.1 of [RFC2396].
>>

to

<<
escape non-ASCII characters in URI attribute values using the method 
defined by Section 5.4 Locator Attribute of [XML Linking Language], except 
that relative URIs must not be absolutized.
>>

. In Section 7.2 of Serialization, third paragraph change
<<
escape non-ASCII characters in URI attribute values using the method 
recommended in [RFC2396] (section 2.4.1).
>>

to

<<
escape non-ASCII characters in URI attribute values using the method 
defined by Section 5.4 Locator Attribute of [XML Linking Language], except 
that relative URIs must not be absolutized.
>>

     May I ask you to confirm that this response is acceptable to the 
working group?  If not, we would ask the I18N working group to suggest the 
most appropriate normative reference for URI escaping that should be used 
by all new W3C Recommendations.

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/xslt#section-HTML-Output-Method
[3] http://www.w3.org/TR/REC-html40/appendix/notes.html#h-B.2.1
[4] http://www.w3.org/TR/2004/PER-xmlschema-2-20040318/#anyURI
[5] http://www.w3.org/TR/2001/REC-xlink-20010627/#link-locators
------------------------------------------------------------------
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, 1 September 2004 13:56:28 GMT

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