- From: boblund via GitHub <sysbot+gh@w3.org>
- Date: Thu, 07 Jun 2018 15:07:37 +0000
- To: public-web-and-tv@w3.org
MSE media specs describe requirements for the media container insofar as required for MSE to process it. It's not apparent emsg has any requirements in this regard, but maybe. "Sourcing In-band Media Resource Tracks from Media Containers into HTML" [1] was created to define how the contents of various media containers should be recognized by the user agent and how the user agent makes this media container content available to web apps via various APIs. [1] is referenced by the HTML and MSE specs. Supporting emsg will require extending [1] to define where the UA should recognize emsgs, in all the relevant media containers, and the common API to make the contents available. For emsgs destined to JavaScript, the API definition will need to reference (or define) some cue format - there are some options in this regard. DataCue is one. If the IG has requirements for emsg use cases beyond events to JavaScript, then something beyond the functionality of DataCue might be required. [1] https://dev.w3.org/html5/html-sourcing-inband-tracks/ -- GitHub Notification of comment by boblund Please view or discuss this issue at https://github.com/w3c/me-media-timed-events/issues/1#issuecomment-395455358 using your GitHub account
Received on Thursday, 7 June 2018 15:07:40 UTC