Proposed Agenda: Media Timed Events Task Force call on Monday, April 30, 2018

Hello All,

a) Review of current use case and gap analysis -
        What areas other than streaming services require media-timed events?  e.g. digital publishing.
        What additional use cases should be considered?
b) Relevant work in other SDO's, including
        CTA WAVE
c) Deliverable format, e.g. document outline:
        1. Use cases & requirements
        2. Relevant standardization efforts
                MPEG Container-enabled web track
                W3C - datacue, WebVTT, TTML metadata cues,
                CTA WAVE -,
        3. Recommendations to W3C on standardization, which could include
	Use cases/Requirements document
	New standardization directions and/or draft API proposals
	Draft charter for new Working Group

-Giri Mandyam

Call details follow:

W3C Media & Entertainment Interest Group, Media Timed Events Task Force call WebEx details:

Monday, 30 April 2018
08-09 San Francisco / 11-12 Boston / 16-17 London / 17-18 Paris /
00-01 Tokyo (Tuesday)

Meeting number: 318 284 177
Meeting password: kgmVJ522
Meeting link:
Host key: 913831
Video address: Dial Audio connection: +1-617-324-0000 US Toll Number Access code: 318 284 177

IRC channel: #me on, port 6665, or

-----Original Message-----
From: Chris Needham <> 
Sent: Friday, April 27, 2018 12:28 AM
Subject: Media Timed Events Task Force call on Monday

Dear all,

Due to the public holiday in Europe, there will be no IG call on Tueday 1 May. The next call will be on Tuesday 5 June.

However, I am happy to announce the start of the Media Timed Events Task Force, as discussed on previous IG calls [1, 2].

The Task Force will meet on Monday, April 30, 2018 at:
11:00 am | EST (New York, GMT-04:00) | 1 hour

The Task force will be led by Giridhar Mandyam, and have three primary deliverables, which we aim to complete by TPAC 2018:

a) Use cases and requirements for media-timed events in web streaming applications.
b) A survey of existing web technologies and whether they can be applied to meet the identified use cases.  This will include existing or planned support in web runtime engines.
c) A proposal on requirements for new APIs or extensions to existing APIs that can be used to meet use cases that are not currently satisfied by existing web technologies. This can include pre-standards API specifications.

There is an initial GitHub repository at [3].

I have posted connection details for Monday's call to the member list. I hope you can join us, although I realise the short notice.

Kind regards,

Chris (Co-chair, W3C Media & Entertainment Interest Group)


Received on Monday, 30 April 2018 13:55:17 UTC