- From: mark a. foltz <mfoltz@google.com>
- Date: Tue, 19 Sep 2017 13:32:19 -0700
- To: "Kostiainen, Anssi" <anssi.kostiainen@intel.com>
- Cc: "gchandok@apple.com" <gchandok@apple.com>, "public-webscreens@w3.org" <public-webscreens@w3.org>
- Message-ID: <CALgg+HGYyDOq4m5evy2d0MtyY-BScJKfdGbMY5CCgjUKXOi2aQ@mail.gmail.com>
Welcome Gurtej! I am the editor of the Presentation API and contribute to both the Remote Playback API and the Open Screen protocol. I hope you can us at our face to face meeting at TPAC 2017, where the Open Screen will occupy a good portion of our agenda. We are working on the agenda now. m. On Tue, Sep 19, 2017 at 3:12 AM, Kostiainen, Anssi < anssi.kostiainen@intel.com> wrote: > Hi Gurtej, > > Welcome to the Second Screen Community Group! > > This group is incubating specifications of network protocols collectively > referred to as "Open Screen Protocol" that underpin the Presentation API > and Remote Playback API. This work happens in GitHub at: > > https://github.com/webscreens/openscreenprotocol > > The Second Screen Community Group's charter talks more about the scope and > expected deliverables: > > https://webscreens.github.io/cg-charter/ > > I thought this might be a good opportunity to share a bit of the > historical background (reproduced from my earlier blog post): > > 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. > > We're looking forward to working with you, and look forward to your > contributions. Please do not hesitate to get in touch with me if you have > any questions. > > Thanks, > > -Anssi (Second Screen Community Group Chair)
Received on Tuesday, 19 September 2017 20:33:34 UTC