13:01:23 RRSAgent has joined #pmwg 13:01:27 logging to https://www.w3.org/2025/06/12-pmwg-irc 13:01:41 zakim, start the meeting 13:01:41 RRSAgent, make logs Public 13:01:43 Meeting: Publishing Maintenance Working Group 13:01:46 present+ 13:01:49 present+ 13:01:54 mgarrish has joined #pmwg 13:02:00 Hadrien has joined #pmwg 13:02:04 present+ 13:02:19 George has joined #pmwg 13:02:25 present+ 13:02:31 CharlesL has joined #pmwg 13:02:41 present+ 13:03:00 present+ 13:03:07 elguerrero7 has joined #pmwg 13:03:15 scribe+ 13:03:31 Topic: Scrolled Comics 13:03:49 wendyreid: first topic is scrolled comics - over to shiestyle 13:04:38 present+ 13:04:39 shiestyle: Our TF discussed specs for scrolled comics 13:05:00 ... we already have webtoons formats in Japan, but the current style isn't good for the specs 13:05:16 ... so we need to determine how to define webtoons in the specs 13:05:34 ... so today we will present two proposals 13:06:04 ... first, we have rendition-scrolled [is that the right one?] 13:06:10 q+ 13:06:16 ... we will add a new value 13:06:59 ... we did not have a strong oposition to rendition-layout: scrolled 13:07:30 ... we want both new and existing features to be valid 13:07:30 q+ 13:07:39 ack Hadrien 13:07:47 ... so we want to update the note like this 13:08:14 Hadrien: Voyager Japan sent an email that was very supportive regarding that approach 13:08:51 ... I think this concept that we add a new thing while acknowledging the old this is consistent with the way we have done this before (e.g. fixed layout) 13:09:34 ... So mention the old way, but encourage the new way for implementation consistency 13:09:42 ack wendyreid 13:09:48 ack wendyreid 13:10:03 wendyreid: What is the fallback scheme? 13:10:07 q+ 13:10:28 ... if we get a book with rendition-layout: scrolled? Most RS would fall back to reflow 13:10:49 ... should we have some sort of fallback? 13:11:02 ... Maybe a fallback rendition-layout value? 13:11:05 ack Hadrien 13:11:42 Hadrien: I have done some testing, first the way the current style works, and they generally just show as fxl 13:11:46 ... which is really bad 13:12:05 ... I then tried the new way and it falls back to flowing, which is also bad 13:12:12 q+ 13:12:29 ... we are asking for a new mode 13:12:41 ... if a RS doesn't have it there isn't much to do 13:12:46 ack SueNeu 13:12:50 q+ 13:13:00 scribe+ 13:13:23 SueNeu: If we decide on a fallback mode maybe ask for pagination from the contet creators 13:13:31 ack duga 13:13:34 ... not great but better than reflow 13:14:14 duga: I'm not sure how feasible that would be, there is actually a company that does this, they make money off paginating webtoons, it's not trivial 13:14:27 ... it would be nice if every webtoon had an alternative that did this. 13:15:03 ... question I had is what is the mandated behaviour of rendition:layout if it's unknown? 13:15:14 ... are we supposed to assume its reflow? 13:15:34 Hadrien: In my testing its treated as reflow 13:15:45 q+ 13:15:51 wendyreid: I am checking now 13:16:08 ... "must use one of the following" 13:16:19 ... reflowable is the default 13:16:24 ack shiestyle 13:17:02 shiestyle: Japanese publishers just won't sell them on platforms where it doesn't work 13:17:16 q+ 13:17:21 ack Su 13:17:30 q+ 13:17:39 SueNeu: How does this relate to panel by panel navigation? 13:17:47 ack Ha 13:17:48 ... will webtoons do that? 13:18:12 Hadrien: I would argue it isn't really necessary since the content was designed for phones 13:18:30 ... panel to panel is helpful for reading things on smaller devices 13:18:40 ... Also maybe for a11y 13:19:01 ... And as far as I am aware panel to panel in Amazon is proprietary 13:19:34 ... And as shiestyle said, just not providing content is probably fine 13:19:51 ... and at some point we should talk to Editour and get the property added 13:20:01 ... so the content can be filtered out 13:20:22 wendyreid: We should get a PR so we can see it in place 13:20:39 ... shiestyle, Hadrien, can you work with Matt to get this done? 13:21:01 Hadrien: Sure we will have a PR ready before the next TF report to this group 13:21:11 Topic: EPUB to ISO 13:21:14 wendyreid: Our other topic was ISO 13:21:22 q+ 13:22:04 ... we want to take EPUB 3.3 to ISO. There are other groups that want it ASAP. ISO is still on 3.0.1 13:22:13 ack gpellegrino 13:22:48 gpellegrino: As you may recall we asked for the group to wait on this until the EU a11y legislation was done 13:23:27 ... If we go to ISO then it will be adopted by the EU, so it will be a different spec than the one publishers are using 13:23:53 ... so we made an arrangement for them to reference the W3C version 13:24:32 ... so the European commission did not require the ICT version 13:24:57 ... This was supposed to be in place in a couple of weeks, but WCAG is delayed until next year 13:25:09 ... so I would request that we wait 13:25:11 q+ 13:25:21 ack gpellegrino 13:25:32 wendyreid: Can't they do whatever they want? 13:25:55 gpellegrino: The ICT is just a reference and the EC will endorse it 13:26:06 wendyreid: How long are they going to make us wait? 13:26:12 DaleRogers has joined #pmwg 13:26:16 q+ 13:26:21 ack mg 13:26:36 mgarrish: Can we split it up? 13:26:55 ... then we can push at least EPUB 3.3, but delay a11y spec? 13:27:37 wendyreid: Is this ICP thing for a11y 1.1 and epub 3.3? 13:27:50 s/ICP/ICT/ 13:28:04 gpellegrino: We presented a11y 1.1, epub 3.3., and RS 3.3, so they may point at those as well 13:28:14 wendyreid: This is very awkward 13:28:45 ... If we go to ISO, one option is they could just keep going with the current path 13:29:02 ... will they decide to change what they are pointint at? 13:29:38 Leonard: They can do whatever, but that doesn't mean they will 13:30:19 wendyreid: So are we really worried about going to ISO, and they will change what they are using? 13:30:32 present+ Leonard Rosenthol 13:30:55 Leonard: They do have to make changes by agreement with the committees involved 13:31:03 q+ 13:31:05 q+ 13:31:19 ack gpellegrino 13:31:31 wendyreid: I want to understand what is technically possible vs what will actually happen 13:31:57 q+ 13:31:59 ack AvneeshSingh 13:32:12 gpellegrino: They decided not to keep the mandate to make a new European standard 13:32:52 AvneeshSingh: ISO is a kind of trigger, and historically we have had trouble keeping European standards in line with us 13:33:22 ... so we really don't want to have to open a new can of worms 13:33:37 q+ 13:33:39 ... gpellegrino what are your thoughts on the previous efforts here? 13:33:42 ack SueNeu 13:34:39 q+ 13:34:43 ack George 13:34:45 gpellegrino: Even with that huge effort (EU version of WCAG), it isn't in a great 13:34:49 ... place 13:34:57 AvneeshSingh: And we are smaller than the web 13:35:14 q+ 13:35:28 George: After [date I missed], there is an existing default standard that will be in place 13:35:58 ... If we wait a little while before going to ISO, the more it establishes the existing defacto standard 13:36:12 ... Once we have that we should be able to go to ISO 13:36:42 ack SueNeu 13:36:50 ... I can't imagine at that point going to ISO would cause a harmonized spec to trigger 13:37:04 SueNeu: Is this a place where backwards compat will help us? 13:37:14 ... Since their older books will still be usable 13:37:48 ... I am not sure of the utility of waiting if everything is backwards compatible. What would happen if we went to ISO with 3.3? 13:37:56 ack wendyreid 13:38:01 s/... This was supposed to be in place in a couple of weeks, but WCAG is delayed until next year/... the EAA will go into effect in two weeks, but as of yet there is no committee request to reference EPUB standards as ICT Technical Specification/ 13:38:02 ... Will this require new things of publishers? 13:38:20 wendyreid: The prime example is WCAG and EN3459 13:38:47 ... For instance the EN spec covers a lot more than the web, web is just one chapter 13:39:18 1+ 13:39:18 wendyreid: But I got on the queue to say we are using the PATH approach to going to ISO 13:39:20 q+ 13:39:38 ... so there isn't much room to change things (just minor termiology) 13:39:50 ... This is per agreement between ISO ad W3C 13:40:19 ... so I don't think we need to worry that it will cause a change anything substantively 13:40:36 ... But all we have been hearing "just wait" with no timeline 13:40:51 ack gpellegrino 13:40:57 ... And the rest of the world is on hold without even having a deadline 13:41:07 gpellegrino: two things on what may happen 13:41:38 ... First, they may require new metadata, and all content made now without it will cause all current epubs to fail 13:42:31 DaleRogers has joined #pmwg 13:42:37 s/They decided not to keep the mandate to make a new European standard/They decided to exclude e-book from the mandate to update EN 301 549/ 13:42:49 wendyreid: I guess we are stuck waiting again 13:42:51 q+ 13:42:56 ack duga 13:43:10 duga: Do we just set a reminder to ourselves to have this conversation again in 6 months, a year? 13:43:15 q+ 13:43:20 gpellegrino: 13:43:23 ack plh 13:43:29 ack gp 13:43:40 gpellegrino: I think TPAC is the right time to discuss again 13:44:07 shiestyle: Let's continue at TPAC 13:44:11 Topic: AOB 13:44:15 q+ 13:44:22 q+ 13:44:26 ack Avne 13:44:55 AvneeshSingh: TPAC - when do we want to have the meeting? APA is already looking at their cross group meetings 13:45:25 ... DAISY will be having meetings on the 12th and 13th, so it would help to have dates ASAP 13:45:46 wendyreid: I have already requested the 10th and 11th, our typical Monday/Tuesday 13:45:51 ack duga 13:46:03 duga: What about the survey? Did we agree on the wording? 13:46:24 SueNeu: yes, we have agreed and we have the Japanese translation 13:46:37 ... And Ivan is working on it, though he is off 13:46:44 q+ 13:46:50 q+ 13:46:53 ack SueNeu 13:47:10 SueNeu: Which brings us to who we ae sending this to 13:47:20 ack CharlesL 13:47:42 q+ 13:47:44 CharlesL: and in addition, do we have the verbage for the email that links to the survey 13:47:59 ack AvneeshSingh 13:48:04 wendyreid: We should have a wiki or doc to coordinate and propose text 13:48:06 +1 13:48:40 AvneeshSingh: We will be sending out the inclusive publishing newsletter, so if it is ready then we can add it there 13:49:06 wendyreid: May SueNeu and I can work on setting up coordination for comms 13:49:43 CharlesL has left #pmwg 13:50:13 rrsagent, make log public 13:50:35 rrsagent, draft minutes 13:50:36 I have made the request to generate https://www.w3.org/2025/06/12-pmwg-minutes.html shiestyle 13:51:57 present+ SueNeu 13:52:07 present+ duga 13:52:15 present+ duga 13:52:19 DaleRogers has left #pmwg 13:52:20 LaurentLM has joined #pmwg 13:52:25 present+ toshiakikoike 13:52:54 present+ LaurentLM 13:53:23 Chair: wendyreid 13:53:41 present+ Dale 13:53:51 rrsagent, draft minutes 13:53:53 I have made the request to generate https://www.w3.org/2025/06/12-pmwg-minutes.html shiestyle 13:54:23 zakim, end the meeting 13:54:23 As of this point the attendees have been gpellegrino, wendyreid, Hadrien, shiestyle, CharlesL, George, mgarrish, Leonard, Rosenthol, SueNeu, duga, toshiakikoike, LaurentLM, Dale 13:54:26 RRSAgent, please draft minutes v2 13:54:27 I have made the request to generate https://www.w3.org/2025/06/12-pmwg-minutes.html Zakim 13:54:33 I am happy to have been of service, shiestyle; please remember to excuse RRSAgent. Goodbye 13:54:33 Zakim has left #pmwg 14:21:40 plh has left #pmwg 15:02:35 gautierchomel has joined #pmwg 15:06:22 LaurentLM has joined #pmwg