14:59:52 <RRSAgent> RRSAgent has joined #tt
14:59:57 <RRSAgent> logging to https://www.w3.org/2025/07/17-tt-irc
14:59:57 <Zakim> inviting RRSAgent
14:59:57 <Zakim> RRSAgent, make logs Public
14:59:58 <Zakim> Meeting: Timed Text Working Group Teleconference
15:00:03 <nigel> scribe: nigel
15:00:08 <nigel> Present: Atsushi, Nigel
15:00:43 <nigel> Agenda: https://github.com/w3c/ttwg/issues/311
15:00:53 <nigel> Previous meeting: https://www.w3.org/2025/07/03-tt-minutes.html
15:01:19 <nigel> Present+ Gary, Andreas
15:01:21 <nigel> Chair: Gary, Nigel
15:01:23 <nigel> Topic: This meeting
15:01:29 <nigel> rrsagent, make minutes
15:01:30 <RRSAgent> I have made the request to generate https://www.w3.org/2025/07/17-tt-minutes.html nigel
15:02:08 <nigel> Regrets: Chris_Needham
15:02:52 <nigel> Present+ Pierre
15:03:10 <nigel> Present+ Cyril
15:03:42 <nigel> Nigel: Today we have:
15:04:40 <nigel> .. DAPT, IMSC 1.3, TPAC 2025 and Interop 2025 WebVTT goals
15:05:30 <nigel> .. And Atsushi added some specifics to discuss with IMSC 1.3
15:05:35 <nigel> .. Anything else for the agenda?
15:06:02 <nigel> nothing
15:06:03 <atai> atai has joined #tt
15:06:19 <nigel> Topic: DAPT
15:06:29 <nigel> Nigel: Good status update today.
15:06:35 <nigel> .. All the open Pull Requests have been closed
15:06:50 <nigel> .. Similarly the tests now all match the spec
15:07:02 <nigel> .. And the Implementation Report has links to all the tests as well, and
15:07:12 <nigel> .. has been updated to match the latest version of the spec,
15:07:25 <nigel> .. which has fewer extension features as a result of those recent pull requests.
15:08:04 <nigel> .. My proposal is that we publish a new CR Snapshot.
15:08:10 <Cyril> Cyril has joined #tt
15:08:21 <Cyril> RRSAgent, pointer
15:08:21 <RRSAgent> See https://www.w3.org/2025/07/17-tt-irc#T15-08-21
15:09:05 <nigel> Subtopic: Publish a CR Snapshot
15:09:21 <nigel> PROPOSAL: Publish a CR Snapshot of DAPT based on the current CR Draft
15:09:39 <Cyril> +1
15:09:40 <atai> +1
15:09:41 <nigel> Nigel: Anyone in favour or against?
15:09:44 <gkatsev> +1
15:09:46 <nigel> +1
15:10:34 <nigel> Nigel: That's 4 in favour, 0 against. Decision review period will be 2 weeks,
15:10:38 <atsushi> +1
15:10:41 <nigel> .. we can confirm it than.
15:10:47 <nigel> .. 5 in favour!
15:11:31 <nigel> .. Any more on DAPT?
15:11:34 <nigel> Cyril: Nothing to add
15:11:47 <nigel> Topic: IMSC 1.3
15:12:44 <nigel> Nigel: There are several subtopics today.
15:13:08 <nigel> Subtopic: PR Preview
15:13:23 <nigel> Nigel: I don't think we have had any PRs opened since we hopefully fixed it, so can't
15:13:29 <nigel> .. show if the fix worked yet.
15:13:41 <nigel> .. I might open one just for testing.
15:14:20 <nigel> Atsushi: I opened a PR but from my fork so maybe not a useful test
15:14:37 <nigel> Subtopic: Namespace documents
15:15:04 <atsushi> https://github.com/w3c/ns/pull/5
15:15:07 <nigel> -> copied namespace documents from imsc#589 ns#5 https://github.com/w3c/ns/pull/5
15:15:58 <nigel> Nigel: I approved this, which was opened 3 weeks ago.
15:16:03 <nigel> .. What do we need to do to make it happen?
15:16:16 <nigel> Atsushi: There's still no formal way to handle this repo as far as I understand
15:16:31 <nigel> .. so I will talk with Philippe maybe later this month or early next month.
15:16:57 <nigel> Pierre: I think we might need to retouch them for IMSC 1.3 so I wouldn't agonise too much about it now.
15:17:08 <nigel> .. When we get closer to Rec for IMSC 1.3 we will really need to insist,
15:17:19 <nigel> .. but no need to waste too much energy on it now.
15:17:31 <nigel> Atushi: To explain the current position, this repo is not automatically deployed to the
15:17:58 <nigel> .. w3.org/ns/ site so even if this is approved here I need to manually push the files to CVS and
15:18:08 <nigel> .. the website to complete it. There's no formal procedure.
15:18:36 <nigel> .. Few specifications have touch the namespaces recently.
15:19:03 <nigel> Subtopic: FPWD Publication
15:19:10 <nigel> Nigel: What's the status of this?
15:19:52 <atsushi> https://www.w3.org/TR/2025/WD-ttml-imsc1.3-20250722/
15:19:55 <nigel> Atsushi: I've installed the material to w3.org/tr to be published next Tuesday
15:20:11 <nigel> .. I believe there should be no issue so it should be published on 22nd July.
15:20:25 <nigel> Nigel: Thank you.
15:20:46 <nigel> .. Pierre and I had an action associated with this to prepare and send a notice out to interested
15:20:54 <nigel> .. parties, which has been drafted.
15:21:57 <nigel> Pierre: We should send that as soon as possible.
15:22:06 <nigel> .. We've already warned people for the Wide Review.
15:22:21 <nigel> .. We should also begin the Horizontal Review process as soon as possible.
15:22:33 <nigel> .. Who will write the explainer, I can do it if someone can give me a template?
15:22:48 <nigel> Atsushi: We can probably copy from IMSC 1.2 when we went through the same process.
15:23:05 <nigel> .. Most of the changes are unrelated to horizontal review areas, except for characters, which should be fine.
15:23:06 <pal> pal has joined #tt
15:23:31 <nigel> .. We will modify it from last time just to explain the changes, so it isn't so difficult.
15:24:22 <atsushi> https://w3c.github.io/spec-releases/milestones/?fpwd=2025-07-22
15:24:25 <nigel> .. There is still a 90 day period and then a 60 day period before Rec so there should be some
15:24:29 <nigel> .. room to get this done.
15:25:15 <nigel> Nigel: Still, we have to initiate the process, as Pierre said.
15:26:12 <nigel> .. I'm happy to find the links to how we do that, and share it off line
15:26:20 <nigel> -> https://www.w3.org/guide/documentreview/#how-to-get-horizontal-review How to get horizontal review
15:27:22 <nigel> -> https://w3ctag.github.io/explainer-explainer/ TAG How to write an Explainer
15:28:03 <nigel> Pierre: Do you want to do the wide review and I can start taking on the horizontal review?
15:28:08 <nigel> Nigel: Yes, can do.
15:28:19 <nigel> Pierre: The horizontal review should be straightforward because the delta is small.
15:29:30 <nigel> Nigel: I think we should mention for the accessibility review the issues that no longer apply
15:29:41 <nigel> .. from the previous review, because of the removal of Image Profile.
15:30:01 <nigel> Pierre: I can see our IMSC-HRM horizontal review request but I don't see them for IMSC 1.2
15:30:13 <nigel> Nigel: Maybe that predated the current system of issues and tracking labels.
15:30:45 <nigel> .. It was quite a while ago.
15:30:53 <nigel> Pierre: It was 2020.
15:31:02 <nigel> -> https://www.w3.org/standards/history/ttml-imsc1.2/ IMSC 1.2 History
15:31:26 <nigel> Atsushi: It was a Rec in 2020, but in that era the system for HR was under development
15:31:41 <nigel> Pierre: I found it. It was an email from Nigel on October 16 2019
15:31:47 <pal> "Request a11y review of IMSC 1.2
15:31:47 <pal> "
15:31:57 <nigel> s/"//
15:32:01 <nigel> s/2/2"
15:32:09 <atsushi> https://lists.w3.org/Archives/Public/public-tt/2019Oct/0037.html
15:32:13 <pal> https://lists.w3.org/Archives/Public/public-tt/2019Oct/0041.html
15:32:44 <atsushi> https://lists.w3.org/Archives/Public/public-tt/2019Oct/0040.html
15:33:08 <nigel> Pierre: I think what I will do is create a template text that explains how IMSC 1.3
15:33:20 <nigel> .. is a minimal change to 1.2, send it to the reflector, which should have no surprises,
15:33:31 <nigel> .. and then I'll submit the FPWD for HR.
15:33:42 <nigel> .. Unless someone else wants to do it - happy for someone else to do it.
15:34:06 <nigel> Atsushi: After that the self-review questionnaire has been developed and we need to
15:34:17 <nigel> .. attach our self-review result to the request.
15:34:26 <nigel> Pierre: Sure
15:34:42 <atsushi> https://www.w3.org/guide/documentreview/#how-to-get-horizontal-review
15:35:03 <nigel> Atsushi: There is a not so short list of items in the questionnaire!
15:35:23 <nigel> Pierre: By the way the questionnaire link is broken
15:36:55 <nigel> -> https://github.com/w3c/imsc/issues/608 I just opened this meta issue
15:37:45 <nigel> Nigel: This has a broken link to the accessibility questionnaire too
15:38:05 <nigel> .. Atsushi, will you follow up on the broken accessibility questionnaire link?
15:43:03 <nigel> Pierre: I think I found it at https://w3c.github.io/fast/checklist.html
15:43:30 <nigel> Atushi: I want to believe that is correct
15:43:39 <nigel> Nigel: I think I've seen that before as well
15:43:50 <pal> q+
15:43:59 <nigel> Gary: The broken URL does have "FAST" in it, it just has /apa/fast so maybe they moved the repo
15:44:03 <nigel> .. and forgot to update the links.
15:44:05 <nigel> ack pal
15:44:25 <nigel> Pierre: What is the policy when you do a minor update to a Rec, do you have to do the whole questionnaire again?
15:44:40 <nigel> atsushi: Usually we use the previous result, but this time we don't have a previous one
15:44:49 <nigel> .. so I don't have an exact answer for that.
15:44:52 <nigel> Pierre: Okay. I'll just proceed.
15:45:52 <nigel> -> https://docs.google.com/document/d/1fP8dX29JZHLkE3M-qExoxj4vK86x-ninXFC9JNt-WWc/edit?tab=t.0 Wide Review request draft text
15:46:05 <nigel> Pierre: I'll proceed quickly with the HR
15:46:10 <nigel> Nigel: And I will also send the WR comms
15:46:45 <nigel> Gary: For the checklist, it might be that since it is an update, we could just ask APA if
15:46:57 <nigel> .. we can proceed since it's an update release, without completing the full checklist.
15:47:02 <nigel> Pierre: How would you go about that?
15:47:18 <nigel> Gary: Probably opening an issue - in the Meta Issue there's a link to the a11y request repo
15:47:33 <nigel> Pierre: I'm recalling that we have a WCAG consideration section that we can reference in the spec.
15:47:46 <nigel> .. We're not designing a UI, so I remember we had a long discussion and a lot of the requirements
15:47:51 <nigel> .. simply don't apply. I will start there.
15:48:17 <nigel> Gary: In the check list a lot of these are "If the technology provides audio..." which we can skip.
15:48:28 <nigel> Pierre: Is the check meant to indicate that you've read it or that it applies?
15:48:47 <nigel> Gary: I think you check the item if it applies.
15:48:56 <nigel> .. Based on my minimal review.
15:49:23 <nigel> Pierre: I will try to do this.
15:49:30 <nigel> Nigel: Ping me if you have any questions
15:49:37 <nigel> Pierre: Thanks, this is super helpful, glad we went through that.
15:50:15 <nigel> Subtopic: IMSC 1.3 streamlined publication
15:50:33 <nigel> Atsushi: Do we want to set up streamlined publication?
15:50:44 <nigel> Nigel: Yes, that's our default unless anyone objects?
15:50:48 <nigel> Atsushi: Any objections?
15:50:57 <nigel> Nigel: You can go ahead and do it
15:51:03 <nigel> Atsushi: Will do.
15:51:56 <nigel> Nigel: The other bullets you added to the comment on this meeting's issue - do we need
15:52:07 <nigel> .. to discuss anything, or can you explain it offline?
15:52:21 <nigel> Atsushi: Streamlined publication has two items - one to publish to /TR and the other to the
15:52:29 <nigel> .. gh-pages branch.
15:52:43 <nigel> .. For IMSC repo we have multiple specs so I don't think we can feed gh-pages from another branch
15:53:00 <nigel> .. so I would keep the main branch as the Editor's Draft and configure the streamlined publication
15:55:20 <nigel> .. to publish the ED to github.io and the latest WD to /TR. They should be the same content
15:55:24 <nigel> .. but with different document status.
15:55:29 <nigel> Nigel: OK, that makes sense.
15:55:39 <nigel> Atsushi: To be honest we don't really need the ED.
15:56:16 <nigel> .. If everything is fine I will raise a PR to configure everything.
15:56:18 <nigel> Pierre: Yes please
15:56:22 <nigel> Nigel: Yes
15:56:27 <nigel> .. Thank you for that.
15:57:20 <nigel> Topic: Interop 2025 WebVTT goals
15:57:33 <nigel> Gary: We'll need to skip this since Dana hasn't joined
15:57:53 <nigel> Topic: TPAC 2025 planning
15:57:59 <nigel> Nigel: Registration is open
15:58:07 <nigel> Gary: Opened today I think
15:58:23 <nigel> -> https://www.w3.org/2025/11/TPAC/schedule.html Published schedule
15:58:42 <nigel> Nigel: The published schedule has a link to registration at the top, too
15:59:27 <nigel> .. Early bird rate of USD370 until 23rd August
16:00:15 <nigel> Topic: Meeting close
16:00:32 <nigel> Nigel: We meet in 2 weeks, on 31st July
16:00:37 <nigel> .. I can't make the 14th August
16:00:47 <nigel> Gary: I am unlikely to be around either, and I can't make the 31st.
16:01:05 <nigel> Nigel: So we're likely to cancel the 14th August call, to be confirmed next time.
16:01:24 <Adam_Page> Adam_Page has joined #tt
16:02:51 <nigel> .. Thank you everyone, see you in a couple of weeks. [adjourns meeting]
16:02:55 <nigel> rrsagent, make minutes
16:02:56 <RRSAgent> I have made the request to generate https://www.w3.org/2025/07/17-tt-minutes.html nigel
16:18:20 <nigel> s|meta issue|meta issue w3c/imsc#608
16:20:14 <nigel> rrsagent, make minutes
16:20:16 <RRSAgent> I have made the request to generate https://www.w3.org/2025/07/17-tt-minutes.html nigel
16:20:41 <nigel> s/Atushi/Atsushi/g
16:20:50 <nigel> s/atsushi/Atsushi/g
16:20:52 <nigel> rrsagent, make minutes
16:20:53 <RRSAgent> I have made the request to generate https://www.w3.org/2025/07/17-tt-minutes.html nigel
16:21:33 <nigel> scribeOptions: -final -noEmbedDiagnostics
16:21:37 <nigel> zakim, end meeting
16:21:37 <Zakim> As of this point the attendees have been Atsushi, Nigel, Gary, Andreas, Pierre, Cyril
16:21:39 <Zakim> RRSAgent, please draft minutes v2
16:21:40 <RRSAgent> I have made the request to generate https://www.w3.org/2025/07/17-tt-minutes.html Zakim
16:21:46 <Zakim> I am happy to have been of service, nigel; please remember to excuse RRSAgent.  Goodbye
16:21:47 <Zakim> Zakim has left #tt
16:21:53 <nigel> rrsagent, excuse us
16:21:53 <RRSAgent> I see no action items