A stable opaque token — a name, title, code, or identifier — is bound by an authoritative, recorded act to an entity and thereafter used to refer to it across contexts. The defining commitment is the decoupling of reference from description: the token's opacity (it refers, not means) is what gives it stability across renames, reattributions, and changes in description.
How would you explain it like I'm…
Giving It A Name
When you get a puppy, you give it a name like 'Rex,' and after that you just say 'Rex' instead of describing the brown furry dog every time. The name is a little tag that points to your puppy. Once it has a name, everybody can talk about that exact puppy without explaining which one.
A Label That Points
Appellation is when you assign a steady label — a name, title, code, or number — to a thing, and then use that label to talk about it everywhere. The big idea is that you no longer have to describe the thing each time; the name just points to it. The label is opaque, meaning its job is to point, not to describe — 'Max' doesn't tell you the dog is brown. Someone with authority, like a parent or a registrar, makes the assignment and usually writes it down, so there's a who and a when. And the name can travel into other systems that know nothing about the thing itself, so people can refer to it and connect records about it.
Name Instead Of Describe
Appellation is the pattern by which a stable token — a name, title, code, or identifier — is assigned to an entity within some authority's bookkeeping and thereafter used to refer to it across contexts. The defining commitment is decoupling reference from description: once an entity has an appellation, you can pick it out and track it without re-describing what it is each time. Three commitments travel with it. The token is opaque — its job is to refer, not to mean, so it doesn't describe its referent, only picks it out. The binding is authoritative and recorded — some designator (a registrar, a standards body, a parent) performs the assignment and writes it down, so the binding has a who, a when, and a warrant. And the token is portable across contexts — once assigned it can travel through systems that know nothing of the underlying entity, supporting joins, references, and citations. The token's opacity is exactly what gives it stability: because the name isn't about the entity's properties, it survives renames and changes in description, and references that route through it absorb those changes without breaking.
Appellation is the pattern by which a stable token — a name, title, code, or identifier — is assigned to an entity within some authority's bookkeeping and thereafter used to refer to that entity across contexts. The defining commitment is the decoupling of reference from description: once an entity has an appellation, it can be picked out and tracked without re-describing what it is each time. The token is short, the entity is whatever it is, and the binding between them is established by an authoritative act. Three structural commitments travel with the pattern. The token is opaque: its job is to refer, not to mean, so the appellation does not describe its referent but merely picks it out. The binding is authoritative and recorded: some designator — a registrar, a standards body, a committee, a parent — performs the assignment and typically writes it down, so the binding has a who, a when, and a warrant. And the token is portable across contexts: once assigned, it can travel through systems that know nothing of the underlying entity, supporting joins, references, citations, and cross-institutional coordination. The pattern recurs wherever a community needs to talk about that particular one repeatedly, across time and across systems, without re-establishing reference each time. Its force is that it concentrates the entire indirect apparatus of description, indexicals, and contextual hints into a single short token that any system can carry and resolve. The token's opacity is what gives it stability: because the appellation is not about the entity's properties, it survives renames, reattributions, and changes in description, and downstream references that route through it absorb those changes without breaking.
Separates the entity, the appellation, and the authoritative binding, making visible that disputes about names are usually disputes about the binding authority, and exposing the design choice between authoritative tokens and local re-identification.
Compresses a vast indirect referential apparatus into one short portable token, making federated joins and citation chains tractable and letting a system swap the underlying entity without touching downstream references.
Supports a reference-versus-description inference, an authority-conflict inference (two registrars binding the same token breaks federation at that join), a token-collision inference (flat schemes scale until collisions), and an indirection-benefit inference (referents are transparently substitutable).
Bibliography → many fields: the registrar/generator/uniqueness/lookup discipline ports to research-data and software citation and device identifier infrastructure.
Software → linked data: the reverse-DNS convention (a namespace tied to an authority's domain) ports to any setting where independent parties mint tokens without collision.
A newly described species receives a binomial under the governing code; because the name is not about the organism's properties, the species can be reclassified or moved to a new genus while citations routed through the prior name still resolve.
Appellation is not a Naming Convention because appellation is the individual binding act fixing one token to one entity, whereas a naming convention is the generative rule-set governing how all such tokens are formed.
Appellation is not Delegation of Authority because appellation establishes a referential handle and transfers no power, whereas delegation hands a right to act downward while the delegator stays accountable.
Appellation is not Identifier Assignment writ large because appellation foregrounds the christening act and its referential function, whereas identifier assignment foregrounds the resolution-and-durability infrastructure.