DASH-IF Logo

DASH-IF IOP v5 Part 9: Text

Living Document,

This version:
https://dashif.org/Guidelines/iop-v5/part09-text.html
Issue Tracking:
GitHub
Inline In Spec
Currently open Part 9 issues
File a new Part 9 issue (then assign to Part 9 project)
Editor:
Stephan Schreiner (Dolby)
Document Status:
Working Draft 0.1.
See Annex A: Document Status for versioning and workflow.
Contributors:
Contributors are maintained via GitHub pull requests to the IOPv5 repository.
Contributing:
See Part 1 §1.4 Contributing and Reviewing.
Key Words:
Text, Subtitles, Captions, TTML, WebVTT

1. Intellectual Property Rights

1.1. Disclaimer

This is a document made available by DASH-IF. The technology embodied in this document may involve the use of intellectual property rights, including patents and patent applications owned or controlled by any of the authors or developers of this document. No patent license, either implied or express, is granted to you by this document. DASH-IF has made no search or investigation for such rights, and DASH-IF disclaims any duty to do so. The rights and obligations which apply to DASH-IF documents, as such rights and obligations are set forth and defined in the DASH-IF Bylaws and IPR Policy, including but not limited to patent and other intellectual property license rights and obligations. A copy of the DASH-IF Bylaws and IPR Policy can be obtained at https://dashif.org/.

The material contained herein is provided on an "AS IS" basis and, to the maximum extent permitted by applicable law, this material is provided AS IS, and the authors and developers of this material and DASH-IF hereby disclaim all other warranties and conditions, either express, implied, or statutory, including but not limited to any (if any) implied warranties, duties, or conditions of merchantability, of fitness for a particular purpose, of accuracy or completeness of responses, of workmanlike effort, and of lack of negligence.

In addition, this document may include references to documents and/or technologies controlled by third parties. Those third-party documents and technologies may be subject to third-party rules and licensing terms. No intellectual property license, either implied or express, to any third-party material is granted to you by this document or DASH-IF. DASH-IF makes no warranty whatsoever for such third-party material.

Note: IPR declarations relevant to DASH-IF specifications are published at https://dashif.org/ipr-declarations/.

1.2. Modal Verbs Terminology

In the present document, shall, shall not, should, should not, may, need not, will, will not, can, and cannot are to be interpreted as described in the ETSI Drafting Rules (Verbal forms for the expression of provisions). must and must not are NOT allowed in DASH-IF deliverables except when used in direct citation.



2. Introduction

This document specifies DASH-IF IOP v5 Part 9: Text.

The present document defines the CMAF Media Profiles and DASH signalling for text tracks, including subtitles and captions, as well as open captions and subtitles in video tracks. This work is derived from DASH-IF IOP v4.3, but does not include non-CMAF profiles.

This part is under reconciliation against the published DASH-IF IOP v5.0.0 Part 9 FINAL document. See rag/reports/reconcile-part09-text.md for the clause crosswalk and remaining table/reference verification items.

3. Scope

This part defines CMAF media profiles and DASH signalling for text tracks, including subtitles and captions, as well as open captions and subtitles in video tracks.

The use of sidecar text files is not covered in this part.

Note: ETSI TS 103 285 [DVBDASH] (the "DVB-DASH" profile) defines its own subtitle constraints based on EBU-TT-D, a profile of TTML distinct from the IMSC1 profile used in this part. Alignment notes with DVB-DASH are provided in the relevant clauses below.

4. References

The following referenced documents are necessary for the application of this part:

5. Terms and Definitions

5.1. General

Terms and definitions are inherited from ISO/IEC 23009-1, ISO/IEC 23000-19, and Part 2 unless defined in this part.

For the purposes of this part, the following terms apply:

A text adaptation set is an Adaptation Set that contains visual overlay information to be rendered as auxiliary or accessibility information. Such an Adaptation Set is identified by one of:

5.2. Symbols and abbreviations

For the purposes of this part, the following abbreviations apply:

Part 9 abbreviations.
Abbreviation Meaning
CMAF Common Media Application Format
CTA Consumer Technology Association
DASH Dynamic Adaptive Streaming over HTTP
IEC International Electrotechnical Commission
IMSC Internet Media Subtitles and Captions
IOP Interoperability Points
ISO International Organization for Standardization
Kbps Kilobits per second
MPD Media Presentation Description
SEI Supplemental Enhancement Information
VTT Video Text Tracks
XML Extensible Markup Language

6. CMAF Media Profiles

Text CMAF media profiles shall be as defined in [MPEGCMAF] clauses 11, A.4 and A.5, including IMSC, WebVTT, and CTA 608/708. @codecs values for WebVTT and IMSC1 shall be as defined in [ISO14496-30].

CTA 608/708 may be carried in a CMAF video track in SEI messages and does not have a separate @mimeType or @codecs value in a text Adaptation Set. Its presence is signalled using the applicable video file brand and video Adaptation Set descriptors. Only CTA-608 is defined for use here, but it is carried in a CTA-708 DTVCC wrapper and is therefore referred to as CTA-608/708.

CTA 608/708 does not have an independent timing model; it is bound to video frames. To the extent that video is properly groomed for the Period, the CTA 608/708 data is aligned with it.

Open captions and open subtitles are addressed in DASH-IF IOP v5 Part 7, Video [DASHIF-IOP5-PART7].

CMAF Media Profile parameters.
Media Profile File Brand @mimeType @codecs Reference
IMSC1 Text im1t application/mp4 stpp.ttml.im1t [MPEGCMAF]
IMSC1 Image im1i application/mp4 stpp.ttml.im1i [MPEGCMAF]
WebVTT cwvt application/mp4 wvtt [MPEGCMAF]
CTA 608/708 ccea n/a n/a [MPEGCMAF]

Additional non-CMAF text/subtitle profiles are outside the scope of this part and can be found in [DASHIF-IOP43].

Note: DVB-DASH [DVBDASH] mandates EBU-TT-D (a constrained TTML profile defined in ETSI TS 103 285 clause 7, related to EBU Tech 3380) rather than IMSC1 for closed subtitles, and requires the @mimeType="application/ttml+xml" signalling without segmentation into CMAF media segments in some deployment modes. Services that need to serve both DVB-DASH and IMSC1-only players should provide separate Adaptation Sets using each profile, since a DVB-DASH client is not guaranteed to support the IMSC1 profiles defined in this clause.

7. Adaptation Set requirements and recommendations

Text adaptation sets should be annotated using descriptors defined by DASH, specifically Role, Accessibility, EssentialProperty, and SupplementalProperty descriptors.

8. Content requirements

8.1. Text tracks

In addition to the general provisions defined in IOP v5 Part 2, text Adaptation Sets shall comply with the provisions of the following table.

Text track Adaptation Set attributes and elements.
DASH attribute or element Use for media type Detailed usage in DASH-IF IOPs
@mimeType M This shall be set to one of the @mimeType values defined in the CMAF Media Profile table.
@codecs M If @mimeType is set to application/mp4, this attribute shall be present and set to one of the @codecs values defined in the CMAF Media Profile table.
@lang M The @lang attribute shall be present and set according to DASH language rules. Language is used as the primary selection mechanism based on user preference.
Accessibility 0 … N If the text track is closed captions, an Accessibility descriptor shall be present with @schemeIdUri="urn:mpeg:dash:role:2011" and @value="caption".
Role 0 … N Role descriptors may be present depending on the nature of the text. Subtitle tracks should use @value="subtitle". Closed-caption tracks shall use @value="caption". Text tailored to beginning readers shall use @value="easyreader" when signalled.

Note: DVB-DASH [DVBDASH] additionally requires downloadable-font signalling for EBU-TT-D subtitle tracks using the DVB-DASH-specific urn:dvb:dash:fontdownload:2014 Supplemental/Essential Property descriptor, which has no direct equivalent in the IMSC1/WebVTT-based signalling defined in this part. Services offering EBU-TT-D subtitles with embedded fonts for DVB-DASH compatibility should consult ETSI TS 103 285 clause 7 for the complete font-download signalling requirements.

Text Adaptation Sets containing alternative content shall differ by at least one of the following annotation labels:

8.2. Video tracks

In addition to text tracks, CTA 608/708 captions can be carried in video tracks. This can be done by open subtitles or open captions coded into video pixels, or by carrying closed captions in video SEI messages according to [SCTE128-1]. This section addresses closed captions in video SEI messages.

Video track Adaptation Set attributes and elements for text-related signaling.
DASH attribute or element Use for media type Detailed usage in DASH-IF IOPs
Accessibility 0 … N If the video Adaptation Set contains CTA 608/708 closed captions, this element shall be present and used as defined by DASH and [SCTE214-1] caption-service signalling. For other uses of Accessibility with a video track, including open captions and open subtitles, see DASH-IF IOP v5 Part 7 [DASHIF-IOP5-PART7].

Since this is a video Adaptation Set, @mimeType and @codecs are set according to the video codec.

9. CEA-608/708 Digital Television (DTV) Closed Captioning

This clause defines requirements for interoperable use of CEA-608/708 Digital Television (DTV) Closed Captioning in DASH presentations.

Note: This clause is compatible with SCTE specification DVS 1208 and therefore SCTE URNs are used for the descriptor @schemeIdUri.

CEA-608/708 captions shall be carried in SEI messages embedded in Representations of a video Adaptation Set, with the encapsulation as defined in SCTE 128-1, section 8.1.

Every Representation in the video Adaptation Set shall have identical CEA-608/708 captions. Both CEA-608 and CEA-708 may be present simultaneously in the same video Adaptation Set.

The presence of CEA-608/708 captions shall be signaled by an Accessibility descriptor on the Adaptation Set level, with @schemeIdUri="urn:scte:dash:cc:cea-608:2015" or @schemeIdUri="urn:scte:dash:cc:cea-708:2015", with an optional @value.

When present for CEA-608 captions, the @value of this descriptor shall describe the caption streams and languages in conformance to the ABNF below.

@value          = (channel *3 [";" channel]) / (language *3[";" language])
channel         = channel-number "=" language
channel-number  = CC1 | CC2 | CC3 | CC4
language        = 3ALPHA ; language code per ISO 639.2/B

Two variants of @value syntax for CEA-608 are described above: a variant with plain language codes and a variant with caption channel numbers. Services should use the variant with channel numbers.

When there is only a single caption channel present, the language-only form may be used.

When more than one caption channel is present, the language-only form should not be used.

Note: This part does not provide the @value syntax for CEA-708.

Signaling of presence of CEA-608 closed caption service in English and Spanish:
<Accessibility schemeIdUri="urn:scte:dash:cc:cea-608:2015" value="CC1=eng;CC3=spa"/>

10. Timed Text (IMSC1)

This clause defines requirements for using IMSC1 text in DASH presentations.

W3C TTML and its various profiles — W3C IMSC1 text and image profiles, SMPTE Timed Text, and EBU Timed Text — provide a rich feature set for text tracks. Beyond basic subtitles and closed captioning, graphics-based subtitles and closed captioning are also supported by IMSC1.

Many clients only implement a subset of IMSC1. The exact feature sets used by clients and services may need careful alignment to ensure mutual compatibility. Do not assume that all of IMSC1 is supported by typical clients.

Conversion of CEA-608 and CEA-708 into IMSC1 shall be done according to SMPTE 2052-10 [SMPTE2052-10] and SMPTE 2052-11 [SMPTE2052-11], respectively.

One of the following storage formats shall be used for IMSC1 Representations:

The ISO BMFF encapsulated form should be used, as stand-alone XML file storage has significant limitations.

The signaling in the MPD shall conform to the below table.

IMSC1 signaling parameters.
Codec Storage @mimeType @codecs
IMSC1 Timed Text Stand-alone XML file application/ttml+xml See W3C TTML Profile Registry
IMSC1 Timed Text ISO BMFF encapsulation application/mp4

11. Chunks and gaps

Text is low bitrate, but has different characteristics compared to audio. In particular, for IMSC1 there is typically only one sample/document in each segment. Text should not be chunked but delivered as separate segments/documents.

Even with short segment duration, encoders shall conform to the IMSC1 Hypothetical Render Model (HRM), applied inter-segment.

When a text track contains a period of no content, continuous segments shall still be present and shall contain the empty document as defined in ISO/IEC 14496-30.

12. Client recommendations

It is expected that DASH clients conforming to this IOP recognize the descriptors, elements, attributes, and values documented in the text-track and video-track Adaptation Set tables.

If caption or subtitle text rendering is enabled, the client selects text Adaptation Sets as follows:

  1. Any text Adaptation Set for which an EssentialProperty descriptor is present and for which the scheme or value is not understood by the DASH client is excluded from the selection.

  2. Any text Adaptation Set for which the client does not have a decoder, such as CTA 608/708, IMSC1, or WebVTT, is excluded from the selection.

  3. If text language preference settings are provided to the client by the system, any Adaptation Set for which @lang is absent, null, or set to und is excluded from the selection, and any Adaptation Set that is not in the preferred text language is excluded from the selection.

  4. Any text Adaptation Set with one or more Role descriptors using @schemeIdUri="urn:mpeg:dash:role:2011" where none of the @value values is described in this part is excluded from the selection.

  5. If multiple text Adaptation Sets remain, the one with the highest @selectionPriority value is chosen.

  6. If multiple text Adaptation Sets remain after the above steps, the DASH client makes a choice for itself.

Note: Text in video tracks does not affect video-track selection.

13. Requirements and Recommendations

The above clauses reconcile the initial Part 9 Bikeshed source with the published DASH-IF IOP v5.0.0 Part 9 FINAL structure. The CMAF media-profile, text-track Adaptation Set, and video-track Adaptation Set table values have been checked against the extracted published text. Remaining migration work is to review generated HTML against the published DOCX/PDF for table formatting, confirm final citation policy for local bibliography aliases, and link testable requirements to Part 12 conformance mapping. [GROUNDED_BY=rag/corpus/published/DASH-IF-IOPv5.0.0-Part9-FINAL.docx.extracted.txt]

14. Open Issues and Work Items

Part 9 open issues and topics to progress.
Topic Status Next action
Published v5.0.0 reconciliation Source-level check complete Initial structure, core requirements, and extracted table values have been checked against rag/reports/reconcile-part09-text.md; generated HTML still needs visual review against the published DOCX/PDF.
Reference mapping In progress Bibliographic aliases exist and SMPTE 2052 aliases are now cited. Confirm final citation policy for ISO/IEC 14496-30, SCTE 214-1, IMSC1/TTML, DASH-IF IOP v4.3, Part 7 Video, and SMPTE 2052 references.
Cross-part alignment Open Align terminology and references with Parts 1, 2, 7, and 12.
Conformance mapping Open Identify validator/test-asset/reference-player expectations and link them to Part 12.

15. Change History

Part 9 change history.
Version Date Change
0.1 Initial Created initial Bikeshed/Markdown shell for Part 9.
0.2 Migration Migrated CEA-608/708 and IMSC1 text codec clauses from DASH-IF-IOP v5-old-draft.
0.3 Reconciliation Added published DASH-IF IOP v5.0.0 Part 9 FINAL structure, CMAF media-profile table, adaptation-set requirements, chunks/gaps, and client recommendations.
0.4 Reconciliation Verified initial source against extracted published Part 9 text and connected SMPTE 2052 references used by the IMSC1 conversion requirement.
0.5 Reconciliation Completed source-level verification of extracted published table values for CMAF media profiles and text/video Adaptation Set signalling.
5.0.0 2022-01-04 Version published as Part 9 v5.0.0.

Index

Terms defined by this specification

References

Normative References

[ISO14496-30]
Information technology - Coding of audio-visual objects - Part 30: Timed text and other visual overlays in ISO base media file format.
[MPEGCMAF]
Information technology - Multimedia application format (MPEG-A) - Part 19: Common media application format (CMAF) for segmented media. 2024. URL: https://www.iso.org/standard/85623.html
[MPEGDASH]
Information technology - Dynamic adaptive streaming over HTTP (DASH) - Part 1: Media presentation description and segment formats. 2022. URL: https://www.iso.org/standard/83314.html
[SCTE214-1]
MPEG DASH for IP-Based Cable Services Part 1: MPD Constraints and Extensions.

Non-Normative References

[CTA608-E]
Line 21 Data Services.
[CTA708-E]
Digital Television (DTV) Closed Captioning.
[DASHIF-IOP43]
DASH-IF Interoperability Points v4.3. URL: https://dashif.org/guidelines/earlier-versions/
[DASHIF-IOP5-PART7]
DASH-IF IOP v5 Part 7: Video. URL: https://dashif.org/guidelines/iop-v5#part-7-video
[DVBDASH]
ETSI TS 103 285: MPEG-DASH Profile for Transport of ISO BMFF Based DVB Services over IP Based Networks. 2024. URL: https://www.etsi.org/standards-search
[IMSC1]
TTML Profiles for Internet Media Subtitles and Captions 1.0.1 (IMSC1).
[SCTE128-1]
AVC Video Constraints for Cable Television Part 1 - Coding. 2020.
[SMPTE2052-10]
Conversion from CEA-608 Data to SMPTE-TT.
[SMPTE2052-11]
Conversion from CEA-708 Caption Data to SMPTE-TT.
[WEBVTT]
WebVTT: The Web Video Text Tracks Format.

Issues Index

This part is under reconciliation against the published DASH-IF IOP v5.0.0 Part 9 FINAL document. See rag/reports/reconcile-part09-text.md for the clause crosswalk and remaining table/reference verification items. ↵
The above clauses reconcile the initial Part 9 Bikeshed source with the published DASH-IF IOP v5.0.0 Part 9 FINAL structure. The CMAF media-profile, text-track Adaptation Set, and video-track Adaptation Set table values have been checked against the extracted published text. Remaining migration work is to review generated HTML against the published DOCX/PDF for table formatting, confirm final citation policy for local bibliography aliases, and link testable requirements to Part 12 conformance mapping. [GROUNDED_BY=rag/corpus/published/DASH-IF-IOPv5.0.0-Part9-FINAL.docx.extracted.txt] ↵