12:09:25 <RRSAgent> RRSAgent has joined #pmwg
12:09:29 <RRSAgent> logging to https://www.w3.org/2026/04/02-pmwg-irc
12:09:29 <Zakim> RRSAgent, make logs Public
12:09:30 <Zakim> Meeting: Publishing Maintenance Working Group
12:09:34 <ivan> ivan has changed the topic to: Meeting Details 2026-04-02: https://lists.w3.org/Archives/Public/public-pm-wg/2026Mar/0027.html
12:09:35 <ivan> Chair: wendy
12:09:35 <ivan> Meeting: Publishing Maintenance Working Group Telco
12:09:35 <ivan> Agenda: https://lists.w3.org/Archives/Public/public-pm-wg/2026Mar/0027.html
12:09:36 <ivan> regrets+ brady, matt
12:50:32 <DaleRogers> DaleRogers has joined #pmwg
12:58:38 <shiestyle> shiestyle has joined #pmwg
12:59:12 <ajellinek> ajellinek has joined #pmwg
12:59:16 <toshiakikoike> toshiakikoike has joined #pmwg
12:59:29 <gautierchomel> gautierchomel has joined #pmwg
12:59:59 <toshiakikoike> present+
13:00:10 <MasakazuKitahara> MasakazuKitahara has joined #pmwg
13:00:19 <MasakazuKitahara> present+
13:00:27 <kimberg> kimberg has joined #pmwg
13:00:34 <kimberg> present+
13:00:35 <ajellinek> present+
13:00:39 <wendyreid> wendyreid has joined #pmwg
13:00:44 <shiestyle> present+
13:00:51 <wendyreid> present+
13:00:56 <sueneu> sueneu has joined #pmwg
13:01:16 <sueneu> present+
13:01:16 <ivan> present+
13:01:16 <DaleRogers> DaleRogers has joined #pmwg
13:01:16 <AvneeshSingh> AvneeshSingh has joined #pmwg
13:01:25 <rdeltour> rdeltour has joined #pmwg
13:01:34 <ivan> present+ rdeltour
13:01:49 <ivan> present+ DaleRogers
13:01:55 <ivan> present+ AvneeshSingh
13:02:00 <gautierchomel> present+
13:02:04 <ivan> present+ george
13:02:15 <ivan> present+ gautierchomel
13:02:16 <gautierchomel> scribe: gautierchomel
13:02:37 <GeorgeK> GeorgeK has joined #pmwg
13:02:39 <wendyreid> Topic: Privacy and Security Review
13:02:52 <gpellegrino> gpellegrino has joined #pmwg
13:02:55 <ivan> present+ gpellegrino
13:03:01 <gpellegrino> present+
13:03:08 <GeorgeK> present+
13:03:23 <ivan> q+
13:03:23 <gautierchomel> wendyreid: privacy and security review have been merged and submitted.
13:03:26 <gautierchomel> q+
13:03:27 <wendyreid> ack ivan
13:03:53 <gautierchomel> ivan: note to ourself,we have done what we are supposed to, wait for comments from other groups
13:03:54 <gautierchomel> q-
13:04:16 <AvneeshSingh> present+
13:04:42 <wendyreid> Topic: Annotations Progress Check
13:05:25 <ivan> present+ elizabeth
13:05:48 <gautierchomel> wendyreid: we've made a lot of progress, but there are still some gaps before sending to review.
13:06:30 <gautierchomel> wendyreid: we should plan two months not more if we want to achieve review by the end of our charter.
13:06:40 <ivan> present+ laurentlm
13:07:35 <gautierchomel> wendyreid: privacy and security for annotation will be a burden, accessibility too probably, the topic comes with high complexity.
13:08:38 <ivan> q+
13:08:51 <gautierchomel> laurentLM: I see no difficulty to solve open issues in the next month.  We've discussed language and text direction so internationalisation should be ok. We use json so I am not worried.
13:08:57 <gautierchomel> q+
13:09:00 <wendyreid> ack ivan
13:10:55 <gautierchomel> ivan: less optimistic by nature. There are terms and objects not defined, not complicated ones but to be defined. Json schema is an empty section. We can try to say this is json so privacy security and accesisbility are covered by this spec. But we might be asked to give some reading suystem considerations on safe and robust implementation.
13:11:19 <wendyreid> q+
13:11:41 <gautierchomel> ivan: we may want to add asecurity section, even non normative, it's often done this way.
13:11:43 <LaurentLM> LaurentLM has joined #pmwg
13:11:47 <wendyreid> ack gautierchomel
13:11:50 <LaurentLM> present+
13:11:52 <wendyreid> scribe+
13:12:18 <wendyreid> gautierchomel: Are we talking about having the document ready for security/privacy review by end of May or everything by end of May?
13:12:22 <wendyreid> ack wendyreid
13:12:28 <ivan> present+ kimberg
13:12:53 <gautierchomel> wendyreid: draft of the document by end of may so we can start the review process.
13:13:21 <CharlesL> CharlesL has joined #pmwg
13:13:36 <ivan> present+ CharlesL
13:14:40 <gautierchomel> wendyreid: for EPUB, we did a risk assesment, I would suggest to follow that path. That's a way to raise questions . What happen is someone use anotations for injection? What about an EPUB silently leaking infos? We may have no response but at least knowing the risks and informing them.
13:14:52 <ivan> q+
13:14:55 <wendyreid> ack ivan
13:16:20 <gautierchomel> ivan: two timelines: may to start the review and all testings done before january.  We need to think about how to test, that would be complexer than for EPUB. At the moment I am not sure how to test annotations.
13:16:45 <gautierchomel> q+
13:16:48 <wendyreid> ack gautierchomel
13:17:37 <wendyreid> gautierchomel: I think that I would be happy to start the risk assessment for annotations, we have some experience since we implemented in Thorium, I can propose some first draft, should I do it in an issue or elsewhere?
13:17:51 <wendyreid> ... I have some ideas about how to test
13:18:08 <wendyreid> ... we've tested them for Thorium desktop, I have some ideas
13:18:12 <wendyreid> q+
13:18:17 <wendyreid> ack wendyreid
13:19:07 <sueneu> q+
13:19:15 <ivan> q+
13:19:18 <gautierchomel> wendyreid: in terms of testing, we need individual tests, as well as exemples embedded in an EPUB vs separate file
13:19:29 <wendyreid> ack sueneu
13:19:35 <gautierchomel> laurentLM: this sounds like testing the RS, not the spec.
13:21:02 <wendyreid> ack ivan
13:21:35 <gautierchomel> wendyreid: short reminder, for each MUST in the spec we need a test. Two implementations to pass. We create the files, RS are invited to test.
13:23:37 <gautierchomel> ivan: an ebook for each MUST statement is a mean, we can work differently and asses different parts with one file. One important feature, is the interchange format, we do not define how RS do that, we have to proof that a RS can export the annotations in the format we specify and that a RS can import it.
13:23:56 <LaurentLM> q+
13:24:01 <wendyreid> ack LaurentLM
13:24:12 <gautierchomel> ivan: we should concentrate on the interexchange
13:25:05 <gautierchomel> LaurentLM: I agree with that, one annotation file with different types inside might be sufficient to proove we can import and export it.
13:26:53 <gautierchomel> LaurentLM: let's solve issues one by one to make sure we have a good draft. There are 10 plus a PR. I have also to add  a section on metadata. I will do that before the weekend.
13:27:06 <sueneu> q+
13:27:13 <wendyreid> ack sueneu
13:27:35 <gautierchomel> sueneu: happy to help if there something I can do to share pressure.
13:28:45 <gautierchomel> LaurentLM: having implementations would be great! even from this beta. It's a few steps to align Thorium and Readium implementations but we definitely want other RS to jump in.
13:29:28 <wendyreid> https://github.com/w3c/epub-specs/issues/2971
13:29:47 <wendyreid> Topic: Aligning text-style properties - https://github.com/w3c/epub-specs/issues/2971
13:31:56 <LaurentLM> q+
13:31:57 <sueneu> q+
13:32:08 <wendyreid> ack LaurentLM
13:32:39 <ivan> q+
13:32:41 <gautierchomel> wendyreid: RS have to deal with dark mode, color contrast, high contrast, etc. i feel we should clarify that "yelow" note does not mean the note must use Yellow CSS color.
13:32:52 <wendyreid> ack sueneu
13:33:00 <gautierchomel> LaurentLM: Agree, I will add this as a clear statement.
13:33:20 <LaurentLM> q+
13:33:34 <wendyreid> ack ivan
13:35:20 <gautierchomel> sueneu: may we use IDs instead of color names ?
13:35:22 <gautierchomel> ivan: maybe we should use different wording, let's say "yellowish" instead of "yellow" to avoid confusions.
13:35:38 <wendyreid> ack LaurentLM
13:37:44 <shiestyle> q+
13:37:49 <wendyreid> ack shiestyle
13:37:55 <gautierchomel> LaurentLM: I don't see a clash, yellow is not a term invented by css, they just use it to qualify a color code. We don't do HTML, we do JSON, so I would prefer to use normal color, witha note that it is defining a range of colors. In our review, all RS use similar colors, yellow, blue, magenta, a set of meaningfull color.  Let's not reword but instead have a clear statement. Yellow existed before css.
13:38:30 <ivan> q+
13:38:37 <LaurentLM> q+
13:38:39 <wendyreid> ack ivan
13:38:48 <wendyreid> q+
13:38:50 <LaurentLM> q-
13:39:16 <DaleRogers> q+
13:39:49 <sueneu> q+
13:39:55 <gautierchomel> ivan: agree not to use HEX color codes, it's a name, acting like an ID, we don't specify what color should a RS apply to Yellow.
13:40:01 <wendyreid> ack wendyreid
13:42:13 <GeorgeK> q+
13:42:34 <sueneu> q-
13:42:37 <wendyreid> ack DaleRogers
13:43:48 <wendyreid> ack GeorgeK
13:43:55 <gautierchomel> wendyreid: also we don't want to test exact color code used by RS, we cannot impose them a color pattern that may not fit in theyre designs. The name acts as a group or a tag.
13:44:37 <LaurentLM> q+
13:44:43 <wendyreid> ack LaurentLM
13:46:26 <gautierchomel> GeorgeK: redlining is a publishing use case,  stroke and red usually means a correction to do. We understand that with words.  All of us in the industry.
13:46:30 <sueneu> GeorgeK +1
13:47:03 <ivan> q+
13:47:09 <wendyreid> ack ivan
13:47:55 <gautierchomel> LaurentLM: that's it, color name is a semantic, the appearence of it as not to be defined at a standard level.
13:48:20 <gautierchomel> ivan: let's see how we word that in a PR.
13:49:06 <gautierchomel> s/as/has/
13:50:17 <ivan> q+
13:50:23 <wendyreid> ack ivan
13:50:39 <wendyreid> https://github.com/w3c/epub-specs/pull/2972
13:51:24 <wendyreid> Topic: AOB?
13:51:28 <gautierchomel> LaurentLM: I have some comments, I'll do them in the PR.
13:54:16 <shiestyle> zakim, end the meeting
13:54:16 <Zakim> As of this point the attendees have been toshiakikoike, MasakazuKitahara, kimberg, ajellinek, shiestyle, wendyreid, sueneu, ivan, rdeltour, DaleRogers, AvneeshSingh, gautierchomel,
13:54:19 <Zakim> ... george, gpellegrino, GeorgeK, elizabeth, laurentlm, CharlesL
13:54:19 <Zakim> RRSAgent, please draft minutes v2
13:54:21 <RRSAgent> I have made the request to generate https://www.w3.org/2026/04/02-pmwg-minutes.html Zakim
13:54:28 <Zakim> I am happy to have been of service, shiestyle; please remember to excuse RRSAgent.  Goodbye
13:54:28 <Zakim> Zakim has left #pmwg
14:09:46 <CharlesL> CharlesL has left #pmwg
15:04:59 <gautierchomel_> gautierchomel_ has joined #pmwg