W3C home > Mailing lists > Public > public-html@w3.org > June 2013

Re: TextTrack API changes

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Wed, 5 Jun 2013 11:23:16 +1000
Message-ID: <CAHp8n2=COgO+jzbDSZ+MXrBxPWC-kELa2VtSAJRR8WDF2bs+1Q@mail.gmail.com>
To: Bob Lund <B.Lund@cablelabs.com>
Cc: Glenn Adams <glenn@skynav.com>, Simon Pieters <simonp@opera.com>, public-html <public-html@w3.org>, "Jerry Smith, (WINDOWS)" <jdsmith@microsoft.com>, "Mark Vickers @ Comcast" <mark_vickers@cable.comcast.com>
On Wed, Jun 5, 2013 at 1:20 AM, Bob Lund <B.Lund@cablelabs.com> wrote:
> 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,
>>>>> "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
>>>>but instead @label is used, I don't know if it's satisfying its use
>>> 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?

I've started working on it now ... let's try together and resolve this asap.
I'll be sending emails soon.

Thanks for your patience,
Received on Wednesday, 5 June 2013 01:24:04 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:46:03 UTC