W3C

Timed Text Working Group Teleconference

02 July 2026

Attendees

Present
Atsushi, Chris_Needham, Gary, Nigel, Pierre
Regrets
Andreas, Cyril
Chair
Gary, Nigel
Scribe
nigel, cpn

Meeting minutes

This meeting

Nigel: Today it looks like we have no DAPT agenda items
… There's one thing for the TTML Media Type and Profile Registry
… an update on interop for WebVTT
… TPAC planning - check the draft schedule
… I don't know of any update on AI technologies
… Any other business, or points to cover?

Pierre: Nothing from me on the agenda

Nigel: Thanks.

TPAC Planning

Draft TPAC schedule

Nigel: There's a draft TPAC schedule. TTWG meets most of the day on the Thursday (29 Oct), after the MEIG + TTWG + APAWG joint meeting
… But that joint meeting is at the same time as AGWG, and ARIA WG. There might be an overlap of people
… Media WG meets on Friday, no overlap
… On Monday, MEIG is the first half, then there's a joint meeting after lunch. Audio WG meets all day Monday
… This means we meet Monday, then Thursday and Friday. If this doesn't work for anybody, this is the time to give feedback

Gary: I won't be there in person, which means I'll only be able to join remotely in the afternoon (in TPAC time)

Nigel: Andreas said he'd prefer to meet towards the end of the week, so it works out for him

Gary: Demuxed hasn't been announced yet, and there's a possibility it will overlap

Nigel: I'll ask Phil not to do that!

Nigel: I'm not hearing reasons to ask for changes
… I think they only want feedback if there are issues

Chris: Yes

Nigel: Anything else on TPAC?

(nothing)

TTML Media Type Definition and Profile Registry

Auto-publish status

Nigel: What's the status of this?

Atsushi: It will be working shortly

Nigel: Anything else on the Registry?

(nothing)

WebVTT

Interop update

Gary: We met last week and we're going to try to meet about every other week
… In the last meeting, the WPT group want scoring criteria to be able to show whether we're making progress or not
… The current rendering tests should cover about 75% of the score, with the other API and parsing tests being the other 25%
… Rendering is the big interop issue, and that exercises the entire stack, which is helpful
… The other thing, is to have people looking at the tests to see if anything is wrong, in their own time. Instead we'll spend meeting time on that, which should work better
… Having people be able to discuss in a meeting is helpful, especially where there subjectivity involved

Nigel: It's interesting that some things are subjective, does that point to things that need to be defined objectively in the spec, or is that by design?

Gary: Sometimes it's unclear what the tests are trying to do, until you look into them a bit more

Nigel: So you don't envisage changes to the spec?

Gary: This interop work is identifying the tests that are definitely failing. Are the tests wrong, are the browsers rendering incorrectly, or is the spec incorrect and needs to be updated?

Nigel: Are there notes?

Gary: Not really, last time only a few of us joined, myself, Dana, and Romain

Nigel: How do people find out about the meetings?

Gary: In GitHub, nothing more formal

<gkatsev_cloud> webvtt interop github

Nigel: Anything more on WebVTT, or other topics?

Meeting close

Nigel: Thanks everyone, we've completed our agenda, let's adjourn.
… See you in 2 weeks 2026-07-16

Agenda issue for 2026-07-16 meeting

Nigel: [adjourns meeting]

Minutes manually created (not a transcript), formatted by scribe.perl version 248 (Mon Oct 27 20:04:16 2025 UTC).