W3C home > Mailing lists > Public > public-web-and-tv@w3.org > June 2018

Re: [me-media-timed-events] ISO BMFF Byte Stream Format spec does not mention emsg

From: Bob Lund <b.lund-contractor@cablelabs.com>
Date: Wed, 6 Jun 2018 15:48:14 +0000
To: John Simmons via GitHub <sysbot+gh@w3.org>, "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>
Message-ID: <BY2PR06MB1814989BCF18CC0700B23A9DBD650@BY2PR06MB1814.namprd06.prod.outlook.com>
I think you are right. This draft https://dev.w3.org/html5/html-sourcing-inband-tracks/ was created to define how the contents of various media containers should be exposed to web apps. It is referenced by the HTML and MSE specs.

Sourcing In-band Media Resource Tracks from Media ...<https://dev.w3.org/html5/html-sourcing-inband-tracks/>
dev.w3.org
Sourcing In-band Media Resource Tracks from Media Containers into HTML Unofficial Draft 26 April 2015 Latest editor's draft: http://dev.w3.org/html5/html-sourcing-inband-tracks/




________________________________
From: John Simmons via GitHub <sysbot+gh@w3.org>
Sent: Wednesday, June 6, 2018 8:43 AM
To: public-web-and-tv@w3.org
Subject: Re: [me-media-timed-events] ISO BMFF Byte Stream Format spec does not mention emsg

My understanding - the scope of the ISO BMFF Byte Stream Format spec is to be used by the Media Source Extensions spec, and that the scope of the Media Source Extensions [https://www.w3.org/TR/media-source](url) spec is the dynamic construction of media streams for <audio> and <video>. Exposing emsg events to JavaScript Apps is out of scope for the Media Source Extensions (DataCue? Other?). And based because it is scoped to use by the MSE spec, emsg is also out of scope for the Byte Stream spec. Thoughts?

--
GitHub Notification of comment by johnsim
Please view or discuss this issue at https://github.com/w3c/me-media-timed-events/issues/1#issuecomment-395094001 using your GitHub account
Received on Thursday, 7 June 2018 00:09:05 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 7 June 2018 00:09:06 UTC