Advancing Remote Playback API to Proposed Recommendation

• From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
• Date: Fri, 20 Dec 2019 09:10:50 +0000
• To: "public-secondscreen@w3.org" <public-secondscreen@w3.org>
• Message-ID: <90B3E696-8EE5-4FF1-ADA6-D99338E5F07E@intel.com>

Hi All,

We now have two independent implementations [1] (thanks Jer!), and as such are one important step closer to Remote Playback API Proposed Recommendation.

Here's the detailed plan how to get there [2].

And here's TL;DR how *you* can help:

Before advancing to PR the group needs to identify whether any of the issues raised since 2017-10-19 [3] are substantive and address them, or whether they should be deferred to the next version of the API. 

Please provide your feedback by 2020-01-17.

I expect us to publish the PR earliest in Q1 2020.

Thanks,

-Anssi (Second Screen WG/CG chair)


[1] https://lists.w3.org/Archives/Public/public-secondscreen/2019Dec/0003.html

[2] https://github.com/w3c/remote-playback/issues/130

[3] https://github.com/w3c/remote-playback/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+created%3A%3E%3D2017-10-19+

Received on Friday, 20 December 2019 09:10:59 UTC