15:00:39 RRSAgent has joined #tt 15:00:44 logging to https://www.w3.org/2026/07/16-tt-irc 15:00:44 RRSAgent, make logs Public 15:00:45 Meeting: Timed Text Working Group Teleconference 15:00:57 scribe: nigel 15:01:03 Agenda: https://github.com/w3c/ttwg/issues/343 15:01:06 Previous meeting: https://www.w3.org/2026/07/02-tt-minutes.html 15:01:09 Present: Nigel 15:01:24 rrsagent, make minutes 15:01:25 I have made the request to generate https://www.w3.org/2026/07/16-tt-minutes.html nigel 15:02:56 nigel has changed the topic to: TTWG Teleconference 2026-07-16. Joining details: https://www.w3.org/events/meetings/74c31b0a-54dc-4869-bc18-4d398335c084/20260716T150000/ Agenda: https://github.com/w3c/ttwg/issues/343 15:03:15 Chair: Nigel 15:06:17 Present+ Atsushi 15:10:21 Present+ Chris_Needham 15:10:40 cpn has joined #tt 15:10:48 present+ Chris Needham 15:12:43 Present- Chris_Needham 15:12:49 Topic: This meeting 15:13:45 Nigel: There are only 3 of us present, and the agenda is very light. 15:14:04 .. Given who is here we could actually discuss TPAC planning and the 15:14:22 .. MEIG proposal for gathering additional requirements for timed text, that I 15:14:23 scribe+ cpn 15:14:31 .. distributed on member-tt just over an hour ago. 15:14:35 .. (it's only short) 15:14:51 Chris: I'm happy to talk about those. 15:15:01 Nigel: Anything else for the agenda? 15:15:04 nothing more 15:15:25 Topic: MEIG proposal for a task force to gather future timed text requirements 15:15:57 Nigel: I sent the proposal to member-tt 15:16:08 -> https://lists.w3.org/Archives/Member/member-tt/2026Jul/0000.html Proposal (member-only visible) 15:16:36 Nigel: I wrote a short document to describe what we want to do, including scope and time limits 15:16:54 .... [Reads through the proposal] 15:19:11 Chris: A few things. You talk about the use of AI or machine analysis to capture more data, 15:19:24 .. and then being able to represent that in timed text formats. 15:19:34 .. Do we also need to consider how that is used or rendered? 15:19:50 .. How does an end user consuming those files experience the extra data, in the way 15:20:00 .. that e.g. TTML defines a rendering model? 15:20:40 Nigel: Yes, the two key parts are capturing richer data, in a cost effective way, then having presentation semantics 15:21:33 ... It may be that the existing presentation semantics are good enough, and you just need to define, for example, when "anger" or "happy" is conveyed, to change the presentation in a particular way 15:21:59 ... I want to make sure we caveat that assigning motive to a speaker is challenging, and error-prone. So no expectation of 100% accuracy 15:22:25 ... There are companies doing something here. One I've talked to is amenable to standardisation of capturing and expressing the data 15:22:55 ... The mapping from that expression into presentation might not need to be standardised and could be part of the content provider's presentation 15:23:04 .. Or let the client handle it in different 15:23:20 .. The proposal should definitely cover this. 15:23:30 s/erent/erently 15:23:48 Chris: MEIG is a member interest group. W3C has two kinds of IG, those that are members 15:23:54 .. and those that allow non-member participants. 15:24:32 .. MEIG is in the former category. As the Chair I tend to invite guests. 15:25:05 .. I want to enable this task force to happen. 15:25:20 .. Provided the Team are comfortable with it we might operate it on a flexible 15:25:27 .. participation basis. 15:27:17 Nigel: I see this as almost a Wide Review exercise, in which the task force can seek 15:27:28 .. input from members and non-members, either in written form or verbally. 15:27:54 .. That doesn't make the task force suddenly open the MEIG to non-members. 15:28:08 .. Even WGs can seek wide review, and are expected to. 15:28:29 Nigel: So actions for the proposal: 15:28:39 .. * clarify that presentation semantics could be in scope 15:28:48 .. * clarify that we want to seek input broadly 15:29:05 Chris: Ok, that handles the structure that we can use. 15:29:16 .. Follow-on question: how to build that group of participants. 15:29:32 .. Do you think we'll be able to get a good set of participants to drive the work? 15:29:40 .. Can MEIG help with that part? 15:29:58 .. Are there liaison groups that we would want to raise this to? What kind of outreach is needed? 15:30:29 Nigel: Yes, I'd hope that some TTWG and MEIG members would be interested to participate, and I'd look to them initially 15:31:02 ... I'm fairly sure we could get input from others. The Motion Picture Academy ran an expressive captioning summit earlier in the year, and there's another coming up 15:31:30 ... I can say we're running a TF to gather requirements, I wouldn't be surprised if there's interest 15:31:41 ... I know two organisations in particular who are creating products 15:32:12 Chris: Kick off at TPAC? 15:33:01 Nigel: I can do another iteration of the document, share with MEIG, possibly start sooner. If we do that, we could have a session at TPAC 15:33:10 ... A breakout there could be good 15:34:30 Nigel: One of the concerns that one TTWG member raised is that starting a TF to gather requirements sounds like a bureaucratic exercise, not attractive 15:34:48 ... So I want to emphasis that it's a lightweight, speedy thing 15:35:46 ... The output should be a document, but I don't want to spend lots of time wrangling words 15:36:04 Chris: Do a gap analysis of what existing formats like EmotionML support? 15:36:20 Nigel: Yes, do as much as possible offline 15:37:08 ... That might support a lot of what's needed. From a presentation perspective, there's varying how the text appears. Uses existing CSS support, but the animation might be trickier 15:37:48 ... TTML supports continuous animation (that's not in IMSC). Doing it upfront may lead it to something very verbose 15:38:16 ... Today's solutions include sending things like animated GIF 15:38:43 ... There's good audience benefits. There are accessibility concerns, I should capture those in the document 15:40:07 Nigel: What's the next step? I can refine the proposal, then what? 15:40:42 Chris: Add to the MEIG GitHub? That's reflected to the public mailing list 15:44:53 -> https://github.com/w3c/media-and-entertainment/issues/122 MEIG issue 15:45:32 Chris: I can add it to the agenda for the August 4 MEIG meeting 15:45:44 Topic: TPAC schedule 15:45:55 Nigel: I think this is OK, any comments? 15:46:11 Chris: I think it's fine, we just need to prepare the agendas 15:46:49 Nigel: I need to create a TTWG issue, and add a page to the wiki 15:47:04 Chris: I've already done that for MEIG and Media WG. There's nothing in it yet, 15:47:09 .. just a skeleton of the times and things to fill in. 15:47:19 .. I can cross-link from that to a TTWG issue or wiki page. 15:47:23 Nigel: Great. 15:47:30 Chris: https://github.com/w3c/media-and-entertainment/issues/121 15:47:57 Meeting Close 15:48:12 Nigel: Thanks everyone, we've covered our agenda, let's adjourn. 15:48:39 .. Next meeting on 2026-07-30 https://github.com/w3c/ttwg/issues/344 15:48:46 .. [adjourns meeting] 15:48:51 rrsagent, make minutes 15:48:52 I have made the request to generate https://www.w3.org/2026/07/16-tt-minutes.html nigel 15:49:30 Regrets: Gary 15:59:30 scribeOptions: -final -noEmbedDiagnostics 15:59:35 zakim, end meeting 15:59:35 As of this point the attendees have been Nigel, Atsushi, Chris_Needham, Needham 15:59:37 RRSAgent, please draft minutes v2 15:59:38 I have made the request to generate https://www.w3.org/2026/07/16-tt-minutes.html Zakim 15:59:44 I am happy to have been of service, nigel; please remember to excuse RRSAgent. Goodbye 15:59:45 Zakim has left #tt 16:01:32 Present: Atsushi, Chris Needham, Nigel 16:01:35 rrsagent, make minutes 16:01:37 I have made the request to generate https://www.w3.org/2026/07/16-tt-minutes.html nigel 16:03:43 rrsagent, excuse us 16:03:43 I see no action items