Move renditions terminology and requirements to multiple renditions document - #1448
Merged
Conversation
add rendition definitions, examples and requirements to multiple renditions specification; add a new background section to multiple renditions spec to explain their purpose; reduce overuse of the phrasing "of the EPUB Publication"; clean up the unique and release identifier sections; move release identifier processing to RS spec;
Member
Author
iherman
approved these changes
Dec 16, 2020
Member
There was a problem hiding this comment.
I believe something should be added to the changes section about the moving of multiple rendition into a separate document. This is, though editorial, a substantial change...
Member
Author
|
Right, I'm getting annoyed with putting those in right now as they keep causing merge conflicts with any other open pull requests that have entries. I'm going to add the change log text after merging until we get the open list of PRs back under control. |
Member
|
@mattgarrish maybe we should use the labels to see which PR-s affect which documents; with a growing number of PR-s this may become messy. We should also try to merge most of them before going FPWD... (Except for a11y, whose FPWD is later.) |
shiestyle
approved these changes
Dec 17, 2020
wareid
approved these changes
Dec 17, 2020
dauwhe
approved these changes
Dec 17, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR picks up from #1438 with a more complete rewrite of the specifications. The primary changes include:
Probably the key section to look at is the publication conformance: https://raw.githack.com/w3c/epub-specs/editorial/issue-1436/epub33/core/index.html#sec-epub-conf
I've tried to retain the original requirement of multiple packages each with its own package document and nav doc but without using the old terminology. There's also a note in the package document intro about multiple package documents being allowed.
The other key section is the container.xml file definition: https://raw.githack.com/w3c/epub-specs/editorial/issue-1436/epub33/core/index.html#sec-container-metainf-container.xml
The multiple renditions document has a couple of new sections to deal with material that is better explained in it: the section on expressing multiple renditions and the clarification that renditions can each contain unique metadata in their package documents.
Otherwise, the rest of the changes are primarily editorial in nature. Everything that was allowed before is still allowed, but this should make the core specification simpler to read.
Fixes #1436
Fixes #1442
Preview | Diff