A system-level, machine-actionable identifier assigned to a digital or physical resource that is intended to provide a stable, resolvable reference over time by decoupling the resource’s identity from its current location or access URI and by relying on governed resolution infrastructure and management policies.

Principle

A persistent identifier functions by separating 'what' is identified (the resource identity) from 'where' it is served (its location); long-term reliability therefore depends on durable resolution services and explicit governance, not on the identifier’s syntax alone.

Demonstration

Illustrative scenario → A university dataset originally hosted at repository A is assigned a DOI. When the university migrates datasets to repository B, the DOI’s resolution metadata is updated to point to the new location. Users who cited the DOI before and after migration retrieve the dataset via the same DOI, preserving citation continuity.

Misapplication

Mistaken interpretation: treating any HTTP URL as a PID. Why plausible: many PIDs are expressed as HTTP URIs. Semantic error: conflating syntactic form with persistence guarantees—an ordinary URL lacks the policy, redirection maintenance, and governance that give a PID its persistence.

Consequence

Because references use stable identifiers rather than transient locations, citation integrity, automated linking, and long‑term metadata management become feasible; conversely, persistence depends causally on the continued operation of the resolution service and governing commitments, so loss of those elements can render the identifier non-resolving even if the identifier string remains unchanged.

Reversal

If the issuing authority discontinues resolution services, or if governance policies permit identifier reassignment, the expected stability fails; likewise, a PID does not by itself ensure content integrity or access (integrity requires checksums and access policy), so persistence of reference and persistence of accessible content are distinct.

Boundary

Clearly within: identifiers issued under a documented persistence policy with a resolution mechanism (e.g., DOI, ARK, Handle, community registries). Boundary case: a locally managed handle without long-term governance—technically resolvable now but with uncertain longevity. Clearly outside: ordinary HTTP URLs or file paths without persistence commitments or resolution infrastructure.

Semantic Tension

Stability ↔ Openness: allocating durable identifiers often requires centralized governance or funding commitments that can conflict with decentralizing openness or low-cost hosting models.

Synthesis

A PID is an infrastructural promise: its usefulness comes from institutional and technical commitments that sustain resolution and metadata, not from the identifier string itself; assessing a PID requires evaluating the underlying governance and resolution mechanisms.