1. FIMS Repository Interface Project Update 01/23/2013

2. 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

3. 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

4. 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, Turner, VSN)

5. Kudos to the Team –The FIMS Rep Team has spent ~45 hours since the beginning of the project in web conferences –Many Team Members have contributed a lot of their time outside of the meetings –Participation has been constant and productive during our weekly sessions

6. 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

7. 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.

8. Scope Consideration for V1

9. 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

10. 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

11. 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 100% completed) –Design and implement WSDL and XSD (draft version 100% completed) Validation and pilot implementations –FIMS DEV Team has reviewed the WSDL and XSD –AVID and DALET have started to map their internal APIs to the WSDL and XSD

12. 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 )

13. Repository Interface Design Defined operations: Repository Interface –GenerateUniqueID, AddObject,AddContent, ReplaceObject, UpdateProperties, UpdateStatus, Lock, UnLock, ClearLock, RetrieveOpenLocks, DeleteContent, UnDeleteContent, DeleteObject, UnDeleteObject, PurgeContent, PurgeObject, GetBMContent, GetBMContents, RetrieveBMEssence, MediaQuery. Defined operations: Repository Notification Interface –NotifyAddContentResult, NotifyAddContentFault, NotifyPurgeContentResult, NotifyPurgeContentFault, NotifyPurgeObjectResult, NotifyPurgeObjectFault, NotifyRetrieveBMEssenceResult,NotifyRetrieveBMEssenceFault, RepositoryEvent.

14. Repository Interface Design Defined operations: Repository Capabilities Registry Service –GetRepositoryState, GetStorageAvailableCapacity, GetPerformanceIndicator, GetRepositoryReport, GetRepositoryGeneralCapability,GetSchemaExtensions, GetUpdatableProperties, GetQueryResultsetDefinitions, GetSearchableProperties, GetRepositoryDefinitions, GetSuperLockToken, GetSupportedStatus.

15. Repository Interface Design Technical information –Detailed description of service interface in “FIMS Repository Service Interface Design.pptx”  To be updated –Latest WSDL and XSD https://www.box.com/s/hq1tn3i88pq6vaj6z7ag

16. Next Steps Design Validation –Review by FIMS-DEV group during Geneva meeting –Validate design by comparing our work with CMIS and CDMI standards –REST API compliance validation Implementation –Define REST API Documentation –Interface documentation –Implementation guideline

17. Next Steps POC Implementation –Vendor repository Interface implementation AVID (already have a working prototype for content ingest, was shown at IBC ) Dalet –Customer repository interface implementation Bloomberg / Triskel

18. Next Steps Major Milestone –Repository Interface draft version by NAB 2013 –Early adopter demo by NAB 2013 –Repository Interface release (or Beta) version by IBC 2013 SOAP Interface REST API Interface (To be re-evaluated post Geneva meeting) Interface documentation