{Minutes} TTWG Teleconference 2026-01-15

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


In plain text:

   [1]W3C

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


                Timed Text Working Group Teleconference

15 January 2026

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

      [2] https://www.w3.org/2025/12/18-tt-minutes.html

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

      [4] https://www.w3.org/2026/01/15-tt-irc


Attendees

   Present
          Atsushi, Chris_Needham, Cyril, Nigel

   Regrets
          Andreas, Gary

   Chair
          Nigel

   Scribe
          nigel, cpn

Contents

    1. [5]Agenda review
    2. [6]DAPT
         1. [7]CRS publication
         2. [8]DAPT/IMSC compatibility
    3. [9]IMSC 1.3
    4. [10]AOB
    5. [11]Meeting close

Meeting minutes

  Agenda review

   Nigel: One PR on DAPT on DAPT/IMSC compatibility
   … For IMSC 1.3, there are open PRs, nothing flagged for the
   agenda
   … Any other topics?
   … I have an AOB regarding Pierre

   (nothing)

  DAPT

    CRS publication

   Nigel: This was published on 18 December
   … Aside from Informative changes that require a new CRS, this
   might be the last one
   … For the implementation report, we haven't worked out what to
   do about the current implementation
   … I haven't open sourced the BBC implementation yet
   … When can we organise that?

   Cyril: Week after next should be fine
   … Week of Jan 26th

   Nigel: Let's aim for that, and that'll push me to do the open
   sourcing

   Nigel: We need to work out how to describe this in the
   implementation report
   … Generating content isn't the same thing as passing tests

   Cyril: We need two passing implementations, they don't both
   need to be validation tools
   … If the authoring tool creates content that represents the
   same features [...]
   … We may have an issue with invalid features, as the authoring
   tool won't generate invalid content

   Nigel: We need two implementations of each feature
   … The test is a validation test. If we show the implementation
   generates content that is good according to a validator that
   passes valid and invalid tests, we're good
   … If content fails validation, I'd say it's not a valid
   implementation of the feature

   Cyril: So have a table showing, for each feature, how many
   implementations are passing, then in the cell how many
   implementations are validating and how many are creating

   Nigel: Something like that, yes. We currently have a "tests
   passed" column, we could have a feature implementation column

   Nigel: [checks the CR exit criteria]

   Nigel: What we document in the table is the number of
   independent implementations of the feature
   … We can say what type of implementation that is, to make it
   clear
   … So we'll need to refactor that table in the implementation
   report

   Cyril: The one feature our tool doesn't implement is the audio
   tag

   Nigel: There is one feature for that,
   #xmlLang-audio-nonMatching
   … For that we need to create content and check the language is
   not different from the parent
   … We also have to deal with all the at-risk features

    DAPT/IMSC compatibility

   Nigel: We have one PR open, #333. Pierre made some comments,
   that I still need to finish responding to
   … Add DAPT signalling to the IMSC signalling section. I need to
   move the IMSC signalling section in the DAPT spec somewhere
   else
   … I need to do an editorial pass to fix this. We have
   references to 3 different versions of IMSC, which isn't
   intentional
   … All informative changes. It'll need review

  IMSC 1.3

   Nigel: CRS publication also happened on 18 December
   … There are a few PRs open, but none marked for the agenda
   today
   … Some PRs have been merged since our last call. That triggered
   a new CR Draft
   … The most recent publication is 20th December
   … I don't think there's any reason we need another CR Snapshot
   as we're not expecting to make more substantive changes
   … Anything to discuss on IMSC 1.3?

   (nothing)

  AOB

   Nigel: As mentioned at the end of our last call, MovieLabs is
   no longer a W3C member, and we're working to see if we can find
   a way to accept Pierre's offer to continue shepherding IMSC 1.3
   to Recommendation

   Nigel: Anything else?

   (nothing)

  Meeting close

   Nigel: Next call in 2 weeks time

   [adjourned]


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

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