- From: <bugzilla@jessica.w3.org>
- Date: Thu, 17 Apr 2014 16:59:39 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25355 --- Comment #6 from Aaron Colwell <acolwell@google.com> --- Ted, You are advocating for the removal of inBandMetadataTrackDispatchType here right? 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? For example, I was thinking of metadata tracks as being useful for transporting auxiliary "data tracks" for things like the Breakdancing Robot Control Protocol(BDRCP) messages. Web applications connected to breakdancing robots would want to be able to identify these tracks and watch for messages so robot dancing could be initiated, but applications that just care about presentation level metadata like ID3 tags might not want to receive these cues. I viewed inBandMetadataTrackDispatchType as a way to determine the type of data conveyed by the particular track so that the web application could set event listeners appropriately. While breakdancing robots may not be popular ...yet... I'm sure there are other "data track" use cases that exist right now that may benefit from keeping inBandMetadataTrackDispatchType to allow grouping of metadata cues. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 17 April 2014 16:59:40 UTC