– DRAFT –
Publishing Community Group

recent EPUB WG + PCG activities

<dauwhe> https://www.w3.org/blog/2022/05/epub-3-3-is-now-in-cr/

<ivan> Publication list and status of the WG

wendyreid: for the last two years, we have been updating EPUB 3.3 - currently in CR status - updates mostly around editorial fixes, made structural changes
… separate RS vs. content creators
… new section: privacy and security - recommendations for authors and content creators - we are still making changes - feel free to log issues - reach out to any of us

<Bill_Kasdorf> Wendy's blog post is really excellent--if you haven't read it, you should.

wendyreid: recommend reading the blog post

<ivan> test suite for EPUB

Dave: Writing tests - at least two implementations for each feature needed - call for assistance in this process

Zheng: updated our web page which now contains links to specs

<dauwhe> Signup for tests: https://docs.google.com/spreadsheets/d/13wgptApSVbQbYzi2L5VXe3D_1QLzJOTGySUAtOxn4sA/edit#gid=0

Ivan: over 130 tests - testing is very important - Dan Lazin (testing champion): we need roughly 50 more -spreadsheet (see link) list test for MUST features
… description how to contribute in IRC
… also RS implementors in the CG - we need RS developers to run the tests and report back to us - if you are in such a company convince people to run these tests and report back
… needed for W3C process

Gautier: responsible for EDRLAB testing - got some questions

Ivan: you can contact me - if you like in French - addition to testing environment: report generator for direct use in Thorium

Zheng: a few task forces - A11Y TF: accessibility metadata
… Documentation TF
… PCG members willing to provide assistance for tests
… plan more incubating work - a lot of members are interested in education - have a TF Use cases in education

Dlazin: test lead for EPUB 3.3 + TF documentation - slowly working getting EPUB docs - only bits and pieces - best documentation in Daisy's database but with a slant towards A11Y
… intend to do basic canonical documentation - got MDN to agree to take care of the doc

<dlazin> https://docs.google.com/document/d/16lNrPwXcGS9w1ePQLFf60Hx-RvbE4roG2YkwjL_X-Hc/edit#heading=h.aorc81xxt93h

<dlazin> https://github.com/dlazin/mdn-yari/blob/main/kumascript/macros/EPUBRef.ejs

<dlazin> https://github.com/dlazin/mdn-content/tree/main/files/en-us/related/epub

Dlazin: this Google doc is a checklist for MDN - basic EPUB sample documents from colleagues - architecture for the documentation - enable to run MDN locally
… we don't want to give it to MDN, before minimum viable set is ready

<Zakim> tzviya, you wanted to explain incubation process (after zheng_xu finishes intro)

tzviya: incubation process - 10 years ago W3C had the idea that experimentation in a CG should precede a WG - you test the waters - collect use cases
… explore what the world of publishing is interested in - could move that forward in a WG - we don't have this conversation of WG and PCG - it is not clear what happens when the work on EPUB 3.3 is finished
… ideas should start at the CG

zheng: let us know if you would like to put forward an idea - one of our missions is to provide feedback to WG - we are looking forward to more active communication from our members
… and also for incubations of ideas

WG FXL A11y, Virtual locators and Testing

<dauwhe> https://w3c.github.io/epub-specs/epub33/fxl-a11y/

wendyreid: TF 1: FXL A11Y - looking for best practices based on existing A11Y specs (e.g. WCAG) - what could we do to make FXL content as accessible as possible using existing standards
… not possible to make FXL content fully accessible
… TF 2: virtual locators in lack of page numbers - criticism in academia: how to cite properly from EPUB? - addressability problem has haunted us again and again
… many slightly different ways to make locators work - how can we reach a consistent standardized solution

George: do you plan to identify a standard for citations ?

wendyreid: no - how do we create a location model that fits into existing citation models

Ivan: how the metadata of the package document can be turned into the IEEE citation style - ACM or IEEE define that
… what is the equivalent of an anchor in an HTML file that I could use to point to a specific location in the EPUB document via a URL - we look for a minimal viable algorithm to address a point in a documnet
… EPUB CFI was one approach - maybe a useful addition - WG spent time on it - would need incubation in terms of implementation and spec work before we start with a WG

BillK: locators TF not working on standardizing citation - just how to define a mechanism

wendyreid: annotations not yet touched - focus on page numbering and page location that is quite incocnsistent -
… solving this addressability problem, we should take a more holistic approach

billk: standardized mechanism for arbitrary locations

wendy: yes - CFI needs more work - are there implementations, how do they work, CFIs very complex - only machine-readable
… looking for sth simpler that is less complex and works both for machines and humans

George: is this problem solved in HTML?

Ivan: many years ago Annotation WG came up with a standard that might be used in HTML for anchoring annotations into an HTML page - never implemented - t
… not very satisfactory - in general, we don't have a solution - if the author hasn't put IDs everywhere, I can't add annotations

George: an individual EPUB on my machine would have annotation - you can't hand this information on or update the EPUB without losing it

tzviya: we could write a spec - but we would need buy-in from the RS developers - different implementations need to a user lock-in - academia needs a solution

<Zakim> tzviya, you wanted to explain the problem

tzviya: there are several solutions, but none is standardized - there is an annotation spec, but it is has not been implemented

<dauwhe> https://wicg.github.io/scroll-to-text-fragment/

Wendy: agree with Ivan and Tzviya - a lot of user pressure about annotations (that should be portable) - if we don't build it, others will do it - slightly shifting tide towards supporting annotations

ivan: how come that these exchangible annotations do work in PDF - works also on other PDF readers

Naomi: you have edited PDF file by adding annotations - but no RS supports editing an existing EPUB

dlazin: for the related question of page numbers, we can only solve it on a standards levels

dave: pasted an option

dlazin: works only in Chrome - simple, but it works

Zheng: Paul will be leading our Education TF

PaulBelfanti: TF for collecting use cases for education - features that would enhance the experience from the view of an educational publisher

BillK: it refers to educational content on the Web - not only EPUB

Zheng: a lot of good directions from today's discussion -

modes of cooperation in CG and with WG

zheng: we have issues in our github repo - how could WG communicate to CG - how can we move things forward? - we have publishers, RS devs, conversion specialists
… how can we make the communication more active?

George: CG meets once a month - whole group or a TF could use that fixed date -

Zheng: each month there is update for TF and option to raise issues
… you may recommend a time for the meeting of each TF
… would members like to have more specific meetings, we can arrange for it

CharlesL: a blitz to publishers - CG is the way to participate in W3C - get more exposure by marketing activities to get more involvement