- From: Chris Needham via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Apr 2020 13:55:28 +0000
- To: public-web-and-tv@w3.org
Thank you! As we start this activity in the IG, I want to clearly define the purpose and scope of the document. Going back to [issue 30][1], the starting points are: (1) the need for improved interoperability for media devices, and (2) that changing HTML spec is unrealistic. While (1) is certainly true, I'd like to clarify whether the goal for the document is information gathering, or producing a set of guidelines. I would be concerned about the IG producing a Note with content similar to, e.g., section 9.6 in [the HbbTV spec][1], for example, which sets requirements how resource contention should be handled by media players. For (2), the IG's role here could be to help coordinate bringing issues to WHATWG. The `mediaElement.currentTime` clarification issue seems straightforward, for example. Input from the Chrome team in issue 30 suggests useful aspects to explore further: "there may be a core set of principles we can document" and "there will come a future time where we can drop the illusion and just fail playback when resources are constrained". So I think there is a useful discussion to be had. I'd prefer to see this in it's own repo. Issue 30 contains a large number of questions, so would be helpful to raise individual issues for each one. [1]: https://github.com/w3c/webmediaporting/issues/30 [2]: https://www.etsi.org/deliver/etsi_ts/102700_102799/102796/01.05.01_60/ts_102796v010501p.pdf -- GitHub Notification of comment by chrisn Please view or discuss this issue at https://github.com/w3c/media-and-entertainment/pull/34#issuecomment-613457624 using your GitHub account
Received on Tuesday, 14 April 2020 13:55:30 UTC