Repository navigation
RFC 085: Identifiers of and within IIIF resources after the migration - #143
Merged
Merged
Conversation
Review notes on the #159 comment thread: the preservation-identifier-canonical outcome, constraints on the form of new preservation ids, the workId redirect contract, and open questions for the RFC 091 rewrite. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The id-form concern splits in two: the Identifiers API absorbs the metadata half (source system, canonical id, deferral instead of shape inference), but the structural half (sub-package suffix parsing, CALM underscore ambiguity, path/case constraints) is inherently local to DDS since RFC 089 stops at the work level. Also records that the registry cannot hold merge-redirect results, and that the DDS CatalogueId refresh has been addressed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Aug 5, 2026
tomcrane
marked this pull request as ready for review
August 7, 2026 14:08
kenoir
approved these changes
Aug 12, 2026
kenoir
left a comment
Contributor
There was a problem hiding this comment.
Good to go, I think we're aligned now.
If you are happy I will merge?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This RFC has been rewritten to record the direction agreed in the RFC 091 discussion (#159); amending RFC 085 was a named deliverable of that RFC.
The earlier version of this RFC proposed making the catalogue Work ID the canonical URI for IIIF Manifests and Collections, with b-number and CALM forms redirecting to it. The RFC 091 review reversed that: the preservation identifier stays the canonical IIIF URI, for old and new content alike, and the Work ID only ever appears as a redirect source.
Much of the original analysis, in particular Canvas IDs and annotation targets, which IIIF clients string-match inside the JSON and which can therefore never be redirected, turned out to be the argument for the reversal, so it is retained as the rationale.
The rewritten RFC covers:
cross-migration and post-migration, Folio- and Axiell-catalogued). For all existing content the migration is invisible: every
published URI stays exactly as it is.
RFC 091 open questions: