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

Re: TTML2 backwards compatibility with TTML1

From: Nigel Megitt <nigel.megitt@bbc.co.uk>
Date: Wed, 31 May 2017 15:25:34 +0000
To: Michael Dolan <mike@dolan.tv>, "public-tt@w3.org" <public-tt@w3.org>
Message-ID: <D5549E5C.40D73%nigel.megitt@bbc.co.uk>
Hi Mike,

The link you provided is an IMSC issue not a TTML2 issue. I'm a bit confused – perhaps there's another example where a TTML2 constraint is being introduced that would mean a TTML2 processor would not process a TTML1 document correctly?

Kind regards,


From: Michael Dolan <mike@dolan.tv<mailto:mike@dolan.tv>>
Date: Wednesday, 31 May 2017 at 16:11
To: "public-tt@w3.org<mailto:public-tt@w3.org>" <public-tt@w3.org<mailto:public-tt@w3.org>>
Subject: TTML2 backwards compatibility with TTML1
Resent-From: <public-tt@w3.org<mailto:public-tt@w3.org>>
Resent-Date: Wednesday, 31 May 2017 at 16:12

I thought we had a (perhaps implicit and unspoken) requirement that TTML2 would be backwards compatible with TTML1.  That is, all conformant TTML1 instance documents would also be conformant TTML2 instance documents.

However, we are making decisions that are at odds with the above, e.g. this week’s change to constrain origin and extent in issue 239 and its PR: https://github.com/w3c/imsc/pull/240  There are other examples.

I think we need to all be on the same page about the above requirement.

My personal view is that unless something is really broken and unusable/untestable from TTML1, that this requirement should hold.

Perhaps we can discuss this tomorrow before committing any more changes that are at odds with it?


Michael A DOLAN
TBT, Inc;  PO Box 190
Del Mar, CA 92014
Received on Wednesday, 31 May 2017 15:26:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:44:11 UTC