13:29:18 RRSAgent has joined #pmwg 13:29:22 logging to https://www.w3.org/2026/03/05-pmwg-irc 13:29:22 RRSAgent, make logs Public 13:29:23 Meeting: Publishing Maintenance Working Group 13:30:13 ivan has changed the topic to: Meeting Details 2026-03-05: https://lists.w3.org/Archives/Public/public-pm-wg/2026Mar/0000.html 13:30:14 Chair: wendy 13:30:14 Meeting: Publishing Maintenance Working Group Telco 13:30:14 Agenda: https://lists.w3.org/Archives/Public/public-pm-wg/2026Mar/0000.html 13:57:37 shiestyle has joined #pmwg 13:57:48 gautierchomel_ has joined #pmwg 13:59:06 GeorgeK has joined #pmwg 13:59:21 present+ 13:59:29 duga has joined #pmwg 13:59:31 present+ george 13:59:33 toshiakikoike has joined #pmwg 13:59:40 present+ 13:59:48 present+ duga 13:59:49 present+ 13:59:57 present+ gautierchomel_ 14:00:10 MasakazuKitahara has joined #pmwg 14:00:12 present+ LaurentLM 14:00:19 present+ 14:00:21 present+ 14:00:24 present+ wendyreid 14:00:25 gman has joined #pmwg 14:00:36 sueneu has joined #pmwg 14:00:40 present+ gman, shiestyle 14:00:40 gpellegrino has joined #pmwg 14:00:54 present+ 14:00:57 present+ 14:00:59 present+ 14:01:27 scribe+ gman 14:01:47 ajellinek has joined #pmwg 14:01:54 present+ 14:01:55 present+ 14:02:21 Topic: Annotations - model to add audiovisual comments 14:02:30 https://github.com/w3c/epub-specs/issues/2925 14:03:06 q+ 14:03:09 ack LaurentLM 14:03:54 LaurentLM: the question is about audio/images annotations 14:04:29 ... Ivan tried to modernize the body format property annotation which go beyond text e.g. audio 14:04:41 ... yet another problem: where to start? 14:04:59 q+ 14:05:11 ... after segmenting and sending to the system, the epub export make problems to emerge 14:05:43 CharlesL has joined #pmwg 14:05:46 Hadrien has joined #pmwg 14:05:46 ack ivan 14:05:47 present+ 14:05:49 present+ 14:06:17 q+ 14:06:29 ivan: is it realistic to transfer an ebook model for export/import? 14:06:39 q+ 14:07:15 s/Ivan tried/... Ivan tried/ 14:07:29 LaurentLM: the audio annotations storage solution will not be in the epub itself 14:07:52 Ivan: when exporting annotations, the zip is exported with json+audio, which works 14:08:04 LaurentLM: which implies an internal structure inside zip 14:08:57 ... the use case i'm worried about the annotations exposrted as part of the file 14:08:58 ack Hadrie 14:09:33 s/Hadrie /Hadrien 14:09:48 Hadrien: open domain content will not arise issues and the file sharing is ok 14:10:33 ... authors writing their own annotations is a possibility hence making this solution a standalone is not the best, having both is the best 14:10:43 ack duga 14:11:22 duga: adding audio etc is not new and feasable 14:12:43 ... relative urls are already present, zipping the annotation will change the input format requirement, and might be confusing 14:12:48 ajellinek has joined #pmwg 14:13:14 ... zip content should be transparent, if json is there it must be clearly stated 14:13:14 q+ 14:13:20 ack LaurentLM 14:14:07 LaurentLM: the issue is that the section 6 of current draft state a singe file usage 14:14:15 q+ 14:14:20 ack duga 14:14:38 q+ 14:14:42 ack Hadrien 14:14:58 Hadrien: OPF shouldn't be touched, by principle 14:15:01 q+ 14:15:39 it will be wierd if multiple things are able to be exported/imported, zip at least open up an extension possibility, which is nice 14:15:52 DaleRogers has joined #pmwg 14:16:07 ack wendyreid 14:16:48 present+ 14:18:14 wendyreid: packaging up and embedding into epub, beyond OPF, do we run up into valdiation issues? 14:18:24 ... otherwise, outside of meta, should we target another new location? 14:18:32 q+ 14:18:32 q+ 14:18:38 LaurentLM: not sure if another folder can be put into meta 14:18:38 ack Hadrien 14:19:20 q- 14:19:21 q+ 14:20:03 Hadrien: audio and other files in the back of epub is more part of an export action process 14:20:25 ack ivan 14:20:28 LaurentLM: the wording would be extended then 14:21:03 q+ 14:21:10 ivan: nothing in there forbids creation of a subdir for annotation 14:21:31 ... with nothing inside, a flat tree structure 14:22:41 ... on the other hand, the complications are overruled by user cases 14:22:43 ack CharlesL 14:23:00 CharlesL: the security is not to be overlooked 14:23:18 ... the injection disguised as annotation is a posibility 14:23:25 +1 CharlesL 14:23:31 LaurentLM: it's true 14:24:12 q+ 14:24:13 q+ 14:24:19 ack duga 14:24:20 ivan: the scope of accepted base media files should stay the same 14:24:55 q- 14:25:10 duga: anything appropriate for epub must be definition be acceptable fo epub 14:25:19 q+ 14:25:21 ack wendyreid 14:25:44 q+ 14:25:46 q+ 14:28:28 gman has joined #pmwg 14:28:36 wendyreid: there are reading system out there that support images not matching the dimensions showing screenshot of annotation in case of problem 14:28:53 ack Hadrien 14:29:29 Hadrien: I'm more worried about images than audio, sure mic needed etc 14:30:43 ... but for example the text layout can be changed completely, the view too, the interoeprable fashion setting might not work as a result 14:30:44 ack GeorgeK 14:31:20 GeorgeK: the annotation access for future use must be exportable too 14:31:55 q+ 14:32:04 q+ 14:32:07 wendyreid: export of annotation only or export of the whole book annotated co-exist 14:32:10 ack ivan 14:33:12 ivan: from specing POV, meta and data handling is not of our problem 14:33:13 q+ 14:33:43 q- 14:34:11 q- 14:34:27 LaurentLM: even if only text annotations exist, we export a zip, with json structure 14:35:14 ajellinek: zip works with export and import as it's widely used 14:35:42 wendyreid: there's a consensus, strcutre is to be defined 14:36:14 q+ 14:36:16 q+ 14:36:20 LaurentLM: once data is stored inside epub, the encryption poses a problem 14:36:23 ack Hadrien 14:36:43 Hadrien: in case of authored annotations, they must be encrypted 14:36:59 ack sueneu 14:37:07 q+ 14:37:19 seuneu: +1 for authored annotations encrypted 14:37:37 q+ 14:37:43 ... namely for copyright reasons, if though it might not be our problem 14:37:47 ack CharlesL 14:37:57 q+ 14:38:15 CharlesL: what about the superposition problem, i.e. annotation on annotation problem? 14:38:15 ack ivan 14:38:59 ivan: it's for the future given the can of worms this discussion opens up 14:39:05 q+ 14:39:44 ... the publishers allows for export of annotations importable by the peers, which just gives the authorization 14:39:52 ack duga 14:39:57 ... a single file without a book containing annotations is ok 14:40:35 q+ 14:40:36 duga: DRM annotation: exportable or not exportable? that is the question 14:40:43 ack CharlesL 14:41:04 q+ 14:41:11 ack Hadrien 14:41:27 CharlesL: the other point: multiple students in front of the same book, does this situation produces a set of subdirs? 14:42:02 Hadrien: the attribution becomes a tricky issue now, should we open the Pandora's box? 14:42:33 wendyreid: the difference between new annotations and responding to existing ones are two different problems 14:43:09 ... the recursivity of annotations is not a topic for now for the current model 14:43:09 ack LaurentLM 14:43:13 q+ 14:43:28 LaurentLM: to be clear, each annotation has its own author 14:43:39 q- 14:43:55 ... all the annotations, whatever the author, are thrown into one universal bag 14:45:05 ... i have a bigger cocnern with authored annotation in a DRM context because the encryption key makes the annotations intrinsic to the book itself 14:45:12 q+ 14:45:18 ack sueneu 14:45:54 seuneu: authored annotations must be processed differently from non authored ones? 14:46:00 LaurentLM: Yes 14:46:13 q+ 14:46:30 q+ 14:47:01 q- 14:47:09 wendyreid: annotated editions encapsualte annotations (i.e. they are part of the book by definition, by essence), thus are treating the annotations as integral to the book as a feature? 14:47:13 +1 to what wendyreid said 14:47:14 ack duga 14:47:31 q+ 14:47:44 duga: annotation mechanism should not be used in a DRM context 14:47:50 +1 to duga 14:48:20 +1 to what Brady is saying 14:48:20 +1 to duga 14:48:24 +1 to duga 14:48:53 ... annotations that are part of the content is not a valid use case here 14:49:18 ... if we ignore it, the DRM problem goes away 14:49:28 q+ 14:49:33 ack Hadrien 14:50:00 Hadrien: mixed feelings here 14:50:05 q+ 14:50:24 ... footnotes are horrible 14:50:44 ... media overlay via authored audio is possible too 14:51:50 ... people's creativity is without boundaries, thus we must be careful in our spec 14:52:19 wendyreid: i don't disagree, but the line must be drawn somewhere 14:53:03 q+ 14:53:10 ack sueneu 14:53:10 ... and it's : Authorized (created by author feat. publisher) vs Unauthorized (the other use cases) 14:53:35 seuneu: agree with Authorized vs Unauthorized idea 14:54:17 ... but with improvements of already existing features 14:54:21 ack shiestyle 14:55:28 shiestyle: the old footnnote feature and this annotation feature are two distinct things 14:55:35 ack LaurentLM 14:56:13 LaurentLM: improving footnotes with the annotation methodology is complex 14:57:18 ... reading systems capabilities are dictated by the market 14:57:30 ... and annotations can be DRM protected just in case 14:57:54 wendyreid: the thing to figure out: where to store these annotations, inside or outside? 14:57:55 q+ 14:57:58 ack ivan 14:58:19 ivan: my feeling -- this issue is PR-ready 14:58:38 ... that's the next step 14:59:22 rrsagent, draft minutes