FIMS Specification Group EBU-AMWA FIMS July 2011

FIMS Specification: July2011: Overall Plan 24 July: 10: :00 –IPR Policy –Agenda –Introductions –IBC Demo planning –FormatID - Lewis –LUNCH: 13: :15 –Overview of Actions remaining from Previous meetings –Status of current draft –FIMS Timing Model - see Section 8.2 (Kojima-san/ Al) –Descriptive and technical metadata (J-P, Lewis)

FIMS Specification: July2011: Overall Plan 25July: 09: :30 –Summary of outcome of Day 1 –Service description technical metadata (Lewis) –Action plan to complete document Service capability & configuration description: Section 7 –Include mapping of fields for Vendor: define fields diagrams Section 9 FIMS WSDL (XML) Capability Description (XML) Configuration Description (XML) –Complete review of current draft (to continue on Day 3) Afternoon: document editing

FIMS Specification: July2011: Overall Plan 26July: 09: :00 (approx) –continue discussion and specification editing –10: :00 [to be confirmed] Phase 2 discussion

FIMS - Intellectual Property Rights Rules "This meeting is being held under the Intellectual Property Rights Policy of the Advanced Media Workflow Association. By signing in and attending this meeting, you have agreed to be bound, and your employer, if a member of the AMWA, is already bound, by that policy. If you are unfamiliar with that policy, please ask the Chair of this meeting, and s/he will provide you with a copy of that Policy. At this time, I would ask that anyone in attendance inform me if they are personally aware of any claims under any patent applications or issued patents that would be likely to be infringed by an implementation of the specification or other work product which is the subject of this meeting. You need not be the inventor of such patent or patent application in order to inform us of its existence, nor will you be held responsible for expressing a belief that turns out to be inaccurate."

Actions from May 2011 (1) (status as at 14 June) –Relationship between FormatID and techMetadata (Lewis) - ON- GOING – Output Filename Pattern needs examples in spec 1.0 FRANK - ON-GOING - Frank/Praveen –Queuing (Lewis) - (6.2.5) ON-GOING - resolved? Now CLOSED – Timing model (PG, Al, Kojima-san) - ON-GOING - CLOSED – What does it mean to be 'FIMS Compliant'? (Jean-Pierre/Giorgio) ON-GOING - ON-GOING J-P – Support in BMObject for a service returning a set of split files for a job (Giorgio) - ON-GOING ? Paul to Giorgio (CONFIRMED CLOSED) – QueryJobRequest (Lewis) - ON-GOING: ExtensionType - need schema : DONE - no more to do – and : add text on acknowledgment: Paul to provide text based on Sony proposal - ON-GOING /

Actions from May 2011 (2) (status as at 14 June) –Harmonise the use of Tech 3293 with RP224: JPE to propose a solution for a RP224 CS Schema compatible with Tech 3293 metadata schema / attributes adopted by FIMS - ON-GOING, Lewis & J-P ON- GOING – DataFormatType: proposals for improvement from Roger: DONE - document to be updated: put on agenda NY meeting - also Service Lifecycle cleanup –Diagrams: several to be modified by IBM (inc. Fig. 7: states associated with long-running job) - ON-GOING Section 9

Actions from June 2011 (3) - Relationship between FomatID and technical metadata (Lewis) See: ON-GOING - Metadata structure proposal: Jean-Pierre to update his proposal (clarify relationship with Lewis action above?) Mapping of fields for Vendor: define fields after discussing with J-P (Lewis) PUT ON AGENDA NY DAY update BaseProfileType to include Atom list KOJIMA-SAN TO REVIEW - Figure 1: amend to make 'Services' generic (Kojima-san) NO ACTION REQD - Figure 4: update (Kojima-san) NOW FIG 2 DONE - Figure 5: amend to indicate two different locations (Kojima-san) DONE - Section 9: move Composite media services to new Appendix (Paul) DONE - Section 9: move parts to Section 5 (Paul) DONE : consider renaming "Source Information Service" to "Media Information Service" DONE - FIMS Job Execution Model (proposed by Al): develop strawman update to specification (Kojima-san) DONE Section 8: Had been updated since M8, but not discussed in M9. This will need to be updated, with updated schemas. NOW SECTION 9. DONE

Summary of outcome of Day 1 IBC Demo Planning –JeanPierre presented the floor plan for the FIMS demo at the EBU booth. –Agreed on the configuration of one 42' screen with a table for the IBM/Sony area. –Kojima to investigate required margin of height and depth of the table. (by when?) –JeanPierre to confirm (by when?) the exact date and time to start the connection test the exact date and place where equipments to be shipped. –All vendors who will provide equipments to provide an equipment list. (by when?)

Summary of outcome of Day 1 IBC Demo Planning (white Paper) –John Footen to update the 'Generic FIMS PowerPoint presentation' used at the NAB Show. –Kojima to create a strawman draft of the FIMS white paper. Target date to circulate draft: 19th August

Summary of outcome of Day 1 Action Plan –IBM to create examples of "Output file name pattern". – Jean-Pierre to create a draft of "What does it mean to be 'FIMS Compliant'?" –Ask Giorgia for the meanings of "Support in BMObject for a service returning a set of split files for a job" (Done, text is in Section 5.4) –Kojima to handle "add text on acknowledgment: Paul to provide text based on Sony proposal" –Clarify final conclusion of the following issue: Harmonise the use of Tech 3293 with RP224: JPE to propose a solution for a RP224 CS Schema compatible with Tech 3293 metadata schema / attributes adopted by FIMS

Summary of outcome of Day 1 Action Plan (Continued) –Roger to present "DataFormatType: proposals for improvement" and "Service Lifecycle Cleanup" on Day 2. –IBM to update schema diagrams in section 9 after all the schemas are fixed. –Kojima to check the meanings of "6.2.8 update BaseProfileType to include Atom list "

Summary of outcome of Day 1 Format ID issue –Lewis and JeanPierre presented the proposal of format ID and metadata issues. –Kojima presented the proposal of format ID. –Agree that format ID will not be used at least in the phase 1. –Question is whether we adopt: formatAbstractType which can choose either format ID or techMetadata –advantage: do not need the basic structure at the phase 2 OR techMetadata only –advantage: simple –All members to review the metadata structure proposed by JeanPierre. (by when?) –Question: who is responsible to reflect the outcome to the FIMS specification and specifically in which section(s)?

Summary of outcome of Day 1 Time Constraints –Kojima presented the proposed Time Constraints consists of Time Constraints parameters –StartJob/FinishBefore, StartProcess/StopProcess Proposal of adding Configuration Description in addition to the Capability Description List of possible issues to be added in the Capability Description and Configuration Description in terms of Capture Service. Proposal of adding an inquiry message to obtain the location of the Capability Description and the Configuration Description. Proposal of adding "availability" parameter in the queue management response. –We have basic consensus. –Question is: are all these proposals approved as is? All members to review the proposals. (by when?)

Summary of outcome of Day 1 Time Constraints (continued) –Question from Kojima Is it a good idea to include following diagrams in the ProposedCaptureRequest_rev4.ppt to the FIMS specification with text? –slide 5: Proposed Capture Request Schema –slide 6-8: Relation between StartJob and StartProcess –slide14: Proposed Stream Time Constraints –slide 15-22: Use case examples

Proposed Assignment of the FIMS Specification FIMS Management? 1.Scope 2.Conformance Language 3.Reference Documents 4.Overview - Overview - What is described in each section Sony? 5.High-Level Architecture FIMS Framework reference model (Final target & current) Media-centric issues (move from (old) section 9) Service Taxonomy

Proposed Assignment of the FIMS Specification IBM? 6.Media Service Management Service life cycle Job life cycle Move Service Behavior to section 8 Cinegy? 7.Media Service Awareness Service registry, Discovery Service Capability, Configuration

Proposed Assignment of the FIMS Specification Sony? 8.Media Service Behavior Move from 6.2 Service Behavior Concept, background of FIMS Service Communication – Mesasge (Notifications) – Event – Essence Container, descriptor – Profiles – Time Constraints Proposed by Sony, Reviewed by IBM? (IBM:WSDL) 9.Media Service Communication Schema Explanation

Summary of outcome of Day 1 Sony? –Appendix Kind of trailer of future versions –Pipelined Media Services, etc