W3C home > Mailing lists > Public > public-secondscreen@w3.org > January 2017

Fwd: Open screen protocol work kickoff

From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
Date: Tue, 3 Jan 2017 15:56:30 +0000
To: "public-secondscreen@w3.org" <public-secondscreen@w3.org>
Message-ID: <9319B26F-992E-497F-A43A-52384B75D0B7@intel.com>
Hi Second Screen WG,

I'd like to bring to your attention this announcement that was sent to the sister Second Screen Community Group before the holidays:

The CG has started its work to incubate and develop specifications of network protocols that implement the Presentation API and the Remote Playback API, referred to as "Open Screen Protocol". Interested contributors should chime in on the dedicated GitHub repo's issues:

https://github.com/webscreens/openscreenprotocol/issues/

[As you may recall, the Community Group was rechartered in September 2016 to take on protocol work. The renewed mission of the CG is to enable protocol-level interoperability, encourage more implementations, and to establish complementary specifications, see: https://webscreens.github.io/cg-charter/]

Thanks Mark for structuring the work streams and kicking off this work in the CG.

Thanks,

-Anssi (WG & CG Chair)

> Begin forwarded message:
> 
> From: "mark a. foltz" <mfoltz@google.com>
> Subject: Open screen protocol work kickoff
> Date: 6 December 2016 at 02:46:35 GMT+2
> To: "public-webscreens@w3.org" <public-webscreens@w3.org>
> Resent-From: <public-webscreens@w3.org>
> Archived-At: <http://www.w3.org/mid/CALgg+HEgApaq60L0KWiqXZuJxbR7Cp9RqRxgfSfNT36YaxLJMw@mail.gmail>
> 
> Greetings Second Screen Community Group members,
> 
> After a post-TPAC pause, in which I've been focused more on Presentation API spec work and testing, I'm starting to turn my attention to the Open Screen protocol work which this group was rechartered to undertake in October [1].
> 
> I've structured the initial work by filing some Meta-issues in GitHub covering several areas that will serve as background research for drafting the protocol itself.  Each of the "meta" issues listed is liked to sub-issues listing concrete tasks or alternatives to evaluate.
> 
> I am thinking each requirements task or evaluation can be resolved by a document in MarkDown checked into the openscreenprotocol repository.
> 
> If there are additional alternatives that should be brought forward for consideration, now would be the time to file an additional GitHub issue for it; I can help link it to the appropriate meta-issue(s).
> 
> There are provisional owners assigned to specific issues based on what we had volunteers for at TPAC.  Of course, additional contributors are always appreciated. 
> 
> I will start checking in requirements drafts (from the earlier work to develop the charter) and outlines for evaluation.
> 
> Once these meta-issues are knocked off, we should have some good background to discuss which alternatives we want to move forward with fuller specification.
> 
> If you have any feedback or questions on the overall work structure, let me know.
> 
> Following is a list of the open Meta issues in the repository.
> 
> [Meta] Write document describing protocol requirements
> https://github.com/webscreens/openscreenprotocol/issues/1
> 
> [Meta] Evaluate presentation screen discovery mechanisms
> https://github.com/webscreens/openscreenprotocol/issues/5
> 
> [Meta] Evaluate protocol transport mechanisms
> https://github.com/webscreens/openscreenprotocol/issues/8
> 
> Control protocols for Presentation API and Remote Playback API
> https://github.com/webscreens/openscreenprotocol/issues/11
> https://github.com/webscreens/openscreenprotocol/issues/12
> 
> [Meta] Propose security mechanisms for Open Screen protocol
> https://github.com/webscreens/openscreenprotocol/issues/13
> 
> Cheers,
> m.
> 
> [1] https://webscreens.github.io/cg-charter/
Received on Tuesday, 3 January 2017 15:57:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:19:02 UTC