-
Notifications
You must be signed in to change notification settings - Fork 63
Closed
Labels
EPUB33Issues fixed in the EPUB 3.3 revisionIssues fixed in the EPUB 3.3 revisionSpec-EPUB3The issue affects the core EPUB 3.X RecommendationThe issue affects the core EPUB 3.X Recommendation
Description
In the end, we only have two properties that don't meet the minimum two implementation threshold in the usage report:
- acquire
- xmp
The question now is what do we do with these? Despite our best efforts, we haven't turned up anyone using either of these properties, so they are better categorized as having no implementations rather than being under-implemented.
One possibility is that we remove both from the specification but leave them as valid in epubcheck:
- the acquire property is defined in the Previews specification which links to its definition in a 3.0.1 vocabulary. That makes it valid even if it is no longer in 3.3.
- the xmp doesn't have an equivalent spec that would make it valid, but we could leave it valid for historical reasons without continuing to promote it for use.
The alternative, of course, is to put "under-implemented" labels on them and leave them in the specification, but given that there are no known users of these properties, it's a bit of clutter that we arguably don't need.
Metadata
Metadata
Assignees
Labels
EPUB33Issues fixed in the EPUB 3.3 revisionIssues fixed in the EPUB 3.3 revisionSpec-EPUB3The issue affects the core EPUB 3.X RecommendationThe issue affects the core EPUB 3.X Recommendation