Skip to toolbar

Community & Business Groups

Call for Participation in Second Screen Presentation Community Group

The Second Screen Presentation Community Group has been launched:


The group’s goal is to define an API that allows web applications to use secondary screens to display Web content. Phones, tablets, laptops and other devices support ways to attach additional display screens. Common methods include attaching through video ports or HDMI, or wirelessly through Miracast, WiDi, or AirPlay. Screens can also be attached over a network. For many of these techniques the operating system hides how the screen is attached and provides ways for applications to use the screens. Native apps on an operating system can easily use these additional screens without having to know how they are attached to the device. The goal of this CG is to define simple APIs to request displaying an HTML page on the second screen and some means for the launching page on the first screen to communicate with and control the second page, wherever it is rendered. That API should hide the details of the underlying connection technologies and use familiar, common web technologies for messaging. The charter for this CG can be found at: https://github.com/webscreens/presentation-api/wiki/Second-Screen-Community-Group-Charter


In order to join the group, you will need a W3C account.

This is a community initiative. This group was originally proposed on 2013-11-05 by Dominik Röttsches. The following people supported its creation: Dominik Röttsches, Anssi Kostiainen, Louay Bassbouss, Jean-Charles Verdie, Mark Finkle. W3C’s hosting of this group does not imply endorsement of its activities.

If you believe that there is an issue with this group that requires the attention of the W3C staff, please send us email on site-comments@w3.org

Thank you,
W3C Community Development Team

Leave a Reply

Your email address will not be published. Required fields are marked *

Before you comment here, note that this forum is moderated and your IP address is sent to Akismet, the plugin we use to mitigate spam comments.

*