Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should be a subset of IMSC1 #14

Open
plehegar opened this issue Nov 4, 2015 · 1 comment
Open

Should be a subset of IMSC1 #14

plehegar opened this issue Nov 4, 2015 · 1 comment

Comments

@plehegar
Copy link
Member

plehegar commented Nov 4, 2015

The profile/authoring guidelines specified in the document should be a subset of IMSC1:

  • it helps narrow down the set of features to be supported, e.g. no need to support #markerMode
  • it simplifies the job of implementers who are already supporting IMSC1

Features have been deemed necessary but are not in IMSC1 should be considered for addition there.

(raised by Pierre-Anthony Lemieux on 2015-09-23)
From tracker issue http://www.w3.org/AudioVideo/TT/tracker/issues/446

@andreastai
Copy link

The TVTT "profile" is a subset of IMSC 1 and therefore, if this is taken as a start, should simplify the mapping process for implementers considerably. With a TVTT document you just have to read the section 2.3 which explains the mapping from TVTT to WebVTT.

If the source document does not comply in certain areas with the TVTT document you just can read selectively parts of the pre-processing section 2.2.

It has been discussed between the authors of the document to restrict from the start the complete mapping to a certain profile (e.g. IMSC 1). But as a result of the discussion this approach has been found to be to constrained and not sufficient for current operational mapping requirements. There are TTML documents that do not comply yet with IMSC 1 but nevertheless needed to be mapped to WebVTT.

It should also be taken into account that the TVTT profile primarily fulfills a didactical purpose to make the complexity of the mapping process manageable and to “distribute” it over several steps. These steps may be used by an implemented mapping algorithm but dependent of context and scope imoplemented processing may be different (as long as the results are the same).

Of course the TVTT profile may also be taken as a start for authoring but this very much depends if the author is willing to take out features that are not supported by WebVTT.

It may be helpful to add a part to the document and note that the TVTT profile is already close to or subset of EBU-TT-D and IMSC 1 so it makes mapping considerably easier if they use these two profiles.

(Andreas Tai, 18 Oct 2015
From tracker issue http://www.w3.org/AudioVideo/TT/tracker/issues/446)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants