13:18:02 RRSAgent has joined #pmwg 13:18:06 logging to https://www.w3.org/2023/11/03-pmwg-irc 13:18:06 RRSAgent, make logs Public 13:18:07 Meeting: Publishing Maintenance Working Group 13:18:40 ivan has changed the topic to: Meeting Agenda 2023-11-03: https://lists.w3.org/Archives/Public/public-pm-wg/2023Nov/0000.html 13:18:41 Chair: wendy 13:18:41 Date: 2023-08-03 13:18:41 Agenda: https://lists.w3.org/Archives/Public/public-pm-wg/2023Nov/0000.html 13:18:41 Meeting: Publishing Maintenance Working Group Telco 13:38:52 ivan has left #pmwg 13:39:04 ivan2 has joined #pmwg 13:57:47 shiestyle has joined #pmwg 13:58:41 present+ 13:58:50 present+ shiestyle 13:59:07 present+ Yong-Sang_Cho 13:59:26 toshiakikoike has joined #pmwg 13:59:41 wendyreid has joined #pmwg 13:59:42 present+ wendy 13:59:52 present+ 14:01:56 present+ rickj 14:02:56 mgarrish has joined #pmwg 14:03:05 present+ mgarrish 14:03:12 present+ avneesh 14:04:43 AvneeshSingh has joined #pmwg 14:04:55 present+ 14:06:04 rickj has joined #pmwg 14:06:08 present+ 14:06:34 Guest42 has joined #pmwg 14:06:43 scribe+ 14:06:44 present+ 14:07:04 present+ LaurentLM 14:07:57 wendyreid: Change of plan, let's discuss publishing 14:08:38 q+ 14:08:44 ... we wanted to be on a six month schedule 14:08:50 ... do we want to do webtoons later 14:08:53 ack ivan 14:09:09 ivan: There's an advice or request in the process to not publish more often than six months 14:09:28 ... if we publish now without webtoons, we might need to wait another 6 months to incorporate that 14:09:36 ... there's nothing urgent to publish now 14:09:42 ... everything is relatively harmless 14:09:50 ... webtoons is the most complex and relevant thing 14:10:01 ... we can wait until we finally say yea or nay on the webtoon changes 14:10:32 q+ 14:10:53 mattgarrish: We don't have anything critical, we have one class three already, if we need to do that approval we might as well wait for webtoons 14:11:03 ... I don't know if it affects for just core or RS 14:11:16 q+ 14:11:21 ... do we need to publish all together, or one doc at a time 14:11:25 ack shiestyle 14:11:39 shiestyle: We might need to discuss webtoons, it could take a while 14:11:46 ... to resolve the topic 14:12:13 ... I have a proposal, to regulate the restriction on rendition:flow 14:12:26 ... we can add a note on this restriction not just for webtoons 14:12:30 ack ivan 14:12:31 q+ 14:12:58 ivan: Just to answer Matt, my personal preference would be to take the 3 recs together 14:13:05 ... it's a unit in three documents 14:13:15 ... keeping them aligned is better message-wise 14:13:25 ack wendyreid 14:14:12 present+ charles 14:14:43 q+ 14:14:47 CharlesL has joined #PMWG 14:14:56 present+ 14:15:14 q+ 14:15:45 wendyreid: To Matt, it's a change to both, to Shinya, it might not take as long 14:16:02 ivan: For class 3 we go to a AC review 14:16:22 ... same way as CR, we must have tests, and implementations to back up the test 14:16:41 ... it's important to have the feedback we need, if it won't pass the testing phase we shouldn't do it 14:16:45 ack ivan 14:16:49 ack LaurentLM 14:17:49 LaurentLM: +1 Ivan, it's not only allowing rendition:flow for FXL, it's also specifying in reading systems when two images should be placed one after another, in HTML, they won't be naturally put border on border 14:17:50 present+ tzviya 14:17:54 q+ 14:17:57 ... it's a need for specific implementations in RS 14:18:01 ... it's an important modification 14:18:08 ... not just one line in the spec 14:18:09 q+ 14:18:10 +1 to LaurentLM 14:18:15 ack shiestyle 14:18:56 shiestyle: In 3.3, rendition:flow can be used in FXL and reflow, only in RS is it forbidden 14:19:16 q+ 14:19:17 ... maybe we need another test, we already allow the use in the package, we may not need a new test 14:19:22 ack wendyreid 14:19:31 q+ 14:21:16 wendyreid: We need to look at the existing tests, and the language, we're usually not that strict with language 14:21:17 tzviya has joined #pmwg 14:21:18 ack ivan 14:21:25 ivan: I don't have the test suite in my head 14:21:32 ... even if we have a test with rendition:flow 14:21:43 ... then the test today should say it's not allowed 14:22:00 ... either we don't have a test, or we have a test where we need to change the criteria 14:22:09 ... long term, we need the feedback of an engineer 14:22:23 ... feedback on implementation, how it went 14:22:44 rrsagent, pointer 14:22:44 See https://www.w3.org/2023/11/03-pmwg-irc#T14-22-44 14:22:46 ... noting that for the CR lines, we would need a test suite that meets the criteria 14:22:55 ... we need 2 implementations 14:22:55 present+ 14:23:03 ack LaurentLM 14:23:28 LaurentLM: Just to add, even if reading systems on FXL support scrolled-continuous, they will put the pages one below the other 14:23:40 ... most of the reading systems will add margins 14:23:46 ... the RS will have followed the riles 14:23:54 ... but the user experience will be poor 14:24:07 ... we need further further specification 14:24:13 ... it's complex 14:24:18 q? 14:24:30 q+ 14:25:00 wendyreid: We're working on a lot of assumptions, let's look at what is currently there. 14:25:03 ack shiestyle 14:25:34 shiestyle: I wonder if we change the restriction in reading systems, RS don't have to implement the ??? 14:25:46 ... reading systems don't have to implement the feature 14:26:02 LaurentLM: I'm not saying if it was allowed that RS must do it, but they would not pass the tes 14:26:03 q+ 14:26:11 ... the systems not implementing would look bad 14:26:32 ... most RS would do it correctly in regards to the spec, not what webtoons are 14:26:35 ack mgarrish 14:26:53 mgarrish: I was just going to say we're spinning our wheels, we need to know the specifics 14:27:11 ... FXL is generally SHOULDs, if we get into MUST that is tricky 14:27:22 ... we need to get what is further into what is needed 14:27:33 ... let's focus on getting this specced out, then build the tests. 14:27:48 ivan: Someone should come up with a PR 14:27:53 ... knowing it's a class 3 change 14:28:01 ... changes marked up in the text 14:28:14 wendyreid: I'll take a crack at it 14:28:27 mgarrish: Might be better to get the text finalized then do the formal diff 14:28:46 +1 to wendyreid 14:29:05 Topi: ISO 14:29:16 s/Topi/Topic/ 14:29:53 https://w3c.github.io/epub-specs/epub33/fxl-a11y/ 14:30:23 q+ 14:30:44 ack ivan 14:31:14 ivan: Just to add more info, we will have a call, Gregorio, Cristina, and I, with the EU Commission in a week 14:31:36 ... to put an end to the discussion on if we publish through ISO does it jeopardize the acceptance of our docs in the EU 14:31:46 ... we'll make a presentation to them 14:31:57 ... hopefully this issue will be resolved by the end of the year 14:32:11 ... we'll know for sure if ISO is a yes or no 14:32:35 ... the other problem is that W3C and JTC1 have discussed the practical details of the PAS process 14:33:06 ... up until last year, my information was, the PAS process was simple, the documents themselves stay as W3C docuemtns 14:33:14 ... HTML format with the styling 14:33:25 gpellegrino has joined #pmwg 14:33:26 ... only thing we'd need to produce is a cover letter of sorts 14:33:30 ... referring to the W3C documents 14:33:39 present+ 14:33:40 ... this means we don't have a lot of editorial work 14:33:55 ... the latest round says, JTC1 requires us to turn the documents to ISO format 14:34:06 ... convert to MS Word, change the styling and layout 14:34:10 ... change some of the language 14:34:15 ... huge amount of editorial work 14:34:26 ... I don't know if it's required or not 14:34:47 ... at the moment there are discussions, we're not the guinea pigs, since WAI has published WCAG 2.2 14:35:12 ... previous versions had an ISO stamp, now they want to push WCAG 2.2 to ISO 14:35:32 ... WCAG 2.2 is more complex than EPUB, maybe JTC1 will come back on their requirements 14:35:36 ... it's an unknown 14:35:50 ... I just expressed our unhappiness about this, hopefully WCAG paves the way for us 14:36:07 present+ cristina 14:36:34 q+ 14:36:39 ack gpellegrino 14:36:58 q+ after ISO discussion 14:37:09 Yong-SangCho: Question, does JTC1 emphasize document format is the most important issue? 14:37:11 q+ 14:37:38 ivan: I was not at the discussion, I saw a presentation on PAS in general, no discussion with ISO on EPUB specifically 14:38:01 ... there may be some other issues, I'm waiting to see if the formatting problem is there or a non-issue 14:38:13 Yong-SangCho: JTC1 and ISO have the same document directives 14:38:24 ... part 2 has normative guidance on writing standards 14:38:46 ... in case of editing, I have experience in converting EPUB to Korean National Standard 14:39:07 ... its a heavy effort, maybe I can volunteer or people from my group can support this conversion 14:39:22 ... aside from formatting, are there other issues in the procedure? 14:39:37 ... if there are, I can volunteer to communicate 14:39:49 ... we'd like to keep the technical side in balance 14:40:06 ... want to keep EPUB an international standard 14:40:28 ... we'd like to adopt it as is if we can 14:41:27 ivan: First of all, thank you, Matt and I, and the other editors, I have not tried to do the conversion before 14:41:36 ... I have edited an ISO standard, but it was a while ago 14:41:55 ... there's a terminology review that is more worrisome than word formatting 14:42:03 ... make sure meanings are the same 14:42:21 ... I think the PAS process means we enter a late stage of the process in ISO 14:42:39 ... PAS process also includes original documents would be the same 14:42:52 ... W3C docs are free, ISO are paid 14:43:11 Yong-SangCho: Since W3C docs are available for free, the same content on ISO is also freely available 14:43:17 ivan: That's good news 14:43:29 ... for the timing, we need to wait on the other problem 14:43:47 ... from our POV, that's the major challenge 14:44:05 ... we should also begin the process after we get the class 3 changes through, we should use that version 14:44:12 q+ to mention archiving 14:44:41 Yong-SangCho: If we have any concerns you want to check with JTC1, please let me know, I can check and communicate, I'll do my best to keep the original content 14:44:45 q+ 14:44:58 q- 14:45:17 tzviya: I don't know Yong-Sang if you know, what about EPUB for archiving? 14:45:30 ... any ideas on how we can coordinate our work with them, they're using an old version 14:45:55 Yong-SangCho: It's just standing on preliminary work items, not yet a formal standard, there's a lot of comments referencing the latest version 14:46:30 ... EPUB Archiving, not sure, we didn't decide the format, there's lots of other document types, we haven't decided yet which document type is appropriate for it 14:46:36 ... it should reference EPUB 3.3 14:46:47 tzviya: It should reference the latest W3C version, not ISO? 14:47:05 Yong-SangCho: Since there's no ISO standard, they can point to W3C's standards 14:47:22 ... EPUB 3.3 need to be in the bibliography, not normative references 14:47:30 ... since it's outside ISO right now 14:47:46 ... that's my understanding 14:47:51 ... we need to discuss more details 14:48:21 ivan: If EPUB 3.3 gets to ISO 14:48:37 ... it would probably become an ISO standard before archiving 14:48:55 Yong-SangCho: It'll be at least 36 months, + 3 or 6 months 14:49:32 ... if EPUB 3.3 gets through PAS track, if EPUB Archive is released after 14:49:45 ivan: then the archive will refer to the latest ISO spec, which would be 3.3 14:49:58 Yong-SangCho: We'd like to share the latest update on EPUB/A 14:50:12 ... it's not isolated or a different specification, it's based on EPUB 14:50:22 ... we'll share the latest when it's ready 14:50:40 ack tzviya 14:50:40 tzviya, you wanted to mention archiving 14:50:44 ack shiestyle 14:51:00 shiestyle: Thanks for coming today Yong-Sang, question about Korean ebook industry 14:51:23 q+ to comment on EPUB archive 14:51:23 ... does it want to bring EPUB 3.3 to ISO, is there a problem if it doesn't? 14:52:04 Yong-SangCho: The industry is flexible, its been operating with what is the latest, but the public sector, the government, will only adapt to ISO 14:52:17 ... textbooks and such. Public sector has stronger regulations 14:52:31 ... needs to use Korean Standards or international standards 14:52:55 ... industry is favoured to taking international standards, since the standards are clearer, more consistent 14:53:02 ... software follows regulations 14:53:12 ack AvneeshSingh 14:53:12 AvneeshSingh, you wanted to comment on EPUB archive 14:53:36 AvneeshSingh: Comment on EPUB Archive, I'm concerned about two international standards, it seems confusing 14:54:02 ... my recommendation would be that EPUB 3.3 is the international standard, and EPUB Archive is a technical specification 14:54:06 ... more clarity 14:54:25 Yong-SangCho: I'll deliver your comment to the lead, we don't want to be trouble makers 14:54:45 topic: Misc 14:55:02 gpellegrino: Just to tell you that we are updating the note with the mapping 14:55:21 ... in view of the meeting we're having with the commission, I'll post a PR over the weekend 14:55:38 ... having you all double check the changes would be helpful 14:55:53 ... if we can approve the mapping, and publish an updated version that would be great 14:56:32 gpellegrino: Does it need a vote to be updated? 14:56:56 wendyreid: Is it published to TR? 14:57:13 ivan: If we follow the procedure, it will autopublished via echidna 14:57:27 ... if there is enough reviewers, we can merge and it will update TR 14:57:34 ... not as formal 14:57:49 mgarrish: We've not had formal calls on notes 14:57:56 ... we've tried to make sure everyone is on board 14:58:15 ... even just sending an email to make sure everyone sees it 14:59:01 wendyreid: We'll make sure there are approvals on the PR 14:59:15 gpellegrino: I'll post the PR and we can proceed from there. 14:59:25 wendyreid: AOB? 15:00:48 CharlesL has left #pmwg 15:03:37 rrsagent, draft minutes 15:03:39 I have made the request to generate https://www.w3.org/2023/11/03-pmwg-minutes.html ivan 15:18:23 Guest42 has joined #pmwg 21:00:55 Zakim has left #pmwg