W3C News

W3C Invites Implementations of Page Visibility Level 2

The Web Performance Working Group invites implementation of the Candidate Recommendation of Page Visibility Level 2. The Page Visibility API defines a means to programmatically determine the visibility state of a top level browsing context, and to be notified if the visibility state changes. This specification defines a means to programmatically determine the visibility state of a document. This can aid in the development of resource efficient web applications.

Media Source Extensions™ is a W3C Recommendation

Media Source Extensions pipeline model diagramThe HTML Media Extensions Working Group has published a W3C Recommendation for Media Source Extensions™. This specification fulfills a vital part of putting video on the Web by extending the HTML5 video capabilities and facilitating a variety of use cases like adaptive streaming, time shifting and video editing, as well as 360° video players. Flexible and powerful, Media Source Extensions™ provides commercial quality IP streaming video for Web applications, across different platforms and between unrelated companies, and is already deployed in major browsers and video services, such as Youtube.

W3C invites implementations of ActivityPub

The W3C Social Web Working Group is calling for implementations of ActivityPub, which is now a Candidate Recommendation. The ActivityPub protocol is a decentralized social networking protocol based upon the ActivityStreams 2.0 data format. It provides a client to server API for creating, updating and deleting content, as well as a federated server to server API for delivering notifications and subscribing to content. The protocol design iterates significantly on the earlier pump.io protocol, and implementors of pump.io clients and servers are particularly encouraged to update.

W3C Workshop Report: Web & Virtual Reality

W3C published today the report of the W3C Workshop on Web & Virtual Reality held on October 19-20 2016 in San Jose, California, USA. During the workshop, 120 participants representing browser vendors, headset and hardware manufacturers, VR content providers, designers and distributors analyzed the opportunities provided by making the Web a full-fledged platform for VR experiences.

They recognized the strong prospects already opened by existing and in-development Web APIs, in particular the WebVR API that was highlighted as an important target for near-term standardization, as well as the high priority of making the Web a primary platform for distributing 360° videos. They also identified new opportunities that would be brought by enabling traditional Web pages to be enhanceable as immersive spaces, and in the longer term, by making 3D content a basic brick available to Web developers and content aggregators.

You may read more in our media advisory.

W3C Invites Implementations of Encoding

The Internationalization Working Group has updated the Candidate Recommendation of Encoding. For new protocols and formats, as well as existing formats deployed in new contexts, this specification requires the utf-8 encoding. It also defines a limited set of other legacy encodings so that user agents can convert to and from utf-8 in a standardized and therefore interoperable way.

W3Cx opens CSS Introduction course

CSS intro course logoToday, W3C announced the start of its new W3Cx MOOC: CSS Introduction, designed in cooperation with the Microsoft Corporation. This 5-week long course will teach how to style your Web sites like a pro, with fonts, colors, layout, etc.

If you start now, you will be just in time to celebrate the 20th anniversary of CSS with us on 17 December and create a cool design to say “Happy Birthday, CSS!”. Learn more about W3Cx courses.

W3C Invites Implementations of Canonical EXI

The Efficient XML Interchange Working Group has published a W3C Recommendation of Canonical EXI. This specification describes a relatively simple method for generating a physical representation, the canonical form, of an EXI document that accounts for the permissible differences. An example of the applications targeted by this specification is one that needs to guarantee non-repudiation using XML Signature yet allows certain flexibility for intermediaries to reconstitute the documents before they reach final destination without breaking the signatures. Note that two documents may have differing canonical forms yet still be equivalent in a given context based on more elaborate application-specific equivalence rules which is out of scope of this specification.