Persistent Identifier Resolver¶
Resolution tool — instantiates Identity-Bounded Change
Gives an entity one permanent identifier and resolves it to wherever the current authoritative version now lives, so the name survives every move and revision.
References break when they point directly at where something is — a URL, a filename, a shelf location — because the thing moves, gets renamed, or is superseded, and every citation to the old address goes dead. Persistent Identifier Resolver breaks that coupling: it assigns the entity one permanent, opaque identifier and maintains a live mapping from that identifier to the entity's current authoritative home, so holders of the identifier resolve it to reach the real thing rather than navigating to a fixed address. Its defining move is a layer of indirection — the identifier never names a location, it names the entity, and when the entity moves or is revised, the mapping is updated while the identifier stays fixed. The name is stable precisely because it was deliberately decoupled from address, owner, storage, and version.
Example¶
A research group publishes a dataset and is issued a DOI — say 10.xxxx/climate-2031. Over the next several years the dataset migrates from a university server to a national repository, its landing-page URL changes twice, and the group releases three revised versions as errors are corrected. A journal article cites the DOI.
Years later a reader follows that citation and lands exactly where they should — the resolver redirects the DOI to the dataset's current authoritative page, even though every underlying URL from the original publication is now dead. If the reader needs the exact release the article analyzed, a version-tagged identifier resolves to that specific frozen version rather than the moving "current" one. One permanent name absorbs all the churn beneath it; the raw links rot, the identifier does not.
How it works¶
- Mint a location-independent identifier. The identifier is opaque and says nothing about where the entity is stored, who owns it, or which version is current.
- Keep a resolution mapping, not a hard link. A registry holds identifier → current authoritative target; readers hit the identifier and are forwarded.
- Update the mapping, never the identifier. When the entity moves or is revised, the registry entry changes and every existing reference keeps working untouched.
- Address versions explicitly. Version-tagged identifiers resolve to exact releases; the bare identifier resolves to whichever version is designated current.
Tuning parameters¶
- Identifier opacity — how much meaning the string carries. Fully opaque identifiers survive reorganization and renaming; human-readable ones are convenient but tempt people to parse and hard-code them.
- Resolution granularity — whether an identifier resolves to the whole entity, to a specific version, or to a particular rendition. Finer addressing improves reproducibility but multiplies the identifiers to mint and maintain.
- Default-target policy — whether a bare identifier points at "latest" or at the version originally registered. Latest keeps citations fresh; frozen keeps them reproducible.
- Governance and update SLA — who is authorized to change a mapping and how promptly moves are reflected. Slow or contested updates quietly reintroduce the breakage the resolver exists to prevent.
When it helps, and when it misleads¶
Its strength is that it defeats link rot: the entity can move between systems, change owners, and issue revisions without orphaning a single reference, because the identifier is the one thing that never changes.[n1] That makes the identifier itself the stable anchor other mechanisms can attach obligations, citations, and continuity decisions to.
Where it misleads is subtle. "Persistent" is a governance promise, not a technical property — an identifier is only as durable as the institution running the resolver, so a string that looks permanent rots the moment the registry lapses. And its sharpest misuse is repointing an identifier to a non-continuous successor: because the identifier stays the same, silently redirecting it to a different entity launders citations, trust, and obligations onto something that is not the thing originally named. The discipline that keeps it honest is to treat repointing as an identity decision, not a bookkeeping edit — mint a new identifier for a genuine successor and record the relation, rather than quietly resolving the old name to new content.
How it implements the components¶
persistent_identity_binding— mints and holds the single permanent identifier that stands for the entity independently of its location, owner, state, or version.source_of_truth_reference— resolution forwards the identifier to the current authoritative copy, making the identifier the canonical route to the real thing.version_identifier— supports version-tagged identifiers that resolve to an exact release alongside the moving "current" target, keeping version identity separate from persistent identity.
It does NOT record what changed between those versions (change_log, versioned_subject) — that is Document Revision History and Version Control System; and it does NOT judge whether the entity stayed the same across the changes it points to (identity_continuity_test) — that belongs to Identity Continuity Review.
Related¶
- Instantiates: Identity-Bounded Change — provides the stable identity anchor that lets an entity move and be revised without breaking the references that depend on it.
- Sibling mechanisms: Document Revision History · Version Control System · Chain-of-Custody Record · Legal Amendment Record · Policy Amendment Register · Split/Merge Change Log · Event-Sourced Entity History · Conservation Treatment Record · Identity Continuity Review · Replacement or Fork Decision Record
Editorial Notes¶
Form Classification¶
Form family: Control, Automation & Runtime
Rationale: Persistent Identifier Resolver operates as a live operational control that automatically routes, enforces, adapts, or responds during execution because it gives an entity one permanent identifier and resolves it to wherever the current authoritative version now lives, so the name survives every move and revision.
Independent corroboration: The frozen evidence defines Persistent Identifier Resolver as 'Gives an entity one permanent identifier and resolves it to wherever the current authoritative version now lives, so the name survives every move and revision', so its operative form is Control, Automation & Runtime.
Nearest alternative: Structure, Architecture & Configuration — Persistent Identifier Resolver includes features of a configured physical, technical, or logical arrangement whose structure creates the effect, but its defining operation is a live operational control that automatically routes, enforces, adapts, or responds during execution.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Library & Information Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Persistent resolution was institutionalized through bibliographic, archival, and digital-object identifier systems.
Related originating lineages:
- Computer Science & Software Engineering — Persistent Identifier Resolver is rooted in computer science and software engineering: Networked resolver architecture implements stable-name-to-current-target indirection against link rot. Network naming and indirection supplied the live mapping and resolution machinery.
Review resolution: Light authoritative-source research resolves the primary-origin disagreement in favor of library, archival, and information science. DOI Handbook: Identifier and Resolution Services directly documents the defining practice or theory described in the selected origin rationale. Other listed domains are retained only where the blind reviews identify material co-development or translation; broader adoption remains separate as domain_reach=multi_domain.
Attribution caveat: The boundary with computer science and software engineering is real because that field materially developed or translated the practice, but the cited provenance places the defining form in library, archival, and information science.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
The resolver holds identity binding, not continuity judgment. It can resolve an identifier to whatever is currently designated authoritative, but it cannot tell whether that designation is justified — whether the current target is truly the same entity or a replacement that was quietly slotted in. Keeping the binding (this mechanism) separate from the continuity test (Identity Continuity Review) is what prevents a stable-looking identifier from silently laundering a replacement as a continuation.
[n1] Link rot (or reference rot) is the steady decay of direct references — URLs, paths, locations — as their targets move or disappear. Persistent-identifier systems such as the DOI and Handle schemes exist specifically to defeat it by resolving a fixed name to a maintained, updatable target rather than to a raw address. ↩