Re: Second Screen Presentation Community Group Proposed

I would support such a group and would like to participate but the vocable "second screen" is now a misnomer as a the tablet is becoming the first screen. How about the "companion screen" instead. In any case good idea as the demands of the non traditional screening devices require new APIs. I would probably be interesting to link this work to some of the webrtc work as well as to some of the "acceleration" mechanisms proposed in the IETF which while not directly related to the "how the device is connected" is inherently linked to user experience.


Marie-Jose Montpetit
mariejo@mit.edu



On Nov 5, 2013, at 6:04 AM, Olivier Thereaux <Olivier.Thereaux@bbc.co.uk> wrote:

> FYI - a "Second Screen Presentation Community Group” has been proposed.
> 
> The proposed charter is here:
> https://github.com/webscreens/presentation-api/wiki/Second-Screen-Community-Group-Charter
> 
> And the main proposing party seems to be Intel, which I don’t believe is participating in this IG. Maybe on opportunity of outreach for our chairs?
> 
> Olivier
> 
> Begin forwarded message:
> 
>> Resent-From: <public-new-work@w3.org>
>> From: Do Not Reply <nobody@w3.org>
>> Subject: Second Screen Presentation Community Group Proposed
>> Date: 5 November 2013 13:40:08 GMT
>> To: <public-new-work@w3.org>
>> 
>> The Second Screen Presentation Community Group has been proposed:
>> 
>> --------------------------------------------------
>> 
>> 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
>> 
>> --------------------------------------------------
>> 
>> You are invited to support the creation of this group:
>> http://www.w3.org/community/groups/proposed#webscreens
>> 
>> Once the group has a total of five supporters, it will be launched and
>> people can join to begin work. Once launched, the group will no longer
>> be listed as "proposed"; it will appear in the list of current groups:
>> http://www.w3.org/community/groups/
>> 
>> In order to support the group, you will need a W3C account. To request one:
>> http://www.w3.org/community/account/request
>> 
>> 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.
>> 
> 
> 
> 
> -----------------------------
> http://www.bbc.co.uk
> This e-mail (and any attachments) is confidential and
> may contain personal views which are not the views of the BBC unless specifically stated.
> If you have received it in
> error, please delete it from your system.
> Do not use, copy or disclose the
> information in any way nor act in reliance on it and notify the sender
> immediately.
> Please note that the BBC monitors e-mails
> sent or received.
> Further communication will signify your consent to
> this.
> -----------------------------
>