[Bug 13359] <track> A way is needed to identify the type of data in a track element

https://www.w3.org/Bugs/Public/show_bug.cgi?id=13359

--- Comment #28 from Bob Lund <b.lund@cablelabs.com> 2011-12-08 21:38:37 UTC ---

(In reply to comment #27)

> 
> Once a UA determines that the track is a metadata text track, here are the
> fields, by media container, that I think should be concatenated in some fashion
> to go in this string (perhaps this should apply to all video, audio and text
> tracks where the UA cannot determine the kind):
> 
> Ogg[1] - Ogg skeleton header fields: content_type, role, name
> 
> MPEG-2 TS[2] - Program map table entry fields: stream_type, any descriptors
> 
> DASH[3] - MPD Role element, e.g.  <Role schemeIdUri=”urn:mpeg:DASH:role:2011”
> value=”subtitle”/>. NOTE: DASH has defined a scheme with a set of values. It is
> expected that other organizations will define additional schemes as needed.
> 
> WebM[4] - trackID and codecId.
> 
> ISOBMFF (MPEG-4)[5] - Contents of the handler reference box (hdlr) in each
> track : attributes handler_type and name. NOTE: MPEG only defines three types
> of track handlers: video, audio and hint. Other organizations can (and have)
> extend the MPEG handler reference box to define new types of tracks.
> 
> [1] http://wiki.xiph.org/SkeletonHeaders
> [2] ITU H.222.0 (5/2006) Table 2-33
> [3]
> http://developer.longtailvideo.com/trac/export/1601/branches/adaptive/doc/specs/dash.pdf
> [4] http://matroska.org/technical/specs/index.html
> [5] ISO/IEC 14496-12
> 
> Bob

Realized I made an error in Comment #27 - the fields for WebM should be
TrackType and CodecId, not trackID and codecId.

Bob

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 8 December 2011 21:39:01 UTC