Skip to content

Remove release identifier#1453

Merged
mattgarrish merged 4 commits intomasterfrom
editorial/issue-1440
Jan 4, 2021
Merged

Remove release identifier#1453
mattgarrish merged 4 commits intomasterfrom
editorial/issue-1440

Conversation

@mattgarrish
Copy link
Member

@mattgarrish mattgarrish commented Dec 24, 2020

This PR fixes #1440 as follows:

  • Removes references to the release identifier from the core specification leaving only a section labelled "last modification date" with the same requirements. Adds a note for future generations about the release identifier to explain why these requirements exist as there's no other context for them.
  • Removes all reference to creating a release identifier from the reading system specification.
  • Removes explanation of release identifier from the overview.
  • Removes the sections on the release identifier from the multiple renditions document and moves the requirements for the unique identifier and last mod date into the publication metadata section.

Preview | Diff

leave note in last modification date about relationship to release identifier in older versions of epub 3
@iherman iherman self-requested a review December 25, 2020 12:44
@mattgarrish mattgarrish merged commit 1dfc72d into master Jan 4, 2021
@mattgarrish mattgarrish deleted the editorial/issue-1440 branch January 4, 2021 14:02
iherman added a commit that referenced this pull request Mar 8, 2021
Per [WG resolution](https://www.w3.org/publishing/groups/epub-wg/Meetings/Minutes/2020-12-18-epub#resolution2) the statement on unique identifiers should not be normative.

I also propose an editorial change: after PR #1453 only the `unique-identifier` property is relevant as an identifier, so I created a new section on the package conformance to handle only that case and removed the old one that was a leftover of a time when we also had release identifiers.

Fixes #1310
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.

Release identifier construction informative?

2 participants