This document lists the use cases, implied requirements and identified gaps that the Media API TF of the Web and TV IG has considered during his first iteration of work (March 2013 - February 2014)
Introduction
The Media APIs task force, part of the W3C Web and TV interest Group, merges the focus of three previously independent task forces (terminal, metadata and recording&downloading) and focuses on:
- Identify requirements for recording and downloading media
- Investigate requirements for discover and control of device capabilities (e.g. tuner control)
- Investigate how to expose TV metadata to web applications
- Investigate mapping between Media Element API and in-band metadata
- Synchronization of broadcast content and web applications up to frame accurate
The task force works in iterations. Each iteration is made of 4 phases of work:
- Phase 1: collect use cases
- Phase 2: generate requirements
- Phase 3: gap analysis: are there existing spec covering this requirements already? If not, which specs/WGs would need to be addressed to fill these gaps?
- Phase 4: consolidate UCs, reqs and gap analysis in one document and discuss next steps (reach out to WGs, etc)
This document it a report of the result of the first iteration of work of the Media APIs task force.
Use Cases and Requirements
During the first phase of his work, the TF has asked members to contribute use cases that they were interested in investigating.
Such use cases have been collected on the TF wiki and are available here
Starting from the Use Cases pointed above, the TF has derived a set of requirements; these are also recorded on the TF wiki and available here
The use cases and requirements have then been cross-referenced in a spreadsheet .