Internet Society and W3C Strengthen Relationship to Help Ensure Open Global Internet

11 December 2009 | Archive

In a joint press release today, The Internet Society (ISOC) and W3C announced a donation from ISOC for the purpose of advancing the evolution of W3C as an organization that creates open Web standards. "ISOC and W3C have worked together for years in a number of areas, and have deeply shared values about the Internet’s development," said Lynn St. Amour, President and CEO of the Internet Society. "Our support to the W3C in their transition efforts demonstrates ISOC's commitment to ensuring the Internet continues to be an open, global platform for innovation." The announcement reflects the two organizations' shared aim of ensuring the continued growth and accessibility of the global Internet and Web, and stewardship responsibilities to ensure these global communication platforms continue to benefit users worldwide. More information is available in the press release and in a FAQ about ISOC and W3C.

New WAI Resource: Contacting Organizations about Inaccessible Websites

06 January 2010 | Archive

The Web Accessibility Initiative (WAI) Education and Outreach Working Group (EOWG) today published Contacting Organizations about Inaccessible Websites as part of the WAI-AGE Project. This new WAI resource guides you through telling organizations about accessibility barriers on their website. WAI would like to know how this resource works for you and how we can improve it. See the blog post: Take a few minutes to encourage web accessibility. Your voice counts. Learn about Accessibility and visit the WAI home page.

Last Call: XProc: An XML Pipeline Language

05 January 2010 | Archive

The XML Processing Model Working Group has published a Last Call Working Draft of XProc: An XML Pipeline Language, a language for describing operations to be performed on XML documents. A pipeline consists of steps. Like pipelines, steps take zero or more XML documents as their inputs and produce zero or more XML documents as their outputs. The inputs of a step come from the web, from the pipeline document, from the inputs to the pipeline itself, or from the outputs of other steps in the pipeline. The outputs from a step are consumed by other steps, are outputs of the pipeline as a whole, or are discarded. Comments are welcome through 02 February. Learn more about the Extensible Markup Language (XML) Activity.

Indexed Database API Draft Published

05 January 2010 | Archive

The Web Applications Working Group has published a Working Draft of Indexed Database API. User agents need to store large numbers of objects locally in order to satisfy off-line data requirements of Web applications. The Web Storage specification is useful for storing pairs of keys and their corresponding values. However, it does not provide in-order retrieval of keys, efficient searching over values, or storage of duplicate values for a key. The current specification provides a concrete API to perform advanced key-value data management that is at the heart of most sophisticated query processors. It does so by using transactional databases to store keys and their corresponding values (one or more per key), and providing a means of traversing keys in a deterministic order. Learn more about the Rich Web Client Activity.

Seven API Publications Advance Web Applications Stack

22 December 2009 | Archive

The Web Applications Working Group has published updates to seven specifications related to APIs that enhance the open Web platform as a runtime environment for full-featured applications. W3C invites implementation experience for the two newest Candidate Recommendations:

  • The Widget Interface defines an application programming interface (API) for widgets that provides functionality for accessing a widget's metadata and persistently storing data. The group's implementation report will be used to track progress.
  • Selectors API Level 1 defines methods for retrieving Element nodes from the DOM by matching against a group of selectors (such as those used in Cascading Style Sheets). The group is developing a selectors API test suite.

Comments on these Last Call Working Drafts are welcome until 30 June 2010:

  • Web Storage provides APIs for Web applications to store key-value data on the client side.
  • Web Workers defines an API for enabling thread-like operations (using message passing) in Web applications, so that certain application tasks can be run in parallel.
  • Server-Sent Events defines an API for a Web application to open an HTTP connection for receiving push notifications from a server, in the form of DOM events.

The group also updated these Working Drafts:

  • Web Sockets API provides an API for full-duplex communication between a Web application and a remote host.
  • Web SQL Database defines an API for Web applications to store data in client-side databases that can be queried using a variant of SQL.

Learn more about the Rich Web Client Activity.

W3C Invites Implementations of Web Security Context: User Interface Guidelines

22 December 2009 | Archive

The Web Security Context Working Group invites implementation of the Candidate Recommendation of Web Security Context: User Interface Guidelines. This specification deals with the trust decisions that users must make online, and with ways to support them in making safe and informed decisions where possible. It specifies user interactions with a goal toward making security usable, based on known best practice in this area. Read the group's expectations about implementation and testing and learn more about the Security Activity.

More news…

Talks and Appearances Header link

Events Header link

  • 2010-01-26 (26 JAN) 2010-01-28 (28 JAN)

    WS-Resource Access WG

    Sunnyvale, CA, USA


  • 2010-03-16 (16 MAR) 2010-03-18 (18 MAR)

    Device APIs and Policy Working Group

    Prague, Czech Republic

    Charles University

  • 2010-03-21 (21 MAR) 2010-03-23 (23 MAR)

    AC Cambridge 2010

    Cambridge, MA