W3C

Timed Text Working Group Teleconference

13 March 2025

Attendees

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

Meeting minutes

This meeting

Nigel: Our agenda is DAPT and IMSC 1.3, then charter questions.
… Given the regrets from Cyril and Pierre there's not much we can do on the first two.
… Thinking about the DST change and attendance difficulties,
… I propose that we move an hour earlier in UTC from next call so we share the load of the
… DST mismatch between the US and Europe equally.

Atsushi: I'm in i18n in the previous hour so I would have a clash for the next meeting

Gary: We should check if it would make a difference to Pierre and Cyril

Nigel: Atsushi, are you OK if we meet without you?

Atsushi: Yes, but I'll be on IRC if needed

Nigel: So we'll do that for the next call

DAPT

Nigel: We published CR!

DAPT 1st CRS

Nigel: Thank you to everybody, this is good news
… I noticed when previewing it, the styling isn't ideal in dark mode. I created a PR to fix it, but the W3C stylesheet seems broken
… Can we fix it in-place?
… I can't do anything about W3C's fixup script

Gary: It should be possible to do it all in CSS, you'd have 4 blocks of stuff in the CSS

Nigel: But there's a bug in the fixup script that it doesn't apply the class on page load

Gary: Is there an issue open against that script?
… Would be good to open an issue

Nigel: Making it readable in dark mode would be an improvement

<nigel> +1 to opening an issue - I don't know which repo fixup.js is in though

Nigel: Atsushi, can you look into the styling problem?

Atsushi: I can't make it happen before publication

Nigel: It works OK only if the in-page setting agrees with the browser-level setting

Team questions about the Charter

Team question in strategy issue thread

Nigel: There are two questions, one on VTT, one on TTML2

Atsushi: This comment was raised in the Team's final review before submitting for AC review
… The main concern from the wider team is that development of these specs seems to be suspended
… Is the WG really intending to continue development especially for the w3c/ttml2#1211 issue?

Nigel: I'm looking at the i18n discussion, The CSS and xsl:fo question needs a bit of research

Nigel: Other concerns?

Atsushi: I think the team wants comment from the WG on its intentions

Nigel: Important to note, with DAPT we'll need some tweaks to TTML2, which I predict we'll do
… The main TTML editor has stepped away a bit. I've raised the question in the past if someone else wants to help with editing
… Even if we don't have another named editor, I'd intend to continue with TTML2, and publish new CRs and go to Rec, at least for TTML2 2nd edition
… I accept it's been a long time since we published CR
… There has been positive discussion about this from other participants in the past
… I feel like we're waiting to have a tight scope defined for the changes. Implementation will be important for getting out of CR
… We wouldn't make a breaking change in TTML2 2nd edition

Gary: On WebVTT, we do want to proceed. Apple championed trying to get VTT into Interop 2025
… It's not in the main Interop this year though. Could be a candidate for full Interop next year
… Should ask Apple to participate in the group more actively
… I'd want to work on it more if there are also others more actively working on it
… It's slow right now as it's just one person doing it in their free time

Nigel: I can sympathise with that

Gary: With the Interop 2025 review focus, I think the ball has started rolling again, so hope we can make progress

Nigel: Is it enough to show the Team that there's this interest, if not the active participation? What can the Team do to encourage participation?

Atsushi: The comments are statements of concern, so we just need to talk

Gary: Seems less of an issue for TTML, but it's more complicated with WebVTT, where seeking additional contributors would be greatly appreciated

Atsushi: This step is about reducing risk of formal of objections at AC review. Referring to WG discussions should be used in the review

Nigel: If the Team wants to have a separate call, I can be available

Gary: Me too, yes

Nigel: Anything else to raise?

(nothing)

Meeting close

Nigel: Thanks everyone, let's adjourn. [adjourns meeting]

Minutes manually created (not a transcript), formatted by scribe.perl version 244 (Thu Feb 27 01:23:09 2025 UTC).