08:57:58 RRSAgent has joined #pmwg 08:58:02 logging to https://www.w3.org/2025/04/03-pmwg-irc 08:58:02 RRSAgent, make logs Public 08:58:03 Meeting: Publishing Maintenance Working Group 08:58:03 ivan has changed the topic to: Meeting Agenda 2025-04-03: https://docs.google.com/document/d/1SePiVZDlyWNg5nhqBffCXSh7_EGC5IXPz9nTd8i1sdw/edit?tab=t.dbiebco88mfi#heading=h.gouartxyduig 08:58:04 Chair: wendy, shinya 08:58:04 Agenda: https://docs.google.com/document/d/1SePiVZDlyWNg5nhqBffCXSh7_EGC5IXPz9nTd8i1sdw/edit?tab=t.dbiebco88mfi#heading=h.gouartxyduig 08:58:04 Meeting: PM Working Group F2F, Sophia Antipolis, 1st Day 08:58:05 present+ 08:58:13 q+ 08:58:13 present+ 08:58:15 q- 08:58:19 present+ dhall 08:58:20 present+ 08:58:27 present+ wendyreid 08:58:36 present+ 08:59:17 rdeltour has joined #pmwg 08:59:47 George has joined #pmwg 09:00:15 present+ 09:00:35 scribe+ 09:00:39 gpellegrino has joined #pmwg 09:00:41 MasakazuKitahara has joined #pmwg 09:00:54 present+ 09:00:54 present+ 09:00:59 present+ 09:01:14 preent+ makoto 09:01:30 Hadrien has joined #pmwg 09:01:45 wendyreid: Welcome the first f2f of the NEW pmwg 09:01:47 present + 09:01:58 https://github.com/w3c/pm-wg/blob/main/meetings/F2FMeetingFrance2025.md 09:02:09 George has joined #pmwg 09:02:10 ... Quick agenda overview, no real change except the times 09:02:49 ... start with comics, mostly focusing on the overall topic. Not really a tech conversion which will be tomorrow 09:02:50 LaurentLM has joined #pmwg 09:02:54 ikkwong has joined #pmwg 09:03:00 present+ 09:03:08 present+ 09:03:40 ... (see agenda for details) 09:03:58 ... no buffer for today, so we may have carryover into tomorrow 09:04:06 ... Questions? 09:04:09 George has joined #pmwg 09:04:25 Makoto: When will we discuss ISO? 09:05:19 wendyreid: I don't think we will discuss, we are waiting for feedback and reaching out to some folks 09:05:31 Topic: Digital Comics 09:05:49 gautier has joined #pmwg 09:06:04 present+ 09:06:06 shiestyle: I have a presentation for this. We have already had our first TF meeting last month 09:06:24 Hadrien: Just to clarify, we shouldn't be touching on tech stuff? 09:06:27 George has joined #pmwg 09:06:54 present+ susan 09:06:58 wendyreid: Yes, tech is fine but we should be more on the general side, tomorrow will be better for tech (more participants) 09:07:37 shiestyle: In Japan we already use epub for scrolled comics 09:08:02 ... We have two approaches both are being used 09:08:17 ... There is also a new proposal from Hadrien 09:08:44 Hadrien: ust to clarify, I am just proposing 'scrolled' to replace the existing methods 09:09:11 shiestyle: We agreed that this is a new feature 09:09:30 s/ust/just/ 09:09:38 ... so the charter is updated for new features 09:09:55 ... We still have no conclusion to the method 09:10:11 ... Some proposals, first Hadrien's proposal 09:10:11 q+ 09:11:07 ... second proposal is a new proposal that keeps pre-paginated but adds new metadata 09:11:21 q+ 09:11:23 ack Hadrien 09:11:31 Hadrien: What are we trying to achieve? 09:11:56 ... 2 things - we are trying fit on width 09:12:05 ... and the other is continuous scrolling 09:12:31 q+ 09:12:31 ... Scrolling exists, but it is really a hint so it is different than what we want 09:12:52 ... pre-paginated doesn't do what we want, flow doesn't fit 09:13:10 Avneesh has joined #pmwg 09:13:12 ... This is a new type of publication 09:13:14 q+ 09:13:26 ... for instance it doesn't even have pages to pre-paginated is weird 09:13:40 ... Since it is a new type, layout makes sense 09:14:22 wendyreid has joined #pmwg 09:14:29 q? 09:14:33 ... We could alias pre-paginated and scrolled to mean webtoons 09:14:41 ... I think a new type makes sense 09:14:42 q+ 09:14:46 ack ivan 09:14:54 ivan: I do not disagree 09:15:03 ... my question is actual practice 09:15:15 ... do we have feedback from Amazon and Apple 09:15:19 q+ 09:15:23 ... will they adopt the new approach 09:15:26 ... ? 09:15:58 ... Are they flexible enough to switch? 09:16:07 Hadrien: This happened with fixed layout 09:16:12 ack wendyreid 09:16:14 q+ 09:16:40 wendyreid: I agree, but I also wonder to take a step back we have an underlying problem in fixed layout 09:17:14 ... Since webtoons is chapter based, this exposes a problem. This content is very chapter based 09:17:25 sue-neu has joined #pmwg 09:17:33 present+ 09:17:50 ... for instance, rendition flow breaks because we don't really have chapters in pre-paginated 09:18:14 ... What if we keep things as they are currently implemented and add better chapter breaks 09:18:31 ... How are these actually created? One file er chapter? or per image? 09:18:39 s/present+ susan// 09:18:42 Hadrien: One file per chapter 09:19:21 ack shiestyle 09:19:21 ... It could be used for selling full seasons 09:19:55 shiestyle: Regarding epub structure, webtoons and manga are all the same structure except the metadata 09:20:02 Makoto has joined #pmwg 09:20:13 +present 09:20:14 ack duga 09:20:16 scribe+ 09:20:18 ... we don't use very long images, so as a result the structure is the same 09:20:47 duga: I was hoping we'd learn more about what is actually being sold on the various platforms. It's hard to think of a technical solution without knowing the business specifics 09:20:58 ... it is a single book, are there collections, will there be collections? 09:21:12 ... what is the problem we're solving, what are people selling, what do people want to sell? 09:21:33 ... it would help to have real cases or an actual webtoon file 09:21:37 ... do we have examples? 09:21:44 ... where is the industry right now? 09:22:18 Hadrien: It's a complex question, complex market 09:22:20 q+ 09:22:35 q+ seth 09:22:43 ack seth 09:23:05 ack LaurentLM 09:23:09 seth: Is each episode just one image? Are the images huge? 09:23:52 q+ 09:23:56 LaurentLM: The people around the table have the freedom to change 09:24:36 ack ivan 09:24:37 ... Can we take a new value? Yes, we can add a note and explain that there are other implementations that should be considered aliases? 09:24:58 ivan: So do we have any chance to pass the CR criteria? 09:25:08 ack dhall 09:25:15 Hadrien: Yes, no problem, I am aware of multiple presentations 09:25:59 dhall: We would continue to support for now, can't discuss future 09:26:00 ack Hadrien 09:26:17 ... And agree that fit width is important and we need to be able to specify it 09:26:37 Hadrien: No one today produces episodes as a single image, largely for performance 09:26:56 ... no one really divides things on semantic boundaries, they are arbitrarily split 09:26:58 q+ 09:27:15 ... it is meant to be displayed as a single image, so these are really just tiles 09:27:50 ... Also want to point out that html is not really used to display this 09:27:53 delackner has joined #pmwg 09:28:08 ... Everyone uses images outside of Apple (not sure about Amazon) 09:28:20 q+ 09:28:35 ... Back to market question, mostly done in specialized readers 09:29:11 ... Mostly this is done by free with ads, or perhaps subscriptions, sometimes there is microtransactions 09:29:17 ... much more like games 09:29:27 ... Mostly this is done in those apps, not epub readers 09:29:41 q+ 09:30:01 q+ 09:30:06 ... These apps are designed around the model (calendars for upcoming, package purchases, etc) 09:30:13 present+ delackner 09:30:16 ... almost all done as individual episodes 09:30:19 q+ 09:30:44 Hadrien: usually is a giant file or zips of images 09:31:03 ... Most places use psd or zip, not epub 09:31:16 ... Korea is interesting as they are pushing to a national standard 09:31:27 ... they are adopting a Readium approach 09:31:45 ... they looked at epub, and thought it was too complex and had too many problems 09:32:06 ack shiestyle 09:32:09 ... so for their archiving work they are using zips 09:32:17 shiestyle: Regarding long images 09:32:32 ... some services accept long images, but these are not in epub 09:32:50 q+ 09:32:58 ... I strongly propose to not add a new value for rendition layout 09:33:18 ... we cannot move to the new system until everyone adopts the new values 09:33:52 ... In Japan we have a big market, but we cannot shift to the new standard due to compat issue 09:33:52 ack sue-neu 09:34:26 sue-neu: Does anyone know about the copyright? 09:34:40 wendyreid: Webtoons is ok, webtoon is not 09:34:44 You can say kleenexes but not kleenex? 09:34:51 ack ivan 09:35:16 q+ 09:35:19 ivan: Why are we doing this? Why not just leave the specialized apps to do it? 09:35:33 ack delackner 09:35:33 ... we seem to be pushing ourselves on people that don't want it 09:35:56 seth: I wanted to ask about the Korean model 09:36:00 gautier has joined #pmwg 09:36:35 ... We have html for a111y, voiceover, etc 09:36:45 s/a111y/a11y/ 09:36:48 ... that is the push to have epub wrap this 09:37:09 ... does the Korean format have an a11y answer? 09:37:47 Hadrien: We are looking at it, it has more of a media overlay flavor 09:38:08 q? 09:38:25 ... We really want to have the text become accessible 09:38:28 ack duga 09:38:46 duga: I've had Ivan's question too 09:38:52 ... we're doing it because people have asked us to 09:39:03 ... EPUB may not be the right format, but some people want to do it that way anyway 09:39:10 ... and we can let them, we can make it work 09:39:34 ... if I were to start a company doing webtoons today, I wouldn't use EPUB, but if they wanted to, I could make it work 09:40:05 ... even manga was a zip archive of images, there was a push to using EPUB, we ended up supporting it because its nice to have metadata 09:40:34 ... issues with pages being wrong order, EPUB fixes that with metadata, it is nice, there are uses 09:40:46 ack wendyreid 09:41:29 wendyreid: The feedback we have gotten is some publishers might want bug collections 09:41:48 ... I agree that if people want it let's help them 09:42:20 ... this group also supports other formats like publication manifest, which might be a more flexible format 09:43:08 ... we need to be responsive to industry need, and we don't need to be stuck in just epub 09:43:09 q+ 09:43:48 ... for instance webtoons have terrible a11y, and it would be great to make this better 09:44:07 ack Hadrien 09:44:12 ivan: I checked the charter, we can update the publication manifest 09:44:27 s/bug/to sell big/ 09:44:49 Hadrien: This is broader and goes into digital comics entirely 09:45:17 ... We should keep in mind, this one distribution channel is not the only one we should consider 09:45:33 ... e.g. libraries making collections 09:45:48 ... And there is also the case of storefronts that might want to sell them 09:46:02 ... You can't really separate the business models from the technical 09:46:06 sue-neu has joined #pmwg 09:46:12 ... back to zip vs epub 09:46:15 present+ 09:46:22 present+ 09:46:32 .... what Korea said was metadata was bad for archival in epub 09:46:52 ... for instance, spread placement isn't a big issue for webtoons 09:47:03 q+ 09:47:16 ... we need to look at what works and what doesn't 09:47:42 ... and I think the most problematic is forcing images into an html wrapper 09:48:12 ... I don't think this just solves the a11y problem. We have a lot of inaccessible xhtml content out there today 09:48:16 q+ 09:48:25 ... we really need to focus on what does and does not work 09:48:27 zakim, close the queue 09:48:27 ok, wendyreid, the speaker queue is closed 09:48:49 ... for a11y we need to focus on specific use cases 09:48:52 ack Avneesh 09:49:27 Avneesh: I am a little alarmed about Korea taking readium manifest, I am concerned about Korea going to ISO quickly 09:49:32 q+ 09:49:38 ack ivan 09:49:43 ... I think it is a problem if we are against the Korean national standard 09:49:49 mgarrish has joined #pmwg 09:50:07 ivan: 2 things - first according to the Koreans epub MD is not good for archival 09:50:14 ... This is something we should address 09:50:41 ... the other is, what is wrong with saying we can put images in the spine with an xhtml fallback? 09:51:07 ack sue 09:51:20 ... but the xhtml fallback isn't the image it is just alt 09:51:43 sue-neu: I have clients looking this as parts of courseware, say for a history book 09:51:56 wendyreid: We will continue this tomorrow 09:52:38 Topic: Accessibility TF 09:52:57 zakim, open the queue 09:52:57 ok, wendyreid, the speaker queue is open 09:53:19 Avneesh: We didn't have time to plan for the a11y TF 09:53:24 https://github.com/w3c/publ-a11y/wiki/PMWG-Accessibility-TF-Topics 09:53:29 ... so we thought we could use this meeting for that 09:53:49 ... so we have a wiki with a list of topics 09:54:46 ... we have strong demand from APA for wcag version 09:54:56 ... then there are some issues from the cg 09:55:16 ... for instance metadata to say text/audio mix 09:55:36 ... then we have a11y md that is missing, for instance no publisher contact info 09:55:58 ... Then with AI we have to know if TTS is AI or human based 09:55:59 CharlesL has joined #pmwg 09:56:12 present+ 09:56:22 ... Then we have to define skippability and escapability 09:56:37 ... Some liason work 09:56:51 q+ 09:56:51 ... any comments? 09:57:16 I had a teleconference with AGWG people including people from the team about the lack of support of non-western languages in WCAG 2.2. People are inclined to create WCAG 2.3 as a solution but I am not sure if AGWG reaches cosensus. 09:57:33 ivan: We should not forget to officially issue a new a11y guidelines with the proper version. We need wg consensus 09:57:45 Avneesh: Yes, let's do that tomorrow 09:57:50 ... now harder topics 09:58:15 q+ 09:58:16 ... we maintain a mapping to EAA 09:58:18 ack ivan 09:58:21 wendyreid 09:58:23 ack ivan 09:58:28 ack wendyreid 09:58:31 ... do we need to add anything to that? 09:59:01 wendyreid: One thing I hear a lot is parts of wcag like image desc where publishers have trouble doing it in the context of books 09:59:18 q+ 09:59:36 ... Wcag doesn't seem to make sense to them, that is mapping web/app descriptions to book descriptions (what to say, how to integrate, etc) 09:59:42 sue-neu has joined #pmwg 09:59:46 .... may be related to footnote work 09:59:58 ... maybe we need some guidelines 10:00:32 q? 10:00:41 ack gpellegrino 10:00:41 ack gpe 10:00:42 q+ 10:00:42 Avneesh: Yes we should discuss, and yes footnotes is similar 10:01:34 gpellegrino: Mybe we need something like an index page to link to everything we provide 10:01:42 ... it is hard to find all the documents we have 10:01:57 +1 10:01:59 q? 10:02:03 ack George 10:02:18 George: I agree there is a lot going on in different places, and I am often confused about where the right place to take issues is 10:03:04 ... For instance back links to a footnote, but if the reading system had go back it wouldn't be needed 10:03:19 ... it is determines how things might be referenced 10:03:37 ... for instance a glossary term that is pointed at 3 times, a back link doesn't work 10:03:54 ... so who addresses these? Us? CG? somewhere else? 10:04:23 wendyreid: I think the CG is usually right, but sometimes it is us 10:04:54 Avneesh: EAA and title 2 - anything else we need to do to support this? 10:05:27 ... and then there is dpub aria 10:05:35 gautier has joined #pmwg 10:05:35 ... Matt is the liason 10:05:51 q+ 10:06:02 ... It has strong use cases and long consistent systems for implementing 10:06:12 ack Hadrien 10:06:14 .... if we want some new roles we have to do it now 10:06:36 Hadrien: On Readium we plan to improve read aloud, the other readability 10:06:50 q+ 10:06:59 ... we will have a lower level building block that supports dpub and dpub aria 10:07:28 ... This will help identify a11y behaviors 10:07:36 ... eg move where footnotes are read 10:08:05 ... We will use the dpub aria for read aloud, which hasn't been used yet. This will be a pretty open implementation 10:08:47 ... We will have multiple implementations, not sure if that counts as 2+ 10:08:55 ... this will be coming this summer 10:09:14 Avneesh: Jaws is supporting 50% of dpub aria coming up 10:09:20 q+ 10:09:27 ack gpellegrinoack gpellegrino 10:09:31 ... so screen reader are starting to support it 10:09:39 present+ CharlesL 10:09:51 q? 10:09:52 q+ 10:09:55 gpellegrino: we found out a while back that talkback on chrome supported all dpub aria roles. 10:09:58 ack gpellegrino 10:10:08 ... the browsers are there, there is still some discussion with Apple 10:10:26 ... I think the dpub aria roles are deeper than epub ones 10:10:55 ... We used to have epub types, then we had aria which lost some things 10:11:28 present+ mattg 10:11:41 ... In many cases these roles are important for the production workflows not just end user 10:11:43 present+ rdeltour 10:11:56 ack CharlesL 10:12:01 ... There is a request to add common ways to identify certain items in there books 10:12:40 q+ 10:12:41 present+ MasakazuKitahara 10:12:53 present+ toshiakikoike 10:13:05 CharlesL: couple things, on title 2 we have heard that the dept of special ed still exists 10:13:08 q+ 10:13:32 ... but there has been a de-emphasis on title 2, unlikely for justice dept to start filling lawsuits on day 1 10:13:38 ... but individuals still can 10:14:13 ... on dpub aria, one thing we may want to require is digital only publications for page breaks (some publishers having issues with that) 10:14:34 ... there is a dpub aria role for it, in our tests everyone handles it differently 10:15:15 ... Then there is the question if it is in code only but doesn't appear 10:15:23 ... or it appears and has more words, etc 10:15:36 ... that can be problematic for AT 10:15:56 ack wendyreid 10:16:37 wendyreid: dpub aria is similar to footnotes, needs best practices 10:16:50 ... so we need expected behavior when we see it 10:16:57 s/present+ mattg// 10:17:06 present+ mgarrish 10:17:17 ... page breaks is similar to footnotes on when and how to read 10:17:31 ... Then there is FL with dpub aria 10:17:48 ... Not every page is a chapter so you can't add it to every files 10:18:13 q+ 10:18:13 ack George 10:18:20 ... Need to see where the gaps are 10:18:57 George: Excercises are important, it would be good to address the issues of how to do exercises and workbooks 10:19:11 ... Publishers will move the epub into an LMS 10:19:29 ack mgarrish 10:19:35 ... so it would be great to address exercises and workbook completions in an epub 10:20:01 mgarrish: We have had problems with roles, and too much verbosity 10:20:26 ... so we can't just keep throwing in new roles 10:21:08 ... For work on 1.2 Tviya works with me, but we will need a new person to help with editing that spec 10:21:15 ack Hadrien 10:21:18 ... because we can't have just one 10:21:31 Hadrien: There was also the structural semantic vocab 10:21:57 ... in readium we primarily target dpub aria, but we have other properties we are pulling in 10:22:08 ... Also aria, which isn't used much in epub 10:22:16 ... So we are agnostic and pull in all 3 10:23:00 ... we have to take into account everything 10:23:03 q? 10:23:50 Avneesh: There are some things we will bring to the TF, not sure if the topic George raised can really be handled there 10:24:07 ... We already keep a list of actionable aria roles 10:24:31 ... It is missing some details (e.g. footnotes go back), but the high level is there 10:24:43 gpellegrino: And we have a test book that has every role 10:25:07 George: And we have a published book with all the dpub aria roles we can support 10:25:23 present+ 10:28:44 ikkwong has joined #pmwg 11:52:56 dhall has joined #pmwg 11:58:19 wendyreid has joined #pmwg 11:59:48 rdeltour has joined #pmwg 12:01:36 gautierchomel has joined #pmwg 12:03:29 scribe+ 12:04:16 wendyreid: we're now speaking about annotations 12:04:46 present+ 12:04:49 sue-neu has joined #pmwg 12:04:50 Avneesh has joined #pmwg 12:04:56 p+ 12:05:09 laurent: I'm going to share some slides 12:05:29 ... today I would like to discuss an agenda of work, not to discuss the single items 12:05:52 ... we would like to start about discussing the incentives for TF participants 12:06:07 ... use cases, business cases, etc. 12:06:21 ... then discuss for annotations, bookmarks, annotations 12:06:53 ... then discuss the scope of the project (embedding, rest protocol, etc.) 12:07:13 ... find existing apps that are already exporting annotations 12:07:47 shiestyle has joined #pmwg 12:07:48 ... check to look at the data model available: W3C Annotation Model, Readium Annotation Model 12:08:04 ... to find differences, and common elements 12:08:39 s/p+// 12:08:55 q? 12:08:56 laurent: so we'll start with the incentives for the participants, what are the market requests 12:09:02 Topic: Annotations 12:09:05 present+ 12:09:32 is there anyone that wants to propose incentives? 12:09:40 q+ 12:09:44 ack mgarrish 12:10:10 present+ 12:10:11 mgarrish: we worked on open annotations years ago with edupub 12:10:22 ... it didn't work 12:10:30 q+ 12:10:42 ack ivan 12:10:44 q+ 12:10:58 ... I think you should clarify if it's for publishers to distribute them, or for users to share them across reading systems 12:11:25 ivan: I have here the list of people that wants to partecipate to the TF 12:12:11 laurent: I asked to ReadWise (?), I may ask to hypothes.is 12:12:37 George has joined #pmwg 12:13:02 present+ 12:13:17 ... because I don't have contacts, and their solution is based on URLs 12:13:32 ack wendyreid 12:13:34 q+ 12:13:40 ivan: I think also Matheus may want to partecipate 12:13:44 s/(?)/(readwise.io)/ 12:13:52 wendyreid: may you publish these slides? 12:14:06 laurent: sure 12:14:11 Participants as of now: Brady, Hadrien, Eloisa, Ivan, George, Laurent, Leonard, potentially Lars Wallin 12:14:19 q+ 12:14:21 q+ 12:14:39 wendyreid: about incentives: I think the focus should be on the readers, to allow them to share annotations and move them around 12:15:01 ... a lot of platforms allow to export annotations 12:15:23 George has joined #pmwg 12:15:26 ... I think it's also important to have educational publishers on the table, because it's relevant for them 12:15:40 ack Hadrien 12:15:42 laurent: these two use cases are quite different 12:15:54 Hadrien: I think focusing on the user is right 12:16:30 ... I think we should keep attention on two things: one is DRMs, the other is the possibility of make it work outside EPUBs 12:17:10 ... we should take one challenge at a time, focusing on endusers 12:17:32 ack ivan 12:17:39 ... when thinking about annotations I would ask: what about bookmarks? what about highlights? 12:17:49 q- 12:18:02 George has joined #pmwg 12:18:03 wendyreid has joined #pmwg 12:18:04 very old list of use cases: https://www.w3.org/TR/dpub-annotation-uc/ 12:18:08 q? 12:18:18 q+ 12:18:19 ivan: when I think to web annotation standard, I see it as an interchange format 12:18:42 ... meaning the standard doesn't say anything about UX of the enduser, it's all about sharing data 12:19:13 q+ 12:19:24 ack George 12:19:29 ... I think we should do the same here, not dictating what reading systems should do 12:19:40 duga has joined #pmwg 12:19:46 q+ 12:19:59 George: I think we should start discussing the difference between annotations and footnotes 12:20:29 ... annotations (like the annotated Alice in wonderland) that are provided by the publisher 12:20:34 q+ 12:20:55 ... while the ones made by users are totally different 12:20:57 present+ tzviya 12:21:18 ... there is also a use case for excersices in text books, the fill-in-the-blank is an annotation 12:21:19 ack duga 12:22:08 duga: I think that there is something we should carry on styling (like the color of the annotations) 12:22:31 q+ 12:22:52 ... about business cases: I think we may invent something really interesting, but we have to be sure that someone will implement it 12:22:55 ack wendyreid 12:23:10 laurent: we also have to find companies that may make money out of it 12:23:11 q+ 12:23:39 ... Readwise may have benefits from a standard for managing annotations 12:24:10 wendyreid: sure, there are some companies that have direct interest, but we also have "secondary market" 12:24:40 ... were companies may be interested in offering the export/import of annotations as part of their service 12:25:13 q+ 12:25:14 ... similarly this may help the switch from one ebook vendor to another (Kobo, Amazon, Apple, Google, etc.) 12:25:21 ack Hadrien 12:26:09 Hadrien: in Readium we'll implement this spec in our toolkit for desktop, mobile and web (Readium) 12:27:13 ... this interoperability will help the interoperability inside Readium ecosystem as weel 12:27:21 s/weel/well/ 12:28:03 ... we also have some statistics from Readium users, so we have some idea on how users manage annotations, exports, etc. 12:28:32 ack George 12:29:18 George: I see the business case for selling annotations, for example for receipts books 12:29:55 ... I think people would like also to be sure to be able to maintain bookmarks in their life, from one vendor to another... 12:30:09 ack ivan 12:30:23 q+ to say there are so many biz issues 12:30:53 ivan: do you have any relation with people working on legal replica? 12:31:06 ... in that business there is a lot of use on annotations 12:31:15 s/on/of/ 12:32:00 ... similarly if we look at specialized business, we may look at translations and multi-lingual content 12:32:17 q+ 12:32:19 ack tzviya 12:32:19 tzviya, you wanted to say there are so many biz issues 12:33:16 tzviya: I'm not sure if translations is a use cases, on the legal side I think we should discuss with someone who has specific knowledge 12:33:26 q+ 12:33:57 ... in particular if we rely on the original content, so IP issues may raise 12:34:11 ack gpellegrino 12:34:27 gpellegrino: I think there is a huge demand in the publishing industry 12:34:32 ... like working with vendors 12:34:46 ... providing feedback is tricky, you can't reference exact locations 12:34:54 +1 12:35:02 ... maybe vendors or conversion houses, may want to have part of this 12:35:16 q+ 12:35:28 ack duga 12:35:55 q+ 12:36:04 duga: will we be able to move annotations from one edition of the book to another? 12:36:19 laurent: it's part of the scope we have to discuss 12:36:30 q- 12:36:45 laurent: I think we should also discuss about annotations vs bookmarks vs citations 12:37:17 Another use-case EPUB certification annotate exactly where issues were found to give the feedback back to the publisher. 12:37:21 q+ 12:37:27 ... for us, for annotations we need: publication metadata, the document, the text selection, the textual note 12:38:03 ... for bookmarks: (similarly) publication metadata, the document, pointer (mark) 12:38:15 q+ 12:38:40 ... for people using assistive technologies is tricky to highlight text, so for them using bookmarks and adding notes to the bookmarks is simpler 12:38:56 ... so bookmarks and annotations are similar 12:39:05 q+ 12:39:21 ... for citations we need: publication metadata, page, text selection (quote) in a specific format 12:39:50 q+ 12:39:58 ... for use citations are not part of the model, are more an export format for annotations 12:40:04 is there consensus on this? 12:40:07 ack shiestyle 12:40:19 s/certification/certification & remediation 12:40:37 q+ to talk about citation 12:40:53 ack Hadrien 12:41:13 shiestyle: for use cases: how can it work for part of publications that are sold separately? (what is the relationship with the complete edition)? 12:41:57 Hadrien: for me the annotation is a text on top of a highlight, or on top of a bookmark 12:42:32 ... if we take this approach, we can make it working on other types of publications, like audiobooks (you mark a timestamp and you add text) 12:42:51 ikkwong has joined #pmwg 12:43:12 ... the problem with highlight is that is very related to text, while we need something that may work with multimedia as well 12:43:17 ack wendyreid 12:44:28 wendyreid: abstracting it, the user is selecting a fragment, attached to the publication metadata, has some form of locator and has some content attached 12:45:14 ... I think we have to find a way to identify selected fragments 12:45:54 ... on another side, more and more reading systems allow users to take hand written annotations 12:46:08 ... so the content attached may be images 12:46:43 ack ivan 12:46:58 q? 12:47:19 ivan: for me there is no difference between annotations and annotations 12:47:35 s/annotations/citations/ 12:48:01 ... the real difference is on how much metadata we have, for providing a high quality citation 12:49:31 ... while on the color side of highlights I think we should work on a higher level 12:49:47 ack George 12:49:57 q+ 12:49:57 ... not about colors, but based on categories, also for accessibility issues (e.g. color blind users) 12:50:30 q+ 12:50:31 George: I agree, we should add semantics to the annotations, to categorize them 12:50:38 ack tzviya 12:50:38 tzviya, you wanted to talk about citation 12:50:45 ... I think that audio annotations are also a thing 12:51:33 ack Hadrien 12:51:49 tzviya: I think we should allow the user to select if in copy-pasting content wants the citation references or not 12:52:11 Hadrien: I think we should be able to attach every type of multimedia to an annotation 12:52:54 ... about color related to annotations, I agree, at the same time I think that people are used to use different colors for different meanings 12:53:20 ... it's difficult to move end users from colors, to categories 12:53:43 q? 12:53:44 ack duga 12:54:02 q+ to color with meaning 12:54:30 q+ 12:54:40 ivan: about colors: my question is what do we want to specify at standard level, and what do we want to leave to implementers? 12:55:07 ack tzviya 12:55:07 tzviya, you wanted to color with meaning 12:55:13 ... I think we should split the information on how the information is displayed 12:55:43 tzviya: I think the GitHub approach is interesting: for labels we are colors + label (text) 12:56:09 ack wendyreid 12:56:18 q+ 12:57:15 ack Hadrien 12:57:24 wendyreid: I think it's more important to mention in the annotation exports that there are different types of annotations (e.g. different colors), more then focusing on colors 12:57:43 q+ 12:57:50 Hadrien: for interoperability I think we should have a set of values 12:57:52 q+ 12:58:18 ... that the user agents can use for tagging annotations 12:58:21 q+ 12:58:27 q- 12:58:38 ack ivan 12:58:52 ... I think we need a default way for managing the interoperability 12:59:32 ivan: we can define types of annotations, but leaving that other applications can define other types 13:00:00 q+ 13:00:01 ... in web annotations we have a similar field 13:00:36 laurent: moving to next slide, we want to check what is already available as standards 13:01:02 ... W3C annotation data model, is mainly for web, but can work in EPUB, using CFIs 13:01:48 marisa has joined #pmwg 13:01:50 ... Hypothes.is has their "standard" 13:02:26 ... kindle, apple, google, kobo have their own system for exporting and syncing annotations 13:02:46 zotero is important 13:03:09 ... readwise.io has CSV/markdown, can import and export to/from many apps 13:03:30 ... Zotero supports EPUBs and export annotations 13:03:50 ... Readium has an profile of W3C annotations 13:04:13 ivan: W3C annotations is actually 3 specs 13:04:43 q+ 13:05:21 ack ivan 13:05:25 ... the data model, the vocabulary, the protocol (for data platforms) 13:07:04 ack Hadrien 13:07:07 ... in the WPUB annotation group note we've worked on annotations that may go across different documents in the spine 13:07:35 q+ 13:07:58 Hadrien: there are a number of things that are referenced from that specs, one is the text fragment 13:07:59 https://wicg.github.io/scroll-to-text-fragment/ 13:08:39 ... my proposal is that what we decide to choose and selector, we should find something that works on web as well 13:08:41 ack ivan 13:09:10 +1 to work on the web. 13:09:16 ivan: I think we have to decision on the life of the CFI 13:09:28 q+ 13:09:47 ... do we want keep it alive, or to kill it? 13:10:32 https://docs.google.com/document/d/11GypOjE9xOTaINATl5bxVIA3Mc9jzNBGCr6GT_KNaQ4/edit?tab=t.0#heading=h.gbsmtjlkuon 13:10:34 ... we cannot avoid this discussion 13:10:42 ack wendyreid 13:10:55 ... it may not work with plain HTML (not XHTML) 13:11:19 wendyreid: we did a lot of these discussions in the virtual locators TF 13:11:27 q+ 13:11:52 ... we worked on "universal locators", interoperable across different reading systems 13:12:48 ... and interoperable across different editions of the same book (e.g. Mobydick) 13:13:04 ack Hadrien 13:13:40 Hadrien: on the web text fragments are quite good 13:13:54 ... the difficult part is creating a text fragment 13:14:17 ... browsers are able to do that, but they do not expose APIs 13:14:40 q+ 13:14:51 ack ivan 13:15:21 ivan: is there any WG in the W3C working on text fragments? 13:16:01 wendyreid: Web Incubator Community Group (WICG) 13:16:11 q+ 13:16:20 ack George 13:16:27 laurent: I think we should find something, like a polyfill in JS 13:17:00 George: maybe the accessibility object model (accessibility tree) may help 13:17:54 laurent: now an overview about W3C annotation spec 13:18:04 ... it's based on JSON-LD 13:18:40 ... without complex structure, just a @context attribute 13:19:12 ... it's very flexible and at the same type it's difficult to fully implement 13:19:49 ... the structure is simple: id, type, motivation (bookmarking, commenting, ...), creator, created, modified 13:20:15 ... a target (with id, type of sources and selector) 13:20:36 ... the selector may have multiple types (including FragmentSelector) 13:21:02 ... the body has an id, a type 13:21:35 laurent: in these last 10 minutes I would like to mention the mailing list address of the TF 13:21:55 q+ 13:22:06 ... it's group-pm-ann@w3.org 13:22:26 q- 13:22:33 ... we have to define the frequency of the calls 13:22:50 ... I would propose to start with a call every two weeks 13:23:04 ... I would organize every call around one of the slide we discussed 13:23:16 ... and find some consensus at the end of the call 13:27:06 some discussion about the best email list to use for task forces, not minuting :) 13:30:20 ivan: editorially how will we manage this spec? 13:30:41 will it be part of the main spec (or reading system spec) or will it be a separate specification? 13:31:23 ... in any case the logical place for storing the document we'll be the EPUB GitHub repository 13:32:28 laurent: I would like to create GitHub pages about the consensus we had, the history behind some decisions 13:32:42 ivan: we may use the wiki 13:33:50 Topic: Evolution of Media Overlays 13:34:01 present+ marisa 13:34:05 scribe+ 13:34:36 LaurentLM has joined #pmwg 13:34:40 present+ 13:36:07 marisa: sharing screen, showing notes in obsidian... 13:37:07 https://github.com/marisademeglio/epub-with-vtt/tree/main/epub-demo/book/EPUB 13:37:12 ... WebVTT is a way to sync points to timed media. Let's see a demo. 13:40:35 https://marisademeglio.github.io/epub-with-vtt/epub-demo/ 13:40:40 marisa: WebVTT is a timing audio + associated data including selector. To use it in EPUB we need to list them in the manifest. We can overload the overlay (SMIL and VTT) and let the reading system use the one he handles. 13:40:54 q? 13:44:49 q? 13:44:50 marisa: using VTT alows to set up custom CSS highlight. 13:44:58 LaurentLM has joined #pmwg 13:45:01 q+ 13:45:01 q+ 13:45:06 ack Hadrien 13:47:18 q+ 13:48:16 q+ 13:48:20 ack LaurentLM 13:48:23 Hadrien: a general comment, we've seen media overlay only used in fixed layout. Aside we see specialised librares (Nota, MTM) willing to use them to replace Daisy files. For long time, MO was niche. If we want to change things to this format, we should make sure we really add features. I'm thinking about Accessible Comics, we could extend media overlay to images fragments. 13:48:54 q+ 13:50:16 LaurentLM: Agree, it's comllex to change now something that starts to be more used. We should remove the burden of IDs everywhere. That's seems to be the case with VTT. The works with selectors is also to consider as a piece to help enhance media overlays. 13:50:28 q+ 13:50:42 delackner has joined #pmwg 13:50:45 +q 13:52:07 ack ivan 13:52:12 marisa: VTT brings greater range of selectors and allows to limit the number of needed IDs. This is a new serialisation format for media overlays. It is to be added, not to replace SMIL. 13:53:02 ivan: is this implemented in webviews? Because Reading systems often depend on Webviews. 13:53:38 q? 13:54:10 ack wendyreid 13:54:14 marisa: I will be happy to help implementors. 13:54:16 q+ 13:55:27 ack Hadrien 13:55:47 wendyreid: we have to make sure we don't break backward compatibility, and think about authoring tools so it is feasible for publishers. 13:57:10 q+ 13:57:27 wendyreid: but on the spec side we tottally can do this addition. 13:58:18 Avneesh has joined #pmwg 13:59:23 ack rdeltour 13:59:31 Hadrien: on implementtaion, when audio is involved, we often prefer native audio APIs than webviews. It allows to support more sysem control like touch etc. 14:01:10 https://w3c.github.io/sync-media-pub/convert-smil/ 14:01:21 rdeltour: I really like the idea of looking at implementation and identifying pain points before going further is a good strategy. If we want to support both SMIL and VTT, how complex or easy it is to convert one into another. Another question is how can we make VTT support escapability and skipability ? 14:02:02 marisa: I experimented conversions successfully. the link in the chat is to let you test that. 14:02:32 marisa: implementtaion is much more easier than SMIL. 14:03:04 ack delackner 14:03:13 q- 14:03:28 marisa: regarding escapibility and skipability, i don't think that the audio / SMIL is the best place. I would drive them from the text file. 14:03:58 q+ 14:04:22 delackner: what are the workflows in place to produce such files? Is there anything we know from the production side? 14:04:35 q+ 14:04:49 rrsagent, draft minutes 14:04:50 I have made the request to generate https://www.w3.org/2025/04/03-pmwg-minutes.html ivan 14:04:57 ack duga 14:06:12 duga: playbook uses media overlay to interact. It's easy because we have the IDs, shall they reprduce the experience with VTTs? 14:06:49 marisa: yes, the selector replace the ID. We can discuss suitable selectors. 14:06:50 ack Hadrien 14:08:26 ack gautierchomel 14:08:27 Hadrien: on production, when it is human voice, it is a struggle today. When it is TTS generated prerecorded voices it is easier. 14:08:55 gautierchomel: Similar to Hadrien, I've implemented an audio workflow when its generated, the system gives you back timestamps 14:09:01 ... I can easily make this webVTT 14:09:14 ... when I try to relink to HTML ids, that is when it is more challenging 14:09:30 q+ 14:09:35 ... this could help a lot, this is the kind of filethat can be output from video for example 14:09:46 ack Hadrien 14:28:14 wendyreid has joined #pmwg 14:28:29 Topic: HTML Serialization 14:28:49 LaurentLM has joined #pmwg 14:29:36 scribe+ 14:30:06 scribe+ 14:30:35 Avneesh has joined #pmwg 14:30:41 subject: HTML serialization 14:31:11 s/subject: HTML serialization// 14:32:12 wendyreid: we're not switching over. It would be an addition. It would probably not break publishing workflows. 14:32:13 gautierchomel_ has joined #pmwg 14:32:35 ... distribution platforms and reading system would need to evolve. 14:33:01 ... how do EPUB validate and open in reading systems? 14:34:21 ... Wendy made an EPUB with different files & different approaches. a) just change file extension b) change doctype c) change media type. 14:34:41 ... run through EPUBCheck. 14:35:01 ... errors. 14:35:25 ... tested on several reading systems. The doctype matters. 14:35:28 q+ 14:35:41 ack shiestyle 14:36:43 shiestyle: I had a survey in Japan with reading system vendors. It is not a heavy modification. 14:37:06 q+ 14:37:24 ack ivan 14:37:39 q+ 14:37:45 q+ 14:38:10 q+ 14:39:12 ivan: I heard that it is a small addition for rs vendors. We need to hear Romain about the checker. A W3C process trick here: we marked it at risk (related to the CR phase). 14:39:59 ack duga 14:40:06 ... we can only guess and wait for reactions. 14:40:23 q+ 14:40:49 ack Hadrien 14:40:51 duga: for rs it can be a pretty big deal. Not well formed XML will break systems in several places. 14:41:20 ack gpellegrino 14:41:21 hadrien: if we don't start we will not know. It is probably the only possible move. 14:41:25 QTI3 continues to use the XML syntax for representing elements borrowed from XHTML. QTI3 is an XML-based markup language for repressenting assessments. 14:42:54 gpellegrino: as part of the LIA process we are relying on some HTML tools, I transform XHTML to HTML. The xml:lang attribute must be moved to a lang attribute. This is the only transform we do. 14:43:47 ... At the industrial level, LIA will require XHTML at the start for certification, because some tools are XML only. The implementation period will be long. 14:43:49 ack mgarrish 14:43:58 Benetech's GCA certification requires both xml:lang and lang attributes to be set the same. 14:45:01 mgarrish: a) epub:type is not solved. b) many publishers will not release EPUBs if they are not sure that every rs cannot read them. 14:45:09 q+ 14:45:11 +1 to EPUB 4 change not a 3.x 14:45:13 ack LaurentLM 14:45:17 q+ 14:45:24 LaurentLM: About old reading systems, not using web engines 14:45:29 ... what do we do with them? 14:46:06 ... if a publisher releases something HTML-based, old reading systems will blow up, how might we manage this? 14:46:47 ... older eInk reading systems, RMSDK? 14:47:07 ack Hadrien 14:47:35 q+ 14:47:37 q+ 14:48:05 q+ 14:48:22 laurent: what about the old rs (eink readers) which will explode if facing HTML-based publications? I'm ok for breaking, but there will be some issues. 14:48:24 ack Avneesh 14:49:32 ack shiestyle 14:49:41 avneesh: we can write a W3C note, it will be a warning, give time to adapt to the publishing industry. In the next charter (2-3 years) we will move to it. 14:49:48 q+ 14:49:54 ack ivan 14:50:27 shiestyle: do we know when XHTML + CSS will break? 14:51:38 q+ 14:51:41 ivan: nobody knows. The package document is not the issue, the navigation document can be one. svg is in xml. 14:52:29 ... I don't see a real difference btw publishing a note now or including the information in the draft now (released in two years). 14:52:45 ... if there is no implementation we can remove it at last minute. 14:52:50 ack gpellegrino 14:53:38 q+ 14:54:08 ack wendyreid 14:54:16 ivan: browsers will continue supporting current XHTML for the known future. But new APIs may not be supported. 14:55:43 q+ 14:56:04 ack duga 14:56:11 wendyreid: we can postpone to EPUB 4, but we are in year 13 of EPUB 3 and we are making important evolutions. There is no will from the industry to move to a major evolution of EPUB. It we do that in EPUB 4 it will take 10 years to fly. 14:56:36 ack CharlesL 14:56:37 duga: many readers display content as HTML today. 14:57:20 charlesL: the driver should be a brand new thing, that we cannot do in XHTML. 14:58:16 q+ 14:58:17 wendyreid: it may not be a publisher who will want to do a new thing, maybe a rs developers will need it to do great stuff. 14:58:36 q+ 14:59:50 q+ 15:00:09 q- 15:00:10 ivan: we should have a PR which shows the changes. and replaces epub:type (or is "epub:type" accepted in HTML5?) 15:01:02 ack George 15:01:19 gpellegrino: epub:type does not break the browser or validator. Querying for epub:type is a question. 15:01:50 ack LaurentLM 15:01:50 george: K12 are putting publications in their LMS, they are moving to HTML. 15:02:49 LaurentLM: 2 comments, following George, we're seeing the same in Brazil, because they need HTML to do the applications they want, better relationship between web reading, and for a prototype, we'd need samples. 15:02:53 ... So we can test on something 15:03:28 q+ 15:03:45 ack CharlesL 15:03:48 laurent: in Brazil, the national program is contemplating moving to Web Publication because HTML is accepted and it brings more coexistence with Web reading. 15:04:14 ... and we need a good sample in the HTMLish varinant of EPUB. 15:04:32 s/laurent/laurentLM/ 15:04:44 PROPOSED: Create a PR for review that implements an HTML serialization for EPUB. 15:04:52 +1 15:04:52 +1 15:04:53 +1 15:04:53 +1 15:04:53 +1 15:04:53 +1 15:04:54 +1 15:04:54 +1 15:04:55 +1 15:05:00 +1 15:05:00 +1 15:05:01 0 15:05:17 +1 15:05:21 +1 15:05:40 RESOLVED: Create a PR for review that implements an HTML serialization for EPUB. 15:06:02 rrsagent, draft minutes 15:06:03 I have made the request to generate https://www.w3.org/2025/04/03-pmwg-minutes.html ivan 15:06:41 CharlesL has left #pmwg 15:30:10 LaurentLM has joined #pmwg 17:29:56 Zakim has left #pmwg 19:13:44 rdeltour has joined #pmwg 19:13:58 rdeltour has left #pmwg 20:27:03 LaurentLM has joined #pmwg