13:50:41 RRSAgent has joined #pbgsc 13:50:45 logging to https://www.w3.org/2024/08/09-pbgsc-irc 13:50:58 zakim, start meeting 13:50:58 RRSAgent, make logs Public 13:51:00 Meeting: Publishing Steering Committee 13:51:15 date: 2024-08-09 13:51:31 rrsagent, draft minutes 13:51:32 I have made the request to generate https://www.w3.org/2024/08/09-pbgsc-minutes.html ivan 13:52:04 rrsagent, set logs public 13:59:25 present+ 13:59:36 present+ wolfgang, avneesh 13:59:55 present+ graham 14:00:08 present+ george 14:00:30 AvneeshSingh has joined #pbgsc 14:00:34 present+ shinya 14:00:37 present+ 14:00:59 shiestyle has joined #pbgsc 14:01:05 present+ liisa 14:01:15 George has joined #pbgsc 14:01:18 present+ wolfgang 14:01:23 present+ rickj 14:01:32 present+ 14:01:33 liisamk has joined #pbgsc 14:01:39 present+ 14:01:51 present+ 14:02:30 present+ billk 14:02:54 rickj has joined #pbgsc 14:03:03 present+ 14:03:05 Bill_Kasdorf has joined #pbgsc 14:03:43 present+ 14:03:53 scribe+ 14:04:17 Not knowing who is chairing or who scribed recently, I propose shiestyle 14:04:42 chair: Graham 14:04:48 present+ 14:05:19 agenda: https://lists.w3.org/Archives/Public/public-publishing-sc/2024Aug/0002.html 14:05:23 zakim, who's on the call? 14:05:23 Present: ivan, wolfgang, avneesh, graham, george, shinya, AvneeshSingh, liisa, rickj, shiestyle, liisamk, billk, Ralph, Bill_Kasdorf 14:05:41 regrets: Cristina, Wendy 14:05:48 regrets+ Daihei 14:06:05 regrets+ Leslie 14:06:20 topic: End of support for XHTML – ramifications for EPUB? 14:06:29 Graham: this came up in conversations 14:06:42 q+ 14:06:42 ... this isn't an urgent issue; it's been the case for several years 14:06:49 q+ 14:06:58 ... does anyone want to suggest there will - or won't - be repercussions? 14:07:24 a+ 14:07:26 q+ 14:07:37 Bill: I've thought that when we said content documents in XHTML we were not talking about the old XHTML spec but rather whatever the current version of HTML is 14:07:40 ... is that correct? 14:07:43 Ivan: that is correct 14:08:07 Graham: I took a Quick Look and it is generally characterized as "the XML form of HTML" 14:08:26 s/Quick Look/Quick Look/ 14:08:41 Bill: I don't understand what it means for W3C to "support" XHTML 14:08:48 Graham: I think the phrase is "maintain" 14:09:00 Ivan: it doesn't mean anything if you think of HTML as a collection of tags 14:09:03 ... there is no difference 14:09:13 ... the big difference comes in when you do scripting 14:09:32 ... if a file has a declaration that it is XML there are subtle differences in the way scripts work 14:09:44 ... off the top of my head I don't recall the differences 14:10:13 ... so what it means, if you look at the HTML spec today, the percentage of the tag-related definitions is lower than the percentage of API-related specifications 14:10:42 ... "maintaining" XHTML means that in all those API descriptions there are some things said "if this is XML then ..." 14:11:10 ... stopping this dualism is what I think we are talking about; the XML part will not be updated for new APIs or changes in APIs 14:11:54 ... this means that if you develop an EPUB and want to add a script that you want to reuse from somewhere else then as long as you are in HTML you can reasonably rely on them but if you are in XHTML you have to be very careful 14:12:09 ... so it's an issue for any EPUB with scripts, no matter how small 14:12:18 ... caveat all this that I'm not an HTML person 14:12:29 ... the EPUB WG discussed this many times 14:12:52 ... what it means if we allow HTML in EPUB 14:13:03 ... most of the RS probably work out of the box, especially the newer ones 14:13:18 ... Brady had commented that most of the newer EPUB systems are based on webview 14:13:51 ... it's a layer around the internal systems that are prepared for both XHTML and HTML 14:14:03 ... so it's not a big deal for most of the systems built around those 14:14:15 ... I don't know how many RS there might be that don't handle HTML 14:14:46 q+ 14:15:01 ... the WG shied away from considering these consequences as we don't know how many [old] RSs might be impacted 14:15:25 ... also knowing that there are still some publishers using EPUB2 14:15:45 q- 14:15:45 present+ Leslie 14:15:50 regrets- Leslie 14:16:10 ... many of the processing chains still are based on XHTML 14:16:29 q+ to suggest that this is part of discussion of advancing EPUB at TPAC 14:16:31 ack Bill_Kasdorf 14:16:34 ack ivan 14:16:36 ... whether it's time to look at EPUB again, I'm not sure 14:16:38 ack rickj 14:17:02 Rick: our experience looking at this as an RS, the arbitrary presence of closing tags (whether they are there or not) is what causes the most problem 14:17:19 ... arbitrary places in toolsets would break when closing tags are omitted 14:17:25 ... it's not clear when and where they would break 14:17:32 +1 to rickj for concerns about not properly closing tags 14:17:49 Graham: we don't know the impact on toolsets but it sounds like the impact on RS should be minor 14:17:59 q+ 14:18:07 ... it certainly should be called out at some future point; we don't want people to be surprised 14:18:12 ... what should we do to prepare? 14:18:14 q+ 14:18:19 q+ 14:18:20 ack tzviya 14:18:20 tzviya, you wanted to suggest that this is part of discussion of advancing EPUB at TPAC 14:18:21 Tzviya: this is part of a much larger conversation 14:18:49 ... this can be part of our TPAC discussion 14:19:01 ... understand the appetite from the business perspective 14:19:07 q? 14:19:10 present+ Tzviya 14:19:18 ... touching all points of the supply chain 14:19:30 ... appetite from the developer, business, and RS perspectives 14:19:41 ... if closing tags are the issue, maybe that's solved by Epubcheck 14:19:53 ... there are many points in the supply change that this affects 14:20:01 ack ivan 14:20:05 ... and this group can help understand the appetite for change 14:20:19 Ivan: is epubcheck prepared for non-XML HTML? 14:20:20 q+ 14:20:38 ... if epubcheck is based on an XML parser then we have a problem 14:21:09 Avneesh: we had plans to build epubcheck on the nuHTML validatore 14:21:13 s/tore/tor 14:21:26 ack liisamk 14:21:28 ... so it doesn't support non-XML at this time but it can be improved 14:21:32 ack AvneeshSingh 14:21:41 Liisa: we need to be mindful that everyone everywhere it touching their EPUBs now 14:21:53 ... if we want to start down this path we need to give them the information now 14:22:01 q+ 14:22:05 ... I don't want to have to fix thousands of EPUBs twice 14:22:41 q+ 14:22:42 Graham: that's right; we need to give as much notice as possible to everyone in the supply chain 14:22:55 ... particularly to publishers who may have to deal with hundreds of thousands of files 14:23:12 ... should this go on in the HTML venue? 14:23:25 ... in this venue we should prepare people 14:23:34 George: yes, prepare 14:23:44 Bill: it's the Maintenance WG that is responsible for any changes 14:24:04 ... can we revise the spec to say it uses the HTML markup but closing tags are required? 14:24:08 q+ 14:24:11 Ivan: I don't think that would work 14:24:13 ack Bill_Kasdorf 14:24:36 ... in the past there were documents about doing things that are both XHTML and HTML compatible 14:24:42 Tzviya: "polyglot" 14:24:50 Ivan: yes, but that didn't really progress 14:25:10 ... but it should not be that bad; books produced in XHTML today and that work and are OK should be OK in the new world as well 14:25:24 ... should require no change to existing books 14:25:45 ... but in the future there could be the possibility to use tools for new books that you can't use now 14:26:00 ... I think the biggest problem is the tools between the publishers and vendors 14:26:07 ... all the tools that today rely on XML 14:26:25 q- 14:26:31 q? 14:26:38 ack ivan 14:26:39 +1 to Tzviya for leaving the technical discussion to the WG 14:26:42 ack AvneeshSingh 14:26:43 Avneesh: this is on the agenda for Anaheim, under "EPUB Next" 14:26:51 topic: Distribution of W3C survey to publishers and others in the publishing supply chain) 14:27:08 Graham: just noting that we should distribute this to as many as possible 14:27:15 ... both W3C Members and non-Members 14:27:33 ... we should pass this on to all of our contacts who may be able to provide useful answers 14:27:38 q+ 14:27:55 George: there's a link for Members and a link for non-Members 14:28:07 ... is it intended for AC Reps? 14:28:14 q+ 14:28:31 ... would I fill out the Member or non-Member version? 14:28:50 Ralph: I understand the expectation to be that anyone affiliated with a Member should use the Member version 14:29:13 ack liisamk 14:29:15 Liisa: is W3C looking for multiple answers from a single organization? 14:29:25 q- 14:29:26 Tzviya: yes; the goal is to get as many individual answers as possible 14:29:31 -> survey references https://www.w3.org/news/2024/w3c-opens-community-wide-survey/ 14:30:20 topic: TPAC plans 14:30:35 Graham: we've already mentioned XHTML/HTML 14:30:40 q+ 14:30:43 ... anything else this group should be doing? 14:31:01 Tzviya: the WG has finalized its agenda; it's in Github 14:31:12 https://github.com/w3c/pm-wg/issues/5#issuecomment-2258541132 14:31:14 ... the timing is rough; the breaks have not yet been added 14:31:26 q+ 14:31:39 ... the XHTML discussion might be moved earlier 14:31:46 ... "substantial changes to EPUB" 14:32:10 ack tzviya 14:32:32 Leslie has joined #pbgsc 14:32:43 Ivan: anyone is welcome to observe any of the TPAC group meetings 14:32:55 ... the a11y meetings might be of interest to most here 14:33:22 ... Wednesday is usually a hectic day; it's a lot of hour-long sessions where many ideas are talked about 14:33:45 ... it would be important for folk from the publishing community would make their voices heard 14:33:55 Graham: who from this group is likely to be there? 14:34:06 virtually, but not physically 14:34:12 Rick: I will be there 14:34:27 Ivan: if you want to come even if you're not in a Member company we can still invite you 14:35:25 Graham: so anyone who wants to attend virtually can ask for an invite? 14:35:27 Ralph: yes 14:35:41 topic: Update on relationship between IDPF and W3C 14:35:52 Rick: the IDPF still lives, to make sure W3C has a license for EPUB 14:36:02 ... financially we can continue 14:36:13 ... though logistically it gets difficult far into the future 14:36:29 ... we'll be talking with Seth about how we can complete the original plan 14:36:35 q+ 14:36:44 q- later 14:36:46 ... the goal is to find a way out of the awkward situation we're currently in 14:36:53 ack George 14:37:21 George: Leslie will need to be notified to pay the insurance premium 14:37:46 Leslie: I usually start the process in October 14:38:42 ... when I find out the total expense I send an invoice to W3C; this happens end of November 14:39:05 Ivan: a question came up last week: at the moment the IDPF web site is frozen 14:39:20 ... there is some errata that should be merged 14:39:27 ... on the a11y spec 14:39:38 ... I don't know if this is possible 14:39:54 Leslie: W3C has all the information 14:39:55 q+ 14:40:16 ack ivan 14:40:29 q- 14:41:02 q+ 14:41:16 ack Ralph 14:41:38 Ralph: W3C has all the bits and serves from our servers 14:41:58 ... technically we can make changes but we want to limit what is change 14:43:18 ... happy to have someone collect in Github a wish list of updates you'd like 14:44:22 q+ 14:44:54 Ralph: has the decision been formalized sufficiently that this steering committee includes all of the IDPF Board as well as the W3C group chairs? 14:45:19 George: Mike Baker hasn't been added to the distribution; he's been hard to reach 14:45:33 Graham: I believe everyone else is on the distribution 14:46:19 q? 14:46:27 ack liisamk 14:47:03 Bill: is it clear that we're saying the Steering Committee consists of the members of those two groups or _includes_ the members of those two groups 14:47:13 ... can others be part of the Steering Committee? 14:47:31 Graham: I suspect it might be "includes" 14:48:48 Ralph: let's figure that out when we know who might be impacted 14:49:35 Graham: let's say the Steering Committee is composed of the IDPF Board and the W3C WG Chairs with the possibility of invited guests 14:49:49 Avneesh: our practice has been to invite people 14:50:01 ... not that they simply join 14:51:41 topic: Lunch and Learn webinars 14:51:42 Yes, looks fantastic! 14:51:55 Graham: this is a proposal from Leslie and Liisa 14:52:29 ... for a set of Eastern US lunch time seminars on subjects of interest to this group 14:52:36 ... presented by BISG 14:52:43 Liisa: co-branded by BISG and W3C 14:53:05 ... Leslie and I have been talking with Brian @BISG for a couple of months about doing a monthly co-branded workshop series 14:53:32 ... getting into concrete examples of implementation, pros and cons of different types of implementation 14:53:45 ... showing examples, talking about marketplace status, and open discussion 14:53:50 ... trying to bring in a few experts 14:53:55 ... encouraging open conversation 14:54:10 q+ 14:54:20 ... the goal is to find a way on a local basis to replace some of what we've been missing with getting people in conversation 14:54:35 ... we've been talking about starting as early as September 14:54:39 ... AI and TDM 14:55:08 ... a11y and metadata; how we're hearing how this plays out in the marketplace, with ONYX and all 14:55:32 ... short alt text, descriptions, automation that can be done and possible AI opportunities, frontlist and backlist 14:55:57 ... page layout; how the original page anchor has changed in the metadata -- there have been many conversations and misunderstandings here 14:56:02 ... mixed layout 14:56:04 ... audio spec 14:56:14 ... if this all works, then figure out where the next generation goes 14:56:29 Leslie: our opportunity niche is in sharing of best practices and examples 14:56:48 q+ to invite Dave Cramer and Rachel C 14:56:57 ... it's annoying to hear the same high-level questions and getting pitches from vendors; we want to focus on the nitty-gritty 14:57:06 ... Brian is open to engaging in something along these lines 14:57:16 ... he's not yet seen this document as fully elaborated 14:57:25 ... we wanted to get your input and then take it to him 14:57:42 q+ 14:57:49 ... we might try to replicate this with other local people 14:57:56 Graham: we have something like this in the UK 14:58:11 ... a series of lunches for several years that often include this sort of event 14:58:21 ... I've provided a couple of comments to Liisa and Leslie 14:58:51 q? 14:58:53 ... it's an evolving document and discussion with BISG; what are your expectations? 14:59:04 Liisa: we're looking [to share it with Brian] sometime in the next week 14:59:08 very good initiative 14:59:23 agreed... I support this. Looks great! 14:59:29 Bill: this looks fantastic; it's well fleshed-out, kudos to Liisa and Leslie 14:59:45 ... it would be important that these be recorded; they will be useful references 15:00:00 ... in which case, who owns those recordings? BISG, W3C, or both? 15:00:24 ... it would be a good idea to set up a formal review schedule, particularly if they are recorded and there are material changes that would prompt an update 15:00:31 ... a systematic way to catch those 15:00:37 tzviya, you wanted to invite Dave Cramer and Rachel C 15:01:05 Tzviya: Rachel and Dave would be great experts to include; they've been very involved in W3C 15:01:09 ... but you know these people! 15:01:30 Liisa: thanks; we're trying to figure out how to get a variety of good examples 15:01:34 ... there's not just one answer 15:02:13 BISG does normally record these, and they appear on the BISG Youtube channel 15:02:32 q? 15:02:45 ack Ralph 15:02:49 Ralph: also kudos 15:03:03 ... please make sure the W3C Comm Team is aware of this and how W3C is being referred-to 15:03:17 George: there's overlap with another monthly series 15:03:21 ... that's fine 15:03:35 ... it would be good to keep a list of reputable resources 15:03:43 ... there's some bad information getting out there 15:03:50 ... it would be great to have authoritative information out there 15:03:52 +1 to George 15:04:01 ... well-vetted 15:04:18 Graham: thanks all 15:04:31 ... see you in a month or so 15:04:33 [adjourned] 15:04:38 As of this point the attendees have been ivan, wolfgang, avneesh, graham, george, shinya, AvneeshSingh, liisa, rickj, shiestyle, liisamk, billk, Ralph, Bill_Kasdorf, Leslie, Tzviya 15:04:40 RRSAgent, please draft minutes v2 15:04:42 I have made the request to generate https://www.w3.org/2024/08/09-pbgsc-minutes.html Zakim 15:04:48 I am happy to have been of service, Ralph; please remember to excuse RRSAgent. Goodbye 15:04:48 Zakim has left #pbgsc 15:05:45 rrsagent, bye 15:05:45 I see no action items