W2
From AMWA-EBU
Thursday 10 December 2009, 17:00 - 18:30 CET
Contents |
List of participants
- Giorgio Dimino
- Ian wimsett
- Brad Gilmer
- David Caroll
- Paul Turner
- Jean-Pierre Evain
- Peter Brightwell
- Dieter Haas
- John Footen
- Alberto Messina
- Rico Zimmmermann
- Andreas Ebner
- Reinhard Knoer
Discussion on the RFT content
Objectives
Giorgio had sent a contribution on how to start the work on the definition of requirements.
Objectives of FIMS from last meeting:
- Framework for interoperable media services
- Goal: publish RFT - > but what can be practical?
Proposal: start from practical use cases - agreed
Identification of use cases
Use cases will form the basis for testing the framework for responses to the RFT in particular in Phase 1 on a 'service definition format'.
Giorgio went through a document prepared with Al Kovalic File:Contribution on RFT discussion.pdf in which several uses cases have been identified - the list was augmented during the discussion:
Case 1: transcode - arguably built at media layer from an SOA perspective (depends on the use case) -core service usable in different contexts. Needs to be well contextualised.
Case 2: multi-processing - cloud computing architectures - dynamically select an instance of a service according to context and requirements -> discovery, description and invocation of the service
Case 3: player control and display selection - real time service
Case 4: capture
Case 5: editing: human/machine interaction
Case 6: news: dynamic operation and service access, prioritisation, resource booking
Additional requirements
- cases should not be limited to internal B2B operation but also apply to exchange between organisations -> what is the impact on service characterisation?
- cases should address security and access in collaborative environments
- cases should address accountability of service usage -> e.g. for pay per use -> monitoring -> reporting (what was done and how much resource was used for what cost) in particualr for use in a multi-client environment
- cases should address manipulation of metadata within the asset
- cases should address quality control (automatic and human)
The RfT on service definition shall also address specific technical requirements such as:
- Specific extensions
- etc.
Use case editing
The following individuals have volunteered to edit a first draft description of one or more use cases as follows:
- John on editing
- David on transcoding
- Paul on interactive with metadata
- Peter and David - reservation and reporting
- Dieter - machine and human intervention related to reservation and reporting
- John - dynamic news environment
- Ian - approval steps including quality control
- Giorgio - capture inc. player control
The above service are seen as 'atomic services'. More complex processes and workflows (e.g. scheduling and play-out) will be considered later based on commercial requirements.
A template will be used based on a combination of the BBC and IRT (EBU P/CP) forms including key concepts from the OASIS model introduced by Jean-pierre during the webex File:OASIS use in FIMS.pdf.
ACTION - Andreas and Peter to send the forms to Jean-Pierre
ACTION - Jean-Pierre to prepare a template combining the forms and OASIS concepts
DONE - File:UseCase template definitions v1.pdf A text version has also been circulated
Administrative matters
Wiki
The wiki has been updated with a 'news' and 'contacts' page.
The wiki is updated regularly with agendas, meeting notes, documents, etc.
Press release
The press release announcing the launch of the FIM TF can be found in the 'news' and 'documents' sections.
F2F
The need for a future F2F meeting has been discussed.
There is a proposal to organise the first F2F meeting at the EBU in Geneva around the PMC seminar (2 to 4 February 2010)
ACTION: Jean-Pierre to organise a survey
