Content Updates and Definitions for TV Metadata

Avails1.7.4, XML 2.4 September 5, 2018

Changes 2 Both Signalling movie to go in TV store (Add GroupIdentity = TVMovie ) Language clarifications (particularly AssetLanguage) Define and Differentiate Volumes, Collections, and Bundles 1.7.4 (Excel) Extended 1.7.3 changes for TVOD New Collections Tab Added PackageLabel 2.4 (XML) Sync with 1.7.3 Added sequence to BundledALIDs. Changed ContractStatus term to TitleStatus to match Excel v1.7.3 Clarify what type to use when mapping GroupingIdentity (@type= channel ) Added time zone examples Add asset dates MovieLabs Confidential

Signaling (TV) Movie goes in TV Store 3 Problem Studios wish to offer certain TV movies in the TV store For example, Hairspray Live! Current approach: Create pseudo-series with 1 season and 1 episode e.g., (same on other sites), https://play.google.com/store/tv/show/Hairspray_Live?id=jUHeag6pfDM Requirement is to express this is a TV movie Solution: Use GroupIdentity GroupingEntity originated in MEC for the purpose of telling retailer where to put the title. Unless there is a conflict (i.e., additional use of GroupIdentity that conflicts), this would be the most natural way to signal this information Add GroupIdentity= TVMovie MovieLabs Confidential

Language Clarifications: AssetLanguage 4 Problem AssetLanguage and LocalizationType are inadequately defined and usage possibly inconsistent Solution Redefine AssetLanguage column to mean: 1) Intended language, 2) language of intended audience, and 3) that asset in that language should be presented in that territory Whether AssetLanguage contractual or not depends on the bilateral contract? If blank, refer to contract Allow multiple languages in AssetLanguage using 1.7.3 syntax. (understanding individual studios might not use this) For example, en:subdub, fr:dub LocalizationType is applicable to a single language in AssetLanguage. LocalizationType must be blank when AssetLanguage has multiple languages or : notation. Remove old AssetLanguage definition (Don t need alternate definition of AssetLanguage) MovieLabs Confidential

Volumes, Collections and Bundles Topics 5 Definitions Similarities and Differences Bundles Note that Bundles is a solved problem Volumes vs. Collections Collections Volumes MovieLabs Confidential

Definitions 6 Bundle: Any combination of movies and/or TV seasons Can also include individual episodes, but only if bundled with movies and/or seasons [if we don t generalize, this gets ugly fast!] Note that movies can be bundled, but not Collections or Volumes [is this statement true?] Volume: Consists of TV episodes from within the same series. These episodes can be from the same season or can span multiple seasons. Includes. split season (1a, 1b) Possible Alternate definition: chronological subset of a season [Need to confirm or refute this] Collection: Consist of TV episodes from across multiple seasons or series Collections are used to group like content together for a single purchase option. Also Compilation: a multi-segment block of short form content that is put together to create a new work. Because this new work is in essence a new stand-alone episode, compilations episodes will typically be represented as such. Bonus/Extras/VAM: Any additional content provided with feature (can be audiovisual, images or apps) MovieLabs Confidential

Similarities and Differences 7 Entitlement Same: Resulting entitlements can be expressed as a collection of ALIDs (i.e., BundledALIDs) Business Terms Same: most business terms covered by existing models (e.g., PriceType) Different: Might be different price models/tiers (need new PriceTypes, LicenseTypes?) Reporting of bundle/collection/volume sales vs. individual units e.g., If it s a 3-movie bundle, do you report bundle sales, individual movies or both? Marketing presentation on retailer sites Same: Metadata for bundle/volume/collection (MEC covers this) Different A volume only needs one series reference, but a collection might require multiple series references MovieLabs Confidential

Bundles 8 Bundle any combination of movies and/or TV seasons Die Hard Series Bundle Serenity (2015 Movie) and Firefly (TV Series) Bundle The Flash Bundle: Seasons 1, 2, and 3 Analogous to shrink wrap around a collection of Blu-rays Bundles are handled in Avails Defined by a list of ALIDs (reference elsewhere in the Avail) Bundle contains the union of all assets in those Avails (including bonus) Bundle has its own ALID and its own terms Not just price: Can include dates, resolutions, etc. Bundle has its own metadata Note: Long-term goal: Bundling non-audiovisual content Best to keep mechanism as general as possible MovieLabs Confidential

Bundles implementation 9 Movies Create row for Bundle (own ALID, terms and metadata) Reference assets in BundledAssets Should this go on Movies or Collections tab? Either? Mixed Movies and TV Use (new) Collections Tab Same as Movies, but TV Season or Episode ALIDs allowed MovieLabs Confidential

Volumes vs. Collections 10 Volumes from same Series Any chance we can constrain this to same season? Collections from different seasons Neither includes movies or anything else (that is a Bundle ) MovieLabs Confidential

Collections 11 Collection: May consist of episodes from across multiple series but it is not limited to this notion. Collections are used to group like content together for a single purchase option. Best of Chandler: 10 episodes from Friends highlighting Chandler Bing Structurally, isn t this a Bundle? Collection has metadata All other metadata comes from referenced ALIDs (in Excel, assumes other objects Availed) Do we need different WorkType, LicenseType or PriceType for collections? MovieLabs Confidential

Volumes 12 Volume: consists of episodes from within the same series. These episodes can be from the same season or can span multiple seasons. Includes. split season (1a, 1b) Doc McStuffins, Vol. 1: 13 episodes (March 2012 - April 2012) Doc McStuffins, Vol. 2: 13 episodes (April 2012 - January 2013) Info available for each component (episode) Original Series (same as volume series by definition) Original Season (for each episode) Original Episode Additional information needed Volume season (e.g., volume 1 or 2a ) [not if constrained to same season] Volume-season episode (e.g., Vol 2, episode 1 = season episode 14) Could use DistributionNumber or add new column [prefer adding column so it doesn t conflict with existing uses of DistributionNumber] Recommendation Use BundledALIDs to reference episode ALIDs. This picks up all other metadata. For Excel, assumes episodes are Availed, even if it s Season Only MovieLabs Confidential

Bundles, Collections, Volumes encoding 13 Object Includes Tab WorkType* BundledALIDs Other Bundle Movies Movies or Collections Collection Movies Bundle Movies+TV Seasons Collections Collection Movies and/or Seasons Bundle Multiple Seasons TV Collection Seasons Collection TV episodes, different series Collections Collection TV Episodes Collection TV, same series TV Collection TV Episodes and/or Seasons Series IDs included. Season and Episode IDs blank TV Volume TV, same season TV Volume TV Episodes VolumeNumber is label for volume (1,2,3). DistributionNumber is volume label ( 1a , 1b ) *Note: Collections tab used when there is more than one series or season in the collection MovieLabs Confidential

Avails conveying package reuse across territories 14 Problem New territories can be added using the same media package Either not using MMC, or don t want to update MMC Note: may need to localize metadata Existing Solutions Option 0: redelivery of media package for new territory Option 1: Add territories to MMC XML 1a redeliver MMC XML 1a1: Use Experience that's worldwide unless there is a territory match 1a2: Always reference specific countries 1b Media Manifest Edit update of MMC XML Recommended Additional Solution Option 2: In Avail, add "PackageLabel". Avails with same value use the same package 2' do same thing in proprietary Avail Also Option 3: Asset Ordering and Delivery Solution MovieLabs Confidential

2.4 (XML)-specific

Change Summary 16 Reference CM 2.7, MM 1.8 Sync with 1.7.3 Minor corrections and improvements Asset dates (for discussion) MovieLabs Confidential

1.7.3 synchronization 17 Problem 2.3 was published before 1.7.3. 1.7.3 includes some changes. Changes Added sequence to BundledALIDs. This mirror the implicit ordering in Excel BundledALIDs Changed ContractStatus term to TitleStatus to match Excel v1.7.3 Define GroupingIdentity= channel for cleaner mapping with 1.7.3 (this is only value accepted in 1.7.3) MovieLabs Confidential

Minor corrections and improvements 18 Changes Added time zone examples. Clarified what Type value to use in GroupingEntity when translating to/from Excel. Fix type in TPR-x term Exclusive term should be xs:boolean, not xs:string BrandingRights should be xs:boolean, not xs:string @assetProvided should be xs:boolean, not xs:string Allow more than one GroupingEntity MovieLabs Confidential

Asset date 19 Problem No way to specify when asset will be provided Solution Add @assetProvidedDate to AssetLanguage When dates are different from Subs and Dubs use distinct AssetLanguage instances for subs and dubs Question: Is one date enough? Question: Would it be better to have @subDate, @dubDate and @metadataDate Question: Should dates be their own structure? MovieLabs Confidential