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

Re: ISSUE-312 (forcedDisplay should be in ttm): forcedDisplay attribute is metadata so should be in ttm not tts namespace [TTML IMSC 1.0]

From: Glenn Adams <glenn@skynav.com>
Date: Sat, 24 May 2014 08:28:15 +0900
Message-ID: <CACQ=j+dHuf+=ZWR-aCD3XKbLOt7iaTEe8pnj6mvU=B_M2SiUwA@mail.gmail.com>
To: Michael Dolan <mdolan@newtbt.com>
Cc: Timed Text Working Group <public-tt@w3.org>
Agreed, this is not metadata. This feature needs discussion and proper
motivation.


On Thu, May 22, 2014 at 2:22 AM, Michael Dolan <mdolan@newtbt.com> wrote:

> This totally alters decoder processing.  Apparently it needs additional
> explanation, but it is not metadata.
>
> -----Original Message-----
> From: Timed Text Working Group Issue Tracker [mailto:sysbot+tracker@w3.org
> ]
> Sent: Wednesday, May 21, 2014 5:40 AM
> To: public-tt@w3.org
> Subject: ISSUE-312 (forcedDisplay should be in ttm): forcedDisplay
> attribute is metadata so should be in ttm not tts namespace [TTML IMSC 1.0]
>
> ISSUE-312 (forcedDisplay should be in ttm): forcedDisplay attribute is
> metadata so should be in ttm not tts namespace [TTML IMSC 1.0]
>
> http://www.w3.org/AudioVideo/TT/tracker/issues/312
>
> Raised by: Nigel Megitt
> On product: TTML IMSC 1.0
>
> The description of tts:forcedDisplay [1] does not define any change in
> processing behaviour so it appears to be metadata and should therefore be
> moved to the ttm: namespace.
>
> Incidentally the note in this section references "forcedDisplayMode" which
> is not defined anywhere.
>
> [1] http://www.w3.org/TR/ttml-imsc1/#tts-forcedDisplay
>
>
>
>
>
Received on Friday, 23 May 2014 23:29:03 UTC

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