This document captures technical requirements for [ttml-imsc1.1], the next revision of [ttml-imsc1.0.1].
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.
This specification is intended to be published as a Working Group Note.
This document was published by the Timed Text Working Group as a Working Group Note.
Comments regarding this document are welcome.
Please send them to
[ttml-imsc] at the start of your email's subject.
Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document was produced by a group operating under the W3C Patent Policy.
This document is governed by the 1 February 2018 W3C Process Document.
Deprecated. Permitted today, but expected to be prohibited in the future.
[ttml-imsc1.1] SHALL retain the scope of [ttml-imsc1.0.1] while adding the minimal set of features necessary to support current practices for worldwide subtitling and captioning delivery.
A valid [ttml-imsc1.0.1] Text Profile document SHALL be a valid [ttml-imsc1.1] Text Profile document, and a valid [ttml-imsc1.0.1] Image Profile document SHALL be a valid [ttml-imsc1.1] Image Profile document.
A [ttml-imsc1.1] presentation processor SHALL present a valid [ttml-imsc1.0.1] document as it would have been presented by an [ttml-imsc1.0.1] presentation processor.
#activeArea specified in [ttml-imsc1.0.1] SHALL be permitted in
A valid [ttml-imsc1.1] Document SHALL be a valid [TTML2] document.
Any [ttml-imsc1.0.1] extension that (i) is not one of the following and (ii) has an equivalent feature in [TTML2] SHALL be deprecated in [ttml-imsc1.1] and the corresponding [TTML2] feature permitted:
When an [ttml-imsc1.0.1] extension is deprecated and an equivalent [TTML2] feature is permitted, a document instance SHALL NOT use both the deprecated extension and the equivalent [TTML2] feature.
[ttml-imsc1.1] SHALL specify a mapping of each of its features to [HTML51] documents including support for [CSS-2017].
The fidelity of the mapping is not necessarily exact, but SHALL provide an acceptable result.
While [ttml-imsc1.1] defines both Image and Text Profiles, distinct Image and Text processors SHALL be defined such that an Image Processor is not required to accept Text Profile documents, and vice versa.
The profile resolution semantics and signaling specified in [TTML2] SHOULD be used whenever possible.
To support Japanese text as used in subtitles and captions, [ttml-imsc1.1] Text Profile SHALL support the following features.
|Ability to apply shear transformations on line areas, as a block, where a line area includes ruby base text, ruby annotations, and emphasis marks.|
To support stereoscopic presentations, both [ttml-imsc1.1] Text and Image profiles SHALL support the
#disparity feature specified in [TTML2].
To support HDR presentations, both [ttml-imsc1.1] Text and Image profiles SHALL support the
feature specified in [TTML2].
To simplify positioning, [ttml-imsc1.1] Text Profile SHALL support the
#position feature specified in
To simplify style authoring, [ttml-imsc1.1] Text Profile SHALL support the
#initial feature specified in
To support the edge styles required by the FCC, [ttml-imsc1.1] Text Profile SHALL support the
feature specified in [TTML2].
To allow straightforward sizing and length-dependent styling of fonts relative to the root container, [ttml-imsc1.1]
Text Profile SHOULD support the
#length-root-container-relative feature specified in [TTML2].