Tensions in Practice: Readable handles in tension with stable reference¶
A hypothetical catalog renames one item
A catalog item changes its name from Oak to Pine. If the name itself is the lookup key, an old saved reference can stop working. A separate opaque handle, Q7, can keep pointing to the same item while a registry updates its description. The handle survives because it never meant Oak—but it now needs that registry to tell a reader what it denotes.
Recognize an item from its key
Make references understandable without a separate lookup.
Keep references through renames
Separate an entity’s identity from a mutable description.
Why these aims pull against each other
Descriptive keys save interpretation work but couple reference to the description; an opaque key transfers that work to maintained resolution.
Choose an arrangement to see what changes and what remains difficult.
Arrows express the declared relations, not measured effect sizes. Examples and quantities are illustrative.
What this choice protects
What it costs
When it fits
Compare the arrangements
Use the name as the key
Derive the current lookup key from the current item name.
- What it protects
- The key is directly readable.
- What it costs
- After a rename, saved old keys need repair or an additional alias mechanism.
- When it fits
- Names remain stable enough, or reference updates are affordable and controlled.
Illustration note: The example excludes redirects to isolate the dependency; real systems can add them at a cost.
Resolve a stable handle
Mint Q7, record its binding, and update the bound item’s name.
- What it protects
- Saved Q7 references do not need to change for this rename.
- What it costs
- The registry must preserve uniqueness, availability and a correct binding.
- When it fits
- A responsible authority maintains the record and resolution protocol.
Illustration note: Q7 is an illustrative opaque token, not a proposed identifier standard.
What this illustration does—and does not—establish
The source supplies the stated tension; the selected arrangements are bounded editorial illustrations. Costs and conditions remain part of the comparison.
- Stable reference is not proof that the underlying record is correct or authorized.
- Mergers, splits and changes of identity need additional policies; a rename alone does not test those policies.
- A name plus a permanent alias is a different managed arrangement, not evidence that all descriptive references must break.
Source entries
Identifier Assignment
This source passage supplies the contextual tension. The concrete arrangements and schematic examples are editorial illustrations, not measured findings.
Opaque versus Descriptive Handle (sign/direction)
T1 — Opaque versus Descriptive Handle (sign/direction). Opacity is the prime's load-bearing virtue — a handle that carries no description survives renames — but opaque handles force a lookup for any fact and reveal nothing on inspection. Descriptive or hierarchical handles save lookups but break the moment the encoded meaning changes.
The source operation
Identifier assignment is the act of minting a durable handle for an entity and binding that handle to the entity in a public, queryable record, so that future reference to the entity can route through the handle without re-describing it each time.