Errata for Packaged Web Apps (Widgets) - Packaging and XML Configuration
Last updated: 17 April, 2014
This document records all
known issues since publication of the Packaged Web Apps (Widgets) - Packaging and XML Configuration specification (hereinafter, "the specification" or "the
The best way to see what has changed is just to look at the differences document. It's nice and color coded and fairly easy to follow.
If you find errors in the specification that are not listed in this document, please
report them to email@example.com. Archives of the mailing list are available at
Table of Contents
- Edition 1
- Substantive Errata
- Editorial Errata
Edition 1 - Published September 25, 2012
The following are changes that could potentially affect conformance.
In section 9.1.9 Rule for Getting Text Content with Normalized White Space, the rule changed from:
In result, convert any sequence of one or more Unicode white space into a single U+0020 SPACE.
In result , convert any sequence of one or more white space characters into a single U+0020 SPACE.
In effect, all whitespace is normalized to U+0020 SPACE.
In section 9.1.12 Rule for Deriving the user agent locales, step 2.C, it said:
If this range contains any subtag ' * ', remove the ' * ' and its preceding hyphen ( U+002F) (e.g., ' en-*-us ' becomes ' en-us ').
The unicode code for preceding hyphen was should actually have been U+002D.
1.2. Editorial Errata
The following are corrections that do not changes to text content.
In the spec, we made minor corrections to letter casing in various places. A few hyperlinks added to make the document a bit easier to use. Removed the dates from the bibliography as they just fall out of date.
The following are corrections that do not affect conformance.
Changed the title of the document from:
Widget packaging and XML Configuration
Packaged Web Apps (Widgets) - Packaging and XML Configuration
As people don't like the word "widget".
Combined definition of space characters and "white space" characters. Space characters are now just defined as a bunch of unicode code points as defined by the Unicode specification.
Clarified a bit more the section 9.1.4 Rule for determining directionality Determining Directionality. It was a bit terse.
Clarified section 9.1.8 Rule for Getting Text Content. It was a bit confusing.
Clarified what "in error" means in section 9.1.2 Algorithm to Process a Configuration Document, Step 5B by saying the id attribute is
not a valid IRI or is an empty string.
Clarified processing of a feature element in section 9.1.2 Algorithm to Process a Configuration Document.