W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2008

[widgets] Packaging & Configuration 1.0 pre-CfC comments

From: Jere Kapyaho <jere.kapyaho@nokia.com>
Date: Wed, 10 Dec 2008 14:47:16 +0200
To: ext Marcos Caceres <marcosscaceres@gmail.com>
CC: public-webapps <public-webapps@w3.org>
Message-ID: <C56586F4.44CF%jere.kapyaho@nokia.com>

Hi Marcos,

finally I got the chance to read the Widgets 1.0 Packaging & Configuration
spec. Great work there; please accept some comments based on the Editor's
Draft 7 December 2008 version, up at [1].

5.3 Zip Relative Paths
The ABNF needs some polishing:
- Rule names like cp437 vs. cp437-chars, utf8-range vs. utf8-chars,
ascii-range vs. ascii-chars.
- ABNF rules are case-insensitive as per RFC 5234 [2]; does this affect the
Language-Tag rule in any way?
- delimiter should be %x2F or just "/" for readability
- In cp437-chars, should say %x80-FF (and no semicolon)
- s/is define in/is defined in/

5.4 Reserved characters
- Minor issue with the table of reserved characters: the "Unicode code
points" column would be better labeled "Unicode character" and be made the
first column. The CP437 column is redundant, IMHO. The column "Character
representation" could be just "Representation" or "Representative glyph".

- Are filenames of ZIP entries case-sensitive or not? The ZIP spec does not
seem to say (or I missed it), but the P&C spec has several recommendations
about case.

6.4 Content localization
- Note that since localized folders now must reside in the root of the
widget package, they "pollute" the root namespace, and it is possible to
(more or less accidentally) have a normal folder whose name is a valid BCP47
language tag. In essence, all valid BCP47 language tags would have to be
treated as "reserved". Should the localized folders instead be placed one
level down from the root, inside folder 'X', where 'X' is a suitable
reserved name like 'resources'?
- If there ever is a case of the WUA having to iterate all the localized
folders, I think it's going to be difficult or impossible to find them all.
We had this problem in JSR 238 [3], and ended up having a metadata entry
that lists the supported locales. It can be generated by a widget packaging
tool. Not ideal, but beats a combinatorial explosion... :) Or maybe you
envision that the lang-priority-list removes the need to iterate?

6.5 Start file and Default Start Files
"See Step X for instructions of how to find the default start file." -- here
X should probably be 9.

8. Steps for Processing a Widget Resource
Step 6 - Determine the base folder and widget locale
- Algorithm step 2.d.i.2 seems to be missing something ("Let base folder
.").
- Algorithm step 2.d.ii refers to "this step 2.4".

References
- ZIP file spec: seems to be revised from time to time, would it be good to
freeze the reference to a particular version?
- Might want to fill in the HTTP, URI, ABNF etc. references before formal
publication. BTW, did you already get someone to volunteer to do it? I'll
help if not too late.
- Make all the URIs also links (like BCP47).

Hope this helps. Best regards,
Jere

[1] http://dev.w3.org/2006/waf/widgets/
[2] http://tools.ietf.org/rfc/rfc5234.txt
[3] http://jcp.org/en/jsr/detail?id=238

-- 
Jere Käpyaho (jere.kapyaho@nokia.com)
Specialist, Developer Platforms Standardization
Devices R&D, Nokia Corporation
Received on Wednesday, 10 December 2008 12:48:03 GMT

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