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:
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.
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:
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:
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:
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:
NOTE: Additional conversion modes will be added to future releases.
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.
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.