1 / 4

FIMS 1.0 Refactoring Action Plan for EBU & AMWA (January 2012)

This document outlines the necessary actions for the FIMS 1.0 refactoring process, conducted by EBU and AMWA from January 23-26, 2012. Key initiatives include fixing the data model, proposing a strawman schema, and modifying Part 1 and Part 2 of the documentation. The plan also details a timeline for document reviews, service descriptions, and updates to the EBU Technical Committee. Coordination among groups is vital, focusing on data model finalization, service operation realignment, and SOAP message definitions. Collaboration with IBM and AMWA is anticipated for effective implementation.

gaetan
Télécharger la présentation

FIMS 1.0 Refactoring Action Plan for EBU & AMWA (January 2012)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FIMS 1.0 Refactoring Action Plan EBU-AMWA FIMS 23-26 January 2012

  2. Main actions required (Kojima-san's Impact Analysis) • Fix the Data Model • Propose a strawman schema based on the data model • Review the strawman schema one by one • Occurrence • Inclusion • Meanings etc. • Modify Part1 at least 8.1.1 Operation Implementation pattern • Description of the new concept could be described in the Implementation Guideline • Modify Part2 whole structure • Both Base and all Service documents • Create Service Description based on the new structure • Full Document Review

  3. Proposed FIMS 1.0 completion schedule - overview • Thursday 26 January • complete updated xsds and updated Part 1 for AMWA and EBU review • Monday 13 February • complete Part 2 documentation: base schema & the three services • IBM to oversee this, with possible AMWA assistance? • 20-21 February FIMS-DEV meeting (location TBA) • final review meeting (including Part 2 documents) • 'demonstration of complete coverage' • deliver Part 2 to EBU and AWMA at conclusion of meeting • 23 February • give update to EBU Technical Committee (J-P/Giorgio, call) • Early April (before NAB) • result of AMWA vote known? • outcome of EBU Technical Committee approval process known? • TBD • finalise Implementation Guidelines

  4. FIMS 1.0 completion schedule - this week • Tuesday morning: • Group 1: Finalise Data Model • BMObject. • merge changes since Herndon, refactor xsds • propose strawman schema (Kojima-san to then investigate,, feedback Weds/Thurs) • Group 2: Service operation re-alignment (Ashraf/Roger) • SOAP RPC message definitions • Group 3: create template(s) for new Part 2 document (Kojima-san) • 12pm to 1pm NAB/IBC discussion (Jungfrau) • Tuesday after lunch: • Group 2: SOAP RPC message bindings - wsdl (Kojima-san feedback Weds/Thurs) • discuss & define possible assistance from AMWA for Part 2 • NB separate Admin Group meeting at 4pm (Giorgio, Paul, J-P, Brad etc) • Wednesday • 9am: brief Plenary discussion, then resume drafting • create service description based on new structure • modify Part 1 Section 8.1.1 Operation Implementation patterns (Richard) • Thursday (NB finish 3.30pm): • review strawman schema, with template (start Wednesday afternoon)? • Implementation Guidelines: define schedule

More Related