• 回复@老老保老张工:那咋分配呢? 2019-11-17
  • 工信部:鼓励婴幼儿配方乳企质量安全追溯体系建设 2019-11-17
  • 第527期:过年该送健康礼,几点秘籍教给你 2019-11-11
  • 竹编:缝隙里的乡愁文章中国国家地理网 2019-11-11
  • 感触名家笔下的端午文化 吃香粽原来可以这样"文艺" 2019-11-06
  • 人民日报召开习近平新闻思想理论研讨会 2019-10-31
  • 鹏城展翅再高飞(壮阔东方潮 奋进新时代——庆祝改革开放40年) 2019-10-31
  • 财经 —频道 春城壹网 七彩云南 一网天下 2019-10-16
  • 酒后躺车内休息也属于酒驾? 交巡警告诉你这些行为都是酒驾 2019-10-09
  • 新疆阿拉山口口岸严防有害生物入境 2019-10-09
  • 香港多地举办龙舟赛共庆端午节 2019-10-02
  • 河北一保时捷车主疑遭枪击 警方悬赏9万元通缉 2019-10-02
  • 【理上网来·喜迎十九大】党的强军思想指引强军事业 2019-09-24
  • 聚焦机构改革:新部门接连挂牌 快速进入角色 2019-09-11
  • 人民网评:用法律致敬英雄烈士 2019-09-11
  • 下载腾讯麻将游戏:TTML Profiles for Internet Media Subtitles and Captions 1.2

    W3C First Public Working Draft

    This version:
    //www.vfdks.tw/TR/2019/WD-ttml-imsc1.2-20191128/
    Latest published version:
    //www.vfdks.tw/TR/ttml-imsc1.2/
    Latest editor's draft:
    https://w3c.github.io/imsc/imsc1/spec/ttml-ww-profiles.html
    Editor:
    Participate:
    GitHub w3c/imsc
    File a bug
    Commit history
    Pull requests
    Latest IMSC1 recommendation:
    //www.vfdks.tw/TR/ttml-imsc1/

    Abstract

    This specification defines two profiles of [ttml2]: a text-only profile and an image-only profile. These profiles are intended to be used across subtitle and caption delivery applications worldwide, thereby simplifying interoperability, consistent rendering and conversion to other subtitling and captioning formats.

    This specification improves on [ttml-imsc1.1] by supporting contemporary practices, while retaining compatibility with [ttml-imsc1.1] documents. Relative to [ttml-imsc1.1], any addition or deprecation of features are summarized at Appendix § L. Summary of substantive changes.

    It is feasible to create documents that simultaneously conform to both [ttml10-sdp-us] and the text-only profile.

    The specification defines extensions to [ttml2], as well as incorporates extensions specified in [SMPTE2052-1] and [EBU-TT-D].

    Both profiles are based on [SUBM].

    Status of This Document

    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 //www.vfdks.tw/TR/.

    This document was published by the Timed Text Working Group as a First Public Working Draft. This document is intended to become a W3C Recommendation.

    GitHub Issues are preferred for discussion of this specification. Alternatively, you can send comments to our mailing list. Please send them to [email protected] (archives) with [imsc] at the start of your email's subject .

    Publication as a First Public Working Draft 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. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

    This document is governed by the 1 March 2019 W3C Process Document.

    1. Scope

    This specification defines two profiles of [ttml2]: a text-only profile and an image-only profile. These profiles are intended for subtitle and caption delivery worldwide, including dialog language translation, content description, captions for deaf and hard of hearing, etc.

    This specification maintains the scope of [ttml-imsc1.1] while adding the minimal set of features necessary to support contemporary practices for worldwide subtitling and captioning delivery.

    The specification is designed such that:

    The Text Profile is a syntactic superset of [ttml10-sdp-us], and a document can simultaneously conform to both [ttml10-sdp-us] and the Text Profile.

    2. Documentation Conventions

    This specification uses the same conventions as [ttml2] for the specification of parameter attributes, styling attributes and metadata elements. In particular:

    This specification uses Feature and Extension designations as defined in Appendices E.1 and F.1 at [ttml2]:

    If the name of an element referenced in this specification is not namespace qualified, then the TT namespace applies (see § 7.3 Namespaces.)

    3. Terms and Definitions

    Associated region. The region element associated with an element according to the [associate region] procedure defined in [ttml2].

    Character Information Item. See Section 2.2 at [ttml2].

    Document Instance. See Section 2.2 at [ttml2].

    Default Processor Profile. As defined in [ttml2].

    Default Region. See Section 9.3.1 at [ttml2].

    Extension. See Section 2.2 at [ttml2].

    External Data Resource. See Section 2.2 at [ttml2].

    Feature. See Section 2.2 at [ttml2].

    Intermediate Synchronic Document. See Section 9.3.2 at [ttml2].

    Document Interchange Context. See Section 2.2 at [ttml2].

    Document Processing Context. As defined in [ttml2].

    Effective Processor Profile. As defined in [ttml2].

    Font Resource. As defined in [ttml2].

    Image Profile transformation processor. A transformation processor that conforms to the Image Profile.

    Image Profile presentation processor. A presentation processor that conforms to the Image Profile.

    Linear White-Space. See Section 2.3 at [ttml2].

    Override Content Profile. As defined in [ttml2].

    Processor. Either a Presentation processor or a Transformation processor.

    Presentation processor. See Section 2.2 at [ttml2].

    Specified Value. As defined in [ttml2].

    Transformation processor. See Section 2.2 at [ttml2].

    Processor Profile. As defined in [ttml2].

    Related Media Object. See Section 2.2 at [ttml2].

    Related Video Object. A Related Media Object that consists of a sequence of image frames, each a rectangular array of pixels.

    Root Container Region. See Section 2.2 at [ttml2].

    Text Alternative. As defined in [WCAG21].

    Text Profile transformation processor. A transformation processor that conforms to the Text Profile.

    Text Profile presentation processor. A presentation processor that conforms to the Text Profile.

    4. Conformance

    As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.

    The key words MAY, SHALL, SHALL NOT, SHOULD, and SHOULD NOT in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

    A Document Instance that conforms to a profile defined herein:

    Note

    A Document Instance, by definition, satisfies the requirements of Section 3.1 at [ttml2], and hence a Document Instance that conforms to a profile defined herein is also a conforming TTML1 Document Instance.

    A presentation processor that conforms to a profile defined in this specification:

    A transformation processor that conforms to a profile defined in this specification:

    A Feature or Extension currently designated permitted-deprecated is intended to be designated as optional or prohibited in future versions of this specification.

    Note

    [ttml2] makes a distinction between a presentation processor, whose purpose is to present a Document Instance, and transformation processor, whose purpose is to process a Document Instance without presenting it. A renderer embedded in the media pipeline of a mobile device is an example of a presentation processor, whereas a validator is an example of a transformation processor.

    Note

    A processor that conforms to one profile defined in this specification is not required to conform to the other profile. For convenience, the terms Image Profile transformation processor, Text Profile transformation processor, Image Profile presentation processor, and Text Profile presentation processor are defined.

    Note

    The use of the term presentation processor (transformation processor) within this specification does not imply conformance to the DFXP Presentation Profile (DFXP Transformation Profile) specified in [ttml2]. In other words, it is not considered an error for a presentation processor (transformation processor) to conform to a profile defined in this specification without also conforming to the DFXP Presentation Profile (DFXP Transformation Profile).

    Note

    This specification does not specify presentation processor or transformation processor behavior when processing or transforming a non-conformant Document Instance.

    Note

    The permitted and prohibited dispositions do not refer to the specification of a ttp:feature or ttp:extension element as being permitted or prohibited within a ttp:profile element.

    5. Profiles

    5.1 General

    This specification defines two profiles of [ttml2]: the Text Profile and the Image Profile. In the Text Profile, timed text is expressed using Unicode text exclusively, whereas, in the Image Profile, timed text is expressed using bitmap images exclusively. The clear distinction between the two profiles reduces authoring and processing complexity. For example, it allows systems to unambiguously specify whether text- and/or image-based timed text is permitted.

    Note

    Image-based timed text images can be used in scenarios where the required text rendering functionality is not available, for example if the required fonts can not be distributed, or if the receiving processor has insufficient computing resources to present text while displaying video. They can also be used to achieve a visual effect that is beyond the capabilities of TTML, e.g. illuminated letters.

    Notwithstanding special cases, e.g. a Document Instance that contains no p, span, br, image element and no smpte:backgroundImage attribute, it is generally not possible to construct a Document Instance that conforms to the Text Profile and Image Profile simultaneously, and it is not possible to construct a Document Instance that results in the presentation of both text data and image data.

    In applications that require subtitle/caption content in image form to be simultaneously available in text form, two distinct Document Instances, one conforming to the Text Profile and the other conforming to the Image Profile, SHOULD be offered. In addition, the Text Profile Document Instance SHOULD be associated with the Image Profile Document Instance such that, when image content is encountered, assistive technologies have access to its corresponding text form. The method by which this association is made is left to each application.

    Note

    The altText named metadata item also allows text equivalent string to be associated with an image, e.g. to support indexation of the content and also facilitate quality checking of the document during authoring.

    Annex § D.1 WCAG Considerations specifically discusses this specification in the context of the [WCAG21] guidelines.

    5.2 Text Profile

    The Text Profile consists of Sections § 6. Supported Features and Extensions, § 7. Common Provisions and § 8. Text Profile Provisions.

    5.3 Image Profile

    The Image Profile consists of Sections § 6. Supported Features and Extensions, § 7. Common Provisions and § 9. Image Profile Provisions.

    5.4 Profile Resolution Semantics

    5.4.1 General

    The Profile Semantics specified in [ttml2] apply.

    Note

    The default value of prohibited attributes, e.g. ttp:contentProfileCombination, applies.

    The Text Profile processor profile includes all of the features required by each of the following processor profiles:

    The Image Profile processor profile includes all of the features required by each of the following processor profiles:

    5.4.2 Override

    If one or more ebuttm:conformsToStandard elements, as specified in [EBU-TT-M], are set to any of the following designators, then the override content profile SHALL be set to the profile associated with any one of the matching designators:

    6. Supported Features and Extensions

    See § 4. Conformance for a definition of permitted, prohibited, optional and permitted-deprecated.

    Feature or Extension Text Profile Disposition Image Profile Disposition
    Relative to the TT Feature namespace
    All features specified in [ttml2] are prohibited unless specified otherwise below
    #animation permitted
    #animation-version-2 Partially supported via #animation.
    #background Partially supported via #backgroundColor.
    #backgroundColor permitted Partially supported via #backgroundColor-region and #backgroundColor-block.
    #backgroundColor-block permitted
    #backgroundColor-inline permitted prohibited
    #backgroundColor-region permitted
    #base permitted
    #base-version-2 Partially supported via #base.
    #bidi permitted prohibited
    #bidi-version-2 Partially supported via #bidi and #unicodeBidi-version-2. prohibited
    #cellResolution permitted
    #color permitted
    Section § 8.5.1 #color specifies additional constraints.
    prohibited
    #content permitted
    #contentProfiles permitted
    #core permitted
    #direction permitted prohibited
    #disparity permitted
    #display permitted
    #display-block permitted
    #display-inline permitted
    #display-region permitted
    #display-version-2 Partially supported via #display, #display-block, #display-inline, and #display-region.
    #displayAlign permitted prohibited
    #displayAlign-region permitted prohibited
    #displayAlign-relative permitted prohibited
    #displayAlign-version-2 Partially supported via #displayAlign-region, and #displayAlign-relative. prohibited
    #displayAspectRatio permitted
    Section § 7.12.5 #displayAspectRatio specifies additional constraints.
    #embedded-audio prohibited
    #embedded-data is however partially supported.
    prohibited.
    #embedded-content Partially supported via #embedded-font. prohibited
    #embedded-data Partially supported via #resources and #source. prohibited
    #embedded-font Partially supported via #embedded-data and #font. prohibited
    #embedded-image prohibited
    #embedded-data is however partially supported.
    Partially supported via #image.
    #extent permitted
    #extent-full-version-2 Partially supported via #extent-version-2.
    #extent-image prohibited permitted
    Section § 9.4.4 TTML #image Feature specifies additional constraints.
    #extent-length permitted
    #extent-length-version-2 permitted See the disposition of #length-version-2.
    #extent-region Partially supported via #extent-length.
    Section § 8.5.2 #extent-region specifies additional constraints.
    Partially supported via #extent-length.
    Section § 9.4.2 #extent-region specifies additional constraints.
    #extent-region-version-2 Partially supported via #extent-region.
    #extent-root Partially supported via #extent-length.
    Section § 7.12.6 #extent-root specifies additional constraints.
    #extent-root-version-2 Partially supported via #extent-root.
    #extent-version-2 Partially supported via #extent and #extent-region-version-2. Partially supported via #extent, #extent-image, and #extent-region-version-2.
    #font permitted
    Section § 8.5.3 #font and #source specifies additional constraints.
    prohibited
    #fontFamily permitted
    Section § 8.5.5 #fontFamily specifies additional constraints.
    prohibited
    #fontFamily-generic permitted
    Section § 8.5.4 #fontFamily-generic specifies additional constraints.
    prohibited
    #fontFamily-non-generic permitted prohibited
    #fontSize Partially supported via #fontSize-isomorphic. prohibited
    #fontSize-isomorphic permitted prohibited
    #fontStyle permitted prohibited
    #fontStyle-italic permitted prohibited
    #fontStyle-oblique permitted prohibited
    #fontWeight permitted prohibited
    #fontWeight-bold permitted prohibited
    #frameRate permitted
    Section § 7.12.7 #frameRate specifies additional constraints.
    #frameRateMultiplier permitted
    #image prohibited permitted
    Section § 9.4.4 TTML #image Feature specifies additional constraints.
    #image-png prohibited permitted
    Section § 9.3 Image Resources specifies additional constraints.
    #initial permitted prohibited
    #layout permitted
    Section § 7.12.1 Region specifies additional constraints.
    #length permitted Partially supported via #length-integer, #length-real, #length-positive, #length-negative, #length-cell, #length-percentage, and #length-pixel.
    #length-cell permitted
    Section § 7.12.8 #length-cell specifies additional constraints.
    #length-em permitted prohibited
    #length-integer permitted
    #length-negative permitted
    Section § 8.5.6 #length-negative specifies additional constraints.
    permitted
    Section § 9.4.3 #length-negative specifies additional constraints.
    #length-percentage permitted
    #length-pixel permitted
    #length-positive permitted
    #length-real permitted
    #length-root-container-relative permitted
    Section § 7.12.9 #length-root-container-relative specifies additional constraints.
    prohibited
    #length-version-2 permitted Partially supported via #length.
    #lineBreak-uax14

    The processor SHALL implement the #lineBreak-uax14 feature.

    No processor requirement is specified.
    #lineHeight permitted
    Section § 8.5.7 #lineHeight specifies additional constraints.
    prohibited
    #luminanceGain permitted
    #metadata permitted
    #metadata-item permitted
    Section § 7.12.2 altText named metadata item specifies additional constraints.
    #metadata-version-2 permitted
    #nested-div permitted prohibited
    #nested-span permitted prohibited
    #opacity permitted
    #opacity-region permitted
    #opacity-version-2 Partially supported via #opacity.
    #origin permitted
    Section § 8.5.8 #origin specifies additional constraints.
    permitted
    #overflow permitted
    #overflow-visible permitted
    #padding permitted prohibited
    #padding-1 permitted prohibited
    #padding-2 permitted prohibited
    #padding-3 permitted prohibited
    #padding-4 permitted prohibited
    #padding-region permitted prohibited
    #padding-version-2 Partially supported via #padding, #padding-1, #padding-2, #padding-3, #padding-4, and #padding-region prohibited
    #position permitted
    Section § 8.5.9 #position specify additional constraints.
    prohibited
    #presentation permitted
    #presentation-version-2 Partially supported via #presentation and #profile-version-2
    #profile permitted
    #profile-full-version-2 Partially supported via #contentProfiles, #profile, and #profile-version-2.
    #profile-version-2 Partially supported via #contentProfiles, and #profile.
    #region-timing permitted
    #resources permitted
    Section § 8.5.10 #resources specify additional constraints.
    prohibited
    #ruby permitted prohibited
    #ruby-full Partially supported via #ruby, #rubyAlign, #rubyPosition, and #rubyReserve. prohibited
    #rubyAlign Partially supported via #rubyAlign-minimal. prohibited
    #rubyAlign-minimal permitted
    Section § 8.5.11 #rubyAlign specifies additional constraints.
    prohibited
    #rubyPosition permitted prohibited
    #rubyReserve permitted prohibited
    #set permitted
    #shear permitted prohibited
    #showBackground permitted
    #source permitted
    Section § 8.5.3 #font and #source specify additional constraints.
    prohibited
    #structure permitted
    #styling permitted
    #styling-chained permitted
    #styling-inheritance-content permitted
    #styling-inheritance-region permitted
    #styling-inline permitted
    #styling-nested permitted
    #styling-referential permitted
    #textAlign permitted prohibited
    #textAlign-absolute permitted prohibited
    #textAlign-relative permitted prohibited
    #textAlign-version-2 Partially supported via #textAlign, #textAlign-relative, and #textAlign-absolute. prohibited
    #textCombine permitted prohibited
    #textDecoration permitted prohibited
    #textDecoration-over permitted prohibited
    #textDecoration-through permitted prohibited
    #textDecoration-under permitted prohibited
    #textEmphasis Partially supported via #textEmphasis-minimal. prohibited
    #textEmphasis-minimal permitted prohibited
    #textOutline Partially supported via #textOutline-unblurred. prohibited
    #textOutline-unblurred permitted
    Section § 8.5.12 #textOutline-unblurred specifies additional constraints.
    prohibited
    #textShadow permitted
    Section § 8.5.13 #textShadow specifies additional constraints.
    prohibited
    #tickRate permitted
    Section § 7.12.10 #tickRate specifies additional constraints.
    #timeBase-media permitted
    #timeContainer permitted
    #time-clock permitted
    #time-clock-with-frames permitted
    #time-offset permitted
    #time-offset-with-frames permitted
    #time-offset-with-ticks permitted
    #timing permitted
    Section § 7.12.13 #timing specifies additional constraints.
    #transformation permitted
    #transformation-version-2 Partially supported via #transformation and #profile-version-2.
    #unicodeBidi permitted prohibited
    #unicodeBidi-version-2 Partially supported via #unicodeBidi. prohibited
    #visibility permitted Partially supported via #visibility-block and #visibility-region.
    #visibility-block permitted
    #visibility-image prohibited permitted
    #visibility-inline permitted prohibited
    #visibility-region permitted
    #visibility-version-2 Partially supported via #visibility. Partially supported via #visibility and #visibility-image.
    #wrapOption permitted prohibited
    #writingMode permitted Partially supported via #writingMode-horizontal.
    #writingMode-horizontal permitted Partially supported via #writingMode-horizontal-lr and #writingMode-horizontal-rl.
    #writingMode-horizontal-lr permitted
    #writingMode-horizontal-rl permitted permitted-deprecated
    #writingMode-vertical permitted prohibited
    #zIndex permitted-deprecated
    Relative to the SMPTE-TT Extension Namespace
    #image prohibited permitted-deprecated
    Section § 9.4.5 SMPTE #image Extension specifies additional constraints.
    Relative to the IMSC Extension namespace
    #activeArea permitted
    #altText permitted-deprecated
    Section § 7.12.3 #altText specifies additional constraints.
    #aspectRatio permitted-deprecated
    Section § 7.12.4 #aspectRatio specifies additional constraints.
    #fillLineGap permitted prohibited
    #forcedDisplay permitted
    #linePadding permitted
    Section § 8.5.14 ebutts:linePadding specifies additional constraints.
    permitted-deprecated
    #multiRowAlign permitted
    Section § 8.5.15 ebutts:multiRowAlign specifies additional constraints.
    permitted-deprecated
    #progressivelyDecodable permitted-deprecated

    7. Common Provisions

    7.1 Document Encoding

    A Document Instance SHALL be concretely encoded as a well-formed XML 1.0 [xml] document using the UTF-8 character encoding as specified in [UNICODE].

    The resulting [xml] document SHOULD NOT contain any of the following physical structures:

    Note

    These physical structures are intended to be prohibited in future versions of this specification.

    Note

    The resulting [xml] document can contain character references, and entity references to predefined entities.

    7.2 Foreign Element and Attributes

    A Document Instance MAY contain elements and attributes that are neither specifically permitted nor forbidden by a profile.

    A transformation processor SHOULD preserve such elements or attributes whenever possible.

    Note

    Document Instances remain subject to the content conformance requirements specified at Section 3.1 of [ttml2]. In particular, a Document Instance can contain elements and attributes not in any TT namespace, i.e. in foreign namespaces, since such elements and attributes are pruned by the algorithm at Section 4 of [ttml2] prior to evaluating content conformance.

    Note
    For validation purposes it is good practice to define and use a content specification for all foreign namespace elements and attributes used within a Document Instance.

    7.3 Namespaces

    The following namespaces (see [xml-names]) are used in this specification:

    Name Prefix Value Defining Specification
    XML xml //www.vfdks.tw/XML/1998/namespace [xml-names]
    TT tt //www.vfdks.tw/ns/ttml [ttml2]
    TT Parameter ttp //www.vfdks.tw/ns/ttml#parameter [ttml2]
    TT Styling tts //www.vfdks.tw/ns/ttml#styling [ttml2]
    TT Feature none //www.vfdks.tw/ns/ttml/feature/ [ttml2]
    SMPTE-TT Extension smpte //www.smpte-ra.org/schemas/2052-1/2010/smpte-tt [SMPTE2052-1]
    EBU-TT Styling ebutts urn:ebu:tt:style [EBU-TT-D]
    EBU-TT Metadata ebuttm urn:ebu:tt:metadata [EBU-TT-D]
    IMSC Styling itts //www.vfdks.tw/ns/ttml/profile/imsc1#styling This specification
    IMSC Parameter ittp //www.vfdks.tw/ns/ttml/profile/imsc1#parameter This specification
    IMSC Metadata ittm //www.vfdks.tw/ns/ttml/profile/imsc1#metadata This specification
    IMSC Extension none //www.vfdks.tw/ns/ttml/profile/imsc1/extension/ This specification
    IMSC 1.2 Text Profile Designator none See Section § 8.1 Profile Designator
    IMSC 1.2 Image Profile Designator none See Section § 9.1 Profile Designator

    The namespace prefix values defined above are for convenience and Document Instances MAY use any prefix value that conforms to [xml-names].

    The namespaces defined by this specification are mutable [namespaceState]; all undefined names in these namespaces are reserved for future standardization by the W3C.

    7.4 Overflow

    A Document Instance SHOULD be authored assuming strict clipping of content that falls out of region areas, regardless of the computed value of tts:overflow for the region.

    Note

    As specified in [ttml2], tts:overflow has no effect on the extent of the region, and hence the total normalized drawing area S(En) at § 10.3 Paint Regions.

    7.6 Synchronization

    Each intermediate synchronic document of the Document Instance is intended to be displayed on a specific frame and removed on a specific frame of the Related Video Object.

    When mapping a media time expression M to a frame F of a Related Video Object, e.g. for the purpose of rendering a Document Instance onto the Related Video Object, the presentation processor SHALL map M to the frame F with the presentation time that is the closest to, but not less, than M.

    Note

    In typical scenario, the same video program (the Related Video Object) will be used for Document Instance authoring, delivery and user playback. The mapping from media time expression to Related Video Object above allows the author to precisely associate subtitle video content with video frames, e.g. around scene transitions. In circumstances where the video program is downsampled during delivery, the application can specify that, at playback, the relative video object be considered the delivered video program upsampled to is original rate, thereby allowing subtitle content to be rendered at the same temporal locations it was authored.

    7.8 Extension Vocabulary

    7.8.1 ittp:aspectRatio

    The #aspectRatio feature is designated as permitted-deprecated in the profiles defined by this specification. The #displayAspectRatio feature provides equivalent semantics.

    The ittp:aspectRatio attributes allows authorial control of the mapping of the Root Container Region of a Document Instance to each image frame of the Related Video Object.

    If present, the ittp:aspectRatio attribute SHALL conform to the following syntax:

    ittp:aspectRatio
      : numerator denominator          // with int(numerator) != 0 and int(denominator) != 0
                                       // where int(s) parses string s as a decimal integer.
    
    numerator | denominator
      : <digit>+                       // no linear white-space is implied or permitted
                                       // between each <digit> token

    An ittp:aspectRatio attribute is considered to be significant only when specified on the tt element.

    If specified on the tt element, the ittp:aspectRatio attribute specifies the display aspect ratio of the Root Container Region. If not specified, then the display aspect ratio of the Root Container Region is determined according to Appendix H of [ttml2].

    7.8.2 ittp:progressivelyDecodable

    The #progressivelyDecodable feature is designated as permitted-deprecated in the profiles defined by this specification.

    A progressively decodable Document Instance is structured to facilitate presentation before the document is received in its entirety, and can be identified using ittp:progressivelyDecodable attribute.

    A progressively decodable Document Instance is a Document Instance that conforms to the following:

    1. no attribute or element of the TTML timing vocabulary is present within the head element;
    2. given two intermediate synchronic documents A and B of the Document Instance, with start times TA and TB, respectively, TA is not greater than TB if A includes a p element that lexically precedes any p element that B includes;
    3. no attribute of the TTML timing vocabulary is present on a descendant element of p; and
    4. no element E1 explicitly references another element E2 where the opening tag of E2 is lexically subsequent to the opening tag of E1.

    If present, the ittp:progressivelyDecodable attribute SHALL conform to the following syntax:

    ittp:progressivelyDecodable
      : "true"
      | "false"

    An ittp:progressivelyDecodable attribute is considered to be significant only when specified on the tt element.

    If not specified, the value of ittp:progressivelyDecodable SHALL be considered to be equal to "false".

    A Document Instance for which the computed value of ittp:progressivelyDecodable is "true" SHALL be a progressively decodable Document Instance.

    A Document Instance for which the computed value of ittp:progressivelyDecodable is "false" is neither asserted to be a progressively decodable Document Instance nor asserted not to be a progressively decodable Document Instance.

    <tt
      xmlns="//www.vfdks.tw/ns/ttml"
      xmlns:ttm="//www.vfdks.tw/ns/ttml#metadata" 
      xmlns:tts="//www.vfdks.tw/ns/ttml#styling"
      xmlns:ttp="//www.vfdks.tw/ns/ttml#parameter" 
      xmlns:ittp="//www.vfdks.tw/ns/ttml/profile/imsc1#parameter"
      ittp:progressivelyDecodable="true"
      ttp:profile="..."
     >
     ...
    </tt>
    Note

    [ttml2] specifies explicitly referencing of elements identified using xml:id in the following circumstances:

    • an element in body referencing region elements. In this case, Requirement 4 above is always satisfied.
    • an element in body referencing style elements. In this case, Requirement 4 above is always satisfied.
    • a region element referencing style elements. In this case, Requirement 4 above is always satisfied.
    • a style element referencing other style elements. In this case, Requirement 4 provides an optimization of style element ordering within the head element.
    • a ttm:actor element referencing a ttm:agent element. In this case, Requirement 4 provides optimization of metadata elements ordering within the document.
    • a content element referencing ttm:agent elements using the ttm:agent attribute. In this case, Requirement 4 provides optimization of metadata elements ordering within the document.

    7.8.3 itts:forcedDisplay

    itts:forcedDisplay can be used to hide content whose computed value of tts:visibility is "visible" when the processor has been configured to do so via the application parameter displayForcedOnlyMode.

    If and only if the value of displayForcedOnlyMode is "true", a content element with a itts:forcedDisplay computed value of "false" SHALL NOT produce any visible rendering, regardless of the computed value of tts:visibility.

    The itts:forcedDisplay attribute has no effect on content layout or composition, but merely determines whether composed content is visible or not.

    The itts:forcedDisplay attribute SHALL conform to the following:

    Values: false | true
    Initial: false
    Applies to: body, div, p, region, span
    Inherited: yes
    Percentages: N/A
    Animatable: discrete

    Annex § C. Forced content illustrates the use of itts:forcedDisplay in an application in which a single document contains both hard of hearing captions and translated foreign language subtitles, using itts:forcedDisplay to display translation subtitles always, independently of whether the hard of hearing captions are displayed or hidden.

    The presentation processor SHALL accept an optional boolean parameter called displayForcedOnlyMode, whose value MAY be set by a context external to the presentation processor. If not set, the value of displayForcedOnlyMode SHALL be assumed to be equal to "false".

    The algorithm for setting the displayForcedOnlyMode parameter based on the circumstances under which the Document Instance is presented is left to the application.

    <?xml version="1.0" encoding="UTF-8"?>
    <tt xml:lang="en"
        xmlns="//www.vfdks.tw/ns/ttml"
        xmlns:ttm="//www.vfdks.tw/ns/ttml#metadata" 
        xmlns:tts="//www.vfdks.tw/ns/ttml#styling"
        xmlns:ttp="//www.vfdks.tw/ns/ttml#parameter" 
        xmlns:itts="//www.vfdks.tw/ns/ttml/profile/imsc1#styling"
        ttp:displayAspectRatio="16 9"
        ttp:contentProfiles="//www.vfdks.tw/ns/ttml/profile/imsc1.2/text">
        
        <head>
            <layout>
                <region xml:id="r1" tts:showBackground="whenActive" tts:origin="10% 2%" tts:extent="80% 10%" tts:color="white" itts:forcedDisplay="true" tts:backgroundColor="black"/>
                <region xml:id="r2" tts:showBackground="whenActive" tts:origin="10% 80%" tts:extent="80% 10%" tts:color="white" tts:backgroundColor="black"/>
            </layout>
        </head>
        <body>
            <div>
                <p region="r1" begin="1s" end="6s">Lycée</p>
    
                <!-- the following will not appear if displayForcedOnlyMode='true' -->
                <p region="r2" begin="4s" end="6s">Nous étions inscrits au même lycée.</p>
            </div>
        </body>
    </tt>
    
    Note

    As specified in [ttml2], the background of a region can be visible even if the computed value of tts:visibility equals "hidden" for all active content within. The background of a region for which itts:forcedDisplay equals "true" can therefore remain visible even if itts:forcedDisplay equals "false" for all active content elements within the region and displayForcedOnlyMode equals "true". Authors can avoid this situation, for instance, by ensuring that content elements and the regions that they are flowed into always have the same value of itts:forcedDisplay.

    Note

    Although itts:forcedDisplay, like all the TTML style attributes, has no defined semantics on a br content element, itts:forcedDisplay will apply to a br content element if it is either defined on an ancestor content element of the br content element or it is applied to a region element corresponding to a region that the br content element is being flowed into.

    Note

    It is expected that the functionality of itts:forcedDisplay will be mapped to a conditional style construct in a future revision of this specification.

    Note

    The presentation semantics associated with itts:forcedDisplay are intended to be compatible with those associated with the forcedDisplayMode attribute defined in [CFF].

    7.8.4 ittm:altText

    The #altText feature is designated as permitted-deprecated in the profiles defined by this specification. The altText named metadata item provides equivalent semantics.

    ittm:altText allows an author to provide a text string equivalent for an element, typically an image. This text equivalent MAY be used to support indexing of the content and also facilitate quality checking of the document during authoring.

    The ittm:altText element SHALL conform to the following syntax:

    <ittm:altText
      xml:id = ID
      xml:lang = string
      xml:space = (default|preserve)
      {any attribute not in the default namespace, any TT namespace or any IMSC namespace}>
      Content: #PCDATA
    </ittm:altText>

    The ittm:altText element SHALL be a child of the metadata element.

    § 9. Image Profile Provisions specifies the use of the ittm:altText element with images.

    <?xml version="1.0" encoding="UTF-8"?>
    <tt xml:lang="fr"
    xmlns="//www.vfdks.tw/ns/ttml"
    xmlns:ttp="//www.vfdks.tw/ns/ttml#parameter"
    ttp:profile="//www.vfdks.tw/ns/ttml/profile/imsc1/image"
    xmlns:tts="//www.vfdks.tw/ns/ttml#styling"
    xmlns:smpte="//www.smpte-ra.org/schemas/2052-1/2010/smpte-tt"
    xmlns:ittm="//www.vfdks.tw/ns/ttml/profile/imsc1#metadata" tts:extent="320px 240px">
        <head>
            <layout>
                <region xml:id="area1" tts:origin="20px 215px" tts:extent="180px 20px"/>
            </layout>
        </head>
        <body>
            <div begin="1s" end="9s" region="area1" smpte:backgroundImage="altText1-img.png">
                <metadata>
                    <ittm:altText>Nous étions inscrits au même lycée.</ittm:altText>
                </metadata>
            </div>
        </body>
    </tt>
    
    
    Note

    In contrast to the common use of alt attributes in [HTML5], the ittm:altText attribute content is not intended to be displayed in place of the element if the element is not loaded. The ittm:altText attribute content can however be read and used by assistive technologies.

    7.8.5 ittp:activeArea

    The Active Area of a Document Instance is the area within the Root Container Region that the author intends to be minimally visible to the viewer. This area typically fully contains all of the referenced regions within the Document Instance.

    Note

    Under normal circumstances, the entirety of the Root Container Region is presented. However, under special circumstances, such as when the related video object is cropped, a system can, for instance, use the ittp:activeArea parameter to avoid cropping areas of the Root Container Region that are intended to be visible to the viewer. The specific behavior of the system is however left undefined intentionally: the system can select a presentation mode appropriate to the display shape, user preferences, etc. The ittp:activeArea is analogous to the Active Format Description (AFD) metadata commonly used in broadcast applications.

    The Active Area is specified using the ittp:activeArea attribute.

    If present, the ittp:activeArea attribute SHALL conform to the following syntax:

    ittp:activeArea
      : leftOffset topOffset width height
      
    leftOffset | topOffset | width | height
      : <percentage>                // where <percentage> is non-negative and not greater than 100%.

    The width percentage value is relative to the width of the Root Container Region.

    The height percentage value is relative to the height of the Root Container Region.

    The width and height percentage values are the width and height of the Active Area.

    The leftOffset and topOffset percentage values specify an alignment point between the Root Container Region and the Active Area.

    The origin top left {x, y} percentage coordinates of the Active Area SHALL be calculated as follows:

    x = leftOffset * (1 - width/100)
    y = topOffset * (1 - height/100)
    Note

    The use of left and top offset positions is co-incident with the [css3-background] background-position property where a two percentage value position is used.

    Note

    The syntax of the ittp:activeArea parameter is such that the Active Area cannot extend outside the Root Container Region in any dimension.

    The ittp:activeArea attribute is considered to be significant only when specified on the tt element.

    If the ittp:activeArea attribute is not specified, the Active Area SHALL be the Root Container Region.

    <?xml version="1.0" encoding="UTF-8"?>
    <tt xml:lang="en"
        xmlns="//www.vfdks.tw/ns/ttml"
        xmlns:ttm="//www.vfdks.tw/ns/ttml#metadata" 
        xmlns:tts="//www.vfdks.tw/ns/ttml#styling"
        xmlns:ttp="//www.vfdks.tw/ns/ttml#parameter" 
        xmlns:ittp="//www.vfdks.tw/ns/ttml/profile/imsc1#parameter"
        ittp:activeArea="50% 50% 80% 80%"
        tts:extent="640px 480px"
        ttp:contentProfiles="//www.vfdks.tw/ns/ttml/profile/imsc1.2/text">
        
        <head>
            <layout>
                <region xml:id="area1" tts:origin="10% 10%" tts:extent="80% 10%" tts:backgroundColor="blue" tts:displayAlign="center" tts:textAlign="center" tts:color="white" tts:fontSize="24px"/>
                <region xml:id="area2" tts:origin="10% 80%" tts:extent="80% 10%" tts:backgroundColor="blue" tts:displayAlign="center" tts:textAlign="center" tts:color="white" tts:fontSize="24px"/>
                <region xml:id="area3" tts:origin="10% 92%" tts:extent="80% 6%" tts:backgroundColor="red" tts:displayAlign="center" tts:textAlign="center" tts:color="yellow" tts:fontSize="24px"/>
            </layout>
        </head>
        <body>
            <div>
                <p region="area1" begin="0s" end="6s">This region is within the editorial area.</p>
                <p region="area2" begin="0s" end="6s">This region is within the editorial area.</p>
                <p region="area3" begin="0s" end="6s">This region is not.</p>
            </div>
        </body>
    </tt>
    

    7.8.6 itts:fillLineGap

    The itts:fillLineGap attribute allows the author to control the application of background between successive line areas.

    If itts:fillLineGap="true" then the background of each inline area generated by descendant spans of the p element SHALL extend to the before-edge and after-edge of its containing line area (before-edge and after-edge are defined at Section 4.2.3 of [XSL11]).

    The itts:fillLineGap attribute SHALL conform to the following:

    Values: false | true
    Initial: false
    Applies to: p
    Inherited: yes
    Percentages: N/A
    Animatable: discrete

    In the following example, the p specifies itts:fillLineGap="true", and, as a result, no gap exists between its lines.

    <?xml version="1.0" encoding="UTF-8"?>
    <tt xmlns="//www.vfdks.tw/ns/ttml"
        xmlns:ttp="//www.vfdks.tw/ns/ttml#parameter"
        xmlns:tts="//www.vfdks.tw/ns/ttml#styling"
        xmlns:itts="//www.vfdks.tw/ns/ttml/profile/imsc1#styling"
        ttp:timeBase="media"
        xml:lang="en"
        ttp:cellResolution="50 30"
        ttp:contentProfiles="//www.vfdks.tw/ns/ttml/profile/imsc1.2/text">
      <head>
        <styling>
          <style xml:id="spanStyle" tts:color="#ffffff" tts:backgroundColor="#000000" />
          <style xml:id="spanStyleSmall" tts:color="#000000" tts:backgroundColor="#dfbb02" tts:fontSize="50%"/>
          <style xml:id="spanStyleBig" tts:color="#ffffff" tts:backgroundColor="#b75800" tts:fontSize="150%"/>
          <style xml:id="paragraphStyle" tts:fontFamily="monospaceSerif" tts:textAlign="center"
                  tts:fontSize="200%" tts:lineHeight="165%"  itts:fillLineGap="true"/>
        </styling>
        <layout>
          <region xml:id="bottom" tts:origin="10% 10%" tts:extent="80% 80%" tts:displayAlign="after" />
        </layout>
      </head>
      <body>
        <div>
          <p xml:id="subtitle1" region="bottom" begin="00:00:00.000" end="00:00:30.000" style="paragraphStyle">
            <span style="spanStyle">##Line gaps##</span>
            <br/>
            <span style="spanStyle">The quick </span>
            <span style="spanStyleBig">brown</span>
            <span style="spanStyle"> fox</span>
            <br/>
            <span style="spanStyle">jumps over the </span>
            <span style="spanStyleSmall">lazy</span>
            <span style="spanStyle"> dog</span>
            <br/>
            <span style="spanStyle">##Line gaps##</span>
          </p>
        </div>
      </body>
    </tt>
    
    itts:fillLineGap rendering example 1
    Figure 1 Illustrative rendition of the example immediately above with itts:fillLineGap="true" removed (left) or preserved (right). Blue lines have been added to show the before-edge and after-edge of each line area, which are coincident for successive line areas.

    Also, as illustrated in the following example, because the line areas of successive p elements are contiguous, no gap exists between two successive p elements where itts:fillLineGap="true".

    <?xml version="1.0" encoding="UTF-8"?>
    <tt xmlns="//www.vfdks.tw/ns/ttml"
        xmlns:ttp="//www.vfdks.tw/ns/ttml#parameter"
        xmlns:tts="//www.vfdks.tw/ns/ttml#styling"
        xmlns:itts="//www.vfdks.tw/ns/ttml/profile/imsc1#styling"
        ttp:timeBase="media"
        xml:lang="en"
        ttp:cellResolution="50 30"
        ttp:profile="//www.vfdks.tw/ns/ttml/profile/imsc1.2/text">
      <head>
        <styling>
          <style xml:id="spanStyle" tts:color="#ffffff" tts:backgroundColor="#000000" />
          <style xml:id="paragraphStyleNoGap" tts:fontFamily="monospaceSerif" tts:textAlign="center" tts:fontSize="200%"
              tts:lineHeight="165%" itts:fillLineGap="true"/>
          <style xml:id="paragraphStyle" tts:fontFamily="monospaceSerif" tts:textAlign="center" tts:fontSize="200%"
              tts:lineHeight="165%" itts:fillLineGap="false"/>
    
        </styling>
        <layout>
          <region xml:id="bottom" tts:origin="10% 10%" tts:extent="80% 80%" tts:displayAlign="after" />
          <region xml:id="top" tts:origin="10% 10%" tts:extent="80% 80%" tts:displayAlign="before" />
    
        </layout>
      </head>
      <body>
        <div region="bottom" begin="00:00:00.000" end="00:00:30.000">
          <p xml:id="subtitle1" style="paragraphStyle">
            <span style="spanStyle">Paragraph 1</span>
          </p>
          <p xml:id="subtitle1" style="paragraphStyle">
            <span style="spanStyle">Paragraph 2</span>
          </p>
        </div>
        <div region="top" begin="00:00:00.000" end="00:00:30.000">
          <p xml:id="subtitle1" style="paragraphStyleNoGap">
            <span style="spanStyle">Paragraph 1</span>
          </p>
          <p xml:id="subtitle1" style="paragraphStyleNoGap">
            <span style="spanStyle">Paragraph 2</span>
          </p>
        </div>
      </body>
    </tt>
    
    itts:fillLineGap rendering example 2
    Figure 2 Illustrative rendition of the example immediately above, where itts:fillLineGap="true" on the two paragraphs of the top region, itts:fillLineGap="false" on the two paragraphs of the bottom region.

    7.9 Profile Signaling

    7.9.1 General

    The ttp:contentProfiles attribute SHOULD be present on the tt element, with exactly one of its values equal to the designator of the profile (either Text Profile or Image Profile) to which the Document Instance conforms.

    Note

    The ttp:contentProfiles attribute is prohibited in some profiles, e.g. [EBU-TT-D] as discussed in § I.2 EBU-TT-D.

    Note

    To minimize the risk of incompatibility, the use of the ttp:contentProfiles attribute and other syntax introduced in [ttml2] is not recommended in documents intended to conform to profiles that are based on [TTML1], e.g. [SMPTE2052-1], [ttml-imsc1] , [ttml-imsc1.0.1] , or [ttml10-sdp-us].

    Note

    The ttp:contentProfiles attribute can include additional designators, beyond those specified herein, including designators for other versions of this specification.

    Note

    § 5.4 Profile Resolution Semantics specifies the process by which the effective processor profile associated with the Document Instance is determined.

    7.9.2 Signaling conformance using EBU-TT metadata

    When using the ebuttm:conformsToStandard element specified in [EBU-TT-M], the designators of the Text Profile and Image Profile SHALL be used when indicating conformance to the corresponding profile.

    Note

    See § I.2 EBU-TT-D for a sample Document Instance that follows the recommendations of this section.

    7.10 Hypothetical Render Model

    It SHALL be possible to apply the Hypothetical Render Model specified in Section § 10. Hypothetical Render Model to any sequence of consecutive intermediate synchronic documents without error as defined in Section § 10.2 General.

    7.11 Style Resolution

    The following style properties SHALL be subject to the Style Resolution procedures specified at Section 10.4 of [ttml2]:

    Note

    The style properties above can be specified as attributes of the initial element specified at Section 10.1.1 of [ttml2].

    7.12 Constraints

    7.12.1 Region

    7.12.1.1 Presented Region

    A presented region is a temporally active region that satisfies the following conditions:

    1. the computed value of tts:opacity is not equal to "0.0"; and
    2. the computed value of tts:display is not "none"; and
    3. the computed value of tts:visibility is not "hidden"; and
    4. either (a) content is selected into the region or (b) the computed value of tts:showBackground is equal to "always" and the computed value of tts:backgroundColor has non-transparent alpha.
    7.12.1.2 Dimensions and Position

    All regions SHALL NOT extend beyond the Root Container Region, i.e. every coordinate in the set of coordinates of each region is also in the set of coordinates of the Root Container Region.

    No two presented regions in a given intermediate synchronic document SHALL overlap, i.e. the intersection of the sets of coordinates within each presented region is empty.

    Note
    7.12.1.3 Maximum number

    The number of presented regions in a given intermediate synchronic document SHALL NOT be greater than 4.

    7.12.2 altText named metadata item

    A altText named metadata item SHALL NOT be present in a Document Instance if any ittm:altText element is also present.

    7.12.3 #altText

    The ittm:altText element SHOULD NOT be present unless compatibility with [ttml-imsc1.0.1] processors is desired.

    A ittm:altText element SHALL NOT be present in a Document Instance if any altText named metadata item element is also present.

    7.12.4 #aspectRatio

    The ittp:aspectRatio attribute SHOULD NOT be present in a Document Instance unless compatibility with [ttml-imsc1.0.1] processors is desired.

    The ittp:aspectRatio attribute SHALL not be present in a Document Instance if any ttp:displayAspectRatio attribute is also present.

    7.12.5 #displayAspectRatio

    The ttp:displayAspectRatio attribute SHALL not be present in a Document Instance if any ittp:aspectRatio attribute is also present.

    7.12.6 #extent-root

    If the Document Instance includes any length value that uses the px unit, tts:extent SHALL be present on the tt element.

    7.12.7 #frameRate

    If the Document Instance includes any clock time expression that uses the frames term or any offset time expression that uses the f metric, the ttp:frameRate attribute SHALL be present on the tt element.

    7.12.8 #length-cell

    c units SHALL NOT be present outside of the value of ebutts:linePadding.

    7.12.9 #length-root-container-relative

    When specified on a tts:extent or tts:position attribute:

    • rh units SHALL NOT be used for horizontal length components; and
    • rw units SHALL NOT be used for vertical length components.
    Note

    7.12.10 #tickRate

    ttp:tickRate SHALL be present on the tt element if the document contains any time expression that uses the t metric.

    7.12.11 #timeBase-media

    This section is non-normative.

    [ttml2] specifies that the default timebase is "media" if ttp:timeBase is not specified on tt.

    7.12.12 #time-offset-with-frames

    This section is non-normative.

    As specified in [ttml2], a #time-offset-with-frames expression is translated to a media time M according to M = 3600 · hours + 60 · minutes + seconds + (frames ÷ (ttp:frameRateMultiplier · ttp:frameRate)).

    7.12.13 #timing

    For any content element that contains br elements or text nodes or a smpte:backgroundImage attribute, both the begin attribute and one of either the end or dur attributes SHOULD be specified on the content element or at least one of its ancestors.

    7.12.14 usesForced named metadata item

    This section is non-normative.

    The usesForced named metadata item does not apply since the condition attribute is prohibited.

    The itts:forcedDisplay attribute is used to specify forced content semantics.

    7.12.15 #zIndex

    This section is non-normative.

    This feature has no effect since, as specified at § 7.12.1.2 Dimensions and Position, presented regions do not overlap in a Document Instance.

    8. Text Profile Provisions

    8.1 Profile Designator

    This profile is associated with the following profile designator:

    Profile Name Profile Designator
    IMSC 1.2 Text //www.vfdks.tw/ns/ttml/profile/imsc1.2/text

    8.3 Reference Fonts

    When rendering codepoints matching one of the combinations of computed font family and codepoints listed in § A. Reference Fonts, a processor SHALL use a font that generates a glyph sequence whose dimension is substantially identical to the glyph sequence that would have been generated by one of the specified reference fonts.

    Note

    This clause only applies to codepoints supported by the processor. See § 8.2 Recommended Character Sets for codepoints that a processor is likely to encounter for various languages.

    Note

    When a content author sets a bounding box for a subtitle, they want to maximize the likelihood that the text will fit within it when displayed by the processor. If the processor doesn't use the specific font the content author had in mind, the font actually used might cause the text to grow in size so that it no longer fits in the bounding box. This is further compounded by differences in the way text wraps when a font has bigger glyphs, which might increase the number of lines used, and increased line spacing, which might also push some of the text outside the bounding box.
    To help ensure that things such as text size, line breaking, and line height behave as expected relative to the size of the bounding box set by the content author, the author can use one of the reference fonts defined by this specification. This specification requires processors to support one or more fonts with similar font metrics as reference fonts. Note that, however, the reference fonts as currently defined only cover characters used for a few writing systems – in particular, a subset of those based on Latin, Greek, Cyrillic, Hebrew, and Arabic scripts.

    Note

    Implementations can use fonts other than those specified in § A. Reference Fonts. Two fonts with equal metrics can have a different appearance, but flow identically.

    8.4 Font Resources

    A Presentation Processor SHALL support font resources of the following media types, as defined in [IANA-MEDIA-TYPES]:

    Note

    [IANA-MEDIA-TYPES] specifies that the media type font/otf includes file extensions .ttf and .otf.

    8.5 Constraints

    8.5.1 #color

    The initial value of tts:color SHALL be "white".

    Note

    This is consistent with [SMPTE2052-1].

    Note

    The named color green defined in [ttml2] is equivalent to the RGB color triple #008000 and is not full luminance. For full luminance green, an author can specify the RGB color triple #00ff00 or the named color lime.

    8.5.2 #extent-region

    For each region element defined in the Document Instance, the specified value of the tts:extent style property SHALL consist of two length expressions that use pixel (px), percentage (%), or root container relative units.

    Note

    If no region element is defined in the Document Instance, then content flows into the default region; conversely, if one or more region elements are defined in the Document Instance, the default region is not used.

    Note

    The requirement above requires the author to explicitly specify the value of tts:extent in the Document Instance, e.g. by specifying the tts:extent attribute for each region element.

    8.5.3 #font and #source

    A font element in the Document Instance SHALL not specify a src attribute.

    All source elements that are children of a font element SHALL reference an external data resource.

    Note
    Note

    8.5.4 #fontFamily-generic

    In absence of specific instructions on the choice of font families, and in order to enhance reproducibility of line fitting, authors are encouraged to use the monospaceSerif or proportionalSansSerif generic font families, for which reference font metrics are defined at § A. Reference Fonts.

    If the computed value of tts:fontFamily is "default", then the used value of tts:fontFamily SHALL be "monospaceSerif".

    Note

    The term used value is defined in CSS 2.1, as normatively referenced by [ttml2].

    8.5.5 #fontFamily

    Linear white-space SHOULD NOT appear between components of the specified value of tts:fontFamily.

    8.5.6 #length-negative

    Strictly negative length expressions SHALL NOT be used with attributes other than:

    • tts:disparity; and
    • tts:textShadow.
    Note

    8.5.7 #lineHeight

    The specified value of the tts:lineHeight attribute SHOULD be such that specified style set of each p element contains a tts:lineHeight property whose value is not normal.

    Note

    Implementation of the normal value is not uniform at the time of this writing.

    8.5.8 #origin

    The value of the tts:origin attribute SHALL consist of two length expressions that use pixel (px) or percentage (%) units.

    If the tts:position attribute is specified anywhere in a Document Instance, then the tts:origin attribute SHALL NOT be specified anywhere in that Document Instance.

    8.5.9 #position

    All length components of the value of a tts:position attribute SHALL use pixel (px), percentage (%) or root container relative units.

    If the tts:origin attribute is specified anywhere in a Document Instance, then the tts:position attribute SHALL NOT be specified anywhere in that Document Instance.

    8.5.10 #resources

    The resources element SHALL not contain any of the following children elements:

    • audio;
    • data; and
    • image.

    8.5.11 #rubyAlign

    The specified value of the tts:rubyAlign attribute SHALL be such that its computed value is center or spaceAround.

    8.5.12 #textOutline-unblurred

    The specified value of the tts:textOutline attribute SHALL be such that its computed value on any span element is 10% or less than the computed value of tts:fontSize attribute on the same element.

    8.5.13 #textShadow

    The specified value of the tts:textShadow attribute SHALL NOT have more than 4 <shadow> values.

    8.5.14 ebutts:linePadding

    In addition to the style element, the attribute ebutts:linePadding MAY be specified on the following elements:

    • region
    • body
    • div
    • p
    • initial

    The processor:

    • SHALL apply ebutts:linePadding to p only; and
    • SHALL treat ebutts:linePadding as inheritable.
    Note

    The ebutts:linePadding attribute only supports c length units.

    Note

    In contrast to this specification, [EBU-TT-D] specifies that the attribute ebutts:linePadding is allowed only on the style element.

    8.5.15 ebutts:multiRowAlign

    In addition to the style element, the attribute ebutts:multiRowAlign MAY be specified on the following elements:

    • region
    • body
    • div
    • p
    • initial

    The processor:

    • SHALL apply ebutts:multiRowAlign to p only; and
    • SHALL treat ebutts:multiRowAlign as inheritable.
    Note

    In contrast to this specification, [EBU-TT-D] specifies that the attribute ebutts:multiRowAlign is allowed only on the style element.

    9. Image Profile Provisions

    9.1 Profile Designator

    This profile is associated with the following profile designator:

    Profile Name Profile Designator
    IMSC 1.2 Image //www.vfdks.tw/ns/ttml/profile/imsc1.2/image

    9.2 Presented Image

    9.2.1 Definition

    A presented image is a div element:

    • with a smpte:backgroundImage attribute or a child image element; and
    • that flows into a presented region.
    Note

    A presented image is never presented in the default region since, as specified in § 9.4.4 TTML #image Feature and § 9.4.5 SMPTE #image Extension, it is always associated with a region defined in the Document Instance.

    9.2.2 Constraints

    In a given intermediate synchronic document, each presented region SHALL contain at most one div element, which SHALL be a presented image.

    9.2.3 Intermediate Synchronic Document Construction

    For the purposes of constructing an intermediate synchronic document, a div element with a smpte:backgroundImage attribute SHALL NOT be considered empty.

    9.3 Image Resources

    An image resource is a PNG datastream as specified in [PNG].

    If a pHYs chunk is present, it SHALL indicate square pixels.

    Note

    [PNG] specifies that, if no pixel aspect ratio is carried, the default of square pixels is assumed.

    9.4 Constraints

    9.4.1 #content

    The p, span and br elements SHALL NOT be present.

    Sections below specify constraints on div elements.

    9.4.2 #extent-region

    The tts:extent attribute SHALL be present on each region element defined in the Document Instance and its value SHALL consist of two length expressions that use pixel (px) units.

    9.4.3 #length-negative

    Strictly negative length expressions SHALL NOT be used with attributes other than:

    • tts:disparity.

    9.4.4 TTML #image Feature

    The image element SHALL only be used in a image presentation context.

    The image element SHALL be a child of a div element that does not have a smpte:backgroundImage attribute.

    A div element SHALL have zero or one child image element.

    A div element that has a child image element SHALL be associated with a region element defined in the Document Instance.

    A div element that contains a child image element SHOULD contain a metadata element containing an altText named metadata item that is a Text Alternative of the image resource referenced by the image element.

    An image element SHALL specify a src attribute, which references an image resource that conforms to § 9.3 Image Resources.

    An image element SHALL specify a type attribute.

    An image element SHALL specify a tts:extent attribute, which shall be equal to:

    • the specified value of the tts:extent style property of the region element in which the image element is presented; and
    • the dimensions (in pixels) of the image resource.

    9.4.5 SMPTE #image Extension

    9.4.5.1 smpte:backgroundImage

    smpte:backgroundImage MAY be used with the semantics of the attribute defined by Sections 5.5.2 of [SMPTE2052-1].

    If a smpte:backgroundImage attribute is applied to a div element:

    • the div element SHALL be associated with a region element defined in the Document Instance;
    • the width and height (in pixels) of the image resource referenced by smpte:backgroundImage SHALL be equal to the width and height expressed by the tts:extent attribute of the region in which the div element is presented;
    • the div element SHOULD contain a metadata element containing an ittm:altText element that is a Text Alternative of the image referenced by the smpte:backgroundImage attribute;
    • The smpte:backgroundImage attribute SHALL reference an image resource that conforms to § 9.3 Image Resources; and
    • the div element SHALL NOT have any image element as a descendant.
    Note

    In order to individually position multiple div elements, each div can be associated with a distinct region with the desired tts:extent and tts:origin.

    Note

    The rendering semantics of smpte:backgroundImage are not identical to those of background-image specified at Section 7.8.3 of [XSL11]. In particular, Section 5.5.6 at [SMPTE2052-1] amends the semantics of background-image by specifying values for its min-height and min-width properties.

    9.4.5.2 smpte:backgroundImageHorizontal and smpte:backgroundImageVertical

    smpte:backgroundImageHorizontal and smpte:backgroundImageVertical SHALL NOT be used.

    9.4.5.3 smpte:image

    smpte:image SHALL NOT be used.

    10. Hypothetical Render Model

    10.1 Overview

    This section is non-normative.

    This Section specifies the Hypothetical Render Model illustrated in Figure 3.

    The purpose of the model is to limit Document Instance complexity. It is not intended as a specification of the processing requirements for implementations. For instance, while the model defines a glyph buffer for the purpose of limiting the number of glyphs displayed at any given point in time, it neither requires the implementation of such a buffer, nor models the sub-pixel character positioning and anti-aliased glyph rendering that can be used to produce text output.

    Hypothetical Render Model
    Figure 3 Hypothetical Render Model

    The model operates on successive intermediate synchronic documents obtained from an input Document Instance, and uses a simple double buffering model: while an intermediate synchronic document En is being painted into Presentation Buffer Pn (the "front buffer" of the model), the previous intermediate synchronic document En-1 is available for display in Presentation Buffer Pn-1 (the "back buffer" of the model).

    The model specifies an (hypothetical) time required for completely painting an intermediate synchronic document as a proxy for complexity. Painting includes drawing region backgrounds, rendering and copying glyphs, and decoding and copying images. Complexity is then limited by requiring that painting of intermediate synchronic document En completes before the end of intermediate synchronic document En-1.

    Whenever applicable, constraints are specified relative to Root Container Region dimensions, allowing subtitle sequences to be authored independently of Related Video Object resolution.

    To enable scenarios where the same glyphs are used in multiple successive intermediate synchronic documents, e.g. to convey a CEA-608/708-style roll-up (see [CEA-608] and [CEA-708]), the Glyph Buffers Gn and Gn-1 store rendered glyphs across intermediate synchronic documents, allowing glyphs to be copied into the Presentation Buffer instead of rendered, a more costly operation.

    Similarly, Decoded Image Buffers Dn and Dn-1 store decoded images across intermediate synchronic documents, allowing images to be copied into the Presentation Buffer instead of decoded.

    10.2 General

    The Presentation Compositor SHALL render in Presentation Buffer Pn each successive intermediate synchronic document En using the following steps in order:

    1. clear the pixels, except for the first intermediate synchronic document E0 for the which the pixels of P0 SHALL be assumed to have been cleared;
    2. paint, according to stacking order, all background pixels for each region;
    3. paint all pixels for background colors associated with text or image subtitle content; and
    4. paint the text or image subtitle content.

    The Presentation Compositor SHALL start rendering En:

    The duration DUR(En) for painting an intermediate synchronic document En in the Presentation Buffer Pn SHALL be:

    DUR(En) = S(En) / BDraw + DURT(En) + DURI(En)

    where

    The contents of the Presentation Buffer Pn SHALL be transferred instantaneously to Presentation Buffer Pn-1 at the presentation time of intermediate synchronic document En, making the latter available for display.

    Note

    It is possible for the contents of Presentation Buffer Pn-1 to never be displayed. This can happen if Presentation Buffer Pn is copied twice to Presentation Buffer Pn-1 between two consecutive video frame boundaries of the Related Video Object.

    It SHALL be an error for the Presentation Compositor to fail to complete painting pixels for En before the presentation time of En.

    It SHALL be an error if the total retrieved font size exceeds 10 MiB.

    Unless specified otherwise, the following table SHALL specify values for IPD and BDraw.

    Parameter Initial value
    Initial Painting Delay (IPD) 1 s
    Normalized background drawing performance factor (BDraw) 12 s-1
    Note

    BDraw effectively sets a limit on fillings regions - for example, assuming that the Root Container Region is ultimately rendered at 1920×1080 resolution, a BDraw of 12 s-1 would correspond to a fill rate of 1920×1080×12/s=23.7×220pixels s-1.

    Note

    IPD effectively sets a limit on the complexity of any given intermediate synchronic document.

    10.3 Paint Regions

    The total normalized drawing area S(En) for intermediate synchronic document En SHALL be

    S(En) = CLEAR(En) + PAINT(En )

    where CLEAR(E0) = 0 and CLEAR(En | n > 0) = 1, i.e. the Root Container Region in its entirety.

    Note

    To ensure consistency of the Presentation Buffer, a new intermediate synchronic document requires clearing of the Root Container Region.

    PAINT(En) SHALL be the normalized area to be painted for all regions that are used in intermediate synchronic document En according to:

    PAINT(En) = ∑Ri∈Rp NSIZE(Ri) ? NBG(Ri)

    where R_p SHALL be the set of presented regions in the intermediate synchronic document En.

    NSIZE(Ri) SHALL be given by:

    NSIZE(Ri) = (width of Ri ? height of Ri ) ÷ (Root Container Region height ? Root Container Region width)

    NBG(Ri) SHALL be the total number of tts:backgroundColor attributes associated with the given region Ri in the intermediate synchronic document. A tts:backgroundColor attribute is associated with a region when it is explicitly specified (either as an attribute in the element, or by reference to a declared style) in the following circumstances:

    Even if a specified tts:backgroundColor is the same as specified on the nearest ancestor content element or animation element, specifying any tts:backgroundColor SHALL require an additional fill operation for all region pixels.

    10.4 Paint Images

    The Presentation Compositor SHALL paint into the Presentation Buffer Pn all visible pixels of presented images of intermediate synchronic document En.

    For each presented image, the Presentation Compositor SHALL either:

    Two images SHALL be identical if and only if they reference the same encoded image source.

    The duration DURI(En) for painting images of an intermediate synchronic document En in the Presentation Buffer SHALL be as follows:

    DURI(En) = ∑Ii ∈ Ic NRGA(Ii) / ICpy + ∑Ij ∈ Id NSIZ(Ij) / IDec

    where

    NRGA(Ii) is the Normalized Image Area of presented image Ii and SHALL be equal to:

    NRGA(Ii)= (width of Ii ? height of Ii ) ÷ ( Root Container Region height ? Root Container Region width )

    NSIZ(Ii) SHALL be the number of pixels of presented image Ii.

    The contents of the Decoded Image Buffer Dn SHALL be transferred instantaneously to Decoded Image Buffer Dn-1 at the presentation time of intermediate synchronic document En.

    The total size occupied by images stored in Decoded Image Buffers Dn or Dn-1 SHALL be the sum of their Normalized Image Area.

    The size of Decoded Image Buffers Dn or Dn-1 SHALL be the Normalized Decoded Image Buffer Size (NDIBS).

    Unless specified otherwise, the following table SHALL specify ICpy, IDec, and NDBIS.

    Parameter Initial value
    Normalized image copy performance factor (ICpy) 6
    Image Decoding rate (IDec) 1 × 220 pixels s-1
    Normalized Decoded Image Buffer Size (NDIBS) 0.9885

    10.5 Paint Text

    In the context of this section, a glyph is a tuple consisting of (i) one character and (ii) the computed values of the following style properties:

    Note

    While one-to-one mapping between characters and typographical glyphs is generally the rule in some scripts, e.g. latin script, it is the exception in others. For instance, in arabic script, a character can yield multiple glyphs depending on its position in a word. The Hypothetical Render Model always assumes a one-to-one mapping, but reduces the performance of the glyph buffer for scripts where one-to-one mapping is not the general rule (see GCpy below).

    For each glyph associated with a character in a presented region of intermediate synchronic document En, the Presentation Compositor SHALL:

    Note

    In the case of external data resource retrieved using [HTTP11], the size in bytes of the external data resource is the entity-length of the message.

    Example of Presentation Compositor Behavior for Text Rendering
    Figure 4 Example of Presentation Compositor Behavior for Text Rendering

    The duration DURT(En) for rendering the text of an intermediate synchronic document En in the Presentation Buffer is as follows:

    DURT(En) = ∑gi ∈ Γr NRGA(gi) / Ren(gi) + ∑gj ∈ Γc NRGA(gj) / GCpy

    where

    The Normalized Rendered Glyph Area NRGA(gi) of a glyph gi SHALL be equal to:

    NRGA(gi) = (fontSize of gi as percentage of Root Container Region height)2

    Note

    NRGA(Gi) does not take into account decorations (e.g. underline), effects (e.g. outline) or actual typographical glyph aspect ratio. An implementation can determine an actual buffer size needs based on worst-case glyph size complexity.

    The contents of the Glyph Buffer Gn SHALL be copied instantaneously to Glyph Buffer Gn-1 at the presentation time of intermediate synchronic document En.

    It SHALL be an error for the sum of NRGA(gi) over all glyphs Glyph Buffer Gn to be larger than the Normalized Glyph Buffer Size (NGBS).

    Unless specified otherwise, the following table specifies values of GCpy, Ren and NGBS.

    Normalized glyph copy performance factor (GCpy)
    Script property (see Standard Annex #24 at [UNICODE]) for the character of gi GCpy
    latin, greek, cyrillic, hebrew or base 12
    any other value 3
    Text rendering performance factor Ren(Gi)
    Block property (see [UNICODE]) for the character of gi Ren(Gi)
    CJK Unified Ideograph 0.6
    any other value 1.2
    Normalized Glyph Buffer Size (NGBS)
    1
    Note

    The choice of font by the presentation processor can increase rendering complexity. For instance, a cursive font can generally result in a given character yielding different typographical glyphs depending on context, even if latin script is used.

    A. Reference Fonts

    Computed Font Family Code Points Reference Font
    monospaceSerif All code points specified in § B. Common Character Sets Courier New or Liberation Mono
    proportionalSansSerif All code points specified in § B. Common Character Sets, excluding the code points defined for Hebrew and Arabic scripts. Arial or Helvetica or Liberation Sans

    C. Forced content

    This section is non-normative.

    Figure 5 below illustrates the use of forced content, i.e. itts:forcedDisplay and displayForcedOnlyMode. The content with itts:forcedDisplay="true" is the French translation of the "High School" sign. The content with itts:forcedDisplay="false" are French subtitles capturing a voiceover.

    Illustration of the use of itts:forcedDisplay
    Figure 5 Illustration of the use of itts:forcedDisplay

    When the user selects French as the playback language but does not select French subtitles, displayForcedOnlyMode is set to "true", causing the display of the sign translation, which is useful to any French speaker, but hiding the voiceover subtitles as the voiceover is heard in French.

    If the user selects French as the playback language and also selects French subtitles, e.g. if the user is hard-of-hearing, displayForcedOnlyMode is set to "false", causing the display of both the sign translation and the voiceover subtitles.

    The algorithm for setting the displayForcedOnlyMode parameter and selecting the appropriate combination of subtitle and audio tracks depends on the application.

    D. WCAG and MAUR Considerations

    D.1 WCAG Considerations

    In order to meet the guidelines in [WCAG21], the following considerations apply.

    Guideline 1.1 of [WCAG21] recommends that an implementation provide Text Alternatives for all non-text content. In the context of this specification, this Text Alternative is intended primarily to support users of the subtitles who cannot see images. Since the images of an Image Profile Document Instance usually represent subtitle or caption text, the guidelines for authoring text equivalent strings given at Images of text of [HTML5] are appropriate.

    Thus, for each subtitle in an Image Profile Document Instance, a text equivalent content in a Text Profile Document Instance SHOULD be written so that it conveys all essential content and fulfills the same function as the corresponding subtitle image. In the context of subtitling and captioning, this content will be (as a minimum) the verbatim equivalent of the image without précis or summarization. However, the author MAY include extra information to the text equivalent string in cases where styling is applied to the text image with a deliberate connotation, as a functional replacement for the applied style.

    For instance, in subtitling and captioning, italics can be used to indicate an off screen speaker context (for example a voice from a radio). An author can choose to include this functional information in the text equivalent; for example, by including the word "Radio: " before the image equivalent text. Note that images in an Image Profile Document Instance that are intended for use as captions, i.e. intended for a hard of hearing audience, might already include this functional information in the rendered text.

    Guideline 1.1 of [WCAG21] also recommends that accessible Text Alternatives must be "programmatically determinable." This means that the text must be able to be read and used by the assistive technologies (and the accessibility features in browsers) that people with disabilities use. It also means that the user must be able to use their assistive technology to find the alternative text (that they can use) when they land on the non-text content (that they can't use).

    Guideline 1.4.12 of [WCAG21] also recommends that no loss of content or functionality occur when spacing of lines, letters, words and paragraphs is modified by a specified amount.

    D.2 MAUR Considerations

    This section is non-normative.

    Authors and implementers are encouraged to consult [media-accessibility-reqs], which presents accessibility requirements users with disabilities have with respect to audio and video on the web.

    E. Sample Document Instance

    This section is non-normative.

    The following sample Document Instances conforms to the Text Profile and Image Profile, respectively. These samples are for illustration only, and are neither intended to capture current or future practice, nor exercise all normative prose contained in this specification.

    <?xml version="1.0" encoding="UTF-8"?>
    <tt xml:lang="en"
        xmlns="//www.vfdks.tw/ns/ttml"
        xmlns:ttm="//www.vfdks.tw/ns/ttml#metadata" 
        xmlns:tts="//www.vfdks.tw/ns/ttml#styling"
        xmlns:ttp="//www.vfdks.tw/ns/ttml#parameter" 
        ttp:displayAspectRatio="4 3"
        ttp:contentProfiles="//www.vfdks.tw/ns/ttml/profile/imsc1.2/text">
        
        <head>
            <layout>
                <region xml:id="area1" tts:origin="10% 10%" tts:extent="80% 10%" tts:backgroundColor="black" tts:displayAlign="center" tts:color="red"/>
            </layout>
        </head>
        <body>
            <div>
                <p region="area1" begin="0s" end="6s">Lorem ipsum dolor.</p>
            </div>
        </body>
    </tt>
    
    <?xml version="1.0" encoding="UTF-8"?>
    <tt xml:lang="fr"
        xmlns="//www.vfdks.tw/ns/ttml"
        xmlns:ttm="//www.vfdks.tw/ns/ttml#metadata" 
        xmlns:tts="//www.vfdks.tw/ns/ttml#styling"
        xmlns:ttp="//www.vfdks.tw/ns/ttml#parameter" 
        xmlns:itts="//www.vfdks.tw/ns/ttml/profile/imsc1#styling"
        tts:extent="640px 480px"
        ttp:frameRate="25"
        ttp:contentProfiles="//www.vfdks.tw/ns/ttml/profile/imsc1.2/image">
    
      <head>
        <layout>
          <region xml:id="region1" tts:origin="120px 410px" tts:extent="240px 40px" tts:showBackground="whenActive"/>
          <region xml:id="region2" tts:origin="120px 20px" tts:extent="240px 40px" tts:showBackground="whenActive"/>
        </layout>
      </head>
      <body>
        <div region="region1" begin="00:00:01:00" end="00:00:02:00">
          <image tts:extent="240px 40px" src="1.png" type="image/png"/>
        </div> 
        <div region="region1" begin="00:00:03:20" end="00:00:04:12">
          <image tts:extent="240px 40px" src="2.png" type="image/png"/>
        </div>
        <div region="region2" itts:forcedDisplay="true" begin="00:00:03:20" end="00:00:04:12">
          <image tts:extent="240px 40px" src="3.png" type="image/png"/>
        </div>
      </body>
    </tt>
    
    

    F. Extensions

    F.1 General

    The following sections define extension designations, expressed as relative URIs (fragment identifiers) relative to the IMSC Extension Namespace base URI.

    F.2 #progressivelyDecodable

    The #progressivelyDecodable feature is designated as permitted-deprecated in the profiles defined by this specification.

    A transformation processor supports the #progressivelyDecodable feature if it recognizes and is capable of transforming values of the ittp:progressivelyDecodable attribute.

    A presentation processor supports the #progressivelyDecodable feature if it implements presentation semantic support for values of the ittp:progressivelyDecodable attribute.

    F.3 #aspectRatio

    The #aspectRatio feature is designated as permitted-deprecated in the profiles defined by this specification. The #displayAspectRatio feature provides equivalent semantics.

    A transformation processor supports the #aspectRatio feature if it recognizes and is capable of transforming values of the ittp:aspectRatio attribute.

    A presentation processor supports the #aspectRatio feature if it implements presentation semantic support for values of the ittp:aspectRatio attribute.

    F.4 #forcedDisplay

    A transformation processor supports the #forcedDisplay feature if it recognizes and is capable of transforming values of the itts:forcedDisplay attribute.

    A presentation processor supports the #forcedDisplay feature if it implements presentation semantic support for values of the itts:forcedDisplay attribute.

    F.5 #altText

    The #altText feature is designated as permitted-deprecated in the profiles defined by this specification. The altText named metadata item provides equivalent semantics.

    A transformation processor supports the #altText feature if it recognizes and is capable of transforming values of the ittm:altText element.

    A presentation processor supports the #altText feature if it implements presentation semantic support for values of the ittm:altText element.

    F.6 #linePadding

    A transformation processor supports the #linePadding feature if it recognizes and is capable of transforming values of the ebutts:linePadding attribute specified in [EBU-TT-D].

    A presentation processor supports the #linePadding feature if it implements presentation semantic support for values of the ebutts:linePadding attribute specified in [EBU-TT-D].

    F.7 #multiRowAlign

    A transformation processor supports the #multiRowAlign feature if it recognizes and is capable of transforming values of the ebutts:multiRowAlign attribute specified in [EBU-TT-D].

    A presentation processor supports the #multiRowAlign feature if it implements presentation semantic support for values of the ebutts:multiRowAlign attribute specified in [EBU-TT-D].

    F.8 #activeArea

    A transformation processor supports the #activeArea feature if it recognizes and is capable of transforming values of the ittp:activeArea attribute.

    A presentation processor supports the #activeArea feature if it implements presentation semantic support for values of the ittp:activeArea attribute.

    F.9 #fillLineGap

    A transformation processor supports the #fillLineGap feature if it recognizes and is capable of transforming values of the itts:fillLineGap attribute.

    A presentation processor supports the #fillLineGap feature if it implements presentation semantic support for values of the itts:fillLineGap attribute.

    G. XML Schema Definitions

    This section is non-normative.

    XML Schema definitions (see [xmlschema-1]) for extension vocabulary defined by this specification are provided here for convenience.

    These definitions are non-normative and are not sufficient to validate conformance of a Document Instance.

    In any case where a definition specified by this appendix diverge from the prose of the specification, then the latter takes precedence.

    H. Extensibility Objectives

    This section is non-normative.

    This section documents extensibility objectives for this specification.

    This specification is intended to allow:

    I. Compatibility with other TTML-based specifications

    This section is non-normative.

    I.1 Overview

    This specification is designed to be compatible with [ttml-imsc1], [ttml-imsc1.0.1], [SMPTE2052-1], [EBU-TT-D] and [ttml10-sdp-us]. Specifically, by selecting a subset of the features and extensions defined in this specification, it is possible to create a document that:

    This specification is also intended to allow straightforward conversion of a document that conforms to the text or image profiles of [CFF] to the Text Profile or Image Profile, respectively.

    I.2 EBU-TT-D

    The Text Profile is a strict syntactic superset of [EBU-TT-D].

    A document that conforms to [EBU-TT-D] therefore generally also conforms to the Text Profile, with a few exceptions, including:

    The profile vocabulary defined in [ttml2] is prohibited by [EBU-TT-D]. Instead, as specified in [EBU-TT-M], multiple ebuttm:conformsToStandard elements are optionally present in the metadata element of the head element, with each ebuttm:conformsToStandard indicating conformance to a specification, including other versions of this specification.

    Note

    Conformance to a [ttml-imsc1.0.1] profile can be indicated as defined in [ttml-imsc1.0.1], by including an additional ebuttm:conformsToStandard element whose value is equal to the designator of the [ttml-imsc1.0.1] profile to which the Document Instance conforms.

    It is not possible for a document that conforms to [EBU-TT-D] to also conform to Image Profile, and vice-versa, notwithstanding the special case where the document also conforms to Text Profile as noted at § 5. Profiles.

    The following is an example of a document that conforms to Text Profile, [ttml-imsc1.0.1] Text Profile and [EBU-TT-D]. Note the presence of multiple ebuttm:conformsToStandard elements, one of which equals the Text Profile designator:

    <?xml version="1.0" encoding="UTF-8"?>
    <tt xmlns:xsi="//www.vfdks.tw/2001/XMLSchema-instance"
        xmlns="//www.vfdks.tw/ns/ttml" xmlns:ttp="//www.vfdks.tw/ns/ttml#parameter"
        xmlns:tts="//www.vfdks.tw/ns/ttml#styling" xmlns:ttm="//www.vfdks.tw/ns/ttml#metadata"
        xmlns:ebutts="urn:ebu:tt:style" xml:lang="en" ttp:timeBase="media" xmlns:ebuttm="urn:ebu:tt:metadata" >
        <head>
            <metadata>
                <ebuttm:conformsToStandard>urn:ebu:tt:distribution:2014-01</ebuttm:conformsToStandard>
                <ebuttm:conformsToStandard>//www.vfdks.tw/ns/ttml/profile/imsc1/text</ebuttm:conformsToStandard>
                <ebuttm:conformsToStandard>//www.vfdks.tw/ns/ttml/profile/imsc1.1/text</ebuttm:conformsToStandard>
    			<ebuttm:conformsToStandard>//www.vfdks.tw/ns/ttml/profile/imsc1.2/text</ebuttm:conformsToStandard>
            </metadata>
            <styling>
                <style xml:id="baseStyle" tts:color="#FFFFFF" tts:lineHeight="100%"/>
                <style xml:id="blackBackground" tts:backgroundColor="#000000"/>
                <style xml:id="greenBackground" tts:backgroundColor="#00FF00"/>
                <style xml:id="startEnd" tts:textAlign="start" ebutts:multiRowAlign="end"/>
                <style xml:id="centerStart" tts:textAlign="center" ebutts:multiRowAlign="start"/>
            </styling>
            <layout>
                <region xml:id="area1" tts:origin="15% 10%" tts:extent="70% 20%" style="greenBackground" tts:displayAlign="center"/>
                <region xml:id="area2" tts:origin="15% 70%" tts:extent="70% 20%" style="blackBackground" tts:displayAlign="center"/>
            </layout>
        </head>
        <body>
            <div style="baseStyle">
                <p xml:id="s1" region="area1" style="startEnd" begin="00:00:01" end="00:00:09">
                    multiRowAlign="end"<br/>textAlign="start"
                </p>
                <p xml:id="s2" region="area2" style="centerStart" begin="00:00:01" end="00:00:09">
                    multiRowAlign="start"<br/>textAlign="center"
                </p>
            </div>
        </body>
    </tt>
    
    

    I.3 SDP-US

    The Text Profile is a strict syntactic superset of [ttml10-sdp-us].

    A document that conforms to [ttml10-sdp-us] therefore also generally conforms to the Text Profile, with a few exceptions, including:

    It is not possible for a document that conforms to [ttml10-sdp-us] to also conform to Image Profile, and vice-versa, notwithstanding the special case where the document also conforms to Text Profile as noted at § 5. Profiles.

    As an illustration, Example 3 at [ttml10-sdp-us] conforms to both Text Profile and [ttml10-sdp-us].

    I.4 SMPTE-TT (SMPTE ST 2052-1)

    [SMPTE2052-1] specifies the use of the DFXP Full Profile (see Appendix F.3 at [ttml2]) supplemented by a number of extensions, including //www.smpte-ra.org/schemas/2052-1/2010/smpte-tt#image.

    This specification defines practical constraints on [SMPTE2052-1], supplemented by extensions defined herein and selected [ttml2] features. These constraints and extensions are intended to reflect industry practice.

    As a result, particular care is required when creating a document intended to be processed according to [SMPTE2052-1], and Text Profile or Image Profile. In particular:

    The following is an example of a document that conforms to both Text Profile and [SMPTE2052-1]:

    <?xml version="1.0" encoding="UTF-8"?>
    <tt xml:lang="en"
        xmlns="//www.vfdks.tw/ns/ttml"
        xmlns:ttm="//www.vfdks.tw/ns/ttml#metadata" 
        xmlns:ttp="//www.vfdks.tw/ns/ttml#parameter"
        ttp:profile="//www.smpte-ra.org/schemas/2052-1/2010/profiles/smpte-tt-full"
        xmlns:tts="//www.vfdks.tw/ns/ttml#styling"
        ttp:frameRate="24">
        <head>
            <layout>
                <region xml:id="area1" tts:origin="10% 70%" tts:extent="80% 20%" tts:showBackground="whenActive" tts:backgroundColor="red" tts:displayAlign="center" tts:color="white"/>
            </layout>
        </head>
        <body tts:lineHeight="100%">
            <div>
                <p region="area1" begin="00:00:01.01" end="00:00:03">This should appear on frame 25.</p>
                <p region="area1" begin="00:00:04" end="00:00:06">This should appear on frame 96.</p>
                <p region="area1" begin="00:00:07.33" end="00:00:09">This should appear on frame 176.</p>
            </div>
        </body>
    </tt>
    
    

    I.5 CFF-TT

    This specification was derived from the text and image profiles specified in Section 6 at [CFF], and is intended to be a superset in terms of capabilities. Additional processing is however generally necessary to convert a document from [CFF] to this specification. In particular:

    I.6 Previous versions of IMSC

    The Text Profile is a strict superset of the [ttml-imsc1], [ttml-imsc1.0.1] and [ttml-imsc1.1] Text Profile.

    The Image Profile is a strict superset of the [ttml-imsc1], [ttml-imsc1.0.1] and [ttml-imsc1.1] Image Profile.

    A document that conforms to [ttml-imsc1] or [ttml-imsc1.0.1] or [ttml-imsc1.1] therefore also conforms to this specification.

    A number of features that were previously permitted in previous versions of IMSC are designated as permitted-deprecated in the Text Profile and Image Profile. Documents that use such features are therefore susceptible to being incompatible with future versions of this specification.

    The following is an example of a document that conforms to both Image Profile and [ttml-imsc1.0.1] Image Profile:

    <?xml version="1.0" encoding="UTF-8"?>
    <tt xml:lang="fr"
        xmlns="//www.vfdks.tw/ns/ttml"
        xmlns:ttm="//www.vfdks.tw/ns/ttml#metadata" 
        xmlns:tts="//www.vfdks.tw/ns/ttml#styling"
        xmlns:ttp="//www.vfdks.tw/ns/ttml#parameter" 
        xmlns:smpte="//www.smpte-ra.org/schemas/2052-1/2010/smpte-tt"
        xmlns:itts="//www.vfdks.tw/ns/ttml/profile/imsc1#styling"
        tts:extent="640px 480px"
        ttp:frameRate="25"
        ttp:profile="//www.vfdks.tw/ns/ttml/profile/imsc1/image">
        
        <head>
            <layout>
                <region xml:id="region1" tts:origin="120px 410px" tts:extent="240px 40px" tts:showBackground="whenActive"/>
                <region xml:id="region2" tts:origin="120px 20px" tts:extent="240px 40px" tts:showBackground="whenActive"/>
            </layout>
        </head>
        <body>
            <div region="region1" begin="00:00:01:00" end="00:00:02:00" smpte:backgroundImage="1.png"/>
            <div region="region1" begin="00:00:03:20" end="00:00:04:12" smpte:backgroundImage="2.png"/>
            <div region="region2" itts:forcedDisplay="true" begin="00:00:03:20" end="00:00:04:12" smpte:backgroundImage="3.png"/>
        </body>
    </tt>
    
    
    Note
    
        

    J. Acknowledgements

    This section is non-normative.

    The editor acknowledges the current and former members of the Timed Text Working Group, the members of other W3C Working Groups, and industry experts in other forums who have contributed directly or indirectly to the process or content of this document.

    The editor wishes to especially acknowledge the following contributions by members: Glenn Adams, Skynav; John Birch, Invited expert; Mike Dolan, Invited expert; Nigel Megitt, British Broadcasting Corporation; Thierry Michel, W3C; Andreas Tai, Institut für Rundfunktechnik; Stefan P?schel, Institut für Rundfunktechnik.

    The editor also wishes to acknowledge Digital Entertainment Content Ecosystem (DECE) for contributing to the initial document for the Member Submission.

    K. Privacy and Security Considerations

    This section is non-normative.

    With the exception of the following, the security and privacy considerations of [ttml2] apply:

    L. Summary of substantive changes

    This section is non-normative.

    L.1 Overview

    This appendix summarize changes made from [ttml-imsc1.1].

    L.2 Changes

    L.2.1 Reference to WCAG 2.1

    Replaced normative references to [WCAG20-20081211] with normative references to [WCAG21].

    L.2.2 Region Extent

    In the Text Profile, and as specified at § 8.5.2 #extent-region, the specified value of the tts:extent style property of a region element can be set using any style association mechanism, e.g. nested styling.

    L.2.3 Added Features

    Added support (partial or complete) for the following features.

    Relative to the TT Feature namespace
    #font
    #resources
    #source

    L.2.4 Deprecated selected Features

    Deprecated support (partial or complete) for the following features.

    Feature or extension Notes
    Relative to the TT Feature namespace

    M. References

    M.1 Normative references

    [CLDR]
    Unicode Common Locale Data Repository. Unicode Consortium. URL: //cldr.unicode.org/
    [css-fonts-3]
    CSS Fonts Module Level 3. John Daggett; Myles Maxfield; Chris Lilley. W3C. 20 September 2018. W3C Recommendation. URL: //www.vfdks.tw/TR/css-fonts-3/
    [EBU-TT-D]
    Tech 3380, EBU-TT-D Subtitling Distribution Format Version 1.0.1. European Broadcasting Union (EBU). URL: https://tech.ebu.ch/files/live/sites/tech/files/shared/tech/tech3380v1_0_1.pdf
    [EBU-TT-M]
    Tech 3390, EBU-TT-M Metadata Definitions 1.0. European Broadcasting Union (EBU). URL: https://tech.ebu.ch/files/live/sites/tech/files/shared/tech/tech3390.pdf
    [HTML5]
    HTML5. Ian Hickson; Robin Berjon; Steve Faulkner; Travis Leithead; Erika Doyle Navara; Theresa O'Connor; Silvia Pfeiffer. W3C. 27 March 2018. W3C Recommendation. URL: //www.vfdks.tw/TR/html5/
    [IANA-MEDIA-TYPES]
    Media Types. IANA. URL: https://www.iana.org/assignments/media-types/
    [namespaceState]
    The Disposition of Names in an XML Namespace. Norman Walsh. W3C. 29 March 2006. W3C Working Draft. URL: //www.vfdks.tw/TR/2006/WD-namespaceState-20060329/
    [PNG]
    Portable Network Graphics (PNG) Specification (Second Edition). David Duce. W3C. 10 November 2003. W3C Recommendation. URL: //www.vfdks.tw/TR/2003/REC-PNG-20031110/
    [RFC2119]
    Key words for use in RFCs to Indicate Requirement Levels. S. Bradner. IETF. March 1997. Best Current Practice. URL: https://tools.ietf.org/html/rfc2119
    [RFC8174]
    Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words. B. Leiba. IETF. May 2017. Best Current Practice. URL: https://tools.ietf.org/html/rfc8174
    [SMPTE2052-1]
    SMPTE ST 2052-1:2013 "Timed Text Format (SMPTE-TT)". SMPTE. URL: https://doi.org/10.5594/SMPTE.ST2052-1.2013
    [ttml-imsc1.0.1]
    TTML Profiles for Internet Media Subtitles and Captions 1.0.1 (IMSC1). Pierre-Anthony Lemieux. W3C. 24 April 2018. W3C Recommendation. URL: //www.vfdks.tw/TR/2018/REC-ttml-imsc1.0.1-20180424/
    [ttml-imsc1.1]
    TTML Profiles for Internet Media Subtitles and Captions 1.1. Pierre-Anthony Lemieux. W3C. 8 November 2018. W3C Recommendation. URL: //www.vfdks.tw/TR/ttml-imsc1.1/
    [ttml10-sdp-us]
    TTML Simple Delivery Profile for Closed Captions (US). Glenn Adams; Monica Martin; Sean Hayes. W3C. 5 February 2013. W3C Note. URL: //www.vfdks.tw/TR/2013/NOTE-ttml10-sdp-us-20130205/
    [ttml2]
    Timed Text Markup Language 2 (TTML2). Glenn Adams; Cyril Concolato. W3C. 8 November 2018. W3C Recommendation. URL: //www.vfdks.tw/TR/2018/REC-ttml2-20181108/
    [UNICODE]
    The Unicode Standard. Unicode Consortium. URL: https://www.unicode.org/versions/latest/
    [WCAG21]
    Web Content Accessibility Guidelines (WCAG) 2.1. Andrew Kirkpatrick; Joshue O Connor; Alastair Campbell; Michael Cooper. W3C. 5 June 2018. W3C Recommendation. URL: //www.vfdks.tw/TR/2018/REC-WCAG21-20180605/
    [xml]
    Extensible Markup Language (XML) 1.0 (Fifth Edition). Tim Bray; Jean Paoli; Michael Sperberg-McQueen; Eve Maler; Fran?ois Yergeau et al. W3C. 26 November 2008. W3C Recommendation. URL: //www.vfdks.tw/TR/2008/REC-xml-20081126/
    [xml-names]
    Namespaces in XML 1.0 (Third Edition). Tim Bray; Dave Hollander; Andrew Layman; Richard Tobin; Henry Thompson et al. W3C. 8 December 2009. W3C Recommendation. URL: //www.vfdks.tw/TR/2009/REC-xml-names-20091208/
    [XSL11]
    Extensible Stylesheet Language (XSL) Version 1.1. Anders Berglund. W3C. 5 December 2006. W3C Recommendation. URL: //www.vfdks.tw/TR/2006/REC-xsl11-20061205/

    M.2 Informative references

    [CEA-608]
    CTA 608-E, Line-21 Data Services. Consumer Technology Association. URL: https://www.techstreet.com/standards/cta-608-e-r2014?product_id=1815447
    [CEA-708]
    CTA 708-D, Digital Television (DTV) Closed Captioning. Consumer Technology Association. URL: https://www.techstreet.com/standards/cta-708-d?product_id=1815448
    [CFF]
    Common File Format & Media Formats Specification (CFF) Version 2.2. Digital Entertainment Content Ecosystem (DECE). URL: https://www.uvcentral.com
    [css3-background]
    CSS Backgrounds and Borders Module Level 3. Bert Bos; Elika Etemad; Brad Kemper. W3C. 17 October 2017. W3C Candidate Recommendation. URL: //www.vfdks.tw/TR/css-backgrounds-3/
    [HTTP11]
    Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing. R. Fielding, Ed.; J. Reschke, Ed.. IETF. June 2014. Proposed Standard. URL: https://httpwg.org/specs/rfc7230.html
    [media-accessibility-reqs]
    Media Accessibility User Requirements. Shane McCarron; Michael Cooper; Mark Sadecki. W3C. 3 December 2015. W3C Note. URL: //www.vfdks.tw/TR/2015/NOTE-media-accessibility-reqs-20151203/
    [MPEGDASH]
    Information technology — Dynamic adaptive streaming over HTTP (DASH) — Part 1: Media presentation description and segment formats. ISO/IEC. August 2019. Published. URL: https://www.iso.org/standard/75485.html
    [SUBM]
    TTML Text and Image Profiles for Internet Media Subtitles and Captions (Member Submission, 07 June 2013). World Wide Web Consortium (W3C). URL: //www.vfdks.tw/Submission/2013/SUBM-ttml-ww-profiles-20130607/
    [ttml-imsc1]
    TTML Profiles for Internet Media Subtitles and Captions 1.0 (IMSC1). Pierre-Anthony Lemieux. W3C. 26 June 2018. W3C Recommendation. URL: //www.vfdks.tw/TR/2018/SPSD-ttml-imsc1-20180626/
    [ttml-profile-registry]
    TTML Media Type Definition and Profile Registry. Glenn Adams; Mike Dolan. W3C. 11 April 2019. W3C Note. URL: //www.vfdks.tw/TR/ttml-profile-registry/
    [TTML1]
    Timed Text Markup Language 1 (TTML1) (Third Edition). Glenn Adams; Pierre-Anthony Lemieux. W3C. 8 November 2018. W3C Recommendation. URL: //www.vfdks.tw/TR/2018/REC-ttml1-20181108/
    [WCAG20-20081211]
    Web Content Accessibility Guidelines (WCAG) 2.0. Ben Caldwell; Michael Cooper; Loretta Guarino Reid; Gregg Vanderheiden et al. W3C. 11 December 2008. W3C Recommendation. URL: //www.vfdks.tw/TR/2008/REC-WCAG20-20081211/
    [xmlschema-1]
    XML Schema Part 1: Structures Second Edition. Henry Thompson; David Beech; Murray Maloney; Noah Mendelsohn et al. W3C. 28 October 2004. W3C Recommendation. URL: //www.vfdks.tw/TR/2004/REC-xmlschema-1-20041028/
  • 回复@老老保老张工:那咋分配呢? 2019-11-17
  • 工信部:鼓励婴幼儿配方乳企质量安全追溯体系建设 2019-11-17
  • 第527期:过年该送健康礼,几点秘籍教给你 2019-11-11
  • 竹编:缝隙里的乡愁文章中国国家地理网 2019-11-11
  • 感触名家笔下的端午文化 吃香粽原来可以这样"文艺" 2019-11-06
  • 人民日报召开习近平新闻思想理论研讨会 2019-10-31
  • 鹏城展翅再高飞(壮阔东方潮 奋进新时代——庆祝改革开放40年) 2019-10-31
  • 财经 —频道 春城壹网 七彩云南 一网天下 2019-10-16
  • 酒后躺车内休息也属于酒驾? 交巡警告诉你这些行为都是酒驾 2019-10-09
  • 新疆阿拉山口口岸严防有害生物入境 2019-10-09
  • 香港多地举办龙舟赛共庆端午节 2019-10-02
  • 河北一保时捷车主疑遭枪击 警方悬赏9万元通缉 2019-10-02
  • 【理上网来·喜迎十九大】党的强军思想指引强军事业 2019-09-24
  • 聚焦机构改革:新部门接连挂牌 快速进入角色 2019-09-11
  • 人民网评:用法律致敬英雄烈士 2019-09-11
  • 北京pk10高手赌法 长期 北京幸运28是正规的吗 半全场胜胜是什么意思 梦想彩票苹果 四川快乐12开奖结果56 好运彩3d 新11选5技巧 11选5任选3胆拖中奖规则 十三水游戏平台 k1彩票网址