+1 for me.
For Presentation API I would like to focus on implementation and developer
feedback, and use that to spec either addenda on level 1 or features for
level 2.
For Open Screen, I would like to focus on consensus around a viable
protocol stack and security architecture, and hopefully have data to share
based on our ongoing evaluation work.
m.
On Wed, Apr 19, 2017 at 5:28 AM, Kostiainen, Anssi <
anssi.kostiainen@intel.com> wrote:
> Hi Second Screen WG and CG,
>
> The W3C will have its annual all-groups TPAC meeting 6-10 November 2017 in
> Burlingame CA, just outside San Francisco:
>
> https://www.w3.org/2017/11/TPAC/
>
> I propose the Second Screen Working Group and its sister Community Group
> will meet at TPAC 2017 on Monday-Tuesday, 6-7 November 2017.
>
> In scope for the F2F would be to wrap-up the Presentation API and Remote
> Playback API work from the Working Group (unless we've already shipped by
> then), and in particular discuss the Open Screen Protocol [1] work from the
> Community Group with possible joint meetings with other groups involved in
> protocol-level work (e.g. WebRTC WG), and manufacturers that might want to
> produce Open Screen Protocol compliant receiver devices, for example.
>
> All - please let us know by 1 May if you have known blockers around the
> TPAC dates. Also, let us know if you already know you are not planning to
> attend. The advance registration for TPAC will open in June 2017, but we
> must inform TPAC planners by mid-May whether we want to meet and when.
>
> Thanks,
>
> -Anssi
> Chair, W3C Second Screen WG and CG
>
> [1] https://github.com/webscreens/openscreenprotocol
>
>
>