W3C   W3C Internationalization (I18n) Activity: Making the World Wide Web truly world wide!

Related links

Other reviews

Review radar

Core WG home page

Internationalization Comments on Widgets 1.0 Packaging and Configuration specs

Version reviewed:http://www.w3.org/TR/2009/WD-widgets-20090528/
Lead reviewer and date of initial review: Addison Phillips, Jul 2009
Subject lead in: [WIDGET PC]

These are comments on behalf of the Internationalization Core WG, unless otherwise stated. The "Owner" column indicates who has been assigned the responsibility of tracking discussions on a given comment.

We recommend that responses to the comments in this table use a separate email for each point. This makes it far easier to track threads. Click on the icons in the right-most column to see email discussions.

ID Location Subject Comment Owner Ed. /
Subs.
Mail
1 Section 7.2 Wrong language tag.

The simple example in Section 7.2 still contains an error. The language tag for Spanish is "es", not "sp". It is shown correctly in the graphic but not the title of the section or elsewhere in the text.

 

AP E
2 Section 8.3 Clarify IRI/URI

Section 8.3 (Attribute Types) contains a subsection called "URI Attribute" which is relevant to our comment above. It says:
--
An attribute defined as containing a valid URI. A valid URI is one that matches the URI token of the [URI] specification or the IRI token of the [RFC3987] specification. The value of this kind of attribute is retrieved using the rule for getting a single attribute value. --
This is problematical, since all URIs are IRIs, but not the converse. We think this should favor IRI and note the relationship to URI.

AP E
3 Section 8.3 Widget metadata

The <widget> metadata does successfully incorporate our comments that multiple languages should be allowed on those attributes that make sense with them.

AP E
4 Section 8.3 Various positive observations

its:dir appears in this document and is a good illustration of its proper use, as does xml:lang. See, for example, section 8.8.

The 'charset' attribute appears in the element <content> and appears to be properly specified

The <its:span> element appears in the document and appears to be properly specified.

AP E
5 Section 9.1, step 5 Too small arbitrary limit on locale ids

In Step 5 of section 9.1, we find an arbitrary limit on locale identifiers (BCP 47 language tags):

Each item in the unprocessed locales must be a string shorter than eight characters, in lowercase form, that conforms to the production of a Language-Tag, as defined in the [BCP47] specification.

This limit is too short for even some simple language tags. Consider "zh-Hant-CN", which is given as an example in the document: it has 10 characters. This limit really should be removed. The eight character limit is on subtags.

AP S
6 Section 9.1, step 5 Use of its:dir

its:dir appears in this document and is a good illustration of its proper use, as does xml:lang. See, for example, section 8.8.

AP E
7 Section 9.1, step 4 Step not necessary?

In this same step, substep 4 is unnecessary. It does save processing time, but it is not required for proper operation. Performing the specific change suggested also has the negative side-effect of altering the user's preferences ahead of the local configuration. The rightmost occurrence would be a better choice for elimination.

AP E

Page template by Richard Ishida (ishida@w3.org).