[Bug 13359] <track> A way is needed to identify the type of data in a track element

https://www.w3.org/Bugs/Public/show_bug.cgi?id=13359

--- Comment #33 from Bob Lund <b.lund@cablelabs.com> 2011-12-13 23:34:20 UTC ---
(In reply to comment #32)
> > > > name is already mapped to the @kind attribute; what more do you expect from it?
> > > 
> > > Definition of @kind enumerates a set of kinds. There is only a single metadata
> > > kind. The definition of name in http://wiki.xiph.org/SkeletonHeaders#Name
> > > states it is a free text string. Inclusion of name could be used to
> > > discriminate the specific type of metadata.
> > 
> > And here I meant @title - I really don't know how I got so confused! :-)
> 
> OK, Christmas is tiring: I meant @label.
> 
> However, @title is actually an attribute that we haven't determined what it's
> used for in <track> and it can take any advisory information for the element.
> So, if all we need is a means to map descriptive information from in-band
> tracks to an IDL attribute, it may be of use?
> 
> So, for your use case, @kind would be fixed and set to the string "metadata",
> @label to whatever is in Ogg's "name" field, and @title could contain a
> concatenation of Ogg's "content-type" field and whatever remains of Ogg's
> "role" field that is not "metadata".

There isn't a @title in either the HTMLTrackElement or TextTrack interface; the
new string proposed in Comment 26 would suffice. Then, as you suggest:
@kind='metadata', @label=Ogg name. I still think it would be valuable to put
the Ogg title into the new string so @new_string=Ogg content_type + role +
title, The reason I think Ogg title is important is that it provides a way to
further differentiate the type of metadata content beyond the more generic
role.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 13 December 2011 23:34:27 UTC