Entertainment Identifier Registry (EIDR) March 2010

Welcome to the Third Level

Dec 13, 2012

Put a tiger in your tank!

2

Core TT Roadmap

• Manifestations (The Third Level)– Digital Encodings/Packagings (e.g. CFF)– Language combinations– Encoding profiles– Individual tracks, e.g. watermarked audio

• Language Version Handling– Original Language(s) vs. non-Original Languages– Where to allow language changes: Manifestations/Encodings only? Edits?– How downstream language versions registered, e.g. which Edit?

• Grouping– Compilations

• Uses: Bundles, Franchises, DVD/BD, Intl Season Groupings

– Composites• Uses: Temporal concatenation

• Related Topic– EIDR ID practices for distribution and reporting

• Granularity/level, EIDR + metadata vs. new EIDR ID

29-Nov-2012

3

Agenda

• Use Cases for the Third Level (Manifestations)• History Lesson: The Fourth Level (SKUs)• Overview of Proposed Manifestations• Overview of Language Handling

29-Nov-2012

4

Manifestation Use Cases

• Digital Encodings– Consumer distributed (e.g. UV CFF)– Digital Asset work flows (e.g. mezzanine files)– Digital Cinema DCPs– DVD/BD image

• Version + Language(s) (independent of encoding)– Downstream metadata aggregators, archives, etc.

• Individual Tracks– Watermarked audio track, late-bound audio track

• Other Manifestations (future)– Film, tape, etc.

• Others?

29-Nov-2012

5

Manifestation Excluded Use Cases

• Fully flexible SKUs• Same asset, different distribution

– Different territory (e.g. same CFF file in UK vs. US)– Different distribution channel (e.g. HBO vs. syndication)– Different distribution mode (e.g. VOD vs. EST)

• Initial HITS/DEG Title/Version/Product model allowed this• Reflected in early 2011 proposed hierarchies

29-Nov-2012

6

Proposed 4-Level: Title/Version/Products/Assets- early 2011

11/21/2011

Tit

leV

ers

ion

sA

ss

ets

IsEditOf IsEditOf

Movie

Theatrical Release

EIDR: Root record

Pro

du

cts

VOD HDVOD SD EST SD

Versions are represented by EIDR Edits. Version-Version hierarchy is optionally permitted, e.g. a country edit of the Director’s Cut could go under the Director’s Cut record or directly under the title.

EST HD

Similar Products & Assets

Here

IsEncodingOf(generic*)

XboxVOD HD

Assets are represented by EIDR Technical Encodings. These are optional for MS in the Warner POC.

IsEncodingOf(generic*)

IsEncodingOf(technical)

Director’s Cut

Assets are tied back to Products using the EIDR Packaging relationship, which is loose and non-parental

XboxVOD SD

XboxEST HD

IsEncodingOf(technical)

XboxEST SD

MSFTMezzanine

IsEncodingOf(technical)IsPackagingOf

OtherEST HD

Other Mezzanine

Requests to EIDR: Additional metadata for Products. Rename Generic Encodings to Products.

Products are represented by EIDR Generic Encodings (*currently HD vs. SD not supported. Workaround needed.)

IsPackagingOfIsEncodingOf

(technical)

24-Jun-2011

4-Level Movie Hierarchy (Product + Asset)- early 2011

Tit

leV

ers

ion

sA

ss

ets

IsEditOf IsEditOf

Movie

Digital Edition

EIDR: Root record

Pro

du

cts

EST

Versions are represented by EIDR Edits. Version-Version hierarchy is optionally permitted, e.g. a country edit of the Director’s Cut could go under the Director’s Cut record or directly under the title.

FutureVOD

IsEncodingOf(generic*)

HDAssets are represented by EIDR Technical Encodings.

IsEncodingOf(generic*)

IsEncodingOf(technical)

Theatrical Version

Assets are tied back to Products using the EIDR Packaging relationship, which is loose and non-parental

SD HD+

IsEncodingOf(technical)

Requests to EIDR: Additional metadata for Products. Rename Generic Encodings to Products.

Products are represented by EIDR Generic Encodings

IsPackagingOf

Mezzanine

MPM-P

MPM-I MPM-I

8

Manifestation Excluded Use Cases

• 4-Level Hierarchies with “Products” were proposed, tried– Complicated to relate assets to SKU/products– More IDs to manage– Reporting: Better handled with reporting metadata than new IDs

• Keep it simple? Or are there strong use cases?

29-Nov-2012

9

Manifestations

• Very similar to current Encodings– But virtually all metadata is optional & all combinations allowed

• Track based– Video, Audio, Subtitle tracks– Most metadata resides on tracks– Plus file and wrapper information

• List of version languages– If detailed track information not available

• Use Common Metadata– EIDR 1.X is similar (but not identical) to current Common

Metadata– Allows direct reuse of CFF metadata for EIDR registration– Common Metadata to be extended to support EIDR use cases

29-Nov-2012

10

Use Case: Consumer Download

• Consumer Downloads (e.g. CFF Files)– Track-based

• Video track• Language tracks

– Maybe just initial ones if others can be downloaded and “late-bound”

• Some track technical metadata (bitrates, video resolution)• Some overall file information

– Wrapper format, e.g. ZIP, WMV– File size or hash

» Not for CFF, since can change in the field

– Simple non-track based• List of languages and forms (audio, subtitle)• Registrant-specific “details” (e.g., Disney SD/HD1/HD2)

29-Nov-2012

11

Use Case: Disposable Mezzanine File

• Encoding “Profile” (e.g. mezz formatted iTunes)– Tracks with A/V technical metadata that defines encoding profile– Perhaps the actual set of language tracks– No file size or hash, “disposable” mezz regenerated as needed

29-Nov-2012

12

Use Case: Language Versions

• Metadata services, archives– Represent version of work with particular languages

• Often independent of media (film, TV broadcast, download)

– Registrant has no technical metadata on tracks– Registers as list of languages + form (audio, subtitle, etc.)

• Need practices for identifying Edit (or registering one)– Use studio registered Edit? Create “unknown” Edit?– More discussion to follow on practices

29-Nov-2012

13

EIDR 1.X Language Handling

• EIDR 1.X Language Handling– In Base metadata on all records– Primary Language (specified on roots and inherited)– Secondary Languages (for subtitles, alternate audio)– Not directly mutable in Base metadata

• Language Variant relationship needed to override inheritance

– LV cumbersome (cannot specify at creation, must add/remove)– Never used

29-Nov-2012

14

Proposed 2.X Language Handling

• Replace Primary Language with Original Language(s)– Specified on root records– Also mutable on Season and Episode

• Add Version Languages– Only specified below “title” records

• Manifestation/Encodings, Clips

– When tracks are specified, automatically populated from them

• Why not just use tracks for all language versions?– Very useful to have in Base metadata, ease of search, etc.

• rather than buried down in track structure

– Allows future flexibility in language handling outside of Manifestations (e.g., proposal to allow on Edits)

29-Nov-2012

15

2.X Language Manifestation EST Example

13-Dec-2012

Title

OriginalLanguage: EN, audio

Edit

OriginalLanguage: ENMadeForRegion: International

Manifestation

OriginalLanguage: EN, audioVerisonLanguage: EN, audio, primaryVersionLanguage: EN, text, SDHVerisonLanguage: EN, audio, commentaryVerisonLanguage: SP, audioVerisonLanguage: FR, audio

Key Points1. Version Languages are track-based2. Original Language remains on leaf record, not replaced3. Digital Asset Metadata also can define track metadata.

In that case, Version Language is populated from detailed digital track metadata

ManifestationClass: EST, HD

16

2.X Language Manifestation: EPG Example

Title

OriginalLanguage: EN, audio

Edit

OriginalLanguage: ENEditUse: Unknown

ManifestationOriginalLanguage: EN, audioVerisonLanguage: SP, audio, primary

Key Points1. EPG provider not knowing studio Edit, creates one of its

own with an EditUse of “Unknown”.2. EPG provider could register multiple Edits, e.g. for

Unknown Director’s Cut vs. Original.

ManifestationOriginalLanguage: EN, audioVerisonLanguage: EN, audio, primary

13-Dec-2012

17

Manifestations and Media-Specific Metadata

• Manifestation Metadata– Manifestation Class

• EST, VOD, Blu-ray, DVD, Broadcast, Mezzanine, etc.• Replaces 1.X Encoding Class

– Choice of one “media” metadata set– Currently just one:

• Common Metadata Digital Asset Metadata

– Future possibilities:• Film• Tape

13-Dec-2012

18

Digital Asset Metadata

• Overall Wrapper/Container information– WrapperType (e.g. ZIP, WMV, etc.)– Size, Hash

• Track-based – md:DigitalAssetTrackList-type– Audio – md:DigitalAssetAudioData-type– Video – md:DigitalAssetVideoData-type– Subtitle – md:DigitalAssetSubtitleData-type– Interactive – md:DigitalAssetInteractiveData-type

• Track Metadata– Size, Hash, Languages, Bitrate, Resolution, Channels, etc.

• Pick and Choose Model– Almost everything is optional

13-Dec-2012

19

2.X Digital Asset Manifestation: EST Example

Title

OriginalLanguage: EN, audio

Edit

OriginalLanguage: ENMadeForRegion: International

Manifestation

Base MetadataOriginalLanguage: EN, audioVerisonLanguage: EN, audio, primaryVerisonLanguage: EN, audio, commentaryVerisonLanguage: SP, audioVerisonLanguage: FR, audioVersionLanguage: EN, text, SDH

Key Points1. Version Languages populated from detailed track

metadata in Digital Asset Metadata

Manifestation MetadataManifestationClass: EST, HD

Digital Asset MetadataWrapperType: ZIPVideo Track: MP4, 4Mbps, 1920x1080, 24fpsAudio Track: EN, primary, AAC, 4.1, 300kbpsAudio Track: EN, commentary, AAC, 4.1, 300kbpsAudio Track: SP, audio, AAC, 4.1, 300kbpsAudio Track: FR, audio, AAC, 4.1, 300kbpsSubtitle Track: EN, SDH

13-Dec-2012

20

Next Steps

• Bring more use cases and map them to proposal• Distribution and Reporting Tiger Team

– Review and provide use cases

• Start detailed review of proposed metadata model– Spec is in progress– Review current Common Metadata Digital Asset Metadata

• Identify where best practices and data governance are needed– Metadata service registration of “unknown” Edits?– How to handle encodings representing multiple Edits, e.g. CPL

mezzanine?

13-Dec-2012