13:27:28 RRSAgent has joined #pmwg 13:27:32 logging to https://www.w3.org/2024/11/01-pmwg-irc 13:27:32 RRSAgent, make logs Public 13:27:33 Meeting: Publishing Maintenance Working Group 13:27:40 Chair: wendy 13:27:40 Date: 2024-11-01 13:27:40 Meeting: Publishing Maintenance Working Group Telco 13:27:40 Agenda: https://lists.w3.org/Archives/Public/public-pm-wg/2024Oct/0000.html 13:54:19 wendyreid has joined #pmwg 13:56:17 duga has joined #pmwg 13:59:12 shiestyle has joined #pmwg 13:59:14 MasakazuKitahara has joined #pmwg 13:59:15 present+ 13:59:20 present+ george 13:59:24 toshiakikoike has joined #pmwg 13:59:25 present+ brady 13:59:30 present+ 13:59:35 present+ 13:59:36 present+ 13:59:43 present+ wendy 13:59:43 mgarrish has joined #pmwg 13:59:50 George has joined #pmwg 14:00:19 present+ 14:00:26 present+ avneesh 14:00:40 AvneeshSingh has joined #pmwg 14:00:56 present+ 14:01:25 present+ 14:01:28 present+ 14:02:41 George has joined #pmwg 14:03:23 present+ charles 14:03:38 CharlesL2 has joined #pmwg 14:03:48 scribe+ 14:03:51 present+ 14:04:06 present+ 14:04:41 George has joined #pmwg 14:05:02 present+ ben_dugas 14:05:21 wendyreid: Welcome Ben 14:05:51 Ben: At Kobo for a long time, I lead the rendering side of things 14:06:01 ... we have a few 14:06:35 ... I used to be on these calls, then wandered off as I wasn't contributing, but Wendy talked me into coming back 14:06:41 George has joined #pmwg 14:07:15 ... I may also get someone more technical to join 14:07:26 ... I am mostly interested in webtoons and related 14:07:48 https://w3c.github.io/publ-maintenance-wg-charter/ 14:07:56 wendyreid: We are back into rechartering 14:08:51 ... there have been some modifications 14:08:58 George has joined #pmwg 14:09:09 ... content hasn't changed much, mostly wordsmithing 14:09:54 ... new scope has webtoons, annotations, a11y, some fixed layout properties, some script/wasm stuff, and a sprinkle of future things 14:10:19 ... biggest change is a11y of comics/manga has changed to broader fixed layout 14:10:30 ... This will be EPUB 3.4 14:10:45 https://github.com/w3c/publ-maintenance-wg-charter/issues/37 14:10:47 q? 14:11:15 ... some outstanding issues 14:11:41 q? 14:11:46 q+ 14:11:47 q+ 14:11:49 ... Start with accessibility - is there anything else we need, particularly with an eye toward upcoming legislation 14:11:51 ack ivan 14:12:37 ivan: To clarify, we have a scope item that says work with the Publishing CG a11y grouo 14:12:46 ack George 14:12:55 s/grouo/group/ 14:12:57 ... but do we need to add any specific language 14:13:36 George: US legistlation may require some metadata, but no change needed 14:14:18 Ben has joined #pmwg 14:14:22 wendyreid: from Avneesh, there was a comment about looking at gaps 14:14:26 q+ 14:14:34 ack AvneeshSingh 14:14:36 ... do we want to consider an update to the crosswalk doc that includes title 2? 14:15:16 AvneeshSingh: We have been discussing with a similar table would be nice or not, we did decide we need to do some gap analysis, but may not want to be a crosswalk table 14:15:30 ... With title 2 it may be more of a strategic issue 14:15:47 q+ 14:15:56 ack George 14:16:09 q+ 14:16:11 q+ 14:16:18 ... It would be good to mention whether we should do more of this work in the CG or add a note from the WG (mention in charter) 14:16:33 ack ivan 14:16:40 George: It would really help adoption to have better communication, not much of a spec issue 14:16:57 ivan: I propose we add something to the charter, but it may not be rec track work 14:17:27 ... Maybe in the first block of scopes say we will look at legislation and consider a note or changes to the spec 14:17:36 ... for political reasons that is a good idea 14:17:54 ... we need links to the various legislation 14:18:23 ack mgarrish 14:18:24 ... can someone send me that info? EU, US, maybe Canada? And mention Japan and India if they have anything 14:18:59 mgarrish: Second Ivan. Getting into legislation is a bad thing to do in spec. It should be notes, etc that aren't on the rec track 14:19:10 ... Probably shouldn't be in epub a11y 14:19:37 wendyreid: Agree. I can try and put together some text. We might not even reference them explicitly by name 14:19:56 ... exhaustive list will be hard 14:20:08 AvneeshSingh" Maybe just EAA as an example 14:20:10 wendyreid 14:20:12 https://github.com/w3c/publ-maintenance-wg-charter/issues/31 14:20:25 wendyreid: Issue 31, mentioning epubcheck 14:20:45 S/just EAA/just EAA and Title II 14:20:58 ... We will need changes in epubcheck if we change the spec, so we need to refer to epubcheck somehow 14:20:58 q+ 14:21:01 ack ivan 14:21:40 ivan: We had it as an extra exit requirement, basically epubcheck must support epub 3.3 14:21:58 ... So adding that is easy, but are we shooting ourselves in the foot? 14:22:07 ... Will there be enough work on it? 14:22:32 ... there are some complex issues for it (annotations) 14:22:36 q+ 14:22:39 ack duga 14:22:41 scribe+ 14:22:47 q+ 14:22:52 duga: I don't know what the current state of funding is? 14:23:00 q+ 14:23:08 ... I remember contributing, and asking organization, but I don't know where that stands 14:23:14 ack AvneeshSingh 14:23:48 AvneeshSingh: In the previous charter it was there because we had the fundraising going, but at this point I don't see anyone raising funds 14:24:07 ... We have reached out to w3c for funding, but no response yet 14:24:16 q- 14:24:32 ... There is no guarantee. We need a proper project if we add it as exit criteria 14:24:46 q+ 14:24:49 ack ivan 14:24:49 ... we could add it as a "will work with the maintainers" 14:25:01 ... and send to steering committee 14:25:15 ivan: I did not understand, is there a separate task force 14:25:33 AvneeshSingh: Yes, we made a TF when we joined w3c 14:25:39 ivan: I had no idea 14:25:46 AvneeshSingh: Maybe ask Romain 14:26:24 ivan: Currently I don't think we should add it. Let's talk to the steering committee, etc, first 14:26:59 ivan: I will update the issue 14:27:20 q+ 14:27:24 ack ivan 14:27:39 wendyreid: Anything else? 14:27:43 https://github.com/w3c/strategy/issues/481#issuecomment-2440853261 14:27:50 ivan: Yes, a PR, not an issue 14:28:05 ... There is a required review 14:28:35 ... The PR has approvals from 4 people, including the w3c security reviewer 14:28:49 ... but I like to leave it open for a little while 14:29:26 ... This is just some blanket language about security issues that may be raised, we promise to look at it 14:29:59 ... I would like to merge, objections? 14:30:03 wendyreid: Not from me 14:30:11 ivan: Ok, I will merge it 14:30:47 ... I would like to close without further action the TDM issue 14:31:11 ... I was wondering if there was anything to add, it seems to me the answer is no 14:31:37 q+ 14:31:41 ack George 14:32:03 ... Ok, I will close it since there are no objections 14:32:16 George: Is there anything we need to be thinking about with metadata? 14:32:48 q+ 14:32:49 ... We have the xwalk, is there any other metadata, particularly a11y, we need to add? And is it in scope? 14:32:51 q+ 14:33:09 ivan: If you are talking about new metadata vocabs, then it is out of scope 14:33:28 ... If you are talking about references, none of those things are normative and can be done now anyway 14:33:38 ... so I don't know what we would add 14:33:45 ack AvneeshSingh 14:33:55 George: So if we want to add values to schema that is out of scope for us 14:33:59 ivan: yes 14:34:40 q+ 14:34:41 ack mgarrish 14:34:41 AvneeshSingh: There are some vocabs we created. Is such an addition of epub domain vocab in scope or not? 14:34:57 q- 14:35:16 mgarrish: We have some metadata, that is what some of the text in the charter is about 14:35:21 q+ 14:35:29 q+ 14:35:32 ... We could incubate something, but not add it to the charter now 14:35:42 ack ivan 14:35:48 AvneeshSingh: Q: if something comes in, can we add it? Sounds like yes 14:36:10 ivan: There is an explicit out of scope section, which includes vocab 14:36:29 ... I just copied it from the last version, I don't know why we had it at all 14:36:50 ... some make sense (e.g. DRM), but I don't know where that comes from 14:36:58 q+ 14:37:27 ack CharlesL2 14:37:28 ... we could just remove the new metadata vocabs from out of scope and we are fine 14:37:33 ack CharlesL 14:37:49 CharlesL2: I agree. We may also need to add more metadata with the new fixed layout work 14:37:58 ack wendyreid 14:38:21 wendyreid: In mentioning the out of scope section, I agree the new metadata stuff doesn't need to be there 14:38:42 ... we also have something about things that impact viewports 14:38:44 q+ 14:39:02 ack duga 14:39:26 duga: I assume that's there because of the pain we experienced from our custom CSS properties and this is our promise to the world we'll never do it again 14:39:39 q+ 14:39:57 ... I noticed it as well, it's very vague, we can get around it by saying "we needed to", and removing it feels like removing our promise to the CSS working group 14:40:12 ... I think we can leave it, we have ways around it when we need it 14:40:15 ack ivan 14:40:52 ivan: Echoing that, that bullet and the previous one was an answer to some people who say we don't need epub at all 14:41:03 ... We do get those types of remarks 14:42:04 wendyreid: Anything else? 14:42:19 ivan: I proposed two to be closed, both refer to dpub aria 14:42:30 ... I propose closing because it isn't in our scope 14:42:54 ... and not something we want to take over (aria wg has taken that over) 14:43:05 q+ 14:43:06 George: Should they go to CG? 14:43:33 ivan: I would think since these are so specific they need to go to aria wg 14:44:01 ack AvneeshSingh 14:44:08 mgarrish: We propbably need a new tf. I don't think that group can move on those at this point 14:44:41 AvneeshSingh: We have an official liason, what we need to do is create strong use cases so we can push it in the aria wg 14:44:50 ... that is all we really need to do 14:45:22 q+ 14:45:43 ack George 14:45:51 wendyreid + AvneeshSingh: Better to come through WG rather than CG 14:46:48 George: One attribute was "exercise", would it be good for the cg (wg?) to work on an interactive question/answer mechanism 14:46:56 q+ 14:46:59 ack ivan 14:47:01 ... clearly it is something the industry needs 14:47:13 ivan: Reminds me of edupub 14:47:33 ... I think it would be premature for the wg, it requires a lot of incubation 14:48:14 ... The right thing is to get a TF in the CG going, just like a11y group 14:48:28 ... then in a few years bring it back to the wg 14:48:52 ... But needs some strong leadership 14:49:32 q- 14:49:58 CharlesL2: When will we start voting on the charter? 14:50:21 ivan: Need horizontal review, we have 2 (international and security) 14:50:28 ... may be a few weeks for the others 14:50:47 ... so charter to AC in mid Dec? Or hold to Jan 1 14:51:09 ... which means if there are no formal objections, then the new charter would start in Feb 14:51:22 CharlesL2: APA has some potential additions 14:52:34 ivan: The sooner the better, since it is being actively reviewed 14:52:46 AvneeshSingh: I don't expect many surprises 14:53:08 CharlesL2 has left #pmwg 14:53:09 rrsagent, draft minutes 14:53:10 I have made the request to generate https://www.w3.org/2024/11/01-pmwg-minutes.html ivan