This web page provides on-line access to services that may be used to create, validate, or modify files used in conjunction with the MovieLabs Digital Distribution Framework (MDDF). The services currently provided on-line are:

• validation of all MDDF file types
• translation of MDDF Avails files from XML to XLSX format
• translation of MDDF Avails and Offer Status files from XLSX to XML format
• translation of XML files to newer versions of an MDDF schema
• compression and clean-up of Avails XLSX files

Additional capabilities may be available via the MDDF desktop tool.

To facilitate the automation of digital workflows and supply chain efficiency, MovieLabs has worked with both content providers and retailers to develop a suite of compatible standards and specifications. They cover core aspects of OTT distribution, including identification, metadata, avails, asset delivery, and reporting. Collectively, these standards form the MovieLabs Digital Distribution Framework (MDDF).

Additional information on the MDDF effort, including the latest versions of all the standards and specifications, may be found on the MDDF project's home page.

1. Begin by configuring the service being requested. Use the Configure button to access the Settings Dialog. Depending on the type of file you choose, various service options will be enabled/disabled for the Service , Encoding , and Version settings.
2. The next step is to specify a MDDF files for processing. This may be done by either drag-n-drop onto the Add MDDF File field or by a left-click on the field. In some cases, e.g., the validation of a Media Manifest, additional files may optionally be included (e.g., MEC files referenced by the Manifest).
3. Use the Run button to initiate processing. When processing is completed, the browser will switch to the Results tab.
4. The Results tab will show a summary of the processing along with a log file containing any specific error or warning messages generated during processing. If the invoked service results in any new MDDF files being created (e.g. an Avails XLSX file has been translated to XML), the Result tab will also include download buttons for the created files.

The number of files that need to be submitted will depend on the specific MDDF type (i.e., Avails, MEC, etc.) and the service being requested. The general procedure is:

• One or more MDDF file may be submitted using the 'add file' buttons:
  
• A file can be added by dragging and dropping or by a left-click to initiate a file-chooser dialogue. Multiple files may be added by dragging and dropping a folder. [ NOTE: this is only supported for resource files.]
• Once added, any file may be removed. You may also remove all selected files using the CLEAR button.

When processing is completed, the display will automatically switch to the 'Results' tab. This will will show a summary of the results followed by a detailed log file:

An icon to the left of the file name will indicate if the service was able to return the desired results. In the example above the green checkmark indicate the manifest was successfully validated and no errors were found.

If the invoked service results in any new MDDF files being created (e.g. an Avails XLSX file has been translated to XML), the Result tab will also display a download button for each created file.

Check-boxes may used to show or hide log entries based on the level of severity. The levels, in order of decreasing severity, are:

• Fatal : Indicates the inability to perform any processing on a file. For example, attempting to process an Avails based on an unsupported version of the schema would result in a FATAL log entry.
• Error : a problem that must be corrected. An example would be the absence of a required property or the use of an unrecognized value for an enumerated type (e.g., an invalid language code)
• Warning : a problem or inconsistency that does not have to be corrected but may be worth looking into. For example, a Transaction with more than one SuppressionLiftDate terms is contradictory but may still be processable by a retailer.
• Notice : indicates that a recommended Best Practice was not followed (e.g. the use of non-EIDR ID values for IDs)

The last type of log entry is an Info message. These are used to provide a user with summary and status information about the file being validated.

A log file may also be saved in CSV format using TAB delimiters. For some services, additional controls or outputs may be displayed.

All files submitted are treated as proprietary and confidential. All operations are carried out in-memory and any temporary data written to, or stored on, disk is encrypted.

Cookies and other forms of tracking are not used. The only statistics collected by Movie Labs indicate the type of services that are being requested. No information contained in the submitted files is collected at any time.

UNLESS OTHERWISE MUTUALLY AGREED TO BY THE PARTIES IN WRITING, LICENSOR OFFERS THE WORK AS-IS AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE WORK, EXPRESS, IMPLIED, STATUTORY OR OTHERWISE, INCLUDING, WITHOUT LIMITATION, WARRANTIES OF TITLE, MERCHANTIBILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, OR THE ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OF ABSENCE OF ERRORS, WHETHER OR NOT DISCOVERABLE. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO SUCH EXCLUSION MAY NOT APPLY TO YOU.

EXCEPT TO THE EXTENT REQUIRED BY APPLICABLE LAW, IN NO EVENT WILL LICENSOR BE LIABLE TO YOU ON ANY LEGAL THEORY FOR ANY SPECIAL, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES ARISING OUT OF THE USE OF THE WORK, EVEN IF LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Validation of MDDF files includes the following checks:

1. conformance with the XML schema for the indicated MDDF type and version.
2. conformance with any additional requirements identified in the MovieLabs MDDF specifications.
3. validation that ratings metadata conforms with the MovieLabs Worldwide Ratings Data.

Files that pass all of these checks are considered VALID and error-free.

Files will also be checked for conformance with recommended Best Practices. Failure to follow Best Practices will generate Warnings and/or Notices in the log output but will not invalidate the file.

Validation of an Avails file in either XML or XLSX format is supported. Only one file may be submitted for validation (i.e., batch processing is not supported).

When an XLSX file is validated, the ' Line ' in the log entries will refer to the row in the spreadsheet.

When an XLSX file is validated, it is first converted into the equivalent XML representation. As a result, there may be situations in which a log entry refers to non-conformance with an XML schema.

Validation of an Offer Status file in either XML or XLSX format is supported. The processing is identical to that done for an Avails file (e.g. only one file may be submitted).

Only one Media Manifest file may be submitted for validation (i.e., batch processing is not supported). The Manifest may, however, contain references to other Manifest and/or MEC files. If so, these supporting MDDF files should be added as Resource files.

Only one Media Entertainment (MEC) file may be submitted for validation (i.e., batch processing is not supported). Since a MEC file can not contain references to other Manifest and/or MEC files, the ability to add Resource files is disabled when validating this type of file.

The Asset Order and Delivery(AOD) file types include Asset Availability, Asset Status, and Product Status files. Only one AOD file may be submitted for validation (i.e., batch processing is not supported). Since an AOD file can not contain references to other AOD files, the ability to add Resource files is disabled when validating this type of file.

Cross Platform Experience (CPE) and Media Manifest Core (MMC) files should be submitted as Manifest files.

Conversion services currently focused on Avails files and fall into two categories:

• The Translation service may be used to translate
  • Avails files either
    • from one format to another (e.g. XML to XLSX) or
    • to a different version of the same format (e.g., XML v2.2 to XML v2.3)
  • OfferStatus files from XLSX to XML. Unlike Avails files, translation from XML to XLSX is not supported.
• The Compression services may be used to 'clean up' an Avails XLSX file by removing unused columns from a template spreadsheet.

NOTE: Additional conversion modes will be added to future releases.

1. Select 'Avails' or 'Offer Status'as the MDDF type. If any other MDDF type is selected, the Translation service option will be disabled.
2. When the Translation service is selected a 'X-LATE TO:' widget is displayed to allow the user to indicate what formats and versions the Avails should be converted to:
   
3. Click in empty box to display a pop-up listing all available target formats:
   
   One or more target formats may be selected:
   
4. After selecting the MDDF file to be translated, use the Run button to initiate the service. The Result tab will include download buttons for each created files.

Note that translating an Avails requires that it be validated first. Validation is automatic and included as part of the Translate services (i.e., it does not need to be separately invoked). Thus, the Result tab will include a Validation log. If any errors are detected, translation is terminated.

1. Select 'Avails' as the MDDF type. If any other MDDF type is selected, the Compression service option will be disabled.
2. Select the Avails file to be processed. This MUST be an Avails that is encoded using XLSX.
3. After selecting the MDDF Avails file to be compressed, use the Run button to initiate the service. The Result tab will include download buttons for the new Avails file.

Note that compressing an Avails does not require that it be validated. Thus, the Result tab does not include a Validation log.

Stand-alone versions of the MDDF Validator/Converter tools are available for download. These provide some additional capabilities not supported by the on-line implementation (e.g. batch processing, integrated editors). The toolkit is provided in the form of an executable Java jar and may be downloaded from GitHub. Instructions for installing and running are provided in the repository README filea>.

All source code is available on GitHub as Free and Open Source Software (FOSS) under a Creative Commons Attribution 3.0 Unported (CC BY 3.0) license.