Skip to content

Manifest properties requirements duplicative and contradictory #2030

Closed

Description

@mattgarrish

This statement in the item element's definition contradicts the requirements in the vocabulary:

EPUB Creators MUST declare all applicable descriptive metadata properties for each Publication Resource in this attribute (e.g., if the resource is the cover image, contains scripting, or references remote resources).

It's true of all but the cover-image, which doesn't have to be identified. This is the problem that typically arises when we make the same requirements in different places. It feels like we should make this informative (possible a note?) and refer to the vocabulary for the requirements.

Same goes for the next sentence that requires the nav property be set, which technically means we require it be set three times (the paragraph above requires it as does its definition).

Activity

  1. mattgarrish commented on Mar 5, 2022

    @mattgarrish
    MemberAuthor

    Or perhaps a new subsection on resource properties would be a better solution.

    We could list the requirements for setting the properties here rather than having them buried in a vocabulary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    EPUB33Issues fixed in the EPUB 3.3 revisionSpec-EPUB3The issue affects the core EPUB 3.X Recommendation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions