Skip to content

Glossary

Canonical identifier

A canonical identifier is a stable reference assigned to one resolved entity within a defined identity system.

Identity and entity resolution

A canonical identifier is a preferred handle for an entity after identity decisions have been made. Its value should remain stable when display names or attributes change. The identifier's namespace and issuer matter: the same string in two namespaces may refer to different entities, while two identifiers can legitimately refer to the same entity under different schemes. The identifier labels a decision about identity; it does not prove it.

In practice, canonical identifiers link source records, claims and revisions to a persistent subject. External identifiers can be retained as cross-references with their issuing schemes and validity periods. If a false merge is later corrected, the mapping history should show which records moved and which claims were affected. Reusing an identifier for a different entity would make older references ambiguous.

For a defensible record, a stable identifier lets a reviewer follow the same subject across time while inspecting changes to the evidence. Entity resolution establishes the referent; the canonical identifier names it; a golden record presents its selected attributes. An identifier is therefore a continuity device, not an independent statement of factual correctness.

Example

Fictional Halden Therapeutics AG keeps the same internal canonical identifier after a spelling correction, while its original registry identifier remains recorded separately.

Properties of a good identifier

A canonical identifier needs to be unique within its system, stable over time, never reused for a different entity, and independent of any attribute that can change. An identifier built from a name or an address fails the last test, since both change. The W3C guidance on cool URIs makes the same point for web addresses: names should not carry information that will change, and a published identifier is a commitment to keep it working. Generic syntax for identifiers is set out in RFC 3986, and RFC 9562 defines the universally unique identifier formats that many systems use to mint identifiers without central coordination.

Many domains already have public identifiers, and a system should map to them without replacing its own. For organisations, the Legal Entity Identifier maintained under GLEIF and the Research Organization Registry identify legal entities and research institutions; for researchers, ORCID identifies individuals; for publications, the DOI system described in the DOI Handbook provides persistent links. A local canonical identifier can hold these as external identifiers, each with the issuing authority and the date it was confirmed.

Identifier lifecycle: split, merge and retire

The hard problems arise when identity decisions change. If two entities were wrongly merged, one identifier must be split into two; if two identifiers were found to denote the same entity, they must be merged. In both cases the old identifier must continue to resolve, with a record of what happened, because other systems and documents refer to it. The usual approach keeps the old identifier as a redirect or a deprecated alias that points to the successor or successors, with a date and a reason, and never reassigns an identifier to a different entity. The article on identifier versioning after corrections examines these cases for graphs in detail.

Treat an identifier as a claim of identity, not as the entity. A record that cites an identifier on a date is making a statement that depends on the identity system's state on that date, which links the topic to point-in-time reproducibility: to reproduce an earlier result one needs to know which entities the identifier denoted then.

A worked example

A system assigns the identifier org-1001 to Halden Therapeutics AG (fictional) and org-1002 to Halden Pharma GmbH, believing them separate. Later review finds that the second record describes a former name of the first. The system marks org-1002 as merged into org-1001 on a stated date, with the reviewer and reason, and keeps org-1002 resolvable with a pointer to org-1001. Documents that cited org-1002 remain valid and are interpreted through the redirect. An as-of query for the date before the merge still returns two entities, because the system holds the history of its own identity decisions. Had the system deleted org-1002, every earlier citation would have become unresolvable.

Checks a reviewer can run

Ask whether any identifier has ever been reused for a different entity; the answer should be never. Ask what happens to a citation of a merged identifier; it should resolve with a visible redirect. Ask whether any identifier embeds a name or address; it should not. Ask whether external identifiers carry their issuing authority and the date of confirmation. Ask whether the identity system itself is versioned, so that the mapping on a past date can be recovered.

Related terms and boundaries

The identifier is the output of entity resolution and the key of a golden record. It supports record linkage across systems by giving them a shared reference, and it is distinct from a content digest, discussed under content addressing, which names bytes and not entities.

Common misreadings

  • Reusing an identifier after a split or deletion.
  • Treating a matching string across namespaces as a match.
  • Assuming an identifier alone validates every attribute.

Related terms

Appears in

Found an error on this page? See corrections for what counts as one, how to report it and the dated log.

Enquiry

Where does "Canonical identifier" bear on a decision of yours?

This entry sits under identity and entity resolution. If a decision in your organization turns on it, send the entity concerned, the sources you fuse to describe it and who may read which of them. We reply with what a first record would cover.

Or write to [email protected] in your own words.