- From: <bugzilla@jessica.w3.org>
- Date: Thu, 02 Feb 2012 00:16:06 +0000
- To: public-html-a11y@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13359 --- Comment #43 from Bob Lund <b.lund@cablelabs.com> 2012-02-02 00:16:05 UTC --- (In reply to comment #42) > FWIW: I also don't think we need yet another mechanism to represent Ogg's role > values in <track> - that's what @kind was created for. Ogg defines 10 text track, 3 video track and 7 audio track Role values. The current HTML5 spec enumerates 5 text track kinds and 6 audio/video kinds. So all of Ogg's roles can't be mapped to @kind. If the definition of @kind was expanded so it could take on the value of Role in Ogg (and designated fields in other media formats) then that would work. > As for what is in Ogg's > name - this was what <track>'s @label attribute was created for. Ogg has no > means to specify what type of metadata is in a track other than giving it in > the "name" field. So, from Ogg's POV there is nothing that we need extra. > > Why can't MPEG also just throw all its extra information about codecs and > metadata types etc into the @label attribute? This is possible, although the current language spec says the label is human readable, which wouldn't be the case for MPEG metadata. -- Configure bugmail: https://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, 2 February 2012 00:16:08 UTC