W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2011

RE: Minor comments on Widgets

From: Phillips, Addison <addison@lab126.com>
Date: Tue, 15 Mar 2011 21:35:05 -0700
To: "public-webapps@w3.org" <public-webapps@w3.org>
CC: "public-i18n-core@w3.org" <public-i18n-core@w3.org>
Message-ID: <131F80DEA635F044946897AFDA9AC3476A664A503D@EX-SEA31-D.ant.amazon.com>
Hi,

One more minor note. In the grammar in section 5.3, you have:

low-alpha      = %x61-71

I suspect you mean for this to be:

low-alpha      = %x61-7a


thanks,

Addison

Addison Phillips
Globalization Architect (Lab126)
Chair (W3C I18N, IETF IRI WGs)

Internationalization is not a feature.
It is an architecture.




> -----Original Message-----
> From: Phillips, Addison
> Sent: Tuesday, March 15, 2011 8:41 AM
> To: 'public-webapps@w3.org'
> Cc: 'public-i18n-core@w3.org'
> Subject: Minor comments on Widgets
> 
> Hello Webapps WG,
> 
> (these are personal comments)
> 
> I happened to be referring to the Widget spec this morning and noticed a few
> minor items that I feel should be brought to your attention.
> 
> 1. Section 5.3 (Zip Relative Paths). The ABNF defines "language-range". I think
> this is not desirable. Language ranges are input to the matching algorithm (i.e.
> the user's request). You don't really want paths like "locale/de-*-1901". You
> want concrete paths here and "*" has no business in a path. Ideally you would
> reference the "Language-Tag" production in BCP 47 (RFC 5646). However, since
> it is a large production and you don't probably want to directly incorporate it,
> you could incorporate the "obs-language-tag" production in the same document
> instead. You should still say that language tags used in paths "must" be valid
> language tags according to the more formal production.
> 
> 2. Section 5.3. The same production corresponds to BCP 47 (RFC 4647)
> "extended-language-range", although it only allows the tags to use lowercase
> letters. I really feel that mixed case is not that difficult to support and that it
> will save many developers from inexplicable silent failures.
> 
> 3. There is no mention of case sensitivity of filenames anywhere that I can find.
> You should define if filenames are case sensitive (or not) and what is meant by
> "case sensitive" if it is supported (just ASCII case? Unicode default case
> mapping?)
> 
> Thanks,
> 
> Addison
> 
> Addison Phillips
> Globalization Architect (Lab126)
> Chair (W3C I18N, IETF IRI WGs)
> 
> Internationalization is not a feature.
> It is an architecture.

Received on Wednesday, 16 March 2011 04:35:46 GMT

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