- From: Brendan Long <B.Long@cablelabs.com>
- Date: Fri, 8 Nov 2013 20:38:38 +0000
- To: Bob Lund <B.Lund@CableLabs.com>, Cyril Concolato <cyril.concolato@telecom-paristech.fr>, "public-inbandtracks@w3.org" <public-inbandtracks@w3.org>
> >- To identify the type of the track data, I don't think we should rely > >on the label. > > [2] uses the label for two different purposes. For 'track description' > metadata text tracks, the label identifies the MIME of the media resource > and that this metadata track holds the other track metadata. The MIME is > needed for JS to know how to parse the metadata Cues. For other tracks, > the label contains the stream ID of the the in-band stream that the track > represents. Someone has suggested that track.id could be used for this > purpose. I don't think we should use the label this way, since it's meant to be displayed to users, and showing users technical information like codecs and PIDs isn't user-friendly. It seems like "id" is already fine for exposing the PID / TrackUID / whatever, but we may need a new attribute to expose the MIME type. Is this not what the metadata dispatch type attribute is for?
Received on Friday, 8 November 2013 20:39:07 UTC