Manifest and Metadata Validator

The Manifest and Metadata Validator will check the validity of a 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).




Current Release

  • Version 1.4, August 8, 2018

    This release of the desktop Maniufest Validation tool has been upgraded to use the latest mddf-lib release. Detailed Change Log is on GitHub here. Additional changes include the following:

    • Manifest validation incorrectly flagged AppGroup and Interactive elements as unreferenced.

Online Validator

Release History

Release history can be found here.

Source Code

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


The Validator is intended to ensure a Media Manifest is 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.


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 Media Manifest Schema (i.e., does the Manifest 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.

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

Common Media Manifest Validation

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

Compliance with the following is determined