- From: Bob Lund <B.Lund@CableLabs.com>
- Date: Thu, 14 Nov 2013 18:01:59 +0000
- To: Brendan Long <B.Long@cablelabs.com>, Philip Jägenstedt <philipj@opera.com>
- CC: Cyril Concolato <cyril.concolato@telecom-paristech.fr>, "public-inbandtracks@w3.org" <public-inbandtracks@w3.org>
On 11/14/13 10:25 AM, "Brendan Long" <B.Long@cablelabs.com> wrote: >> Another approach was suggested by Cyril, which I like. This was to set >>an >> attribute on all video, audio and text tracks that contain that tracks >> media resource metadata. The inbandTrackMetadataDispatchType [1] >>attribute >> essentially fills this role for TextTracks with 'kind' == metatdata. We >> could propose adding this attribute to video and audio tracks, and >> renaming it trackMetadata. I will also write up this alternative and put >> it in the Wiki so we can compare the two. > >inbandTrackMetadataDispatchType is defined as a DOMString. The encoding for binary data is specified as hexadecimal representation. > Are we planning to expose the metadata as JSON or something like that, >or would it make more sense to expose it as binary? > >I'm personally a fan of JSON, but it sounds like other developers would >prefer directly exposing the original binary (although in some cases, >like MPEG-TS, that might be a *lot* of data). I am going to propose the same encoding - a hexadecimal representation. This will be easier for the UA than JSON. Of course, all of this is open to discussion. I just want to get something on the Wiki.
Received on Thursday, 14 November 2013 18:03:12 UTC