{Minutes} TTWG Teleconference 2025-07-31

Thanks all for attending today’s TTWG meeting. Minutes can be found in HTML format at https://www.w3.org/2025/07/31-tt-minutes.html


We confirmed one resolution following the call for consensus issued 2 weeks ago:

RESOLUTION<https://www.w3.org/2025/07/31-tt-minutes.html#c451>: Publish a CR Snapshot of DAPT based on the current CR Draft

The review period for this resolution has concluded.

Those minutes in plain text:

   [1]W3C

      [1] https://www.w3.org/


                Timed Text Working Group Teleconference

31 July 2025

   [2]Previous meeting. [3]Agenda. [4]IRC log.

      [2] https://www.w3.org/2025/07/17-tt-minutes.html

      [3] https://github.com/w3c/ttwg/issues/312

      [4] https://www.w3.org/2025/07/31-tt-irc


Attendees

   Present
          Andreas, Atsushi, Matt, Nigel, Pierre

   Regrets
          Cyril, Gary

   Chair
          Nigel

   Scribe
          nigel

Contents

    1. [5]This Meeting
    2. [6]DAPT
         1. [7]Publish a CR Snapshot
    3. [8]IMSC 1.3
         1. [9]Wide Review
    4. [10]TPAC 2025 planning
    5. [11]Meeting close
    6. [12]Summary of resolutions

Meeting minutes

  This Meeting

   Nigel: Today we have DAPT and IMSC 1.3, and TPAC 2025 planning
   … Anything else for the agenda? Any points to make sure we
   cover within those topics?

  DAPT

    Publish a CR Snapshot

   PROPOSAL: Publish a CR Snapshot of DAPT based on the current CR
   Draft

   Nigel: I issued the call for consensus for this in the last
   call, and have had no objections.
   … Last chance for questions/comments/objections?

   no objections

   RESOLUTION: Publish a CR Snapshot of DAPT based on the current
   CR Draft

   Nigel: That resolution won't have a further review period.
   … (because it's had the 2 weeks already)
   … Atsushi, do you need anything further to make that happen?

   Atsushi: I haven't checked but I think we need to update the
   change log and there have
   … been a number of substantive changes, so we need a delta
   review from the last CRS.

   Nigel: I think we've been updating the change summary as we
   have been going along.

   Atsushi: I haven't had time to go through the pull requests
   since the last CRS.

   Nigel: Will you initiate that delta review with the pull
   requests merged, or do you need
   … anything from us?

   Atsushi: I need the change summary

   [13]Substantive Changes Summary

     [13] https://www.w3.org/TR/dapt/substantive-changes-summary.txt


   Atsushi: The delta review should check the changes since the
   previous CRS

   Nigel: We've only tracked since FPWD so I will go and add a
   subheading for CRS in that change summary
   … Unless you want to do that?

   Atsushi: I may not be able to get to this until 14th.

   Nigel: How will you do the delta review?

   Atsushi: Same as requesting HR, but noting that it's a delta
   and not the first CRS.

   Nigel: OK

   Atushi: We have a link that has a template for doing this which
   we can use, pasting a link to the change log.
   … Normally we use the same self-review checklist that we
   already did.

   Nigel: Makes sense, I don't think anything has changed.

   Atsushi: Completing the request should be straightforward once
   we have the change log.

  IMSC 1.3

   [14]FPWD was published on 2025-07-22

     [14] https://www.w3.org/TR/ttml-imsc1.3/


    Wide Review

   Nigel: Wide Review looks like it's going okay
   … We sent outgoing liaison messages, and opened the HR issues.
   … And we've had some response back.
   … I believe TAG and Security have closed with no comments.

   Atsushi: i18n have closed on this in the last hour

   Nigel: Great, that leaves privacy and accessibility remaining.
   … Pierre, anything to add?

   Pierre: No, thank you for following up with the security
   review.
   … I think there's no action to take on IMSC?

   Nigel: I think so, yes, from those reviews anyway.

   Pierre: We have a bunch of smaller issues to deal with before
   CR so I will start processing those.

   Nigel: Like what?

   Pierre: There's a leftover editor's note.
   … Ordering subsections.
   … Editorial stuff, it's minor, but I'll work through it.

   Nigel: Thank you.
   … I also have an action about the examples.

   Pierre: Yes, that's [15]w3c/imsc#553.

     [15] https://github.com/w3c/imsc/issues/553


   Nigel: Not sure when I will get round to it.

   Pierre: No urgency, ideally before publication!

   Nigel: [laughs]

  TPAC 2025 planning

   Nigel: The schedule is now available.

   [16]TPAC 2025 Schedule

     [16] https://www.w3.org/2025/11/TPAC/schedule.html


   Nigel: The Accessibility Guidelines WG moved their slots from
   Thursday and Friday back to Monday and Tuesday.
   … Really unfortunate from my point of view.

   Pierre: That's really unfortunate, is there a way to influence
   it?

   Nigel: I don't know, I will ask the Chair.
   … Any agenda+ items for TPAC at this stage?
   … On my list is DAPT implementation and IMSC 1.3 progression
   … I guess there might be some WebVTT stuff too.

   Andreas: No items at the moment but I'm thinking of topics to
   raise.

   Nigel: It doesn't fit in our remit but I expect there to be
   some discussion about timed text in
   … media source extensions too.
   … And possibly more on TextTrackCue refactoring

  Meeting close

   Nigel: Next call is scheduled for 14th August, but neither Gary
   nor I can make it.
   … Anyone want to go ahead in our absence, or shall we conform
   we are cancelling it?

   Andreas: Makes sense to skip the call

   Pierre: Nothing urgent on IMSC, hopefully we will start getting
   feedback from our Wide Review
   … (Horizontal Review)

   Nigel: OK, I will cancel that and our next call will be on 28th
   August.
   … Thanks for attending everyone. [adjourns meeting]

Summary of resolutions

    1. [17]Publish a CR Snapshot of DAPT based on the current CR
       Draft


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

     [18] https://w3c.github.io/scribe2/scribedoc.html