DASH-IF Logo

DASH-IF IOP v5 Part 12: Conformance and Reference Tools

Living Document,

This version:
https://dashif.org/Guidelines/iop-v5/part12-conformance-reference-tools.html
Issue Tracking:
GitHub
Inline In Spec
Currently open Part 12 issues
File a new Part 12 issue (then assign to Part 12 project)
Editors:
Daniel Silhavy (Fraunhofer FOKUS)
Thomas Stockhammer (Qualcomm)
Document Status:
Working Draft 0.6.
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:
Conformance, Reference Tools, Validator, dash.js, livesim2, Test Assets

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. Scope

The present document provides an overview of the DASH-IF reference and conformance tools. In particular, it introduces the conformance software used to verify service offerings, the dash.js reference client, the livesim2 live source simulator, and the DASH-IF test assets. It also describes how conformance keywords used across the IOP parts are interpreted by these tools.

Any identified bugs or missing features may be submitted through the DASH-IF IOPv5 issue tracker at https://github.com/Dash-Industry-Forum/IOPv5/issues. Use the label Part 12 or the title prefix [Part 12]: to associate the issue with this part. For issues related to other parts, use the corresponding label or prefix (e.g. [Part 2]:, [Part 4]:).

3. Terms and Definitions

DASH-IF Conformance Validator

The DASH-IF open-source software that validates DASH Media Presentations (MPD, MPD updates, and Segment formats) against the requirements and recommendations of a DASH profile.

dash.js

The DASH-IF JavaScript reference client for MPEG-DASH playback in browser environments supporting Media Source Extensions (MSE) and Encrypted Media Extensions (EME).

livesim2

The second-generation DASH-IF live source simulator, which generates a wall-clock-synchronized, effectively infinite live stream by looping VoD DASH assets and rewriting timestamps.

4. Conformance Interpretations

4.1. Introduction

This clause provides guidance on the contextual interpretation of the conformance terms shall, shall not, should, should not, and may, beyond what is described in the ETSI Drafting Rules, in terms of how the DASH-IF tools treat each keyword.

4.2. Content Authoring

Where an IOP document associates a conformance keyword with a content-authoring statement, the following applies:

4.3. Client Processing

Where an IOP document associates a conformance keyword with DASH client behaviour, the following applies:

5. Conformance and Reference Tools

5.1. Overview

DASH-IF leads the development of testing tools that support the development and deployment of interoperable DASH-based streaming. These tools are publicly available for community use and contribution, and are hosted under https://github.com/Dash-Industry-Forum.

An implementor or service provider for DASH Media Presentations is encouraged to use the DASH-IF Conformance Validator to verify that a service conforms to the requirements indicated by the Media Presentation, and to check playback with the dash.js reference player. An implementor of a DASH client is encouraged to use the relevant test assets for testing. As a necessary condition, test assets must pass DASH-IF conformance validation.

Note: The relationships between the tools are shown in Figure 1.

%%{init: {'theme':'neutral','themeVariables':{'fontSize':'15px','fontFamily':'system-ui, Segoe UI, Arial, sans-serif','lineColor':'#333'},'flowchart':{'curve':'linear','nodeSpacing':55,'rankSpacing':80,'padding':14,'htmlLabels':true,'useMaxWidth':true,'wrappingWidth':200}}}%%
flowchart LR
    CA["Content author / service provider"] --> V["DASH-IF Conformance Validator"]
    V -->|errors / warnings| CA
    TA[Test assets] --> V
    TA --> P[dash.js reference player]
    LS[livesim2 live source simulator] --> P
    LS --> V
    P -->|playback verification| DEV["Client / player developer"]
    classDef box fill:#eef3f8,stroke:#33475b,stroke-width:1.4px,color:#1a2733;
    class CA,V,TA,P,LS,DEV box;
DASH-IF conformance and reference tools and their relationships.

5.2. Conformance Validator

The DASH-IF Conformance Validator validates DASH Media Presentations against the requirements and recommendations of a DASH profile. It covers the MPD (and MPD updates) as well as the Segment formats, reporting expected and unexpected behaviour observed in a Media Presentation that claims conformance to one or more profiles. It therefore provides a test and validation environment for content providers, service providers, and player developers.

Development of the validator began after the first edition of MPEG-DASH [MPEGDASH] and has been continuously updated for new features and newer editions of the supported standards. It is open-source software, available on GitHub at https://github.com/Dash-Industry-Forum/DASH-IF-Conformance, and is hosted by DASH-IF at https://conformance.dashif.org.

5.3. Reference Player: dash.js

dash.js is a free, open-source MPEG-DASH player that serves as the JavaScript reference client for implementing production-grade DASH players. It relies on HTML5 media, Media Source Extensions (MSE) with the ISO BMFF byte-stream format, and Encrypted Media Extensions (EME) as defined by the W3C.

It is available on GitHub at https://github.com/Dash-Industry-Forum/dash.js and as an npm module (dashjs). Current entry points include:

dash.js is released under the BSD licence, and issues are raised on GitHub. Sample streams are included in a drop-down menu in the sample reference UI and serve as inputs for implementing and verifying features.

5.4. Live Source Simulator: livesim2

livesim2 is the second-generation DASH-IF live source simulator (superseding the original livesim). It produces a wall-clock (UTC) synchronized, effectively infinite linear stream of segments by looping input VoD DASH assets and rewriting timestamps, so that an asset of duration D restarts every D relative to the epoch. It is written in Go and compiles to a single binary that serves content over a built-in HTTP/2 server, with optional automatic HTTPS via Let’s Encrypt.

It is available on GitHub at https://github.com/Dash-Industry-Forum/livesim2 and hosted by DASH-IF at https://livesim2.dashif.org.

Notable characteristics relevant to conformance testing:

Note: Input VoD assets must be in the isoff-live profile (individual segment files) using either SegmentTimeline with $Time$ or SegmentTemplate with $Number$, with additional constraints on segment-duration regularity.

5.5. Test Assets and Test Cases

Test assets are essential to ensure large-scale interoperability. DASH-IF maintains a Test Assets Database of test vectors covering a wide variety of features — static and dynamic Media Presentations, on-demand and live services, different media components and codecs, DRM protection, single- and multi-period presentations, text tracks, captions and subtitles, and ad insertion.

The Test Assets Database is open source, split into a user-interface project and a backend dataset:

It is hosted by DASH-IF at https://testassets.dashif.org. As a necessary condition, test assets must pass DASH-IF conformance validation.

Note: CTA-WAVE test content is a common companion asset set and can be fetched with dashfetcher; see livesim2.

5.6. Active local validator-start coverage

The following local MPD-level validator-start tools and fixtures are maintained as implementation scaffolding for the current IOP v5 migration. These tools do not replace the DASH-IF Conformance Validator; they provide deterministic local checks and fixtures that can be promoted into the formal validator and test-asset workflow.

Local validator-start coverage for active migration parts.
Part Validator-start tool Fixture root Planning/report reference Runtime dependency
Part 2 Core CMAF tools/validation/validate_part2_core_cmaf_mpd.py specs/part02-core-cmaf/examples/ rag/reports/part02-core-cmaf-conformance-plan.md Segment parser for CMAF brands, chunks, and switching constraints.
Part 3 On-Demand tools/validation/validate_part3_on_demand_mpd.py specs/part03-on-demand/examples/ rag/reports/part03-on-demand-conformance-plan.md dash.js seek and random-access playback checks.
Part 4 Live and Low-Latency tools/validation/validate_part4_live_mpd.py specs/part04-live-low-latency/examples/ rag/reports/part04-live-low-latency-conformance-plan.md livesim2 deterministic live streams and dash.js live-edge behavior checks.
Part 5 Ad Insertion tools/validation/validate_part5_scte35_events.py; tools/validation/validate_part5_ad_content_mpd.py; tools/validation/validate_part5_if5_spliced_mpd.py specs/part05-ad-insertion/examples/ rag/reports/part05-f0010-test-vector-inventory.md; rag/reports/part05-f0010-next-implementation-batch.md dash.js playback, livesim2 SGAI, and Part 6 EME/DRM coverage.
Part 9 Text tools/validation/validate_part9_text_mpd.py specs/part09-text/examples/ rag/reports/part09-f0009-test-vector-inventory.md Segment parser and dash.js rendering/selection behavior checks.

The roll-up dashboard for this local validator-start coverage is maintained in rag/reports/conformance-validator-start-dashboard.md.

5.7. Issue Tracking and Coordination

DASH-IF maintains public issue trackers on GitHub for the IOP and the individual tools; new work for IOP v5 is tracked at https://github.com/Dash-Industry-Forum/IOPv5/issues, and each reference tool uses the issue tracker of its own repository.

DASH-IF coordinates with other organizations and open-source projects to support interoperable DASH deployment, including DVB, CTA WAVE, MPEG, ATSC, W3C, and 3GPP, as well as projects such as FFmpeg and GPAC.

5.8. The Desired Approach for Interoperability

Effective interoperability balances good specifications, test and conformance tools, reference implementations, open-source software, and lessons learned from deployments. As a general model, a new feature is first added to a draft IOP document (possibly by reference to or collaboration with the organization owning a referenced specification, e.g. MPEG), then supported by test content, the conformance validator, and the reference player, and finally — once all pieces are complete — promoted to a fully supported feature. Intermediate steps may involve one or more community-review rounds.

6. Change History

Part 12 change history.
Version Date Change
0.1 Initial Migrated from the Part 12 draft; reference-tool sections updated to current dash.js and the second-generation livesim2 (CMAF Ingest, SGAI, stateless URL parameters).
0.2 Reconciliation Added initial Part 9 text-track conformance mapping for CMAF text profiles, text/video Adaptation Set signalling, CTA 608/708, IMSC1, chunks/gaps, and client selection.
0.3 Reconciliation Added initial Part 5 ad-insertion conformance mapping covering IF-3 through IF-9 validator, dash.js, livesim2, and test-asset expectations.
0.4 Reconciliation Added initial Part 2 core CMAF and timing model conformance mapping (10 features: Period timing, segment addressing, clock sync, availability window, MPD updates, period connectivity, timing constraints, forbidden techniques, segment loss, stand-alone text). Added initial Part 4 live service conformance mapping (5 features: dynamic service requirements, MPD snapshot validity, segment-based updates, UTCTiming, live client joining).
0.5 Reconciliation Added initial Part 3 on-demand service conformance mapping (6 features: static presentation requirements, determinable duration, full period coverage, on-demand profile, wall-clock-independent availability, multi-Period on-demand).
0.6 Reconciliation Added initial Part 7 video conformance mapping (6 features: adaptation set signalling, color space, H.264/AVC, H.265/HEVC, Codec Registry compliance, scan type). Added initial Part 8 audio conformance mapping (5 features: adaptation set signalling, HE-AACv2, E-AC-3/AC-4 AudioChannelConfiguration, MPEG-H 3D Audio, Codec Registry compliance).

7. Conformance Mapping

7.1. Overview

This clause provides initial conformance mapping tables for each IOP v5 part, identifying test and validation expectations for the DASH-IF Conformance Validator, dash.js reference player, and DASH-IF Test Assets Database. These tables are starting points for issue creation and test-asset planning.

7.2. Initial Part 2 core CMAF and timing model conformance mapping

The following initial mapping identifies test and validation expectations for DASH-IF IOP v5 Part 2 core CMAF and timing model requirements. This table is a starting point for issue creation and test-asset planning; it does not by itself define new Part 2 requirements.

Initial Part 2 core CMAF and timing model conformance mapping.
Part 2 feature Primary validation target Reference/test asset expectation
Period timing (zero-duration, first/last period rules) The DASH-IF Conformance Validator checks that no Period has zero duration, that the first Period in a static presentation starts at 0, and that the last Period in a static presentation has Period@duration. Test assets should include static and dynamic presentations with correct Period timing, plus negative cases for zero-duration Periods and missing Period@duration on the last static Period.
Segment addressing modes (SegmentBase, SegmentTemplate, SegmentTimeline) The validator checks that @timescale is present, that all Representations in an Adaptation Set use the same addressing mode, and that SegmentTimeline S elements are consistent with @t, @d, and @r. Test assets should cover all three addressing modes (indexed, explicit, simple) with correct and incorrect @timescale values, mixed-mode Adaptation Sets (negative), and SegmentTimeline gaps.
Clock synchronization (UTCTiming) The validator checks that dynamic presentations include at least one UTCTiming element using a permitted scheme (http-xsdate, http-iso, http-head, direct). Test assets should include dynamic presentations with each permitted UTCTiming scheme and a negative case with no UTCTiming element.
Availability window and time shift buffer The validator checks MPD@timeShiftBufferDepth presence and consistency with @availabilityTimeOffset values; checks that MPD@suggestedPresentationDelay does not result in a zero or negative effective time shift buffer. Test assets should include dynamic presentations with various timeShiftBufferDepth and suggestedPresentationDelay combinations, including boundary cases.
MPD updates (minimumUpdatePeriod, publishTime) The validator checks that MPD@publishTime is present in dynamic presentations and that MPD@minimumUpdatePeriod is consistent with the announced segment timeline. Test assets (via livesim2) should include MPD-controlled live services with regular MPD updates, end-of-live signalling (removal of minimumUpdatePeriod), and live-to-VoD conversion.
Period connectivity and continuity signalling The validator checks that period-connectivity and period-continuity descriptors (urn:mpeg:dash:period-connectivity:2015, urn:mpeg:dash:period-continuity:2015) are not simultaneously present on the same Representation, and that AdaptationSet@id values match across connected Periods. Test assets should include multi-Period presentations with period-connected and period-continuous Adaptation Sets, including negative cases for conflicting signalling.
Timing constraints (timescale, xs:duration) The validator checks that no timescale or timestamp value exceeds 253, and that xs:duration fields do not use year or month units. Test assets should include presentations with 90 KHz and other common timescales, plus negative cases with oversized timescale values and year/month duration units.
Forbidden techniques (@presentationDuration, @availabilityTimeComplete) The validator checks that @presentationDuration and @availabilityTimeComplete are absent from all MPD elements. Test assets should include negative cases with these forbidden attributes present.
Segment loss handling (no missing content segments) The validator checks that no Period signals "missing content segments" per [MPEGDASH] clause 6.2.6. Test assets should include multi-Period presentations that correctly handle representation gaps via Period splitting, and negative cases with missing segment signalling.
Stand-alone text track timing (@presentationTimeOffset absent) The validator checks that stand-alone IMSC1/WebVTT Representations do not carry @presentationTimeOffset. Test assets should include stand-alone text track Representations with and without @presentationTimeOffset (negative case).

This Part 2 mapping is an initial source-level conformance inventory. It should be reconciled with actual DASH-IF Conformance Validator coverage, dash.js sample coverage, and the DASH-IF Test Assets Database before being treated as a complete conformance plan. The corresponding local validator-start tool is tools/validation/validate_part2_core_cmaf_mpd.py.

7.3. Initial Part 3 on-demand service conformance mapping

The following initial mapping identifies test and validation expectations for DASH-IF IOP v5 Part 3 on-demand service requirements. This table is a starting point for issue creation and test-asset planning; it does not by itself define new Part 3 requirements.

Initial Part 3 on-demand service conformance mapping.
Part 3 feature Primary validation target Reference/test asset expectation
Static presentation requirements (MPD@type="static", no minimumUpdatePeriod) The DASH-IF Conformance Validator checks that MPD@type="static" presentations do not carry MPD@minimumUpdatePeriod, MPD@timeShiftBufferDepth, or MPD@suggestedPresentationDelay. Test assets should include static presentations with and without the forbidden dynamic attributes (negative cases).
Determinable presentation duration The validator checks that the total presentation duration is determinable from MPD@mediaPresentationDuration or from the sum of Period durations (last Period must have Period@duration). Test assets should include static presentations with explicit mediaPresentationDuration, with implicit duration from Period structure, and a negative case where the last Period lacks Period@duration.
Full period coverage with media segments The validator checks that every Representation in a static presentation provides enough Media Segments to cover the entire time span of its Period. Test assets should include presentations where all Representations fully cover their Periods, plus negative cases with gaps or under-coverage.
On-demand profile (@indexRange, single sidx) The validator checks that Representations using the DASH-IF On-Demand profile carry SegmentBase@indexRange and that only a single sidx box is present. Test assets should include on-demand profile Representations with correct indexRange signalling and negative cases with missing indexRange or multiple sidx boxes.
Segment availability independent of wall clock The validator checks that static presentations do not use @availabilityStartTime-dependent segment availability (i.e., all segments are immediately available). Test assets should include static presentations served from standard HTTP origins without time-gated availability.
Multi-Period on-demand (mixed profile) The validator checks that multi-Period static presentations have explicit Period timing and that period-connected Adaptation Sets are correctly signalled per Part 2. Test assets should include multi-Period on-demand presentations with period-connected and period-disconnected transitions, covering chapter-based and ad-insertion scenarios.

This Part 3 mapping is an initial source-level conformance inventory. It should be reconciled with actual DASH-IF Conformance Validator coverage, dash.js seek/random-access sample coverage, and the DASH-IF Test Assets Database before being treated as a complete conformance plan. The corresponding local validator-start tool is tools/validation/validate_part3_on_demand_mpd.py.

7.4. Initial Part 4 live service conformance mapping

The following initial mapping identifies test and validation expectations for DASH-IF IOP v5 Part 4 live and low-latency service requirements. This table is a starting point for issue creation and test-asset planning.

Initial Part 4 live service conformance mapping.
Part 4 feature Primary validation target Reference/test asset expectation
Dynamic service requirements (MPD@type, availabilityStartTime, publishTime) The DASH-IF Conformance Validator checks that MPD@type="dynamic" presentations include MPD@availabilityStartTime and MPD@publishTime. Test assets (via livesim2) should include dynamic presentations with all mandatory attributes and negative cases with missing availabilityStartTime or publishTime.
MPD snapshot validity and content add/remove rules The validator checks that minimumUpdatePeriod is consistent with the segment timeline, that segment references are not added to non-last Periods, and that expired segment references are removed per the EarliestRemovalPoint algorithm. livesim2 test streams should exercise MPD update cycles including content addition, expiry removal, and end-of-live signalling.
Segment-based MPD update signalling (InbandEventStream) The validator checks that InbandEventStream is signalled for Adaptation Sets carrying MPD validity expiry events. Test assets should include segment-based MPD update streams with urn:mpeg:dash:event:2012 events and corresponding InbandEventStream signalling.
Clock synchronization (UTCTiming scheme restriction) The validator checks that only permitted UTCTiming schemes are used (http-xsdate, http-iso, http-head, direct) and that at least one is present in dynamic presentations. Test assets should cover each permitted scheme and a negative case with a non-permitted scheme.
Live client joining and presentation delay dash.js exercises live-edge detection, suggestedPresentationDelay usage, and initial buffer fill before playout. livesim2 test streams should include presentations with and without suggestedPresentationDelay, covering normal join, late join, and seek-to-live-edge scenarios.

This Part 4 mapping is an initial source-level conformance inventory. It should be reconciled with actual DASH-IF Conformance Validator coverage, dash.js live-service sample coverage, and livesim2 test stream coverage before being treated as a complete conformance plan. The corresponding local validator-start tool is tools/validation/validate_part4_live_mpd.py.

7.5. Initial Part 7 video conformance mapping

The following initial mapping identifies test and validation expectations for DASH-IF IOP v5 Part 7 video requirements. This table is a starting point for issue creation and test-asset planning; it does not by itself define new Part 7 requirements.

Initial Part 7 video conformance mapping.
Part 7 feature Primary validation target Reference/test asset expectation
Video adaptation set signalling (@par, @sar, @width, @height, @frameRate) The DASH-IF Conformance Validator checks that AdaptationSet@par, Representation@sar, and either @width/@height/@frameRate at adaptation set or Representation level (but not both) are present in video adaptation sets. Test assets should include video adaptation sets with correct and incorrect signalling of @par, @sar, @width, @height, and @frameRate.
Color space signalling (Color Primaries, Transfer Characteristics, Matrix Coefficients) The validator checks that Representations in the same video adaptation set do not differ in Color Primaries, Transfer Characteristics, or Matrix Coefficients, and that CICP descriptors are present when different adaptation sets use different color spaces. Test assets should include SDR and HDR video adaptation sets with correct CICP descriptor signalling.
H.264/AVC codec signalling (avc1/avc3, @codecs, SPS/PPS storage) The validator checks that H.264 Representations use permitted @codecs strings, that all Initialization Segments in the same adaptation set use the same sample description, and that bitstream-switching adaptation sets use avc3. Test assets should include H.264 Representations with avc1 and avc3 sample descriptions, correct @codecs strings, and bitstream-switching adaptation sets.
H.265/HEVC codec signalling (hvc1/hev1, @codecs, VPS/SPS/PPS storage) The validator checks that H.265 Representations use permitted @codecs strings, that all Initialization Segments in the same adaptation set use the same sample description, and that bitstream-switching adaptation sets use hev1. Test assets should include H.265 Representations with hvc1 and hev1 sample descriptions, correct @codecs strings, and bitstream-switching adaptation sets.
DASH-IF Codec Registry compliance The validator checks that @codecs strings for video Representations are registered in the DASH-IF Codec Registry (https://dashif.org/codecs/). Test assets should include Representations with registered and unregistered @codecs strings (negative cases).
Scan type (@scanType="progressive") The validator checks that @scanType is absent or has the value progressive. Test assets should include a negative case with @scanType="interlaced".

This Part 7 mapping is an initial source-level conformance inventory. It should be reconciled with actual DASH-IF Conformance Validator coverage, dash.js sample coverage, and the DASH-IF Test Assets Database before being treated as a complete conformance plan.

7.6. Initial Part 8 audio conformance mapping

The following initial mapping identifies test and validation expectations for DASH-IF IOP v5 Part 8 audio requirements. This table is a starting point for issue creation and test-asset planning; it does not by itself define new Part 8 requirements.

Initial Part 8 audio conformance mapping.
Part 8 feature Primary validation target Reference/test asset expectation
Audio adaptation set signalling (@lang, @audioSamplingRate, AudioChannelConfiguration) The DASH-IF Conformance Validator checks that AdaptationSet@lang is present on every audio adaptation set, that @audioSamplingRate is present at adaptation set or Representation level (but not both), and that AudioChannelConfiguration is present with a valid @schemeIdUri. Test assets should include audio adaptation sets with correct and incorrect signalling of @lang, @audioSamplingRate, and AudioChannelConfiguration.
HE-AACv2 codec signalling (mp4a.40.2, mp4a.40.5, mp4a.40.29) The validator checks that HE-AACv2 Representations use permitted @codecs strings and SAP type 1. Test assets should include HE-AACv2 stereo and multichannel Representations with correct @codecs strings.
Enhanced AC-3 / AC-4 AudioChannelConfiguration scheme The validator checks that E-AC-3 and AC-4 Representations use @schemeIdUri="tag:dolby.com,2014:dash:audio_channel_configuration:2011" for AudioChannelConfiguration. Test assets should include E-AC-3 and AC-4 Representations with correct and incorrect AudioChannelConfiguration signalling.
MPEG-H 3D Audio constraints (mhm1.*, MHADecoderConfigurationRecord) The validator checks that MPEG-H Representations use permitted @codecs strings and that each Media Segment starts with a SAP of type 1. Test assets should include MPEG-H 3D Audio Representations at LC Profile Levels 1, 2, and 3.
DASH-IF Codec Registry compliance The validator checks that @codecs strings for audio Representations are registered in the DASH-IF Codec Registry (https://dashif.org/codecs/). Test assets should include Representations with registered and unregistered @codecs strings (negative cases).

This Part 8 mapping is an initial source-level conformance inventory. It should be reconciled with actual DASH-IF Conformance Validator coverage, dash.js sample coverage, and the DASH-IF Test Assets Database before being treated as a complete conformance plan.

7.7. Initial Part 9 text-track conformance mapping

The following initial mapping identifies test and validation expectations for DASH-IF IOP v5 Part 9 text, caption, and subtitle requirements. This table is a starting point for issue creation and test-asset planning; it does not by itself define new Part 9 requirements.

Initial Part 9 conformance mapping.
Part 9 feature Primary validation target Reference/test asset expectation
CMAF text media profiles The DASH-IF Conformance Validator checks MPD @mimeType, @codecs, and CMAF brand/profile consistency where the required information is available. Test assets should include IMSC1 Text (im1t / stpp.ttml.im1t), IMSC1 Image (im1i / stpp.ttml.im1i), WebVTT (cwvt / wvtt), and CTA 608/708 carried in video.
Text-track Adaptation Set signalling The validator checks @mimeType, @codecs, @lang, Accessibility, and Role usage for text Adaptation Sets. Test assets should cover subtitle, caption, and easy-reader signalling, including multiple alternative text Adaptation Sets that differ by language, role, accessibility, or codec.
CTA 608/708 in video tracks The validator checks the presence and syntax of the video Adaptation Set Accessibility descriptor used for CTA 608/708 closed-caption signalling. Test assets should include CEA-608 channel/language signalling such as CC1=eng;CC3=spa, single-language shorthand, and multi-channel cases where the language-only shorthand is not used.
IMSC1 storage and signalling The validator checks MPD signalling for IMSC1 text tracks and the segment/package form where applicable. Test assets should include ISO BMFF encapsulated IMSC1 and, where retained for compatibility, stand-alone XML file delivery.
Chunks and gaps The validator checks that text tracks are not chunked in conflict with Part 9 guidance and that periods without text content still provide continuous segments with empty documents where required. Test assets should include empty-document gaps and short-duration text segments that still conform to the IMSC1 Hypothetical Render Model.
Client text-track selection dash.js and other reference clients exercise language, codec, EssentialProperty, Role, Accessibility, and @selectionPriority based text-track selection. Test assets should include multiple selectable text tracks and negative-selection cases for unsupported descriptors, codecs, or languages.

This Part 9 mapping is an initial source-level conformance inventory. It should be reconciled with actual DASH-IF Conformance Validator coverage, dash.js sample coverage, and the DASH-IF Test Assets Database before being treated as a complete conformance plan. The corresponding issue-ready coverage index is maintained in rag/reports/part09-f0009-issue-index.md.

7.8. Initial Part 5 ad-insertion conformance mapping

The following initial mapping identifies validator, reference-client, livesim2, and test-asset expectations for DASH-IF IOP v5 Part 5 ad insertion. This table is a starting point for F-0010 issue creation and does not by itself define new Part 5 requirements.

Initial Part 5 ad-insertion conformance mapping.
Part 5 feature Primary validation target Reference/test asset expectation
IF-3 opportunity metadata and SCTE-35 MPD Events The DASH-IF Conformance Validator checks DASH EventStream syntax, event timing, @presentationTime, @duration, duplicate-event @id handling where feasible, and SCTE-35 event scheme usage. Test assets should include SCTE-35 MPD Event examples for time_signal() plus segmentation_descriptor(), legacy splice_insert(), early termination, expected-duration correction, and duplicate-event filtering.
IF-4 DASH-IF ad content storage and Table 4 requirements The validator checks ad-content MPD constraints including one static Period, MPD@profiles, absent forbidden timing attributes, Period BaseURL usage, AssetIdentifier, EventStream/InbandEventStream presence, and CMAF profile compatibility. Test assets should include DASH-IF ad content MPDs with multiple codecs/resolutions, Ad-ID and DASH-IF asset identifiers, slate content, and negative cases for forbidden attributes.
IF-5 MPD and segments with ad placements The validator checks multi-Period MPD structure, Period start/duration rules, continuity/connectivity signalling, EventStream splitting/copying, UTCTiming expectations, and ad-content Period insertion constraints where mechanically testable. Test assets should include SSAI multi-Period presentations for exact duration match, ad overrun/truncation, ad underrun/slate insertion, overlapping segment boundaries, and mixed main/ad Periods.
IF-6 ad metadata and DASH Callback Events The validator checks event signalling syntax once the callback event scheme and payload rules are finalized; dash.js samples exercise event dispatch and callback timing. Test assets should include inserted ad Periods with callback metadata aligned to Period and media timelines, including split/truncated ad cases.
IF-7 remote resolution and URL parameter decisioning livesim2 and dash.js exercise Server-Guided Ad Insertion and remote entity / Remote Period resolution; validator checks MPD syntax and remote-reference structure where applicable. Test assets should include SGAI late-binding examples, URL-parameter decisioning, content-conditioning parameters, remote Period resolution, and re-decisioning after seek/rewind.
IF-8 ad tracking and measurement Reference applications and dash.js samples exercise VAST tracking callbacks, Open Measurement SDK integration points, and alternative measurement metadata association. Test assets should include VAST tracking events for impression/start/quartiles/complete and metadata mapping to inserted Periods after splitting or truncation.
IF-9 reference playback and decryption dash.js validates playback behaviour across main/ad transitions using MSE and EME where encrypted assets are provided; validator checks MPD/content-protection signalling. Test assets should include clear and encrypted multi-Period ad insertion cases, key changes at boundaries, compatible CMAF headers, and Part 6-aligned protection signalling.

This Part 5 mapping is an initial source-level conformance inventory. It should be reconciled with actual DASH-IF Conformance Validator coverage, dash.js SGAI/sample coverage, livesim2 SGAI support, and the DASH-IF Test Assets Database before being treated as a complete conformance plan.

M1 synchronization note: execution has started for the Part 5 / F-0010 visual review and validator-start work package. The current M1 checklist is tracked in rag/reports/part05-f0010-m1-visual-validator-start.md.

Initial local validator tools, fixtures, and the explicit fixture inventory are now available for the first three Part 5 validator buckets. The inventory is maintained at rag/reports/part05-f0010-test-vector-inventory.md:

Initial Part 5 validator tool and fixture inventory.
Bucket Validator tool Fixture directory Status
F-0010-A IF-3 SCTE-35 MPD Events tools/validation/validate_part5_scte35_events.py specs/part05-ad-insertion/examples/scte35/ MPD-level checks and initial SCTE-35 command-type parsing implemented.
F-0010-B IF-4 DASH-IF ad content MPD / Table 4 tools/validation/validate_part5_ad_content_mpd.py specs/part05-ad-insertion/examples/table4/ Initial structural checks implemented.
F-0010-C IF-5 spliced-output MPD / Table 5 tools/validation/validate_part5_if5_spliced_mpd.py specs/part05-ad-insertion/examples/table5/ Initial IF-5 multi-Period structural checks implemented.

Remaining Part 5 conformance synchronization items include:

Index

Terms defined by this specification

References

Normative References

[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

Issues Index

This Part 2 mapping is an initial source-level conformance inventory. It should be reconciled with actual DASH-IF Conformance Validator coverage, dash.js sample coverage, and the DASH-IF Test Assets Database before being treated as a complete conformance plan. The corresponding local validator-start tool is tools/validation/validate_part2_core_cmaf_mpd.py. ↵
This Part 3 mapping is an initial source-level conformance inventory. It should be reconciled with actual DASH-IF Conformance Validator coverage, dash.js seek/random-access sample coverage, and the DASH-IF Test Assets Database before being treated as a complete conformance plan. The corresponding local validator-start tool is tools/validation/validate_part3_on_demand_mpd.py. ↵
This Part 4 mapping is an initial source-level conformance inventory. It should be reconciled with actual DASH-IF Conformance Validator coverage, dash.js live-service sample coverage, and livesim2 test stream coverage before being treated as a complete conformance plan. The corresponding local validator-start tool is tools/validation/validate_part4_live_mpd.py. ↵
This Part 7 mapping is an initial source-level conformance inventory. It should be reconciled with actual DASH-IF Conformance Validator coverage, dash.js sample coverage, and the DASH-IF Test Assets Database before being treated as a complete conformance plan. ↵
This Part 8 mapping is an initial source-level conformance inventory. It should be reconciled with actual DASH-IF Conformance Validator coverage, dash.js sample coverage, and the DASH-IF Test Assets Database before being treated as a complete conformance plan. ↵
This Part 9 mapping is an initial source-level conformance inventory. It should be reconciled with actual DASH-IF Conformance Validator coverage, dash.js sample coverage, and the DASH-IF Test Assets Database before being treated as a complete conformance plan. The corresponding issue-ready coverage index is maintained in rag/reports/part09-f0009-issue-index.md. ↵
This Part 5 mapping is an initial source-level conformance inventory. It should be reconciled with actual DASH-IF Conformance Validator coverage, dash.js SGAI/sample coverage, livesim2 SGAI support, and the DASH-IF Test Assets Database before being treated as a complete conformance plan. ↵