This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
https://html.spec.whatwg.org/multipage/embedded-content.html#dom-audiotrack-kind Sourcing AudioTrack and VideoTrack attribute values (in particular @kind, @id, @label and @language) should reference the "Sourcing In-band Media Resource Tracks from Media Containers into HTML" spec rather than duplicate it: http://dev.w3.org/html5/html-sourcing-inband-tracks/
I don't understand. What is duplicated?
Basically, everything that relates to particular file formats, such as Ogg, WebM, MP4, DASH at https://html.spec.whatwg.org/multipage/embedded-content.html#dom-audiotrack-kind . In particular: * The following sentence's meaning is in the sourcing spec: "For Ogg files, the Role header field of the track gives the relevant metadata." see http://dev.w3.org/html5/html-sourcing-inband-tracks/#ogg point 4, about @kind. * And continuing: "For DASH media resources, the Role element conveys the information." see http://dev.w3.org/html5/html-sourcing-inband-tracks/#mpegdash point 4, about @kind. * And continuing: "For WebM, only the FlagDefault element currently maps to a value." see http://dev.w3.org/html5/html-sourcing-inband-tracks/#webm point 4, about @kind. * And then the "Examples" column in the @kind table below.
Those are just non-normative helpful hints, just like where the spec says "For example, user agents are required to close all open constructs upon finding the end of a style sheet unexpectedly" or "The HTTP specification requires that 301, 302, and 307 redirects, when applied to methods other than the safe methods, not be followed without user confirmation".
Despite being non-normative, the level of detail and it being in the HTML spec may make ppl follow it. Also, the last field in the table is already wrong: "Any other track type, track role, or combination of track roles not described above." mapped to "" For example, Ogg video tracks with role="captions" should be mapped to "captions" - this is missing from your list and thus would create a mapping to the empty string. So, that statement may make people think that this is a final and complete list, which it likely will never be. To be honest, I'd rather there weren't any mapping examples in that table and the table would just describe the defined categories.
I've removed the example for "" since yeah, that made no sense. Not having any examples at all though is contrary to the usual feedback I get — people love examples, and generally want more and more.
OK, fair enough.