Re: TextTrack API changes

On 6/4/13 2:00 AM, "Silvia Pfeiffer" <silviapfeiffer1@gmail.com> wrote:

>On Tue, May 14, 2013 at 6:06 AM, Bob Lund <B.Lund@cablelabs.com> wrote:
>>
>>
>> On 5/12/13 8:47 PM, "Silvia Pfeiffer" <silviapfeiffer1@gmail.com> wrote:
>>
>>>On Mon, May 13, 2013 at 5:00 AM, Glenn Adams <glenn@skynav.com> wrote:
>>>>
>>>> First, I'm talking about the Media Type of a text track resource here,
>>>>not a specific @kind (usage) of a text track resource. For example,
>>>>"text/vtt",
>>>> "application/ttml+xml", "application/x-mpeg2-psi" [I just made that
>>>>up], etc.
>>>
>>>OK, this is taking the discussion into a completely different and
>>>unrelated direction, because we were discussing TextTrackCue and not
>>>TextTrack types. Also, the changes you are proposing below are not
>>>possible because <track> is an empty element and we are not going to
>>>break backwards compatibility on the markup. But I'll entertain the
>>>discussion of the use cases that they imply rather than the particular
>>>specification proposal.
>>>
>>>I'm still curious about the one question I had before: are you or
>>>anyone else aware of any implementations of the
>>>inBandMetadataTrackDispatchType attribute? Since it's not even used in
>>>http://www.cablelabs.com/specifications/CL-SP-HTML5-MAP-I02-120510.pdf
>>>but instead @label is used, I don't know if it's satisfying its use
>>>case.
>>
>> This document was written before the definition of the dispatch type
>> attribute. The spec will be rev'd to make use of this new attribute.
>
>Let's make sure that we have the <track> element in better shape
>before you make changes to that spec, so it can be adapted
>appropriately for all <track> aspects.

Thanks for the heads-up. When do you think this will be?

>
>Regards,
>Silvia.

Received on Tuesday, 4 June 2013 15:21:43 UTC