#816: CR Snapshot Review for EPUB 3.3

Visit on Github.

Opened Feb 13, 2023

こんにちは TAG-さん!

I'm requesting a TAG review of EPUB 3.3, EPUB Reading Systems 3.3, and EPUB Accessibility 1.1.

A review of these specifications was completed mid-way through 2022, but as we approach PR we have been asked to get another review and sign off for our latest CR snapshot. You can review the change logs for each document (linked below), but the majority of the changes made since last review have been editorial clarifications of existing features, additions based on review (specifically our addition of the Security and Privacy sections for each document), and clarifications based on test results.

Further details:

  • I have reviewed the TAG's Web Platform Design Principles
  • Relevant time constraints or deadlines: We plan to publish our CR Snapshot on February 21st, then go to PR on April 11 barring any issues.
  • The group where the work on this specification is currently being done: EPUB 3 Working Group
  • Major unresolved issues with or opposition to this specification: None

You should also know that...

We appreciate your feedback!

We'd prefer the TAG provide feedback as (please delete all but the desired option):

🐛 open issues in our GitHub repo for each point of feedback

Discussions

Comment by @wareid Feb 14, 2023 (See Github)

Changes we think will be of interest to the TAG: EPUB 3.3

  • 11-Jan-2023: Marked the dir attribute under-implemented due to lack of support in reading systems. See pull request 2515.
  • 18-July-2022: The viewport meta element for specifying the initial containing boundary in fixed-layout documents is now formally defined. See issue 2292.
  • 07-June-2022: The usage of File URLs has been disallowed. See issue 2324.
  • 07-June-2022: Updated privacy and security recommendations to use normative language. See pull request 2297.
  • 27-May-2022: Added recommendation to only reference remote resources via https. See issue 2263.

EPUB Reading Systems 3.3

  • 06-Jan-2023: Reduced the requirement to support prefixed CSS properties to a recommendation. See pull request 2514.
  • 22-July-2022: The name and version properties of the epubReadingSystem object have been deprecated. See issue 1872.
  • 07-June-2022: The usage of File URLs has been disallowed. See issue 2324.
  • 07-June-2022: Noted that unsigned EPUB publications represent a security risk and added recommendation to treat sideloaded unsigned publications as untrusted. See issue 2265.
  • 07-June-2022: Updated privacy and security recommendations to use normative language.
  • 27-May-2022: Added reading system conformance section. See issue 2271.
  • 27-May-2022: Added recommendation to only load remote resources referenced via https. See issue 2263.

EPUB Accessibility 1.1

  • 07-June-2022: Updated privacy and security recommendations to use normative language.
Discussed Feb 27, 2023 (See Github)

Amy: the've left a list of issues and PRs... I'm asking if they can do a tiny bit more work...

Thanks for the summary list of changes for us to review. 

We appreciate the strengthening of the security and privacy sections.

We're finding it difficult to review the other changes based on links to PRs and issue discussions however. We'd like to be able to provide meaningful feedback that is useful to the WG. Could you put together a small explainer for the important changes, including what user needs have been addressed by them and why you ended up with the solutions you did? And if you have any specific questions or sections of the spec(s) it would be useful for us to focus on, could you let us know that as well?

Dan: lgtm

Comment by @rhiaro Feb 28, 2023 (See Github)

Thanks for the summary list of changes for us to review.

We appreciate the strengthening of the security and privacy sections.

We're finding it difficult to review the other changes based on links to PRs and issue discussions however. We'd like to be able to provide meaningful feedback that is useful to the WG. Could you put together a small explainer for the important changes, including what user needs have been addressed by them and why you ended up with the solutions you did? And if you have any specific questions or sections of the spec(s) it would be useful for us to focus on, could you let us know that as well?

Discussed Mar 6, 2023 (See Github)

Amy: no response back yet

Comment by @wareid Mar 16, 2023 (See Github)

@rhiaro Apologies for the massive delay on this, I was trying to come up with an explanation for the other items.

To be honest, none of the changes we have made have been particularly significant, many involve reacting to test results. Since the overall work on EPUB 3.3 has been refining the specs as opposed to introducing new features, our changes have been incremental.

Discussed Mar 27, 2023 (See Github)

Dan: wendy got back to us - we could take this at face value and close.

Hadley: if we do that we could say "we don't have enough info".

Dan: can you leave that comment and set to "out of scope"? And close.

Hadley: OK.

closed

Comment by @hadleybeeman Mar 28, 2023 (See Github)

Hi @wareid et al! Given that you've told us that 3.3 contains only incremental changes, we surmise that there are no new architectural issues — so we we won't do a TAG review.

Best of luck with this work, and do come back to us if there is anything we can help with.

Comment by @wareid Mar 29, 2023 (See Github)

@hadleybeeman Thanks so much! Much appreciated.