EMA Avails Product Content Delivery Definition Media Manifest Media Manifest Best Practices Product CPE-Manifest CPE-Appdata Core (MMC) for Delivery Definition

EMA Avails Product Content Delivery Definition Media Manifest Media Manifest Best Practices Product CPE-Manifest CPE-Appdata Core (MMC) for Delivery Definition

WORKING GROUP RECAPS http://movielabs.com/dsca-bam1 140 Working Group Report-Outs • SVOD • TVOD Avails • Asset Ordering • Metadata • QC Nomenclature (EMA) • Ratings • API • Adoption Pitch (DEG) • Digital Finance and Accounting http://movielabs.com/dsca-bam1 141 Working Group Report: SVOD http://movielabs.com/dsca-bam1 142 SVOD Working Group • WG members from: Amazon, Cinedigm, DEG, Discovery, Disney, EMA, Google, Lionsgate, Microsoft, MovieLabs, Netflix, NBCU, Paramount, Scripps, WB • Recurring Monthly conference calls • Evaluated and approved for release 1.7.3 for SVOD Title Lists (July 9, 2018)! http://movielabs.com/dsca-bam1 143 1.7.3 SVOD Title List Features New Fields • Licensee - Indicates licensee associated with the Avail. • EpisodeTitleID - Title/Abstraction identifier for episode • GroupIdentity - Subscription Type/Channel • TerritoryExclusion - Compliment to Territory to list excluded territories • Download - Is download allowed on a per-title basis • Director - Added for manual title matching • TitleStatus - State of title (Approved/Pending license) • Exclusivity – Whether a title has exclusive rights and related attributes • Window Timing – StartLag, EndLag, Duration, added “Immediate” and “Open” Start • RequiredFullfillmentLanguages – Languages content provider is committed to provide http://movielabs.com/dsca-bam1 144 1.7.3 SVOD Title List Features Other Improvements • Improved Language/Localization Type Handling – indicate language and localization type(s) together • Added allowed values “Immediate” and “Open” Start field for window timing • EpisodeCount changed from optional to required • Added 'Library' LicenseType - Title was acquired under an EST license, but is no longer Avail'd for EST but can be fulfilled • Clarified FormatProfile note to include this: "Note: For SVOD or AVOD, highest resolution should be listed and lower resolutions can be assumed." • Clarified that Rating System/Value/Reason must be compatible • Clarified DMA_ID field - Indicates that title is MA eligible • Cell A3 can contain date+time information for versioning • Clarified in general instructions that Full Delete and 'End' date in past, both have the effect of bringing down titles • Miscellaneous corrections and clarifications http://movielabs.com/dsca-bam1 145 SVOD Working Group, Cont. Next steps • Supporting 1.7.3 implementations • Develop SVOD Title List use cases • Title list core template • Tutorials, conference calls • Other work as identified by the SVOD WG http://movielabs.com/dsca-bam1 146 Working Group Report: Avails http://movielabs.com/dsca-bam1 147 Avails Working Group • WG members from: Amazon, DEG, Discovery, EMA, Fandango, Google, HBO, Lionsgate, Microsoft, MovieLabs, NBCU, Paramount, Scripps, Sony PlayStation, Viacom, WB • Recurring Monthly conference calls http://movielabs.com/dsca-bam1 148 Avails Working Group, Cont. TVOD updates included in 1.7.3 • Added EpisodeTitleID - Title/Abstraction identifier for episode, typically an Abstraction EIDR ID. • Added 'Library' LicenseType - Title was acquired under an EST license, but is no longer Avail'd for EST but can be fulfilled • Clarified that Rating/System/Value must be compatible • Clarified DMA_ID field - Indicates that title is MA eligible • Clarified treatment for Full Delete and changing end date • Added general instruction that cell A3 can have sequence information or date+time (for versioning) http://movielabs.com/dsca-bam1 149 Avails Working Group, Cont. Evaluating proposed updates (for next version) • Adding collections tab for bundles, removing ‘BundleALID’ from Movies tab • Support for more robust language and localization type combinations in language fields (see 1.7.3 for SVOD LicenseType) • Discussing “Full Extract with omissions”, reporting, use of AvailID and related issues • Adding TVOD support for SVOD only fields in from 1.7.3 http://movielabs.com/dsca-bam1 150 Working Group Report: Asset Ordering http://movielabs.com/dsca-bam1 151 Asset Ordering Working Group • WG Members from Amazon, DEG, Disney, EMA, Google, HBO, Lionsgate, Microsoft, Netflix, Paramount, Scripps, Showtime, SPE, and WB • Four in person meetings • Defined the problem space, areas of agreement and open questions http://movielabs.com/dsca-bam1 152 Asset Ordering Working Group Problem Statement There are potentially dozens (or even hundreds) of different assets needed to fulfill a single title in a given context — e.g. languages, formats, and bonus content. • How does a retailer indicate which assets are needed, which have been received, and which are missing? • How does a provider indicate which assets are available, and which they intend to fulfill? http://movielabs.com/dsca-bam1 153 Asset Ordering WG, Cont. Areas of alignment • Communicating the priority of assets ordered should be considered as part of the specification to inform which assets a provider should focus on first. The WG has defined priority as a derived value based on due date, provider value, retailer value and relative complexity/completeness of the deliverable. • The specification should accommodate both concrete (by explicit asset ID) and abstract (attributes of the assets, e.g. fr-FR subtitles for Title 12345) orders. http://movielabs.com/dsca-bam1 154 Asset Ordering WG, Cont. Open questions • How do providers communicate explicitly when they acknowledge or reject (will not fulfill) an order? • Should we use manifests as “asset catalogs” to let providers communicate available assets to retailers? • What levels of order granularity (avail, title, abstract element, specific asset) should the spec support? Next Steps • Confirm data flow • Review draft specification http://movielabs.com/dsca-bam1 155 Working Group Report: Metadata http://movielabs.com/dsca-bam1 156 Metadata Working Group (MEC & MMC) • WG members from Amazon, DEG, Discovery, Disney, EMA, Fandango, Google, HBO, Lionsgate, Microsoft, MovieLabs, NBCU, Paramount, Scripps, Sony PlayStation, Viacom, WB • Recurring, monthly conference calls http://movielabs.com/dsca-bam1 157 Applicable Specs EMA Avails Product Content Delivery Definition Media Manifest Media Manifest Best Practices Product CPE-Manifest CPE-AppData Core (MMC) for Delivery Definition CPE-HTML CPE-Appearance CPE Best Practices Common Media for IMF Manifest* MDDF API Media Common Entertainment Metadata* *Almost every spec references Common Metadata Core (MEC)* Most reference Media Manifest and MEC http://movielabs.com/dsca-bam1 158 Development Work (summary) • Common Metadata 2.6 • www.movielabs.com/md/hot.html#cm • Media Manifest 1.7 • www.movielabs.com/md/hot.html#manifest • MMC for TV • www.movielabs.com/md/mmc/hot.html • Best Practices • www.movielabs.com/md/practices http://movielabs.com/dsca-bam1 159 Common Metadata 2.6 • CM is base spec for MEC, Media Manifest/MMC, Avails and more • Changes in v2.6 • ‘Added People/Job/CharacterInfo for localization and IDs • Parent (esp. for regional episode ordering) • Added SequenceInfo • Added Region/RegionExcluded? • Universe, Brand and Franchise • “Based on” (book) • Improved gender identity encoding • noforced’ subtitle Type • ‘Production’ ReleaseType • CountryOfOrigin 0..1 → 0..n • Status: • Solid draft—in review http://movielabs.com/dsca-bam1 160 Media Manifest 1.7 • Proposed Changes in v1.7 • Reference CM v2.6 • Added ‘Source’ to MediaManifestEdit (as for MediaManifest) • Add descriptive info to Presentation/TrackMetadata to make it easier to sort out what the grouping is for (e.g., commentary). • Allow objects other than Experience to be external (TBD) • Consider allowing timecode in hh:mm:ss:FF (frame). Currently, we only support fractional seconds (for encoding independence) (TBD) • Status • Incomplete draft posted on www.movielabs.com/md/hot.html#manifest http://movielabs.com/dsca-bam1 161 Media Manifest Core for TV (MMC 2.0) • Defines how to structure TV deliveries • Series, Season, Episodes, Volumes, Bundles, Compilations, Bonus • Season passes, complete seasons/series, etc. Case 1b: No bonus, Active Season 13 • Deliver Season 3 • Precondition: Seasons 1 already delivered Series Season 1 Season 1, Episode 1 Season 1, Episode 2 Season 1, Episode n Season 1 Metadata S1 E1 Metadata S1 E2 Metadata S1 E3 Metadata Series Metadata `` ... S2 E1 Presentation S1 E2 Presentation S1 En Presentation Child Experiences Season 1 Child Experiences • Season and Series Series Season 2 Series updated (redelivered) to reference new season Series Metadata Season 2 Metadata Season delivered Child Experiences • No episode references • Episodes delivered as they become available Season 2, Episode 1 Season 2, Episode 2 Season 2, Episode 3 Season 2, Episode 4 Season 2, Episode 5 Episodes: S2 E1 Metadata S2 E2 Metadata S2 E3 Metadata S2 E3 Metadata S2 E5 Metadata S2 E1 Presentation S2 E2 Presentation S2 E3 Presentation S2 E4 Presentation S1 E5 Presentation • Identical structure to Case 1a = Manifest delivery • Includes examples (episodes, season, series, XML Avails) http://movielabs.com/dsca-bam1 162 Media Manifest Core for TV (MMC 2.0) • Defines how to structure TV deliveries • Series, Season, Episodes, Volumes, Bundles, Compilations, Bonus • From simple to complex • Includes examples (episodes, season, series, XML Avails) Series Series Metadata Child Experiences Season 1 Season 2 Season 3 Series Retrospective Series Gallery Series Navigation Season 1 Metadata Season 2 Metadata Season 3 Metadata Retrospective Metadata Gallery Metadata App Metadata Season 1 Child Experiences Season 2 Child Experiences Season 3Child Experiences Retrospective Presentation Series

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    50 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us