[widgets] P&C Last Call 3

Hi All,
After a successful CR period, P&C is now ready to go to LC3 (should be
out by friday).

http://dev.w3.org/2006/waf/widgets/

The last call period will end on the 19th of Nov.

Below is the list of changes form last  pub (taken from the spec).

[[

This section describes the high level changes that have occurred since
this document was last published. This list is not exhaustive, but
gives a general overview of what changed and anything new that was
added. For a complete view of all the changes, please see the
differences between the last published draft and this document.

Conformance checker requirements are no longer part of this
specification. The conformance checker requirements will be worked on
independently from this document. An unpublished draft is available.

A number of bugs were fixed. The details can be found in the following emails:

[widgets] P&C BUG ALERT: Conformance checker behavior intermixed with
UA behavior
[widgets] BUG ALERT for P+C spec: Try to fallback to default start
files when src path is invalid or not existing
[widgets] BUG ALERT for P+C spec: deprecated, grandfathered, and
redundant tags should be skipped.
[widgets] Potential bug in Rule for Identifying the Media Type of a File
[widgets] Preference element is underspecified :(

ITS is no longer marked as being "at risk". ITS will remain the
recommended technology to allow localization of certain localized text
nodes within a configuration document.

The document no longer defines conformance criteria for Zip archives:
most archives are valid, but some may not be supported.

The ABNF for zip relative path has been updated to address a number of issues.

To reduce verbosity in the specification, the reserved folder names
table was merged into the reserved file names table.

It is no longer a normative requirement that P&C user agents behave as
a policy enforcement point with regards to scripts accessing the
content of a digital signature. In addition, it is no longer a
normative requirement that P&C user agents behave as a policy
enforcement point with regards to scripts running in SVG icons. These
requirements may appear in other specifications at a future date,
however.

Removed assertions that were repetitions of functionality defined in
the steps for processing a widget package.

Added more text that is required for MIME type registration, including
security considerations, interoperability issues, and encoding
considerations.

The icon element no longer supports xml:lang for internationalization proposes.

The relax NG schema was removed from the spec. It will be maintained
separately so it can be updated as the various specs that depend on it
mature.

The rule for identifying the media type of an image was merged with
the rule for identifying the media type of a file.

The definition of the widget family of specifications was moved to the
working group's wiki.

This specification now only defines conformance criteria for one class
of products (User Agents). In previous drafts, it included conformance
checkers and documents. Zip archives can no longer claim conformance
to this specification.

A user agent is now more clearly defined in terms of what other
specifications one must support.

Validity of zip relative paths is no longer dependent on encoding.
Validity is now simply based on whether a zip path matches the ABNF
for a zip relative path.
]]


-- 
Marcos Caceres
http://datadriven.com.au

Received on Tuesday, 27 October 2009 20:03:24 UTC