[w3ctag/spec-reviews] Remote Playback API (#145)

Hello TAG!

I'm requesting a TAG review of:

  - Name: Remote Playback API
  - Specification URL: https://w3c.github.io/remote-playback/
  - Explainer, Requirements Doc, or Example code: See [Use cases and Requirements](https://github.com/w3c/remote-playback/blob/gh-pages/use-cases.md) document, and note the [Introduction](https://w3c.github.io/remote-playback/#introduction) and [Examples](https://w3c.github.io/remote-playback/#examples) sections in the spec.
  - Primary contacts: @avayvod, @mounirlamouri, @tidoust, @anssiko

Further details (optional):

  - Relevant time constraints or deadlines: by end of 2016. The group intends to finalize the API beginning of 2017 and transition to CR then.
  - [ ] I have read and filled out the [Self-Review Questionnare on Security and Privacy](https://www.w3.org/TR/security-privacy-questionnaire/). The Second Screen WG will run that evaluation in parallel. The spec does not contain a Privacy and Security section yet.
  - [x] I have reviewed the TAG's [API Design Principles](https://w3ctag.github.io/design-principles/). I had not noticed this document before. The Remote Playback API seems to follow these principles.

The Remote Playback API is to media content what the Presentation API is to web content. Although the API is different (the Remote Playback API extends the `HTMLMediaElement` interface), the spec re-uses patterns and design consideration from the Presentation API whenever appropriate.

Work on the API is not over yet. The Second Screen WG does not anticipate major changes to the API surface though and believes now is a good time to gather wide review on the document. [Known issues](https://github.com/w3c/remote-playback/issues) so far are considered minor, expect [issue #41](https://github.com/w3c/remote-playback/issues/41) which discusses the set of media playback features that remote playback devices must support and the impact of remoting playback on the observable behavior from the controlling page's perspective. The group welcomes feedback from the TAG on this issue. Let us know if you'd like us to go deeper into details.

For background, we mentioned the Remote Playback API (the spec did not have a name at the time) when we requested a TAG review of the Presentation API. The [resulting TAG review](https://github.com/w3ctag/spec-reviews/blob/master/2015/presentation-api.md) contains some thoughts on "Presenting the content of an `<audio>` or `<video>` element" in particular.

We'd prefer the TAG provide feedback as (please select one):

  - [x] open issues in our [Github repo](https://github.com/w3c/remote-playback/) for each point of feedback
  - [ ] open a single issue in our Github repo for the entire review
  - [ ] leave review feedback as a comment in this issue and @notify [github usernames]

(any of these options is fine in practice)


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/spec-reviews/issues/145