Media APIs

From Web and TV IG

Media APIs Task Force [apis]

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

Current Work

The TF has finished an iteration of work on a list of Use Cases and Requirements. The use cases and requirements have then been cross-referenced in a spreadsheet, and we are now working on gap analysis against a list of known technologies. One of these gaps is for a Tuner API which the Task Force thinks should be addressed by forming a Community Group.

Other documents - historical - include:

  1. The initial repository of Terminal Capabilities Use Cases
  2. The initial repository of Recording and Downloading Media Use Cases
  3. A list of known Metadata Formats to be used as reference in discussions about APIs and metadata exchange.

How we Work

Iterations and Timeline

The task force work 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)

The First Iteration of work is due to end around the time of TPAC 2013. As suggested by e-mail and discussed at the 2013-08-21 teleconference, the timeline of work for this iteration is as follows:

  • Aug 28th: last chance to submit UCs for inclusion in the first iteration
  • Sept 4th (conf call): discuss and agree on the final list of use cases included in the first iteration
  • Oct 2nd (conf call): finalize and agree a list of requirements derived from the use cases
  • Oct 30th (conf call): finalize gap analysis
  • 12th of November (TPAC): review and approve the WG note including UCs, Req. and Gap analysis and discuss next steps.

The Second Iteration of work will proceed according to the following schedule:

  • May 28, 2014 (conf call): last chance to submit UCs for inclusion in this iteration
  • Jun 25, 2014 (conf call): final list of use cases included in this iteration
  • Jul 23, 2014 (conf call): publish the first draft note on requirement extraction and gap analysis
  • Aug 20, 2014 (conf call): decide what group we should have joint sessions during TPAC 2014
  • Oct 1, 2014 (conf call): finalize requirement extraction and gap analysis
  • Oct 27?, 2014 (TPAC) review and approve the IG note including UCs, Req. and Gap analysis and discuss next steps.
  • End of 2014: finalize note and kick off next steps

Submitting New Use Cases and New Ideas for Second Iteration of Work in 2014

A dedicated wiki page to gather New Use Cases and New Ideas for the Second Iteration of work in 2014 is available. The following process shall be followed:

  • Everyone is encouraged to contribute a Use Case or even a Topic of Interest for further discussion. The contributor is the Owner of the submitted Use Case or Topic of Interest.
  • The Owner takes the full responsibility for providing sufficient details of a Use Case or a Topic of Interest.
  • If, at the time of submission, the details of a Use Case or a Topic of Interest is unclear and further discussion is expected, the Owner takes the full responsibility for driving the related discussion and supplying sufficient details following the discussion.

Please note: The Use Case or Topic of Interest will be removed if there is still no sufficient details by the time the final list of use cases is scheduled to complete.

Discussion & Calls

Meeting Agenda and Minutes

Submission process

  1. Some document have named editors. In such a case, suggestions for changes should be discussed on the list, and will be enacted by the editor.
  2. For a new piece of work or an addition or change to a document without an identified editor, refer to the process described above.
    1. The target use case is described, including use case, proposed technology, ...
    2. Each use case is discussed into the mailing list
  3. An Editor or moderator will consolidate information


  • Bin Hu (AT&T) — moderator
  • JC Verdié (MStar) — moderator
  • Olivier Thereaux, BBC — moderator
  • Bob Lund (CableLabs)
  • Calin Ciordas (Irdeto)
  • Christian Fuhrhop (Fraunhofer FOKUS)
  • Steve Calzone (Cox Communications, Inc.)
  • Daniel Davis (W3C)
  • David Corvoysier (Orange)
  • Geun-Hyung Kim (Mobile Web Forum)
  • Giuseppe Pascale (Opera)
  • Glenn Adams (for Cox Communciations, Inc.)
  • Graham Clift (Sony)
  • JC Dufourd (Telecom ParisTech)
  • Jean-Pierre Evain (EBU)
  • José Luis Redondo (EURECOM)
  • Kaz Ashimura (W3C)
  • Mark Vickers, Comcast
  • Pablo Cesar (CWI)
  • Paul Gausman, AT&T
  • Pierre Lemieux (supported by MovieLabs)
  • Raphael Troncy (EURECOM)
  • Sheau Ng (Comcast-NBCUniversal)
  • Sung Hei Kim (ETRI)
  • Wook Hyun (ETRI)
  • Yosuke Funahashi (Tomo-digi)
  • Cyril Rickelton-Abdi (Turner Broadcasting System, Inc.)
  • Bryan Sullivan, (AT&T)
  • Skip Pizzi (NAB)
  • Louay Bassbouss (Fraunhofer FOKUS)
  • Tatsuya Igarashi (SONY)
  • Giri Mandyam (Qualcomm Innovation Center)
  • Glenn Adams (Cox Communications)
  • Edit and add your name here