W3C home > Mailing lists > Public > public-qt-comments@w3.org > August 2005

Re: [Serial] Normalization and References (qt-2004Nov0037-01)

From: Joanne Tong <joannet@ca.ibm.com>
Date: Tue, 2 Aug 2005 14:14:40 -0400
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Cc: public-qt-comments@w3.org
Message-ID: <OF6FEFA752.ADDBE4E0-ON85257051.00625C6B-85257051.00642C35@ca.ibm.com>
Hi Bjoern

Since we did not hear back from you for so long, this comment is 
considered closed.   Since then, we had a second last call period where we 
used the bugzilla tool to raise and track comments.  Regarding your 
dissatisfaction in #2, I created a new bug report 
http://www.w3.org/Bugs/Public/show_bug.cgi?id=1829 to track this issue. As 
for #3, the XLink reference has been removed due to another comment. 
Please review the resolution in bug 1327 and 1524.  If you find this 
resolution unsatisfactory, please post a comment in bug 1327 within one 
week.  Thank-you.

Joanne

Bjoern Hoehrmann <derhoermi@gmx.net> wrote on 08/02/2005 10:42:56 AM:

> * Joanne Tong wrote:
> 
>[http://lists.w3.org/Archives/Public/public-qt-comments/2004Nov/0037.html]
> 
> >Thank you for submitting this comment.  The editors handled this 
comment 
> >and would like to point out the following:
> >1.  Character expansion is now an ordered list. 
> >2.  The editors felt it is clear on inspection that a character changed 
by 
> >URI escaping is not changed by a character affected by Unicode 
> >Normalization (triggered by the normalization-form parameter). 
Therefore, 
> >no clarification is necessary.
> >3.  The editors felt that the reference to Section 5.4 of [XLink] 
provides 
> >sufficient information and any further details would be outside the 
scope 
> >of this specification.  Therefore, no clarification is necessary.
> >4.  The reference to the Character Model specification is now 
> >http://www.w3.org/TR/2004/WD-charmod-norm-20040225
> 
> I'm fine with #1 and #4 but not with the others. It's not clear to me
> that normalization-form has no impact on resource identifier escaping
> and the current reference to XLink 1.0 is inconsistent with XLink 1.1
> and RFC 3987 (the IRI specification). For example, with 
> 
>   escape-uri-attributes = no
>   normalization-form = NFC
> 
> input such as
> 
>   <a href='Bjo&#x308;rn' ...
> 
> would yield in
> 
>   <a href='Bj&#xf6;rn' ...
> 
> With 
> 
>   escape-uri-attributes = yes
>   normalization-form = NFC
> 
> however it would yield in, as I understand it,
> 
>   <a href='Bjo%CC%88rn' ...
> 
> which is not in NFC even though that has been requested. Also note that
> RFC 3987 requires the result to be NFC-normalized under some circum-
> stances, so I think this needs to be clarified in the draft.
> -- 
> Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
> Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld..de
> 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Tuesday, 2 August 2005 18:16:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:07 UTC