M14
From AMWA-EBU
FIMS Geneva, January 2012
Meeting times:
Monday 23 January, Tuesday 24 January, Wednesday 25 January: 9am – 6pm Thursday 26 January: 9am – 3.30pm
List of participants
Roger Sacilotto, Avid; Manuel Escribano, VSN; Mathias Elser, IRT; Jean-Pierre Evain, EBU; François Helt, Doremi; Richard Cartwright, /Quantel; Praveen Dharmavaram, IBM; Chris Lennon, Harris; Zsolt Fulop, Harris; Paul Gardiner, Sony; Toshiaki Kojima, Sony; Mizuki Kanada, Sony; Jordi Gilabert, VSN; Yoshiaki Shibata (part of time), metaFrontier; Giorgio Dimino, RAI; Andreas Aust, Tixel; Loic Barbou, Bloomberg; Ashraf Tadros, Bloomberg; Brad Gilmer (from day 2), AMWA; Frank Schaffa (part of time), IBM; Peter Brightwell (part of time), BBC; Dan Shockley (part of time), TBS;
Day 1 - Monday 23 January: 9am - 6pm
Introductions
Done
Approval of Agenda
Approved
Meeting structure: Monday - Thursday
Approved with potential need for changes as discussion evolves
Status of updates to FIMS 1.0 specification
Updates made to latest draft since Herndon
updates remaining to be done (Kojima)
Kojima-San proposed a new template for describing classes in the specification. This was suggested on the reflecto. In the absence of comments, this has been implemented in a new version of the specification. See below the 'input documents'.
Minor Outstanding issues from Herndon meeting
Sony action items (Kojima)
- Error codes
Kojima-san took the group through the error code numbering scheme. Adopted policy will be reflected in the next version of the specification. OPN => SVC
- Implementation guidelines (with IBM)
The implementation guidelines should contain tips and examples (e.g. on SOAP-RPC and RESTful Implementations inc. sample sequence charts, sample xml and tips).
There could also be implementation guidelines on the service implementation and usage side (in.c sample code too).
IBM action items
- Extension
- Example of OutputFileNamePattern
- BaseProfile
- Service Consumer Interface
Major Outstanding issues from Herndon meeting
- Criteria for decision on way forward
This time is a unique chance to refactor the specification. Decision to be done after reports from the refactoring groups and review of comments.
Will need to be more specific about what is informative and normative.
An important part of refactoring is the definition of resources (in particular to be RESTful friendly).
- Refactoring (Richard)
From generic needs to technical details.
- Impact analysis on the current specification document (Kojima)
Kojima-san presented his views on job management for both RESTful and SOAP-RPC.
Part 1: At least need to modify/rewrite the Operation Implementation Pattern. -> limited impact (but smallest part of the document)
Part 2: Resource, messages, types and parameters. 1) implementation of new template 2) transition from "capture job resource" to "capture messages"
Kojima-san provided a significant list of necessary changes:
step1: fix the data model - THIS MEETING
step2: propose strawman schema - THIS MEETING
step3: review proposed schema -> cardinalities, etc. - THIS MEETING
step4: Modify part 1 / 8.1.1 - operation implementation pattern - POST MEETING EDITING
step5: Modify part 2: whole structure -> base and service documents - POST MEETING EDITING
step6: Create service description based on new structure - POST MEETING EDITING
step7: Full document review - POST MEETING EDITING
- Metadata (Loic)
Loic presented what is believes needs to be done to adapt the business object/content model to better address business needs.
The new approach to folders and locators seems to be converging with AS-02 but also open for any future specified or custom locator/folder structure.
Refactoring model was well received and work should lead in the implementation of the improved bmcontent data model. It was suggested to define the locators and related storage information under different namespaces, i.e. separate xsds.
AHG to work on formalisation in the document.
Also look at service capability description and classification schemes for audio/video codecs, container formats, etc. Look at plugin mechanism, etc.
- Discuss impact and conclude
1) An AHG on xsds will work in the morning of day 2 to come with a stable model and xsd. [Richard, Loic, Giorgio, Jean-Pierre, Praveen]
2) Another AHG can work on service operation re-alignment.
DECISIONS:
- BMObject - agreed with proposal from Bloomberg
- QueueInfo: In FIMS 1.0 report information for ONE queue only
- Consumer Service Interface: consider AFTER FIMS 1.0
- Refactoring: consensus to proceed: do minimum needed to be able to start AMWA review process quickly
PROCESS:
- send part 1 and xsds to AMWA Technical Group for review (checking that the specification covers the scenarios)
- work in parallel on template and final editing (fund external editor -> see fims-adm decision??)
- final review meeting on 20-21 February in Europe, announce coming specification to EBU TC call on 23rd February
- synchronise final 2-week voting/review in both AMWA and EBU
- get FIMS 1.0 published before NAB 2012
Day 2 - Tuesday 24 January: 9am - 6pm
Short Plenary discussion: 9am - 9.15am
Action Plan: see File:FIMS RefactoringActionPlan.ppt
Drafting groups: from 9.15 am
Three AHGs:
- Data model and XSDs
- Service management
- Template for part 2
General issues: 12pm - 1pm
- NAB 2012: paper, demo?
FIMS has not received any notification of acceptance or otherwise of the paper that had been proposed for the conference. We understand that the deadline for submission of a full paper seems to be traditionally around January 20th.
We have a proposal for a demo from Bloomberg, and the possibility of giving presentations on the booth. In principle, it is therefore a 'green light' for FIMS at NAB.
Bloomberg have offered to show us a demo during this meeting, and this is proposed for early on Thursday morning (shortly after 9am).
Roger Sacilotto is to coordinate the logistics of the FIMS booth, and will liaise with Lewis Kircaldie concerning an offer from Cinegy to help organise the delivery and build of the shell as per NAB 2011.
Jean-Pierre Evain will provide information on the cost of NAB 2011 and an estimate of the possible cost share for NAB 2012. Sponsors will be invited to support the effort finacially.
It is not realistic to expect to see FIMS-compliant products at NAB, with a final FIMS 1.0 specification being released only in March. FIMS members must avoid making product announcements, which would put the project in a difficult position when using the free space of the new technology area.
- IBC 2012: paper
There will be a coordinated collective abstract submitted to the IBC CfP, the deadline for which is February 10. FIMS members actively involved in the development of the specification are invited to inform Jean-Pierre Evain if they wish to be co-authors.
- Responses to Phase 2 update (brief) and next steps
Results of the RfT can be found on the wiki: [[1]]
Progress report from AHGs and actions
- AGH data model and xsd
Richard presented the results of the data model refactoring discussion held with Loic and with the other members of the data model AHG. The result is currently a simplification of the representation of the bmObject and BmContent. Frank Schaffa joined the webex and will do some tests (e.g. on grouping) using the current structure.
Final conclusion on the data model on Wednesday morning
Working version: [[2]]
Additional technical attributes:[[3]]
- bitrate, bitratemode, codecType (as proposed plus URI to CS term), + sample type + scanning format (see choice with mode)
- Service alignment across SOAP-RPC and RESTFul
Roger reported on the alignment issues and presented three scenarios.
The specification wouldn't need to be fundamentally changed but RESTful vs. SOAP could be covred through guidelines.
- template for part 2
Kojima-san reported on the new template.
The main attributes to be addressed have been identified. A template should be approved by the end of the week, which could be used by an external editor.
A solution is needed to address things like 'profiles', etc. but solutions have been identified when refactoring the xsd.
Day 3 - Wednesday 25 January: 9am - 6pm
1. Plenary discussion at 9am to identify/discuss outstanding issues.
- feedback from IBM on complex objects, resultMAP, formatID
- any other open issues? if so, resolve this morning.
- outline of schema review needed at this meeting (Kojima-san)
- modifications needed to Part 1
- define exact scope of work required for automation tool in XSDs->document generation
- logistics of passing our output to AMWA/EBU for review
- continue xsd preparation in small group(s)
2. Start of detailed strawman schema review: 2pm (tentative)
Discussion on feedback from IBM (Frank): the Implementation Guidelines will explain how the desired objectives may be achieved in the short term using FIMS 1.0. We will address the use case for complex objects at a later date - beyond the release of 1.0.
Work on xsds: is on track, will continue during the morning in a small group (Richard).
A second group continues to develop a schema template during the morning (Kojima-san).
At the conclusion of the meeting, formal notification to AMWA and EBU that the necessary information is available for the formal FIMS 1.0 review process to begin is to be made by FIMS-DEV chair (Paul Gardiner) to Brad Gilmer and Hans Hoffmann by email. This will contain links to the files (xsds and Part 1 'General Description' documentation) that will be made availabel on the Wiki.
Elephant in the room: Service Description schema - there might not be time to complete this during this week's meeting.
Day 4 - Thursday 26 January: 9am - 3.30pm
Review of data model and xsd drafting (formatId, descriptive metadata, etc.)
- FormatId:
now covered by the addition of resourceId and format is now a resource. The videoFormat, AudioFormat, ContainerFormat etc. also keep their IDs for referencing at service capabality description level
- Descriptive metadata:
general meeting participant agreement that minimum (DC/EBUCore like) descriptive metadata should be added to the FIMS xsd. A small AHG has reviewed and agreed on a profile of EBUCore for FIMS -> final decision by the group during plenary session
- Review of the properties of capture/transform/transfer
pending: add actual time properties to StartProcess in the base media service (although curerntly used only by the capture service extending the base service type)
- Additional technical properties
bitrateMode -> currently enumeration of variable and constant. Use of "none" to be discussed and make the schema consistent according to final decision
mode -> is no longer used -> replaced by resolution and scanningformat
Discussion on reference implementation and SDK according to decisions on refactoring
Not discussed
Bloomberg demo
Review Actions required to complete FIMS 1.0
General plan:
- Scope of phase 1 specification: SOAP-RPC with a data model compliant for future RESTful implementations
- Use Part 1, XSDs and reference implementation software to start the AMWA review process. Send doc to EBU TC for review in parallel.
- Finalisation of Part 2 (next Feburary meeting) for delivery at NAB
- Gather feedback at NAB and develop guidelines in time for IBC
Tools:
ACTION: Richard and Brad to investigate editorial support for developing a specification automatic editing tools (starting from the XSDs)
Important deadlines:
-> see Paul slide
- EBUCore descriptive metadata subset for fims will go in the XSD with a "description" namespace (see fims namespace structure) and 'desc' prefix.
ACTION: JP to send the latest finalised version to Richard on Friday 27 January, as reviewd and approved by the descc metadata AHG and with correct namespace and prefix.
Final review meeting: confirm date (21-22 February proposed) & location
Input Documents for discussion
Working Draft Specification FIMS_R1.0.0_20120117 (edited by Sony following Herndon updates)
- Part 1: General Description
- see: File:FIMS R1.0.0 Part1 SD4.zip
- Part 2: S0 Base Schema
- see: File:FIMS R1.0.0 Part2 Base SD4.zip
- Part 2: S1 Transfer Service
- see: File:FIMS R1.0.0 Part2 Transfer SD4.zip
- Part 2: S2 Transformr Service
- see: File:FIMS R1.0.0 Part2 Transform SD4.zip
- Part 2: S3 Capture Service
- see: File:FIMS R1.0.0 Part2 Capture SD4.zip
- Service Description (xsd files)
- see: File:ServiceDescription.zip
- Service Schema (xsd files)
- see: File:ServiceSchema.zip
Sony Presentations:
- Updates made to latest draft: File:20120118 Updates made to latest draft.ppt
- Sony Action Plan File:20120118 Sony Action Plan.ppt
- Data Model Refactoring Impact Analysist: File:20120118 ImpactAnalysis.ppt
Richard Cartwright - refactoring page - Proposed new FIMS data model [[4]]
Loic Barbou Presentation on bmcontent refactoring - see File:Bmobject structure v5.pdf
Richard Cartwright - XSD development in progress - end 24/01/2012: see File:Fims xsds RIC 20120124b.zip - mid 25/01/2012: see File:Fims xsds RIC 20120125b.zip - end 30/01/2012: updates in progress to base services File:BaseMediaService-V1 0 1-RIC-20120127.zip
Output Documents
Completed edits of XML schemas following the meeting: - File:FIMS V1 0 2 xsds.zip
The latest validated version of the schema is to be downloaded from here:
- File:FIMS V1 0 3 xsds.zip
Updates by Richard as per discussions on Thursday 2nd February 2012:
- File:FIMS V1 0 4.zip
- File:BaseMediaService-V1 0 4 1.zip
Updates on 9th February 2012 coordinated between Jean-Pierre and Richard following comments on v1.0.4:
- File:FIMS V1 0 5.zip
Update on baseMediaService after test with Bloomberg
- File:BaseMediaService-V1 0 5 4.zip
Update on 15th February 2012 after debugging session with Bloomberg and other cardinality corrections:
- File:FIMS V1 0 6.zip
IMPORTANT: subsequent updates including FIMS_V1_0_6-SD please see http://wiki.amwa.tv/ebu/index.php/M15
