- From: <bugzilla@jessica.w3.org>
- Date: Thu, 17 Apr 2014 20:28:56 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25355 --- Comment #8 from Bob Lund <b.lund@cablelabs.com> --- (In reply to Brendan Long from comment #7) > (In reply to Aaron Colwell from comment #6) > > Does this mean that all metadata should be multiplexed into a single > > "metadata" TextTrack? If not, how is the application expected to select the > > "right" metadata track for the specific metadata it is interested in? > > I think this is what's being suggested. What I heard from people at Apple > was that we don't necessarily know what type of metadata we're looking at, > so maybe it would be better to have separate tracks for each type like we > have now, and then have some sort of "we don't know what type this is" > metadata track? I'm not sure that track would ever be useful to web authors > though. It seems to be a UA implementation, and perhaps a media container format, issue whether the type of data in a metadata track is known when the track is created. In the case where the type is known at track creation, having the type associated with each Cue in that track works but is sub-optimal. It also seems that a UA, again perhaps based on media resource format, will either multiplex all Cue types into a generic metadata text track or it will create type specific metadata text tracks. I can't construct a use case why both would be done for a specific media resource instance. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 17 April 2014 20:29:00 UTC