- From: <sysbot+notifier@w3.org>
- Date: Thu, 14 Apr 2022 13:19:56 +0000
- To: public-transition-announce@w3.org
This is a transition request for a Candidate Recommendation
CR Request for EPUB 3.3, EPUB 3.3 Reading Systems, and EPUB 3 Accessibility 1.1
from https://github.com/w3c/transitions/issues/427
# Document title, URLs, estimated publication date
- EPUB 3.3
- URL: https://www.w3.org/TR/epub-33/
- Long URL: https://www.w3.org/TR/2022/CR-epub-33-20220505/
- Editor's Draft: https://w3c.github.io/epub-specs/epub33/core/
- Estimated Publication date: 2022-05-05
- EPUB 3.3 Reading Systems
- URL: https://www.w3.org/TR/epub-rs-33/
- Long URL: https://www.w3.org/TR/2022/CR-epub-rs-33-20220505/
- Editor's Draft: https://w3c.github.io/epub-specs/epub33/rs/
- Estimated Publication date: 2022-05-05
- EPUB Accessibility 1.1
- URL: https://www.w3.org/TR/epub-a11y-11/
- Long URL: https://www.w3.org/TR/2022/CR-epub-a11y-11-20220505/
- Editor's Draft: https://w3c.github.io/epub-specs/epub33/a11y/
- Estimated Publication date: 2022-05-05
(The documents are not yet installed on /TR, please look at either the editors' drafts or using the short names.)
# Abstract
- https://w3c.github.io/epub-specs/epub33/core/#abstract
- https://w3c.github.io/epub-specs/epub33/rs/#abstract
- https://w3c.github.io/epub-specs/epub33/a11y/#abstract
# Status
- https://w3c.github.io/epub-specs/epub33/core/#sotd
- https://w3c.github.io/epub-specs/epub33/rs/#sotd
- https://w3c.github.io/epub-specs/epub33/a11y/#sotd
# Link to group's decision to request transition
- https://www.w3.org/publishing/groups/epub-wg/Meetings/Minutes/2022-04-08-epub#resolution4
Note: that resolution was made on the 8th of April, and a 5 business day window was [announced](https://lists.w3.org/Archives/Public/public-epub-wg/2022Apr/0003.html) for objections. That period is over on April 15, at noon Boston time.
# Changes
- https://w3c.github.io/epub-specs/epub33/core/#change-log
- https://w3c.github.io/epub-specs/epub33/rs/#change-log
- https://w3c.github.io/epub-specs/epub33/a11y/#change-log
# Minimum deadline for CR comments
2022-10-30
# Requirements satisfied
Quoting from the [main requirements in the WG charter](https://www.w3.org/2020/12/epub3-wg-charter.html#scope):
> […] the interoperability of EPUB 3 content, and the conformance of EPUB 3 reading systems, remain a serious issue. There is a need for a more rigorous and comprehensive testing of EPUB 3; this may also mean the need for a further clarification of the standard text itself. […] The EPUB 3 Working Group will advance, refine, and clarify the EPUB 3 standard to ensure its relevance as digital publishing continues to evolve, and specify a comprehensive testing environment for EPUB 3.
The WG has:
- Reviewed, restructured, and updated the former EPUB 3.2 documents and made numerous changes to the texts for clarification, handling possible specification bugs, to make the specifications more precise. Although the change logs show many issues that have been handled (the change logs, together, contain references for over 120 substantial issues, i.e., these do not account for the purely editorial changes) only a handful of those are genuinely new technical features, mostly to answer to internationalization and to security issues.
- The working group has set up a functional testing environment to contribute to the interoperability of EPUB Reading System. At present the [list of tests](https://w3c.github.io/epub-tests/) contains around 120 individual tests which concentrate on the EPUB specific features (i.e., not including, say, HTML tests), and this number is expected to be growing during the CR period.
The WG believes that fully satisfied the requirement for the clarifications needed in the specification, as well as specifying a comprehensive testing environment.
# Dependencies met (or not)
There were no major dependencies.
# Wide Review
Horizontal reviews:
See [horizontal review tracker](https://www.w3.org/PM/horizontal/review.html?shortname=epub)
- A11y review:
- [mail from Janina](https://lists.w3.org/Archives/Group/group-epub-wg-chairs/2022Mar/0005.html)
- [a11y review issues by jasonjgw](https://github.com/w3c/epub-specs/issues?q=is%3Aissue+sort%3Aupdated-desc+label%3Ai18n-tracker) (all closed)
- [Joint TPAC meeting with APA](https://www.w3.org/publishing/groups/epub-wg/Meetings/Minutes/2021-10-25-epub) (all closed)
- I18N review:
- [mail from Fuxiao](https://lists.w3.org/Archives/Group/group-epub-wg-chairs/2022Mar/0003.html)
- [`i18n-tracker` issues](https://github.com/w3c/epub-specs/issues?q=is%3Aissue+author%3Ajasonjgw) (all closed)
- [`i18n-needs-resolution` issues](https://github.com/w3c/epub-specs/issues?q=sort%3Aupdated-desc+label%3Ai18n-needs-resolution) (all closed)
- Privacy/Security review:
- [`privacy tracker` issues](https://github.com/w3c/epub-specs/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Aprivacy-tracker)
- [Joint TPAC meeting with PING](https://www.w3.org/publishing/groups/epub-wg/Meetings/Minutes/2021-10-26-epub)
- [WG Call with PING participation, 2021-10-28](https://www.w3.org/publishing/groups/epub-wg/Meetings/Minutes/2021-10-28-epub#section4)
- [WG Call with PING participation, 2022-01-28](https://www.w3.org/publishing/groups/epub-wg/Meetings/Minutes/2022-01-28-epub#section1)
- [Privacy issues](https://github.com/w3c/epub-specs/issues?q=is%3Aissue+label%3ACat-Privacy+) (all closed from the WG's point of view but never answered by PING)
- [Security issues](https://github.com/w3c/epub-specs/issues?q=is%3Aissue+label%3ACat-Security+) (all closed from the WG's point of view but never answered by PING)
- TAG review:
- [Issue on the WG repository](https://github.com/w3c/epub-specs/issues?q=is%3Aissue+author%3Arhiaro+)
- [Issue on the TAG repository](https://github.com/w3ctag/design-reviews/issues/684), explicitly [closed by the TAG](https://github.com/w3ctag/design-reviews/issues/684#issuecomment-1091985272)
The WG discussions were conducted through [github issues](https://github.com/w3c/epub-specs/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc). The group took over the repository used to develop earlier versions of EPUB, and that meant ≈100 open issues at the time the Working Group started (September 2020); some of those were around for years. During the lifetime of the Working Group ≈400 issues were added, coming both from the wider community and the Working Group itself, with the participation of experts outside the group.
# Issues addressed
The change log items listing the substantial changes, i.e.:
- https://w3c.github.io/epub-specs/epub33/core/#change-log
- https://w3c.github.io/epub-specs/epub33/rs/#change-log
- https://w3c.github.io/epub-specs/epub33/a11y/#change-log
include references to the issues that were addressed by those changes.
# Formal Objections
None.
# Implementation
The exit criteria of the Working Group are described in:
- https://w3c.github.io/epub-specs/epub33/reports/exit_criteria.html
with links to the report documents that will, eventually, contain the results of testing.
There are numerous EPUB 3 Reading System implementations on the market, some major ones are represented on the Working Group (Google, Apple, Kobo, EDRLab, VitalSource, Colibrio, etc.). We expect most of these will contribute to the test results. Also, the group has numerous contacts with Publishers, as well as accessibility organizations, who can contribute to the CR testing of, e.g., vocabularies.
Finally, there is a strong cooperation between the Working Group and the developers of [epubcheck](https://www.w3.org/publishing/epubcheck/), that already has a beta version of an EPUB 3.3 checker. (This is particularly important, because epubcheck is used by virtually all publishers before releasing a new publication.)
We expect the CR period open until the end of December 2022.
# Patent disclosures
https://www.w3.org/groups/wg/epub/ipr
# Additional note on CR exit
The [Working Group's charter](https://www.w3.org/2020/12/epub3-wg-charter.html) has a very strong clause on backward compatibility:
> Any existing valid EPUB 3.2 should remain valid under EPUB 3.X, unless it relies on features discovered to have serious issues (such as a security bug).
What this means that the usual CR approach, whereby if a feature does not get the right number of implementation per the exit criteria must be removed from the specification, cannot be applied in this case. Instead, the WG has introduced a special category called ["under-implemented features"](https://www.w3.org/TR/epub-33/#under-implemented) to mark those features in the final publication.
---
Cc @dauwhe @mattgarrish @shiestyle @wareid
--
This email was generated automatically using https://github.com/w3c/transition-issues-bot
Received on Thursday, 14 April 2022 13:20:03 UTC