Public Newsletter

Call for Review: Service Modeling Language, Version 1.1 Proposed Recommendation

2009-02-13: The Service Modeling Language Working Group has published the Proposed Recommendations of Service Modeling Language, Version 1.1 and Service Modeling Language Interchange Format Version 1.1. SML extends the coherence-checking mechanisms of W3C XML Schema from individual documents to collections of documents. SML-IF extends the utility of SML by providing mechanisms for gathering together a set of documents whose coherence is guaranteed by an SML schema, which itself is part of the resulting package. Comments are welcome through 12 March. Learn more about the Extensible Markup Language (XML) Activity. (Permalink)

Drafts of HTML 5, Differences from HTML 4 Published

2009-02-12: The HTML Working Group has published Working Drafts of HTML 5 and HTML 5 differences from HTML 4. In this version of HTML5, new features are introduced to help Web application authors, new elements are introduced based on research into prevailing authoring practices, and special attention has been given to defining clear conformance criteria for user agents in an effort to improve interoperability. Learn more about the HTML Activity. (Permalink)

Incubator Group Report: RDB2RDF

2009-02-10: The RDB2RDF Incubator Group published their final report. In the report, the group recommends that the W3C initiate a WG to standardize a language for mapping Relational Database schemas into RDF and OWL. This publication is part of the Incubator Activity, a forum where W3C Members can innovate and experiment. This work is not on the W3C standards track. (Permalink)

Widgets 1.0: APIs and Events

2009-02-10: The Web Applications Working Group has published the First Public Working Draft of Widgets 1.0: APIs and Events. This specification defines a set of APIs and events for the Widgets 1.0 Family of Specifications that enable baseline functionality for widgets. The APIs and Events defined by this specification defines, amongst other things, the means to:

• access the metadata declared in a widget's configuration document,
• receive events related to changes in the view state of a widget,
• determine the locale under which a widget is currently running,
• be notified of events relating to the widget being updated,
• invoke a widget to open a URL on the system's default browser,
• requests the user's attention in a device independent manner,
• and check if any additional APIs requested via the configuration document's feature element have successfully loaded.

Learn more about the Rich Web Client Activity. (Permalink)