W3C home > Mailing lists > Public > public-tt@w3.org > September 2014

Re: {minutes} Geneva F2F day 1 16/09/2014

From: Glenn Adams <glenn@skynav.com>
Date: Mon, 22 Sep 2014 07:39:59 -0600
Message-ID: <CACQ=j+fGreOsusWYwaBrcDVQC-q80m5E+x7gC4RBNoMZ63kmZA@mail.gmail.com>
To: Simon Pieters <simonp@opera.com>
Cc: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Nigel Megitt <nigel.megitt@bbc.co.uk>, TTWG <public-tt@w3.org>, "public-texttracks@w3.org" <public-texttracks@w3.org>
On Mon, Sep 22, 2014 at 5:31 AM, Simon Pieters <simonp@opera.com> wrote:

> On Sun, 21 Sep 2014 02:41:47 +0200, Silvia Pfeiffer <
> silviapfeiffer1@gmail.com> wrote:
>
>  Interesting. How does this work in the context of browsers?
>>
>
> Browsers don't support xml:id and AFAIK don't want to. Having more than
> one attribute for IDness increases complexity all over the place and
> doesn't give any benefit.
>
> Browsers have also always allowed any value in id="" (also in XML). So the
> spec change in HTML was just aligning with reality.


For purposes of performing TTML to HTML mapping, xml:id may be mapped to
id. For purposes of performing VTT to TTML mapping, id values will need to
be munged to become legal ID syntax (from XML perspective). Other
considerations aren't particularly relevant to this discussion.


>
>
> --
> Simon Pieters
> Opera Software
>
Received on Monday, 22 September 2014 13:40:46 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 5 October 2017 18:24:18 UTC