Meeting minutes
<duga> +1
hadrien: wiki are not great on github. GDoc is usable. Discussions and issues are best.
laurent: w3c/
Laurent: will come back to the WG chairs
George: embed in the content doc or ?
Laurent: in the package
Leonard: it is tbd.
Leonard: is it only when they reference an EPUB?
Laurent: yes
Brady: this is what I'd like to see from a cross-platform annotation feature. Who is implementing this? we need 2 implementations.
Brady: people at Google would only be intersted if there is a good business case behing it. There are not so interested for now.
Hadrien: Readium Mobile toolkits (100+ apps) will include it. Readium Web also. Users iclude libraries, retailers .... And there there are apps developed by EDRLab: Thorium Desktop, Thorium Web, Thorium iOS, Thorium Android.
Laurent: Readwise is ok, they will implement a new export/import.
Brady: implementations count even if they are from the same organization. It would be better if there are different organizations.
George: the Daisy requirements and RFP of a Scandivanivan org will call for a reader with annotations.
George: I'd like to add to the scope, for education: exercices in books / workbooks (filling info, give to the teacher). A class of annotation could be such answers to exercices.
Dale: in the education sphere, LMS are more apps than ebooks. Answers are sent to a store. The technology is already there.
<leonardr> https://
Dalerogers: this is a replacement for scorm, xapi.
<leonardr> xAPI is actually maintained by a US Gov't agency (https://
<leonardr> however, standardized by IEEE - https://
Dalerogers: having worked on LMS, to engage with students, and the annotation is in the EPUB, the teacher will receive the book + annotations. It is different from personal annotations for personal use. We have to talk about security...
Laurent: it can be seen as a sequence: a- annotation in the reading system b- exported as a file c- exported in the EPUB and maybe d- sent to a server. At point d, maybe xapi will be the answer.
George: possible use case, people selling their annotations.
duga: if annotation selectors contain bit of the text, there will be IP issues.
leonardr: the W3C annotation addresses such issues with different selectors.
duga: publishers may not appreciate people making money with annotations if they contain bits of the text.
dalerogers: In the education domain, going though an LMS is required to log / document and secure exchanges between teachers and students.
george: in home education, there is no LMS. Simpler exports / imports are useful.
hadrien: a clear requirement from end users: switch between reading systems and get their annotations back (and bookmarks and reading location). Another example in education, PhD student, lots of citations and annotations. If I use a specialized platform, I want to keep it for later.
hadrien: about keeping annotations between book version, using EPUB URI schemes was difficult. I would be worried if we try to go too deep in this direction. We can recommand selectors that are stable enough to survive modifications, but trying to identifiy version of an ebooks will be impossible. If the annotation is "un-anchored" but has some contect, it is still valuable.
leonard: are annotation version-specific or publication-specific? There is no consensus in the community. We must take a stand. We'll have a great conversation
George: usually, there is not enough metadata in an epub to make proper citation. We'll need to give recommendations for EPUB metadata.
duga: it is not strictly in our TF goals.