Identifier¶

Version: v3 · 2026-09-28 · History
Prime #: 1596
Domain group: Applied Sciences & Engineering
Origin domain: Computer Science & Software Engineering
Subdomains: Databases, Data Modeling → Computer Science & Software Engineering
Also from: Library & Information Science

Core Idea¶

An identifier is a sign or finite symbol sequence assigned within a declared scheme to distinguish an entity, class, or record so an intended resolver can recover the reference consistently. Its structure combines a referent, token, namespace, assignment, resolver, and rules for collision, persistence, aliases, and reassignment. The token may be meaningful or opaque, and it may identify a class or one instance. Identifier is a strict kind of Representation because it adds governed distinction and resolution to the broader standing-for relation.

How would you explain it like I'm…

The Which-One Name

An identifier is a special name or number that tells things apart. In your class, two kids might both be named Sam, so the teacher says "Sam R." and "Sam T." Now whenever someone says "Sam T.," everyone knows exactly which Sam they mean.

A Label That Picks One

An identifier is a label, like a name, number, or code, used to pick out one particular thing from others so that everyone points to the same thing. Your library card number, a jersey number on a sports team, and a house address are all identifiers. An identifier works inside a certain place or system: jersey number 7 means one player on your team, but another team has its own number 7. There also have to be rules for handing out labels and for what happens if a label is reused. The label itself doesn't need to describe the thing; it just needs to point to it clearly.

Scoped Unique Labels

An identifier is a sign or string of symbols used within a defined system and scope to single out one entity, category, or record from the alternatives, so that references to it can be resolved the same way every time. It has several working parts: the thing being identified, the token (the name or code), the scheme that hands out tokens, a scope in which duplicates are prevented, and rules for how long the assignment lasts and whether a token can be reused. Your student ID, a book's ISBN, a variable name in a program, and a species' scientific name all fit this pattern. Identifiers are a kind of representation, but a narrower one: a picture of a thing represents it without necessarily distinguishing it from everything else. The key test is the assignment link: if nothing ties a token to a specific referent, it's just a symbol, not an identifier.

An identifier is a sign or finite symbol sequence used within a declared scope and scheme to distinguish one entity, class, or record from alternatives so that references to it resolve consistently. It can be a word, number, letter, symbol, or combination, and it can label a unique instance or a unique class, whether the referent is a person, a physical object, a substance, an idea, or a data record. Its constitutive structure joins a referent, a token, and an identification scheme and namespace, completed by an assignment relation from token to referent. A scope in which collisions are controlled governs how the token may be interpreted, and persistence and reassignment rules determine whether the binding still holds, for example whether a retired phone number can be given to someone else. Its genus is representation, but identifiers add a narrower invariant: the point is discrimination and consistent resolution, not depiction, so a descriptive portrait represents without identifying. Note that the abbreviation "ID" is ambiguous, sometimes meaning identity, sometimes the process of identification, and sometimes an identifier. The test for a genuine identifier is counterfactual: remove the assignment from token to referent and the case should collapse into something else, such as a mere string or description.

Broad Use¶

Database keys resolve records; docket and registration numbers resolve governed legal objects; accessions distinguish specimens and sequences; network addresses distinguish endpoints within protocol scopes; DOIs identify scholarly objects while their current locations change; and part versus serial numbers distinguish a design class from a produced instance. These uses share the same token–referent assignment even though their authorities, media, granularity, and lifetime rules differ.

Clarity¶

A clear claim states the exact referent granularity, token, issuing scheme, namespace, assignment authority, resolver, uniqueness scope, and lifetime. “Unique” without a universe and interval is incomplete. A repeated label can describe several items without identifying any one; an opaque random value can be an excellent identifier when a governed lookup binds it reliably. The same string may legitimately resolve different referents in different namespaces.

Manages Complexity¶

Identifier replaces a potentially complex referent with a compact handle while moving ambiguity management into the scheme. That makes storage, citation, exchange, and retrieval tractable, but it also exposes design choices: centralized versus distributed issuance, readable versus opaque syntax, persistence versus reuse, and local versus global scope. Collisions, aliases, mergers, splits, and corrections are not marginal anomalies; they test whether the scheme can preserve intended reference through change.

Abstract Reasoning¶

First fix whether the target is a class, instance, record, event, or changing object. Next identify the token and its normalization rules, then declare the namespace and assignment authority. Show how an intended resolver recovers the target and adjudicates aliases or collisions. Finally inspect time: can the token be retired, redirected, or reassigned? As a collapse test, remove the assignment relation. If the mark remains just as useful, it was likely a description or decoration rather than the identifier doing the distinguishing work.

Knowledge Transfer¶

The transferable cargo is the governed mapping referent ← assignment → token inside a namespace, completed by a resolver and lifecycle policy. It maps literally from a database key to a specimen accession, docket number, serial number, network address, or DOI. Transfer stops when only the symbol moves: printing a DOI-like string on an unrelated object does not import its registry assignment, and a descriptive category code need not resolve any instance. If only standing-for remains, reduce the comparison to the parent Prime Representation.

Example¶

Within namespace N, assignment f maps token i to referent x under declared uniqueness and lifetime rules. Another namespace may reuse i without collision, and x may have aliases. A DOI supplies a concrete instance: the registered string remains assigned to a scholarly object while resolver metadata can change its current URL. Here the object is the referent, the DOI is the token, the registration agency governs assignment, and the resolver plus persistence policy completes identification.

Relationships to Other Abstractions¶

Current abstraction Identifier Prime

Parents (1) — more general patterns this builds on

Identifier is a kind of Symbolic Representation Prime

Identifier is the Symbolic Representation species whose conventional sign sequence distinguishes and resolves one entity, class, or record within a declared scope and scheme.

Children (3) — more specific cases that build on this

Regnal number Domain-specific is a kind of Identifier

A regnal number is a scoped name-plus-ordinal identifier resolved through office, realm, or house reckoning.
Smart number Domain-specific is a kind of Identifier

A smart number is a unique identifier that additionally encodes information about its entity.
U-Form Domain-specific is part of Identifier

U-Form contains Identifier as a constitutive part because its immutable UUID is an internal identifier that carries object identity across mutable attributes and replicas.

Hierarchy path (1) — routes to 1 parentless root

Identifier → Symbolic Representation → Representation → Abstraction

Not to Be Confused With¶

Representation. A representation can stand for something without distinguishing it from alternatives in a namespace; an identifier adds scoped assignment and resolution.
Name. A name can be shared, descriptive, social, or honorific. It becomes an identifier only when a practice uses it to resolve a target and govern ambiguity.
Code. A code can communicate a category, attribute, or instruction without identifying a referent. Some codes are identifiers, but encoding meaning is neither necessary nor sufficient.
Address. An address is often a specialized identifier with a routing or location function; dynamic reassignment shows why present address and persistent identity can diverge.
Label. A label may describe or decorate many items. It identifies only when its use participates in a distinguishing scheme.