This page details the release history of Media Manifest.
Versioning: Number changes (e.g., 1.2) constitute schema changes. Letter changes (1.1c) are documentation-only changes.
Backwards Compatible means that elements were added, but old elements still exist. Therefore, an old XML document with the new namespace will validate. All updates are backwards compatible except 1.4 to 1.5
Incorporated Common Metadata 2.5 features (referenced 2.5 schema).
Support for Immersive video including VARM (Virtual, Augmented and Mixed Reality) and 360 Video.
Improved image and interactive Digital Asset data.
Additioanl support for supply chain use cases.
- Version 1.6 Specification, December 20, 2016
- Presentations in schema is now optional (matches spec).
- Added @workflow to assist processing. Also added to ManifestEdit.
- Clarified file location nomenclature
- 360 degree video thumbnails
- Ability to reference Timed Text object(s) for proper display of timed text or graphics
- Add markers to Presentation (SMPTE 2067-3), such as start of credits.
- For preorder, App/AppGroupID and Gallery/PictureGroupID are optional
- Add Type/SubType to Experience for future use. Type=’external’ supports referencing Experiences in other files.
- Add deprecated entitlement IDs (for retailers to cross reference)
Structural change to Mainfest to avoid incorrect encoding. Supply chain improvements.
- Version 1.5 Specification, October 13, 2015
NOT Backwards Compatible
Experience structure previously allowed multiple instances of Audiovisual, App and Gallery. This was redundant with the more general ExperienceChild construct. In 1.4 there were two completely different means to encode the same information. 1.5 restricts this to the more general construct (ExperienceChild).
Simplified Experience structure to simplify generation and processing (non-backwards compatible change mentioned above)
- Only one instance of audiovisual, app, or gallery is now allowed.
- Removed option to include metadata in Experience. Must be referencable (e.g., in Inventory).
Added Profile in compatibility to convey which the profile to which the Manifest complies.
Added People and Product (GTIN) to Timed Event.
- Added ability to specify multiple prioritized Locations in Inventory and FileManifest
- Provided the ability to deliver an Interactive Media Manifest as a Delivery Manifest’s Inventory
- Added language to text group to allow correct text to be selected based on the playback language. Multiple instances of TextGroupID added to Timed Events.
Added ability to determine which Dub Card or audiovisual track corresponds with an audio language track.
Release to support Cross-Platform Extras (CPE-Manifest) features.
- Version 1.4 Specification, June 12, 2015
- Timed Events
- Event Location
- Text Objects
- Thumbnail support in images
- Application and Gallery Basic Metadata'
- Region-specific child sequencing (i.e., episode sequencing)
- Track-level Media Profile support in Presentation
Support for HDR and ancillary tracks, inline metadata and pre-sale.
- Version 1.3 Specification, February 10, 2015
- Reference Common Metadata 2.2 to incorporate latest HDR metadata and Ancillary tracks
- Added means to encode metadata in the Inventory to reduce redundancy
- Updated Audiovisual to support content-less deliveries (i.e., pre-sale)
- Version 1.2 (schema-only), October 15, 2014 (references Common Metadata 2.2)
- Version 1.1a Specification, September 16, 2014
- Added updateNum to Experience-Type
- Allowed multiple instances of SubType in Audiovisual-type
- Added FileDeleteManifest and MediaManifestEdit to support delivery use cases.
Version 1.0 Specification, July 1, 2014
BEST PRACTICES AND APPLICATION-SPECIFIC USAGE
These best practice describes approriate usage of Avails, Media Manifest and File Manifest for deliverying files through distribution to a retailer. These are intended for studios; post production companies providing distribution services; and for retailer or any other party receiving media files and/or metadata.
Using Media Manifest, File Manifest and Avails for file Delivery (Best Practice), BP-META-MMMD, v1.2, October 13, 2015 (PDF), showing differences from v1.1 (PDF)
Interoperable Master Format (IMF)
The following document describes how to use Media Manifest with Interoperable Mastering Format (IMF) as described in the in the SMPTE ST 2067 family of standards. This is useful in conjunction with File Delivery desribed above.
Using Common Media Format with Interoperable Media Format, TR-META-MMMIFM, v0.5a, July 23, 2015 (PDF, Word)
The following best pratice describes a process for ensuring seamless playback of Playable Sequences.
Seamless Sequential Playaback (Best Practice), BP-META-MMMSP, June 12, 2015 (PDF)
Using Media Manifest, File Manifest and Avails for file Delivery (Best Practice), BP-META-MMMD, v1.1, June 12, 2015 (PDF), showing differences from v1.0 (PDF)
Using Media Manifest, File Manifest and Avails for file Delivery (Best Practice), BP-META-MMMD, v0.7, August 1, 2014 (PDF, Word). Version showing changes to v0.8 (PDF, Word)
Using Media Manifest, File Manifest and Avails for file Delivery (Best Practice), BP-META-MMMD, v0.6, June 8, 2014 (PDF, Word). Version showing changes to 0.7 (PDF, Word)
Please submit questions and comments to