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

Re: Resolving TextTrackCue issues

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Sat, 7 Sep 2013 15:24:05 +1000
Message-ID: <CAHp8n2nQomYJJ56XpZOrhz5cisGjbWyjO5FxCWZTr_DRkC83pA@mail.gmail.com>
To: Glenn Adams <glenn@skynav.com>
Cc: Cyril Concolato <cyril.concolato@telecom-paristech.fr>, public-html <public-html@w3.org>
On Fri, Sep 6, 2013 at 2:43 AM, Glenn Adams <glenn@skynav.com> wrote:
>
>
> On Thu, Sep 5, 2013 at 8:19 AM, Silvia Pfeiffer <silviapfeiffer1@gmail.com>
> wrote:
>>
>> > Could we compared example codes?
>>
>> I can give you an example: if you have TTML in-band in MP4, it's
>> caption content, a browser has no parser and renderer for it, but can
>> in theory extract the cues from the MP4 encapsulation -
>>
>> - the WHATWG spec would either not expose them to JS at all, or expect
>> them to be exposed as VTTCue objects with @kind=metadata
>
>
> This would not work, since VTTCue interprets cues of kind metadata as WebVTT
> metadata text [1], which is most definitely incompatible with TTML that has
> been serialized into intermediate synchronic document instances, each of
> which is effectively an XML document.
>
> [1]
> https://dvcs.w3.org/hg/ttml/raw-file/tip/ttml2/spec/ttml2.html#extension-designations

So this is what we have to resolve. Why do you think VTTCue of
@kind=metadata can't contain TTML intermediate synchronic document
instances (i.e. a XML document) ?

Silvia.
Received on Saturday, 7 September 2013 05:24:52 UTC

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