13:00:48 RRSAgent has joined #pmwg 13:00:52 logging to https://www.w3.org/2025/02/13-pmwg-irc 13:00:52 RRSAgent, make logs Public 13:00:53 Meeting: Publishing Maintenance Working Group 13:01:01 ivan has changed the topic to: Meeting Details 2025-02-13: https://lists.w3.org/Archives/Public/public-pm-wg/2025Feb/0006.html 13:01:02 Chair: shinya 13:01:02 Meeting: Publishing Maintenance Working Group Telco 13:01:02 Agenda: https://lists.w3.org/Archives/Public/public-pm-wg/2025Feb/0006.html 13:24:48 regrets+ wendy 13:25:10 regrets+ george 13:48:06 shiestyle has joined #pmwg 13:56:24 present+ 13:56:49 m2gbot, help 13:56:49 ivan, I am an IRC bot to link github issues and PRs to the minutes of the meetings where they were discussed. 13:56:49 ... I am an instance of minutes_to_gh version 0.8.1. 13:56:50 ... To know more, see https://github.com/pchampin/minutes_to_gh 13:57:32 dhall5 has joined #pmwg 13:58:17 present+ 13:59:00 present+ dhall5 13:59:08 present+ dale 13:59:20 present+ 13:59:20 present+ shinya 13:59:28 present+ rickj 13:59:35 MasakazuKitahara has joined #pmwg 13:59:47 present+ 13:59:49 present+ mattg 13:59:57 mgarrish has joined #pmwg 14:00:07 rickj has joined #pmwg 14:00:17 CharlesL has joined #pmwg 14:00:31 present+ 14:01:20 present+ charles 14:01:21 toshiakikoike has joined #pmwg 14:01:28 present+ brady 14:01:32 present+ 14:01:35 present+ avneesh 14:01:46 duga has joined #pmwg 14:02:10 AvneeshSingh has joined #pmwg 14:02:11 present+ 14:02:23 Dale has joined #pmwg 14:03:04 present+ 14:03:04 zakim, pick a victim 14:03:04 Not knowing who is chairing or who scribed recently, I propose duga 14:03:08 present+ hadrien 14:03:21 scribe+ 14:03:36 Topic: Overview of the plan for the next few weeks 14:03:45 q+ 14:03:45 ikkwong has joined #pmwg 14:03:48 Hadrien has joined #pmwg 14:03:54 present+ 14:04:05 present+ ikkwong 14:04:07 present+ 14:04:13 shiestyle: The ew charter is in 14:04:32 ivan: And we as the leads did some planning the other day 14:04:54 ... we know the big things in the charter we need to do (annotations and webtoons) 14:05:02 ... we will discuss those are the f2f 14:05:26 ack ivan 14:05:27 ... so for the calls until then we will discuss the smaller items in the charter 14:06:27 ... For instance, we had some long discussions about WebAssembly and whether we could add it to the spec before, we put some of that off 14:06:50 ... so those discussions will keep us busy for now 14:07:06 ... We also did some work on the spec structure to prepare 14:08:06 ... There will be a new release of 3.3 in March [scribe note: I missed what the changes are, sounds editorial] 14:08:26 ... Then we will set up a new 3.4 area of the repo, that will be for new work 14:08:49 ... Also chairs call has changed to Wednesday to match the new group meeting 14:09:00 present+ 14:09:20 present+ 14:09:21 shiestyle: One more thing - the membership was renewed 14:09:30 ... So everyone needs to rejoin 14:09:47 q? 14:10:32 https://www.w3.org/groups/wg/pm/join 14:10:35 present+ 14:11:20 present+ susan 14:11:27 Does it mean I need to remove everyone in DAISY and join everyone again? 14:11:54 q+ 14:12:10 q+ 14:12:17 ack duga 14:12:36 SueNeu has joined #pmwg 14:12:43 present+ 14:12:50 q+ 14:13:01 AvneeshSingh: We already seems to be members 14:13:17 ivan: Yes, DAISY is, but all the individual people need to rejoin 14:13:32 duga: I didn't have a join button 14:13:47 ivan: Expected, the process is different for IE 14:13:54 q? 14:13:59 ... Everything this is working as expected 14:14:00 ack ivan 14:14:00 ack ivan 14:14:11 ack dhall 14:14:20 q? 14:14:25 dhall5: My AC rep is pinged, I am also dragging in a coworker 14:14:36 Topic: WebAssembly discussion 14:15:15 mgarrish: The question was do we allow webassembly? 14:15:41 ... it isn't explicitly referenced from the script tag 14:16:13 q+ 14:16:16 ... we had a discussion around it, I think all we need to do is add a comment that it is ok 14:16:38 ... We could add it to the script tag, or just exempt that tag entirely 14:16:59 ... Main question is do we want add something to reading systems? 14:17:25 ... It will work if they support the API, so not sure what we would need to add 14:17:29 q+ 14:17:35 ack ivan 14:18:08 ivan: I think there are no problems, but there was a question around security 14:18:15 q+ 14:18:45 ... My feeling is it is scripting, and so no, but maybe we should point at the security section 14:19:05 mgarrish: I am not sure what else there is outside of JS 14:19:23 ack duga 14:19:24 ... we should ask our security person 14:19:29 gpellegrino has joined #pmwg 14:19:38 present+ 14:20:58 duga: Do we want to explicitly call out webassembly, or just make it vague? 14:22:21 ack Hadrien 14:22:22 mgarrish: I think we can leave it vague, and use webasssembly as an example 14:22:45 Hadrien: When it comes to webassembly it opens some doors 14:22:56 ... but our scripting has always been spotty 14:23:04 ... so this pushes the issue further 14:23:52 q+ 14:23:59 ... the more things like this we add, the more of a balance there is with reading systems. Just something to keep in mind 14:23:59 s/WebAssembly discussion/https:\/\/github.com\/w3c\/epub-specs\/issues\/2649/ 14:24:19 shiestyle: Can the reading system distinguish between JS and webassembly? 14:24:49 mgarrish: Short of inspecting the file, no, but doesn't need to 14:24:58 q+ 14:25:03 ack me 14:25:04 ack shiestyle 14:25:05 ... we would have to flag it 14:25:15 ack duga 14:26:52 q? 14:26:59 q+ 14:27:04 ack ivan 14:27:05 duga: No, there isn't really a way of detecting it, but it doesn't really matter 14:27:16 ivan: What is the next step 14:27:57 mgarrish: I think we just need to change the exemption text a little 14:28:07 ... real question is the script tag itself 14:28:30 shiestyle: I will ask Voyager for their opinion 14:29:06 shiestyle + toshiakikoike: Discussion in Japanese 14:30:34 MasakazuKitahara: adds to discussion in Japanese 14:31:11 q+ 14:31:15 ack ivan 14:31:22 shiestyle: The feeling is there is a risk, and they are not seeing any need for it in Japan 14:31:31 ivan: I am curious what the risk is 14:31:49 ... The only thing is adding some speed, so it is not clear what the risk is 14:31:50 q+ 14:32:40 shiestyle: Well, the security risk. We already have JS, so maybe there is a little more risk? 14:32:54 ivan: Yes, but we can't block JS, it is already allowed 14:33:08 ... so my feeling the only thing this brings is performance 14:33:09 ack mgarish 14:33:26 ack mgarrish 14:33:42 mgarrish: We aren't forcing support, so it is fine to block from a RS perspective. 14:33:53 ... It would be very hard to ban this 14:34:05 ... it is already going through via an exemption 14:34:25 q+ 14:34:31 ack duga 14:34:58 SueNeu has joined #pmwg 14:35:10 present+ 14:35:35 shiestyle: relaying conversation in Japanese 14:35:59 toshiakikoike: continues in Japanese 14:37:04 shiestyle: toshiakikoike says JS is allowed, so webassembly can be allowed, so they understand 14:37:17 q? 14:37:54 ... so they understand, this is just their feeling 14:38:12 Topic: Accessibility work to be done in this charter 14:38:18 duga: And I also would add this is already supported per the spec 14:38:30 shiestyle: Moving on 14:38:47 ... we have to discuss what the a11y work will be 14:38:52 q+ 14:39:10 ack AvneeshSingh 14:39:22 AvneeshSingh: The broad things are in the charter, there are also new things we are finding as we do the work in the TF 14:39:35 ... those things need to be discussed in the wg 14:39:48 ... and there are some clarifications we will need to provide 14:40:10 ... The question we have is whay wcag 2.0 - why not 2.1 or 2.2? 14:40:28 ... We also need to discuss escapeability in Media overlays 14:40:46 ... We will also need to consider the new work in annotations 14:41:14 ... EAA is coming soon, so we may have feedback there 14:41:26 q+ 14:41:28 ... So this is the broad direction 14:41:32 ack me 14:42:08 q+ 14:42:20 shiestyle: The coformance version of wcag is a big change 14:42:46 ack CharlesL 14:42:55 q+ 14:43:01 AvneeshSingh: We will probably need to update for changes, not clear if it will be 1.1, or 1.1.2 or 1.2 14:43:14 ack ivan 14:43:17 CharlesL: There is also webtoons and fixed layout that may impact a11y 14:43:30 ivan: I was wondering about that as well. 14:43:50 q+ 14:43:51 ... We have the note on FL a11y, I was wondering if there was something from there that could be used 14:44:30 CharlesL: Yes, we are working towards using that information, and we are currently working on techniques for using that 14:44:48 ... There could be implications as we go through each item 14:44:54 q+ 14:45:19 ... and as a side note, Amazon publishing has just sent someone to that task force 14:46:01 ack mgarrish 14:46:05 q+ 14:46:14 ... There may by issues with wcag aa, may just be single a 14:46:36 ack ivan 14:46:39 mgarrish: There is also some property that will cause a change to the main spec 14:46:46 q+ 14:46:48 ack Hadrien 14:47:15 Hadrien: Thorium web is coming 14:47:39 ... One item we have is a "readability mode" which will be for fixed layout as well 14:48:03 ... we extract the structure and text, and provide that as another view 14:48:17 ... with full control (text size, etc) 14:48:33 ... This could be of interest to lots of people. 14:48:49 ack ivan 14:48:54 ... We view the feature as experimental, but it may be a good basis for a11y designs 14:49:22 ivan: Admin comment - a11y was done by a TF with separate meeting times 14:49:31 ... is that how it will work going forward? 14:50:00 AvneeshSingh: CG work needs to continue, we can't move that to all to WG 14:50:33 ... The meetings are a good way to keep things going 14:50:57 ... We will try to meet twice a month, and see how it is working out 14:51:05 Topic: admin 14:51:30 shiestyle: For the next call, we will cancel it, so the time is available if any TF wants to meet 14:51:41 ... does any TF want to meet? 14:52:01 AvneeshSingh: We don't need the time 14:52:04 q+ 14:52:08 ack duga 14:52:54 duga: Do we even have taskforces yet? 14:53:04 ivan: Not really, there is still work to do 14:54:12 ivan: we need names of people, etc. So we need that from say shiestyle and Hadrien 14:54:26 Hadrien: We have some ideas, do you want an early list 14:54:39 ivan: Give me a first list ASAP 14:54:40 Topic: AOB 14:56:34 duga: How many people will attend f2f in person? 14:56:44 ivan: Lots and lots! 14:57:01 shiestyle: Next week is canceled 14:57:13 rrsagent, draft minutes 14:57:14 I have made the request to generate https://www.w3.org/2025/02/13-pmwg-minutes.html ivan 14:58:58 s|https:\/\/github.com\/w3c\/epub-specs\/issues\/2649|https://github.com/w3c/epub-specs/issues/2649| 14:59:07 rrsagent, draft minutes 14:59:08 I have made the request to generate https://www.w3.org/2025/02/13-pmwg-minutes.html ivan 14:59:43 s/Topic:admin/Topic: Task Force admin/ 15:00:10 m2gbot, help 15:00:10 ivan, I am an IRC bot to link github issues and PRs to the minutes of the meetings where they were discussed. 15:00:10 ... I am an instance of minutes_to_gh version 0.8.1. 15:00:11 ... To know more, see https://github.com/pchampin/minutes_to_gh 15:00:37 m2gbot, link with transcript 15:00:37 sorry ivan, I don't understand "link with transcript" 15:00:51 m2gbot, link issues with transcript 15:00:51 Something wrong happened: Failed loading JSON from https://raw.githubusercontent.com/w3c/groups/refs/heads/main/wg/pmwg/repositories.json 15:04:24 CharlesL has left #pmwg 15:18:12 rrsagent, bye 15:18:12 I see no action items