KEMBAR78
epub:type restriction that's outlived its usefulness · Issue #2070 · w3c/epub-specs · GitHub
Skip to content

epub:type restriction that's outlived its usefulness #2070

@mattgarrish

Description

@mattgarrish

These statements date from a time when we thought assistive technologies might use epub:type semantics like ARIA roles:

The inflected semantic MUST express a subclass of the semantic of the carrying element. In the case of semantically neutral elements, such as the [HTML] div and span elements, the inflected semantic MUST NOT attach a meaning that is already conveyed by an existing element (e.g., that a div represents a paragraph or section).

We have recommendations on what elements to use the semantics on in the structure vocabulary, but these have never been enforced and were always meant as guidance. In other words, they don't even bear out these requirements.

I don't see the harm in making these statements informally, so switch these to lowercase should/should not.

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