W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2009

RE: [P&C] utf8-char in Zip-rel-path

From: Marcin Hanclik <Marcin.Hanclik@access-company.com>
Date: Sun, 26 Jul 2009 23:29:56 +0200
To: Marcin Hanclik <Marcin.Hanclik@access-company.com>, "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <FAA1D89C5BAF1142A74AF116630A9F2C2890BCA4F3@OBEEX01.obe.access-company.com>
Hi,

Given the fact that

"Rule names are case insensitive."
http://tools.ietf.org/html/rfc5234#section-2.1

it could potentially be better to rename the rule from "utf8-char" to something else, since it may get confused with "UTF8-char" rule from http://tools.ietf.org/html/rfc3629#section-4.

Taken into account my comments in the mail below, we could have new rule replacing utf8-char:
zip-UTF8-char   = UTF8-2 / UTF8-3 / UTF8-4
UTF8-2      = %xC2-DF UTF8-tail
UTF8-3      = %xE0 %xA0-BF UTF8-tail / %xE1-EC 2( UTF8-tail ) /
                 %xED %x80-9F UTF8-tail / %xEE-EF 2( UTF8-tail )
UTF8-4      = %xF0 %x90-BF 2( UTF8-tail ) / %xF1-F3 3( UTF8-tail ) /
                 %xF4 %x80-8F 2( UTF8-tail )
UTF8-tail   = %x80-BF

The problem may be with the allowed ranges of the Unicode characters.
The above grammar seems to allow 0080-10FFFF (the UTF-16 accessible range minus characters < 0080)
http://tools.ietf.org/html/rfc3629#section-3
whereas the current utf8-char rule is more selective.

Thanks.

Kind regards,
Marcin

________________________________________
From: public-webapps-request@w3.org [public-webapps-request@w3.org] On Behalf Of Marcin Hanclik [Marcin.Hanclik@access-company.com]
Sent: Sunday, July 26, 2009 1:59 PM
To: public-webapps@w3.org
Subject: [P&C] utf8-char in Zip-rel-path

Hi Marcos, All,

Following my previous email about Zip-rel-path and concluding that utf8-char non-terminal is wrongly specified (i.e. it indicates that Zip-rel-path operates on characters, not bytes, whereas I assume operation on bytes is our target), I wonder whether Zip-rel-path shouldn't refer to UTF8-char non-terminal from http://tools.ietf.org/html/rfc3629#section-4.
This would probably disambiguate the P&C spec and may result in Widgets 1.0: URI Scheme's widget-URI being correct.

Thanks.

Kind regards,
Marcin

________________________________________

Access Systems Germany GmbH
Essener Strasse 5  |  D-46047 Oberhausen
HRB 13548 Amtsgericht Duisburg
Geschaeftsfuehrer: Michel Piquemal, Tomonori Watanabe, Yusuke Kanda

www.access-company.com

CONFIDENTIALITY NOTICE
This e-mail and any attachments hereto may contain information that is privileged or confidential, and is intended for use only by the
individual or entity to which it is addressed. Any disclosure, copying or distribution of the information by anyone else is strictly prohibited.
If you have received this document in error, please notify us promptly by responding to this e-mail. Thank you.


________________________________________

Access Systems Germany GmbH
Essener Strasse 5  |  D-46047 Oberhausen
HRB 13548 Amtsgericht Duisburg
Geschaeftsfuehrer: Michel Piquemal, Tomonori Watanabe, Yusuke Kanda

www.access-company.com

CONFIDENTIALITY NOTICE
This e-mail and any attachments hereto may contain information that is privileged or confidential, and is intended for use only by the
individual or entity to which it is addressed. Any disclosure, copying or distribution of the information by anyone else is strictly prohibited.
If you have received this document in error, please notify us promptly by responding to this e-mail. Thank you.
Received on Sunday, 26 July 2009 21:30:55 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:33 GMT