FIMS Repository Interface IBC 2012

A Bit of History How did it start? –FIMS members defined the need to standardize repository operations –FIMS business board selected the repository interface as the next project for the FIMS technical board –FIMS business board defined scope by creating business use cases –FIMS members created a sub group dedicated to the repository interface project: FIMS REP

User Involvement: Business Board A group of users –Ad-Id, AMWA, BBC, Bloomberg, CBC, EBU, HBO, ITV, MLB, MTV, NBC, NFB, RAI, Red Bee Media, Turner, Viacom Scope –Identify business needs –Prioritise FIMS work Selected Project –Repository service Interface

FIMS REP Group Overview –The FIMS Rep has started its operation on June 6 th 2012 – It is lead by Loic Barbou (Triskel / Bloomberg) Contributors –The members have not stopped growing since the inception of the group and are represented by consumer and vendor organizations (AMWA, AVID, Bloomberg / Triskel, BBC, Dalet, EBU, IBM, PointSource, SONY, SVN, Turner)

The Repository Interface Objectives –Basic CRUD functions on Assets within the repository (create, read, update, delete) –A mechanism to handle versioning of assets –Simple locking capability (check in, out) –Management of simple, self contained media assets –Management of complex, composite media assets –Management of core metadata set with pass-through of implementation specific “dark” metadata. –Query of core metadata set (see search comment under constraints) –Creation of FIMS asset GUID –Support for mapping of house and industry ID’s to FIMS asset GUID’s

The Repository Interface Objectives –It is possible that some implementations will not support all functions of the repository interface. There should be an API that advertises all supported operations so that external systems can automatically determine a repository’s capabilities. –Passing of credentials to support externally managed security mechanisms –Event model that allows external systems to subscribe to events that occur within the repository –There should be a capability for an external management system to re-synchronize state with a repository. –Mapping mechanism that allows complex objects to be mapped to the underlying asset object model. Should allow for new complex assets to be created without significant effort.

Scope Consideration for V1

The Repository Interface Definition What it does: –Provide interface for media operations (Ingest,Create, Read, Update, Delete) –Expose a way to manipulate content and metadata –Enable a query interface to retrieve media assets –Represent a service interface to be consumed by a workflow engine

The Repository Interface Definition What it does NOT do: –Handle complex workflow operation (Archive, Transcoding, … ) –Control relationships between assets (Parent-Child, Logical Grouping) –Provide an interface to be directly used by a user facing application

Project Progress Requirements –Translate business objectives into technical use cases (100% completed) –Define specifications (100% completed) Design interface operations –Design service operations and associated payload (draft version 80% completed) –Design and implement WSDL and XSD (draft version 75% completed) Validation and first implementations –AVID and DALET have started to map their internal APIs to the WSDL and XSD

FIMS 1.07 and Repository Interface Same philosophy –The repository interface operations follow the same patterns defined in FIMS 1.07 –SOAP and REST web services compatibility Object definition –Existing objects defined in FIMS 1.07 are reused to represent payload in repository operation –Same media asset representation (BmContentType) allowing easy chaining of FIMS services (Repository, Catpture, Transform, Data transfer )

Repository Interface Design Defined operations –GenerateID, AddObject, AddContent, Repository Capability Settings, UpdateObject, UpdateProperties, UpdateState, Lock, Unlock, DeleteContent, UndeleteContent, DeleteObject, UndeleteObject, PurgeContent, PurgeObject, GetBMContent, GetBMContents, RetrieveBMEssence,…… Technical information –Detailed description of service interface in “FIMS Repository Service Interface Design.pptx” –WSDL and XSD Repository-V1_0_0.wsdl TODO publish doc to wiki and put the links Repository-V1_0_0.xsd

Next Steps Complete Design –Interface operation and payload –Generation of WSDL and XSD –REST API Documentation –Interface documentation –Implementation guideline

Next Steps Validation & Implementation –Vendor repository Interface implementation AVID Dalet –Customer repository interface implementation Bloomberg / Triskel

More Information --- Need to be updated Demo –Need to get status from Stephane and Roger FIMS Wiki Site – Contact Information –Loic Barbou –Group Distribution list