Avails Validator

The Avails Validator will check the validity of a Avails file for schema compliance (XSD); Avails spec compliance; and, as applicable, best practices. The users select the specific specifications and best practices and the Validator lists errors (violations of normative requirements) and warnings (values and constructs that seem out of bounds).


Releases

Current Release

  • Version 1.1.2, March 3, 2017
    • Validates XML v2.1 and v2.2
    • Validates Excel v1.6, and v1.7
    • Translates Excel v1.6 and v1.7 to XML v2.2

Validator Source

MDDF Library and the Validator Tool code is available in this GitHub repository: https://github.com/MovieLabs/mddf


Release History

Release history can be found here.


Functionality

The Validator is intended to ensure an Avails is compliant with all applicable specifications relating to a specific defined use (i.e., full season, single movie, etc). Some validation is general (e.g., schema validation) and some validation is specific to a given use. Capabilities include:

  • Validates that one or more Avails files are in conformance with the Avails specification.
  • Optional checks for conformance with applicable best practices or similar guidance.
  • Integrated XML Editor with linkage to any errors or warnings detected.
  • Ability to run in a scripted mode for batch processing of multiple files.

Scope

Validation of conformance with all constraints and requirements specified in the applicable specifications:

  • Schema: Validation of compliance with the Avails Schema (i.e., does the XML comply with the schema XSD).
  • Controlled Vocabulary: Where contwwww.movrolled vocabulary is not defined in the schema, the Validator will ensure correct terms are used. In areas where controlled vocabulary exists but is not strictly enforced, warnings will be issued for nonstandard vocabulary. Ratings controlled vocabulary is also checked.
  • Consistency: This includes checking the internal consistency of the manifest to verify that all internal references are valid.

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 example, checks that an Avails is compatible with a given Manifest (e.g., uses the same ALID values) 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.