Entertainment ID Registry TWG, BMWG, And POC Update September 17, 2012

Transcription

Entertainment ID RegistryTWG, BMWG, and POC UpdateSeptember 17, 2012EIDR Confidential1

AgendaThis meeting now encapsulates the Technical WorkingGroup, Business and Marketing Working Group and thePOC Status Meeting.Topics/Agenda: Welcome New Members/Introductions (5 min)– TWG - Technical Updates and Discussion Topics (45 min)– Jim HelmanPOC Status and Updates (5 min)– Don DulchinosRichard KroonBusiness and Marketing Updates and Membership (5min)–Don Dulchinos

Welcome New MembersNew Members for August/September1.Time Warner Cable1.2.David Bell, Chief ArchitectChad Enney, Frank Figueroa, Steve Smith

TWG – 1.2 Update New 1.2 Development Effort Initiated–– Renamed to 1.2 due to scope of schema changesPrimary development work in Q3 / deployment in OctoberFeatures–Principal Agent, Directors (2), Actors (4) Agreement reached to allow maximum of 4 actorsRequired Metadata Change: PA or Director or 4 ActorsPrincipalAgent strings required significant schema changesPrincipalAgent element replaced by AssociatedOrg– Implementing with 1.1 API compatibilityNew scoring for overlapping sets (AssociatedOrgs, Actors)–––Uses MovieLabs Common Metadata types for ID string namesGives higher weight to partial overlapsMetadata AuthorityDe-duplication mode for bulk changes4

TWG – Documentation & Resource UpdatesDocumentation Registry Programmer’s Guide – Published and Available Online5

TWG - Episodic Change Overview Purpose– To address the various issues raised during the Episodic Tiger Teammeetings and the results of our recent Episodic practices survey. Main Changes– Allow three numbering systems– All seasons and episodes will have title strings (some optionally generated)– Metadata for special matching/de-duplication handling Release Time of Day (0.1 occurrences)– Used to distinguish programs with more than one episode per day Episode Class (0.n occurrences)– Controlled vocabulary to describe the type of episode (Pilot, Omnibus, etc.) Season Class (0.n occurrences)– Controlled vocabulary to describe special types of seasons (Mini-Series, Recut,etc.) Features agreed to by Tiger Team Full spec to be distributed before next TWG for approval– Please review overview in the backup section of this dec17-Sep-126Copyright 2012 EIDR

TWG - EIDR Q4 Planning Status Process––– Currently Developing Specifications for Q4 DevelopmentTargets–––– Tiger Team agrees to featuresEIDR engineering develops specifications and scopes effortTWG reviews specifications and approves engineering planRemaining items from original “1.2” scope not addressed in Q3Episodic changes reviewed and approved by Tiger TeamEncoding/Manifestation, Container/Bundle/Franchise, etc.Priority issues from Ticketing Systems (Jira & Zendesk)Prioritized list of candidate Q4 features underdevelopment7

TWG - Q4 Candidate Features Improved UltraViolet support–– Improved support for bundles/containers–– Separate structure for franchisesAllows more intuitive treatment of compilations/compositesManifestations––– Based on experience from Member-provided test casesUVVU/Common Metadata/EIDR schema synchronizationImproved structure below Edits for digital asset and distributionproductsReplaces Language Variants with a track-based language approachOptional encoding profile (e.g. retailer-specific mezz. independentof an instance)Changes to required metadata––Country of Origin“Provisional” metadata (e.g. runtime on early registrations)8

POC – Status Update Richard has been covering POCs in Andrew’s absenceHari will take over responsibility for POCs starting Sept. 24In the interval, new POC activity has included:–––– Viacom experimenting with Clip registrationsDisney starting a new systems integration (Medusa)V2 spinning up as a new POC service provider (initially for Sony andBaseline)Feasibility research into external catalog matching (as was used fora recent HBO matching effort with incomplete metadata)Looking for volunteers to participate in new POCs (and follow-onTiger Teams)––––Video ServicesTheatrical window title registrations (MPAA/BBFC ratings pilot)Box office tracking via RentrakLive Events (with an initial focus on sports programming)9

Business, Marketing and Membership Updates Recruiting– European outreach at IBCCalendar – Q4–SeptemberOctober–Later Fall:– CableLabs Interop EventEMA Conference, 10/3, L.A.SCTE Cable Tec Expo – Demo at CableLabs Exhibit10/16-19, OrlandoEIDR Hosted Lab Event – L.A. or,All-day Member Meeting – exhibits, presentationsOther–––Cognizant Business Model study in progressStandards alignment/inclusion of EIDR (SMPTE, FIAT/IFTA, EBU/DVB)Revised Web site – accomplishments, deployments, use case handouts

Backup11

Edits/VersionTelevision Episodic MetadataMatching and Authority PracticesGovernance (parallel path) Will be ongoingBundles, Packages, Compilations Some discussions as part of episodicManifestations Products: based on languagetracks/resolution/format, not distributionchannelTrailers, VAM Previous discussions led to“Supplemental” referent type in 1.1PriorityWorkgroup QueueActiveTWG - Tiger Teams Priority/StatusStatusX1100%--X2100%-- 3ongoing-- 425%LateSeptember2 to 3 weeks510%LateSeptember4 weeks650%October2 to 3 weeks Target StartDate12ProposedDuration

POC’sDescriptionFinalizedStatusRecordsEIDR POCs – CompletedRovi CS POC1st of the Continuous Seeding efforts of new Rovi data recordsQ3 ‘11 26KDisney POCImplement APIs & Studio RegistrationQ3 ‘11 1.5KBaseline POC 1aBaseline ID's as Alt ID's for EIDRs.Q1 ‘12 4KComcast POC 1aInitial Asset Tracking: MSO-VODQ1 ‘12 10WB POCAPI Integration & Alt IDs (ISAN)Q1 ‘12 3K(1K)BUFVC POCRegistration of UK Broadcast TV ArchiveQ1 ‘12 500NBCU POCInitial API IntegrationQ1 ‘12 --IVA POC 1Alternate ID’s AddedQ2 ‘12 17KBaseline POC 1cAPI IntegrationJune ‘12 --Baseline POC 2EIDR Provided in feed to Baseline CustomerJuly ‘12 1KHBO POCInitial Data Model, Title Matching and API integrationAug ‘12 --WB/MSFT POCRetail DistributionAug ‘12 --

POC’sDescriptionETAStatusRecordsEIDR POCs - ACTIVEBaseline POC 1bGap Baseline records input & EIDR ID's to Baseline recordsQ3 ‘12C6KCIMM/TAXIRegistrations (CIMM participants)Q3 ‘12C5-10 perFox POCData Model, Title Matching and APIQ3 ‘12CTBDIVA POC 2API & Reg. of TrailersQ3 ‘12C25KSony POC 2Data Model, Title MatchingQ3 ‘12C45KNBCU/RentrakMetricsQ3 ‘12CTBDComcast POC 1bLarger scale Asset Tracking: MSO-VODQ3 ‘12CTBDBUFVC POC 2Matching & Registration (News & Dailies)Q3 ‘12C200Ericsson POCEIDR Integration (Initial stages – finding partner)Q3 ‘12C--MPAA POCEIDR#/Ratings Requests (Initial Stages – find partner studio)Q3 ‘12C--Disney POC 2New API & Title RegistrationQ3 ‘12C--Sony POC 3API IntegrationQ3 ‘12C--UFC (Zuffa)Data Model AlignmentQ4 ‘12C--Shaw POCData Model, Title Matching and APITBD (Q4)6--Comcast POC 2Linear-VOD Linkage via EIDRTBD6TBD

EIDR POCs: Deployment Projects – CompletedDescriptionParticipantsStatusAPI integration - digital distribution infrastructureDisneyDoneAPI integration – title-level registrationWB, NBCU, Baseline, HBODoneBaseline ID's as Alt ID's for EIDRs.BaselineDoneInitial Asset Tracking: MSO-VODComcastDoneUltraViolet registrationsSony, NBCU, WB, Fox,NeustarDoneMonthly seeding process for new movie/TV recordsRoviDoneNational TV Archive phase I registrationsBUFVCDoneAlternate ID’s added (ISAN & IVA ID’s)WB, IVADoneEIDR in metadata feeds to customerRovi, BaselineDoneWorkflow integration – online retailWB/MSFTDone7/23/2012EIDR Confidential15

EIDR POCs: Deployment Projects – ActiveDescriptionParticipantsStatusAPI integration - title management workflowShaw, Sony, Disney, BUFVCOngoingUltraViolet workflow integrationSony, NBCU, WB, Fox, Neustar, OngoingVOD workflow integrationComcast, NBCU, iNDEMAND,OngoingVOD link to linear metadataComcast, RoviOngoingMatching internal records to EIDR IDsDisney, WB, NBCU, Sony, Fox,Rovi, Baseline, BUFVC,OngoingRegistration of news & dailiesBUFVCStartingMetrics (VOD, Features & Advertising)Disney/ABC, Comcast, NBCU,Rentrak, CIMM(TAXI), othersStartingTrailers and supplemental materialsIVAStartingUse of EIDR ID’s for ratings requests, title and piracy trackingMovieLabs/MPAAStartingSports ProgramingHBO, UFC (Zuffa)Starting7/23/201216

Backup: Episodic Overview17

Episodic Change: Numbering Purpose– To address the various issues raised during the Episodic Tiger Team meetings, taking intoaccount the results of our recent Episodic practices survey.Schema Changes–Distribution Number (0-1 occurrences) –Studio Number (0.1 occurrences) –The identifier assigned by the producing/commissioning entityArbitrary string formatIncludes a domain to identify the sourceUsed in matching when availableAlternate Number (0.n occurrences) 17-Sep-12Typically original distribution/broadcast sequence within the seasonInteger with suffixSometimes requiredUsed for matching, across studio - metadata provider divideIncludes a domain to identify the sourceReplaces Sequence NumberCaptures other distribution or production number, e.g. from broadcasterNot used in automated de-duplicationIncludes a domain to identify the sourceSeeded House Numbers to be moved here18Copyright 2012 EIDR

Episodic Change: Season and Episode Naming Purposes– To capture studio and other naming– To provide useful display titles– To determine when the title has high value in matching Changes– Title has an attribute indicating whether it is derived from othermetadata (and therefore subject to practices variations) “series numeric” (existing title class value) “series date” (added for news and daily programming)– If no title is provided, rather than inheriting series title, one isgenerated from episode number and/or air date. No more inheritance of series title to seasons and episodes17-Sep-1219Copyright 2012 EIDR

Episodic Change: Validation Changes Allow mixed named and numbered episodes in a season– Currently, an entire season is considered ordered or unordered An Episode must have at least one of:– ResourceName, DistributionNumber or a full ReleaseDate– If TitleClass is “series numeric”, DistributionNumber is required– If TitleClass is “series date”, a full ReleaseDate is required17-Sep-1220Copyright 2012 EIDR

Episodic Change: Episode Class Purposes– Provide information for special matching handling Currently, episodes only matched against siblings in same season Some episodes should be matched against root TV/Movie records Pilots, holiday specials – practices can vary– Capture nature of non-standard episodes Changes– Add optional EpisodeClass (0-N occurences) “main” – part of main original sequence of episodes “pilot” – was the pilot for the series “standalone” – was or is in distribution as a standalone TV program (e.g. mergedpilot or mini-series) “special” – a holiday or other special “omnibus” – an edited down synopsis of other episodes (UK) “recut” – split, merged, e.g., 2-night from original 7-night– Allows pilots, specials and other standalone episodes to be matchedagainst root records for de-duplication17-Sep-1221Copyright 2012 EIDR

Episodic Change: Season Class Purposes– Provide information for special matching handling Currently, episodes only matched against siblings in same season Some episodes should be matched against root TV/Movie records Mini-series – practices can vary, especially on 1 or 2 night recuts– Capture nature of non-standard “seasons” Changes– Add optional SeasonClass (0-N occurrences) 17-Sep-12“main” – part of main original sequence of episodes“recut” – consists of episodes recut from an existing season“adjunct” – other extra season, e.g. original “webisodes”“placeholder” – for “null” season for series without seasons, whenoriginator’s data model requires an EIDR for a dummy season, suchas for mini-series groupings22Copyright 2012 EIDR

Episodic Change: Series Class Purposes– Provide information for special matching handling Mini-series and shorts sometimes registered as separate roots Practices vary, especially for two-part shows or mini-series– Support search for special types of series Changes– Add optional SeriesClass (0-N occurrences) “episodic” – normal episodic series “anthology” – non-episodic series, e.g. “Carstoons”, “ThreeStooges”, etc. “mini-series” – a mini-series In future could do special types for daily shows, sports, etc., ifneeded17-Sep-1223Copyright 2012 EIDR

TWG - 1.2 Update New 1.2 Development Effort Initiated - Renamed to 1.2 due to scope of schema changes - Primary development work in Q3 / deployment in October Features - Principal Agent, Directors (2), Actors (4) Agreement reached to allow maximum of 4 actors Required Metadata Change: PA or Director or 4 Actors PrincipalAgent strings required significant schema changes