14:00:26 RRSAgent has joined #pm-ann 14:00:31 logging to https://www.w3.org/2025/09/04-pm-ann-irc 14:00:31 RRSAgent, make logs Public 14:00:32 please title this meeting ("meeting: ..."), ivan 14:00:59 meeting: PM WG Annotation Task Force telco 14:01:08 chair: LaurentLM 14:01:12 present+ 14:01:19 present+ LaurentLM 14:01:34 present+ ajellinek 14:01:37 gautierchomel has joined #pm-ann 14:02:18 DaleRogers has joined #pm-ann 14:02:52 Brady has joined #pm-ann 14:03:06 present+ 14:03:45 we'll start in when Ivan is back 14:04:28 present+ gautierchomel 14:04:37 present+ dalerogers 14:07:12 scribe+ 14:07:25 Use Cases and Requirements: https://w3c.github.io/epub-specs/wg-notes/annotations-ucr/ 14:07:36 LaurentLM: welcoming Abe from Berkeley university, working with Zotero. 14:07:39 agenda: https://www.w3.org/mid/2E290787-9BC5-433F-8C48-C93CF322D85D@edrlab.org 14:10:15 present+ jim_saiya 14:10:30 q+ 14:10:49 q- 14:10:57 LaurentLM: We listed that we can anotate a text, an image and the part of an image 14:11:12 ivan: shall we add video? 14:11:17 ivan: and audio? 14:12:31 LaurentLM: that mean we have to tackle the time issue. I suggest to add audio only because video players will be more complex to get into to extract an exact position. 14:13:03 q+ 14:13:14 scribe+ 14:13:33 gautierchomel: I recently had an interaction on Vimeo where I added comment 14:13:56 ... The interface made it easy to annotate a timestamp in the video 14:14:15 ... But I agree let us stick with audio only 14:15:14 q+ 14:15:20 LaurentLM: the part of an image is interesting. Complex to do for ceveloppers because that mean we have to draw. 14:15:38 ack gautierchomel 14:15:45 ack DaleRogers 14:16:30 q+ 14:16:48 q- 14:17:29 LaurentLM: formating annotations sounds a wish from users. Not sure how wide it is implemented yet. 14:17:43 q+ 14:18:48 ajellinek: we support that in zotero, we store annotations as HTML. standardising that across editor may be tricky. Not all editors accept HTML. Often we see subsets. 14:19:33 LaurentLM: maybe the note part can have a `content type` like HTML, MarkDown or PlainText, to drive the industry while letting space for flexibility. 14:19:36 q- 14:20:53 q+ 14:21:01 LaurentLM: there are anotations and also bookmarks that need to be interoperable. That's part of the use case document too. 14:21:02 ack ivan 14:21:58 ivan: a general remark, what can be anotated, what can be boorkmak? Can i anotate an anotation, a footote? are there limitations to consider? 14:22:46 LaurentLM: this is not tracked yet. what does the group think about this? 14:22:49 q+ 14:22:59 ack gautierchomel 14:23:17 gautierchomel: I think it is useful, but recognize it may add complexity 14:23:33 ... there is a use case for annotating other annotations and footnotes 14:24:07 s/footote/footnote/ 14:24:30 LaurentLM: footnote can come with difficulties to locate if they are outside the HTML. 14:24:43 q+ 14:25:08 ajellinek: we don't support annotating annotations, 14:25:10 q+ 14:25:13 q- 14:25:20 ajellinek: but it is a reasonable use case 14:26:06 ivan: it is also related to where the anotation is stored. When coming to technical, we may not be able to implement. 14:27:09 LaurentLM: i see a way if we consider it a thread of annotations instead of anotating anotations. 14:27:43 ivan: it's diferent, there are usecase where i want to select a part of an anotation to anotate. 14:27:45 q- 14:29:11 q? 14:29:27 LaurentLM: exporting & importing is a big part too. We have different scenarios here, from publishing a book with anotations to users sharing anotations, including in a classroom context. 14:30:51 q+ 14:31:32 DaleRogers: in the past authors responded books by publishing a new book, an article or a document. This technology may bring new usecase as responding to an ebook with an annotation. 14:33:03 ivan: the usecase I see is more in scholar or academic context, in a teacher to student relation or researcher communities. 14:34:21 LaurentLM: the implication of considering those usecase is that we'll study how to standardise. We've hear about a known US author who solds annotated book and did that with popup because there was not standardised way. 14:35:30 q+ 14:36:38 ack ivan 14:36:42 ack gautierchomel 14:37:40 gautierchomel: For annotation in social media, sharing annotations in a social media context 14:38:01 LaurentLM: I am an end user for this? 14:38:17 gautierchomel: Yes, I am in a book club, and I am sharing with other people in the club 14:38:35 ... I could try to monetize that and sell annotations at 1 euro per book 14:38:44 LaurentLM: Can you write the text for that? 14:38:45 +1 to gautierchomel 14:38:50 gautierchomel: yes, I will do that 14:40:15 LaurentLM: section 5 is about syncronizing. 14:41:22 LaurentLM: that mean among devices, among readers, among versions of ebooks. 14:43:30 q+ 14:44:11 ivan: i anotate the book i purchased, if i share with another person, they probably want to make sure they can diferenciate theyre annotations from mine. Identification is a use case to add here. 14:44:51 q+ 14:45:30 q+ 14:45:41 ack DaleRogers 14:45:50 LaurentLM: among device is easy, it means I stand in my ecosytem, identification is easy. While sharing among users comes with identification complexities. 14:47:07 DaleRogers: i see it similar to customer support id tickets. 14:48:05 ack gautierchomel 14:48:06 LaurentLM: unique identifier to ebooks is not suficienrtly used 14:48:28 gautierchomel: Among device could also be among vendors 14:48:48 ... so I read from one vendor, added annotations, now I want to use a new app 14:49:03 ... so I have changed the ecosystem, and I should be able to do that 14:49:21 LaurentLM: So I can move annotations between reading systems 14:49:44 gautierchomel: I am not confortable with the distinction between secions 4 & 5 14:50:03 LaurentLM: The big difference is the protocol 14:50:22 ... In the first, it is just files, in the second there has to be some sort of protocol 14:50:32 gautierchomel: But many use case are in both 14:51:20 ... So for a publisher providing them, they could be by file or protocol 14:51:20 q? 14:51:28 ack ivan 14:52:45 ivan: back to the identification part, 5.1 is my ebook; 5.2 is other people ebooks. I have to refer to the book instead of my ebook. 14:53:04 gautierchomel: I think it lives in both 14:54:42 LaurentLM: it's true but usecases are to make sure we do not forget anything. Then file sharing and protocol may be used for all usecases. 14:55:22 LaurentLM: last point is how to make sure we survive versions. It's a real burden here. 14:55:56 ajellinek: we met the problem and still looking how to solve it. 14:56:37 Requirements for locators https://github.com/w3c/epub-specs/issues/2763 14:56:40 LaurentLM: with the additions discussed today, I think we can start the requirement. An issue is open. 14:57:15 LaurentLM: we have no more time to discuss that today, I invite you to check and commenbt the issue. 14:57:40 s/commenbt/comment/ 14:58:49 rrsagent, draft minutes 14:58:50 I have made the request to generate https://www.w3.org/2025/09/04-pm-ann-minutes.html ivan 14:59:42 rrsagent, bye 14:59:42 I see no action items