The Second Screen Community Group (CG) explores the use of secondary screens from Web pages. This Community Group incubates and develops specifications of network protocols that implement the Presentation API and the Remote Playback API.
This work has three primary purposes:
Enable interoperability among implementations of the Presentation API.
Encourage implementation of the Presentation API by browser vendors.
Establish complementary specifications for the Presentation API.
The scope of work proposed here goes beyond the current scope of the Second Screen Working Group (WG). Given wider support and adequate stability, we plan to migrate the proposals generated in this Community Group to an appropriate standards track, for example the IETF Standards Track or a W3C Working Group, for further contributions and formal standardization.
At TPAC 2013, the Second Screen Community Group was created to incubate an idea of making secondary screens first-class citizens on the Web. The Community Group produced an early version of the Presentation API specification that was used as a starting point for the Second Screen Working Group‘s formal standards work that commenced in 2014. The API that started its life in this Community Group is now implemented in a major browser and is advanced on the Recommendation Track.
Encouraged by the great feedback from the wider community, this Community Group was rechartered in September 2016 to do further exploratory work. Specifically, the group was chartered to incubate and develop specifications of network protocols that implement the Presentation API and the Remote Playback API. The renewed mission of this Community Group is to enable protocol-level interoperability, encourage more implementations, and to establish complementary specifications.
Join the Community Group to shape the future of the web-connected screens around you!
The Second Screen Presentation Working Group was chartered a couple of months ago at W3C, thanks to the support of W3C members, especially those participating in this Community Group. As described in its charter, the mission of the Working Group is to take the Presentation API specification along the Recommendation track up to its final publication as a Web standard.
To ease the transition and provide a concrete starting point for the Working Group, the Community Group published an updated version of the Presentation API as final report yesterday. This report includes the outcomes of recent discussions within the Community Group while the Working Group was being created.
The Community Group will now cease its work on the Presentation API specification and let the Working Group take it from there. Please note that the Community Group remains active though! It will typically explore potential future work items that are not yet in scope of the Working Group.
The <video> sharing demo that investigates using the HTMLMediaElement interface to control a video presented on a second screen.
The HTML Slidy remote demo that takes the URL of a slide show made with HTML Slidy and presents it on a second screen, turning the first screen into a slide show remote.
The Fraunhofer FOKUS’ Competence Center Future Applications and Media (FAME) has also been working on a number of implementations of the Presentation API as part of FAMIUM, an end-to-end prototype implementation for early technology evaluation and interoperability testing introduced by FAME.
Different types of second screens are supported depending on the demo considered, using custom version of Web browsers, browser extensions, etc. All demos fallback to opening the content in a separate browser window.
We will try to keep these demos aligned with the evolutions of the Presentation API, and complete the Presentation API demos page with additional ones over time. Feel free to share demos or suggestions on the group’s mailing-list!
Using the binaries from the page, or building your own version of Chromium with the provided patches applied, you can get an impression of what using Presentation API might look like and the sort of new usage scenarios that it enables. It’s also possible to experiment and build your own examples.