Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify that ocf processing files are not listed in the manifest #2506

Merged
merged 2 commits into from
Dec 30, 2022

Conversation

mattgarrish
Copy link
Member

@mattgarrish mattgarrish commented Dec 16, 2022

As raised in w3c/epubcheck#1452, I don't know that we can ever perfectly clarify what publication resources are, but PR makes clear that the mimetype file and meta-inf files are not, so they are not listed in the manifest.

That should make the statement about the manifest only listing publication resources redundant, as the other cases are now explained (linked resources and the above files).

There will still be impossibilities for epubcheck to determine, like whether a publication resource without any reference to it is intentionally travelling in the container or was forgotten to be removed, but as noted in the epubcheck issue we can add usage messages to flag those.


Preview | Diff

@rdeltour
Copy link
Member

See also #2413, for reference.

Copy link
Member

@rdeltour rdeltour left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. I like that this removes a normative statement that cannot be checked.

epub33/core/index.html Outdated Show resolved Hide resolved
@mattgarrish mattgarrish merged commit 5c53746 into main Dec 30, 2022
@mattgarrish mattgarrish deleted the fix/manifest-rules branch December 30, 2022 20:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants