Persistent-Identifier Resolution Policy¶
Resolution protocol — instantiates Carrier-Independent Work Identity Governance
Pins a stable identifier to the work and defines how it keeps resolving to the right thing through changes of location, format, custodian, and version.
A Persistent-Identifier Resolution Policy assigns a work a stable identifier decoupled from any physical location or carrier, and specifies the rules by which that identifier continues to resolve to the correct target as the world underneath it changes. Its distinguishing concern is the pointer, not the work: it does nothing to preserve the content itself, only to guarantee that the name keeps pointing to the right thing across moves, reformats, custodian handoffs, and versions — so a reference made years ago still lands. Where other mechanisms protect what the work is, this one protects the durability of what it is called.
Example¶
A scientist changes institutions three times, publishes across five journals, and has their name spelled four different ways. Anyone trying to assemble "their work" from names and homepage URLs fails — link rot and homonyms defeat it. A Persistent-Identifier Resolution Policy is what an identifier like an ORCID iD implements: the researcher holds one identifier, independent of any employer or publisher (the "carrier"), and the policy defines how it resolves — to a canonical record the researcher controls, which in turn points to the current homes of each output. The same policy governs the DOIs on the papers: a DOI resolves to a landing page, and when a publisher is acquired or a journal migrates hosts, the resolver is updated so the DOI still lands and the citation in a decade-old reference list keeps working. The policy also fixes what happens to a withdrawn paper — its DOI resolves to a tombstone that states the withdrawal rather than 404-ing or silently redirecting. The identifier, not the URL, is the durable name.
How it works¶
- Separate name from location — mint an identifier that names the work itself, not where it currently sits, so the carrier can change without breaking the name.
- Maintain the resolver record — keep an authoritative mapping from identifier to current target, and define exactly who is allowed to update it.
- Define resolution behavior across change — specify how the identifier resolves through moves, reformats, and custodian handoffs, and what it points to for superseded or withdrawn versions (latest, pinned, or tombstone).
- Make it the citation anchor — publish guidance that references cite the identifier rather than a volatile URL, so every reference inherits the resolver's durability.
Tuning parameters¶
- Granularity of identity — one identifier for the whole work versus a distinct one per version or manifestation (e.g., a concept identifier plus per-version ones). Finer granularity cites exactly but multiplies identifiers.
- Resolution target — always-latest versus pinned-version versus tombstone-on-withdrawal; the choice trades currency against citation stability.
- Update authority — who may repoint the resolver, and under what review. Loose authority keeps links fresh but invites hijacking; tight authority is safe but can go stale.
- Custodian durability — whether resolution depends on one organization or a federated/decentralized registry (e.g., a self-sovereign identifier) that survives any single custodian.
- Opacity — whether the identifier is human-meaningful or deliberately opaque, so it need never change when facts about the work change.
When it helps, and when it misleads¶
Its strength is that it is the direct defense against reference rot[n1] — the slow decay by which citations and links stop resolving as content moves — and it lets a work's identity outlive any particular host, custodian, or format. Named well, the identifier survives everything the carrier does.
Its failure modes hide behind the appearance of permanence. A persistent identifier is only as persistent as the institution and resolver behind it, so it can look eternal while quietly depending on a registry that may lapse, be defunded, or be captured. Loose update authority lets a resolver be silently repointed at a different target — the durable name now lending its authority to the wrong thing. And a stable identifier says nothing about whether the target still means the same thing; it can faithfully resolve to a work that has been gutted. The discipline is to fund and govern the resolver as long-lived infrastructure, log and constrain every repointing, and pair resolution with a semantic check so that a resolving link is never mistaken for an unchanged work.
How it implements the components¶
authority_and_resolver_record— its core: the authoritative identifier-to-target mapping, plus the rule for who may change it.reference_and_citation_guidance— it designates the identifier as the thing to cite, so references resolve durably instead of rotting with URLs.
It keeps the pointer valid but does not carry the work's surrounding context through a system move — that is Migration Context Preservation Plan — nor hold the authoritative statement of what the work is, which the Abstract Work Register maintains, and it displays no lineage, which the Version Lineage Graph does.
Related¶
- Instantiates: Carrier-Independent Work Identity Governance — provides the durable name that lets identity outlive its carrier.
- Consumes: Version Lineage Graph to know which version an identifier should resolve to; the Abstract Work Register for the authoritative work it names.
- Sibling mechanisms: Migration Context Preservation Plan · Version Lineage Graph · Abstract Work Register · Edition and Manifestation Catalog · Archival Provenance Metadata Template
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Persistent-Identifier Resolution Policy operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it pins a stable identifier to the work and defines how it keeps resolving to the right thing through changes of location, format, custodian, and version.
Independent corroboration: The frozen evidence defines Persistent-Identifier Resolution Policy as 'Pins a stable identifier to the work and defines how it keeps resolving to the right thing through changes of location, format, custodian, and version', so its operative form is Rule, Policy & Commitment.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Library & Information Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Persistent-Identifier Resolution Policy is rooted in library and information science: Identifier stewardship defines how a stable work identity survives custodial, format, version, and location changes.
Related originating lineages:
- Computer Science & Software Engineering — Computer science and software engineering materially shaped Persistent-Identifier Resolution Policy through algorithms, software architecture, security, and distributed systems. Indirection and resolver architecture materially shaped how persistent tokens continue to locate moving targets.
- Law & Governance — Law and governance materially shaped Persistent-Identifier Resolution Policy through rights, duties, due process, contracts, and institutional rules.
Review resolution: Both blind reviewers agree that library, archival, and information science is the primary origin. Reconciliation resolves alternate_origin_disagreement. Formative alternate lineages are retained as computer_science, law_governance; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
An identifier's persistence is a social and funding commitment far more than a technical one. The protocol — mint, map, resolve — is the easy part; the hard part is guaranteeing that some custodian will keep the resolver running for decades. A policy that specifies elegant resolution behavior but names no durable owner for the registry has described permanence without paying for it.
[n1] Link rot (and its scholarly cousin reference rot) — the progressive failure of URLs and citations to resolve as content is moved, reorganized, or taken down. Persistent-identifier systems exist precisely to break the dependence on location that causes it; the W3C maxim "Cool URIs don't change" (Tim Berners-Lee) states the same principle for the plain web. ↩