Closed dauwhe closed 2 years ago
Hi @dauwhe just fyi we've started our review at our virtual f2f this week and we'll be starting to surface some of that feedback here soon and asking questions.... Thanks for bearing with us.
- Relevant time constraints or deadlines: We hope to move to CR at the end of 2021
We now plan for CR in Q1 of 2022.
Hello, I have opened a couple of issues (#1957, #1958, #1959) primarily around privacy considerations, as part of this review.
The main point here is that more expansive privacy considerations sections in both the EPUB and EPUB Reading Systems specs would be great.
I also want to note some other ongoing threads I'm particularly interested in the outcomes of:
Looking at this in our W3CTAG breakout session.
Just noting that in two of the issues that @rhiaro opened, the working group minutes (mentioned in @iherman's reply) indicate that they are planning to address them and will get back to us.
And it doesn't look like there is any comment yet on the third: [TAG] Reading systems and permissions prompts #1958.
Looking at this in our W3CTAG breakout session.
Just noting that in two of the issues that @rhiaro opened, the working group minutes (mentioned in @iherman's reply) indicate that they are planning to address them and will get back to us.
There has been extensive changes recently on the security and privacy section of the specs (as a result of the relevant horizontal reviews), see
we feel that these answer most of the TAG issues, too. Apologies not to ping you here earlier.
And it doesn't look like there is any comment yet on the third: [TAG] Reading systems and permissions prompts #1958.
cc @dauwhe @wareid
Casual drive-by question - is there any path forward for a non-ZIP container here? ZIP isn't great for streaming.
@cynthia there were lots of discussions in the past few years (although not as part of the EPUB Working Group) about using the Web packaging specs. Future versions of EPUB may very well adopt that specification in some way or other, but it is certainly too early to do that in the present version of EPUB.
Thanks for the great work on the Privacy and Security sections. The threat models and mitigations now look very comprehensive, and we appreciate the effort that went into these.
I had one question remaining around permission prompts, which is not blocking, but I hope to see the conversation continue.
Having completed our review, we are happy to see this move forward. Thanks!
Thank you, Amy.
Greetings and salutations, Technical Architecture Group of the World Wide Web Consortium!
I’m requesting a TAG review of EPUB 3.3.
EPUB 3.3 is a packaging mechanism for web content, designed for electronic books. In a nutshell, an EPUB is a zip package, containing an XML manifest file and XHTML5 content documents.
EPUB’s roots go back to 1999, with the OEB 1.0 specification from the Open Ebook Forum (which evolved into the IDPF) In 2007, a packaging format was introduced and OEB became EPUB 2.0. In 2011, EPUB 3.0 added support for XHTML5. Changes since then have been minor. The IDPF was absorbed into W3C in 2017, and responsibility for the maintenance of EPUB fell to the EPUB 3 Community Group, which released EPUB 3.2 in 2019 as a community group note. EPUB is twenty-one years old, but has never gone through the W3C Recommendation track, until now.
EPUB 3.3 consists of five specifications, three of which are normative and on the W3C Recommendation Track:
Spec URL: EPUB 3.3 Overview, a non-normative overview of EPUB 3.3
Spec URL: EPUB 3.3 Core, the specification of the file format
Spec URL: EPUB 3.3 Reading Systems, the specification for user agents, known as EPUB Reading Systems.
Spec URL: EPUB Accessibility 1.1, the accessibility specification that builds on WCAG.
Spec URL: EPUB Accessibility Techniques 1.1, a non-normative techniques document.
Tests: https://github.com/w3c/epub-tests
User research: none
Security and Privacy self-review: https://github.com/w3c/epub-specs/blob/main/epub33/explainers/EPUB-33-security-privacy.md. Note the Working Group met with PING on October 26, 2021, and work with them is ongoing.
GitHub repo (if you prefer feedback filed there): https://github.com/w3c/epub-specs
Primary contacts (and their relationship to the specification):
Organization(s)/project(s) driving the specification: none
Key pieces of existing multi-stakeholder review or discussion of this specification: none
External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): none
Further details:
You should also know that...
We’d prefer the TAG provide feedback as:
🐛 open issues in our GitHub repo for each point of feedback