MDDF Validator

The MMDF Validator will check the validity of Avails, Cross-Platform Extras (CPE-Manifest), Media Manifest , Media Manifest Core, Common Metadata and Media Entertainment Core (MEC) for schema compliance (XSD); spec compliance; and, as applicable, profiles and best practices. The users select the specific specifications, profiles and best practices and the Validator lists errors (violations of normative requirements) and warnings (values and constructs that seem out of bounds).

Starting with version 1.5, the validator for Avails and validator for Metadata and Manifest functions are combined into the MDDF Validator.


ReleaseS

Current Release

  • Version 1.5, November 20, 2018

    This release combines the two validators (Avails and metadata) into one. It also adds support for Common Metadata 2.7, Media Entertainment Core (MEC) 2.7, Media Manifest v1.8 and Media Maniest Core (MMC) 2.0. Detailed Change Log is on GitHub here.

    Although not unique to this release, the online validator was added since the last release.

Online Validator

Release History

Release history can be found here.


Coverage

Version 1.5

  • Avails
    • Validates XML v2.1, v2.2, and v 2.3
    • Validates Excel v1.6, v1.7, v1.7.2, and 1.7.3
    • Translates between Excel v1.7, v1.7.2, and v1.7.3 to XML v2.2 and v2.3, also translates from Excel v1.6
  • Common Metadata: v2.4 - v2.7
  • Media Entertainment Core (MEC): v2.4 - 2.7
  • Media Manifest: v1.5 - v1.8
  • Media Manifest Core (MMC): v1.0, v2.0
  • CPE-Manifest Profiles: IP-1, IP-01 (against any applicable version of Media Manifest and Common Metadata)

Source Code

Manifest Validator is part of MovieLabs Data Distribution Framework (MDDF). The MDDF Library and Tools is available on GitHub here: https://github.com/MovieLabs/mddf


Functionality

The Validator is intended to ensure failers are compliant with all applicable specifications relating to a specific defined use (i.e., delivery, interactivity, etc). Some validation is general (e.g., schema validation) and some validation is specific to a given use.

Scope

Validation of conformance with all constraints and requirements specified in the applicable specifications. When validating a manifest with this tool, the user may select what level of validation checks will be applied.

  • Schema: Validation of compliance with the schema (i.e., does the XML comply with the schema XSD).
  • Controlled Vocabulary: Where controlled vocabulary is not defined in the schema, the Validator will ensure correct terms are used. In areas where controlled vocabular exists but is not strictly enforced, warnings will be issued for nonstandard vocabulary.
  • Consistency: This includes checking the internal consistency of the manifest to verify that all internal references are valid (e.g., if a PictureGroupID is referenced by an Experience then a PictureGroup with that ID value is also defined).

Some use cases contain constraints specific to particular partners but are not part of the specifications. These are not checked by the Validator. Some examples are as follows:

  • The Validator does not check that the correct media is referenced. For exampel, checks that a given audio or video track is what it supposed to be is outside the scope of the Validator.
  • The Validator does not check that URLs to external links are valid.
  • The Validator does not check limits specific to a particular business, unless those limits are included in the general specifications.

Avails Validation

Compliance with the following is determined

Common Metadata and Media Manifest Validation

As of Version 1.1, validation for Media Manifest Core is supported.

Compliance with the following is determined

CPE-Manifest Validation

This function is used when a Manifest is created for Cross Platform Extras. When selecting an Interactivity Profile (e.g., IP1), the Validator will determine if the file is compliant with the constraints of that Profile.

Compliance with the following is determined