- From: <bugzilla@jessica.w3.org>
- Date: Thu, 03 Nov 2011 21:36:36 +0000
- To: public-html-a11y@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13359 --- Comment #21 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-11-03 21:36:35 UTC --- So the use case here is that there are in-band streams, e.g. TV, that have application-specific metadata, e.g. ad targeting keywords, game data, and the like, which are to be handled by specific modules on the client side as they arrive, basically "dispatching" each track to a separate blob of code that does not know ahead of time whether it will be needed or not. We can't use "label" because some formats already provide a human-readable string even for metadata tracks (for debugging?). Is there any particular reason there needs to be multiple metadata tracks for this, instead of the media stream having a single metadata stream that uses a convention of putting the "dispatch" type code in the first line of the cue, or something along those lines? (That would also avoid the problem of having to keep track of when these new tracks come along and enabling them.) -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Thursday, 3 November 2011 21:36:46 UTC