Common Extras Manifest Metadata, v0.71, September 10, 2013 http://www.movielabs.com/md/extras/
[TR-META-MMM]
Common Metadata Media Manifest. http://www.movielabs.com/md/manifest
[TR-META-CM]
Common Metadata, TR-META-CM, v2.1c, January 4, 2014, http://www.movielabs.com/md/md
[TR-META-CR]
Common Metadata Ratings, http://www.movielabs.com/md/ratings/
A.7. Best Practices for Maximum Compatibility
This API specifies interfaces intended to provide functionality in several areas, including package management, content access, media playback, and social networking. Developers may, if they choose, implement either enhancements to the existing capabilities or additional features outside the scope of this API. If, however, developers choose to do so, it must be done in a manner that does not conflict with the interfaces and state behaviors specified by this API.
A.8.Change Log
Version
Description
Sections
V0.92
P_STATE_EXITING added to Package lifecycle states
D.1.1
D.3.1.5
P_STATE_STARTED has been renamed P_STATE_LOADED
D.1.1
D.3.1.5
Revised instructions re the initialization() function
4.3.1.1
requestId is no longer an optional argument.
5.2.1.2
New code ACCNT_SIGNED_IN
F.2.1.1
Section 7.2.3.1 is deleted as it duplicates Section 7.3.1.1
7.2.3.1
Player Event Codes PE_READY and PE_VISIBILITY added
G.3.1.1
playerId argument added to functions createPlayer() and destroyPlayer()
G.2.2
advanced argument added to functions createPlayer()
Functions requestPeriodic() and cancelPeriodic() added.
7.2.8.5
7.2.8.6
Function setPoster() added
G.2.3
Function isVisible() added
G.2.3
Function jumpTo() is now part of the Player Basic sub-group instead of the Trickplay sub-group.
7.2.3.9
Function setPlayerDimensions() deleted. This function is not used as resizing is automatically handled via CSS property. The player will always be optimized to fill its container. If the player dimensions are to be fixed then the appropriate mechanism is to set the height/width of the containing DIV.
(was 7.2.9.5)
Annex B. Primary Components
The CPE is defined in terms of Content Providers who create Packages, Retailers who create Frameworks, and Viewing Environments that execute the Package and Framework to create an Interactive Experience for a Consumer. This is illustrated below.
More formally:
Consumer: the individual(s) viewing the content in their home via an on-demand and interactive platform (e.g., streaming to a tablet device).
Content Provider: the organization that owns the content (e.g., a movie studio).
Retailer/Distributor: the organization that is responsible for making the content available to consumers and the collection of any associated fees (e.g., streaming services or on-line retailers).
CPE defines APIs in terms of three conceptual components:
Viewing Environment: consumer’s hardware platform and operating system (e.g., Android tablet, iPhone, Windows 8 PC, etc.).
Framework: software that allows the consumer to use their selected viewing environment to view, and interact with, content. The framework may include components running within the consumer’s viewing environment as well as components residing on servers or cloud-based platforms.
Package: set of content files and supporting control software that defines the state behavior of the interactions. The package content files will consist of both primary content (i.e., the movie that is the focus of the consumer’s attention) and the supporting content (e.g., behind-the-scenes commentary, deleted scenes and interviews).
