How English Works | The Registry

A spreadsheet can contain a list.

A database can contain records.

An index can help us find them.

None of those facts alone makes the collection a registry.

A registry carries an additional promise:

These are the recognised assignments according to this authority, under these rules, at this time.

That promise changes the job of the language.

Who may add an entry?

What evidence is required?

Can two people receive the same value?

Can an assignment be changed?

What happens when an entry is obsolete?

Which document defines the meaning?

A registry is not merely a pile of names.

A registry is a maintained public memory of recognised assignments.

Quick Read

One-sentence answer: a registry works when a recognised authority maintains unique or otherwise controlled assignments under explicit registration rules, preserves enough provenance and references to explain each entry, and changes the registry in a way that keeps past and present users coordinated.

IANA provides one of the clearest large-scale real-world examples. Its protocol registries coordinate globally unique identifiers used across Internet protocols. IANA tells applicants to check the specific registry’s registration procedures and reference documents, while RFC 8126 defines common policy models for how values may be allocated.

This gives us the registry’s main architecture:

registry: the bounded set of recognised assignments;
entry: one recorded assignment;
authority: who maintains the registry;
policy: what process admits or changes entries;
identifier or value: what is being assigned;
reference: where the assignment’s meaning is documented;
status: active, reserved, temporary, deprecated or another defined state;
history: the trace of changes over time.

The Registry Is Not the Index

An index answers:

Where can I find the item?

A registry answers:

Which assignments are officially recognised in this naming or value system?

An index can list documents it discovers automatically.

A registry normally needs admission rules.

index = retrieval structure
registry = authoritative assignment structure

This keeps Registry separate from eduKateSG’s existing How Indexing Works.

The Registry Is Not the Database

A registry may be stored in a database.

The database is the storage technology.

The registry is the governance meaning placed on the records.

A database table can accept any row permitted by its schema.

A registry may require:

review;
evidence;
approval;
uniqueness checks;
defined references;
change history.

database tells us how records are stored
registry tells us why an assignment is recognised

The Registry Is Not the Namespace

A namespace creates a scope in which names can be unique.

A registry records which names or values have actually been assigned inside that scope.

Namespace:

media-type names

Registry:

the maintained list of recognised media-type assignments and their references

The namespace defines the naming world.

The registry maintains its admitted inhabitants.

namespace = available naming space
registry = controlled assignment history inside a naming space

An Entry Needs More Than a Name

Weak registry row:

42 — Example

What does Example mean?

Who registered it?

Which specification defines it?

Is it current?

A stronger entry may contain:

assigned value;
official name;
description;
reference document;
registration date;
status;
contact or change controller where appropriate.

The exact fields depend on the registry.

The principle is stable:

an authoritative assignment needs enough context to remain interpretable after the original registrant is gone

Authority Has to Be Explicit

Imagine three websites each publish a “global registry” of the same code values.

The lists disagree.

Which one governs?

The word registry does not create authority by itself.

Authority can come from:

a standard;
a contract;
a government mandate;
an industry body;
a protocol specification;
an organisation’s internal governance.

registry authority is a relationship between a maintained list and the community that agrees to treat its assignments as controlling

Registration Policy Controls the Gate

RFC 8126 describes several familiar registration policy models.

They differ in how much review is required before an assignment becomes recognised.

At one end, a registry may use a relatively lightweight process such as First Come First Served.

At another, it may require Expert Review, Specification Required, Standards Action or another higher-threshold process.

These are not mere administrative styles.

They reflect the cost of a bad assignment.

the scarcer or more consequential the namespace, the stronger the admission gate may need to be

First Come First Served Optimises Availability

Suppose values are plentiful and collisions are the main risk.

A lightweight policy can say:

If the requested value is available and the submission meets the required form, assign it.

This keeps the barrier low.

The trade-off is limited substantive review.

The registry may verify uniqueness without endorsing the wisdom of the design.

registration can mean “recognised assignment” without meaning “best practice”

Expert Review Adds Judgement at the Gate

Some registries need a knowledgeable reviewer to assess whether a proposed assignment is suitable.

The expert may ask:

Is the documentation adequate?
Does the request duplicate an existing assignment?
Is the value range appropriate?
Would the assignment damage interoperability?
Does the request meet the registry’s published criteria?

The review is only trustworthy when the criteria are visible enough for applicants to understand what is being judged.

expert judgement becomes governance when its boundaries are documented

References Make Assignments Legible

IANA guidance asks registrants to use the document that provides the best and most current documentation for an item.

This matters because the registry row is usually compressed.

It cannot carry the whole technical definition.

The reference creates a route to deeper meaning.

registry entry = compact assignment
reference = authoritative explanation

This is the same layered-information principle found in The Footnote, The Appendix and The Link.

Registration Prevents Collision by Making Assignment Visible

Two independent developers both want numeric code 17.

If neither knows about the other, collision is easy.

A central registry turns hidden private intention into visible public state.

requested → checked → assigned → published

The second applicant can see that 17 is already taken and choose another value.

The registry is therefore a coordination device across people who may never communicate directly.

Reserved Values Protect Future or Special Use

A registry does not need to assign every available value.

Some can be marked:

Reserved

The word creates an exclusion state.

It says:

This value is intentionally unavailable for ordinary assignment.

Reasons may include:

future expansion;
testing;
private use;
special semantics;
compatibility protection.

Reserved is different from unassigned.

unassigned = potentially available
reserved = deliberately withheld

Temporary Assignments Need an Expiry Story

IANA supports early allocations in some situations and marks them temporary, with review requirements.

Temporary states are useful when work needs to proceed before permanent standardisation finishes.

But temporary must answer:

When does this expire?
Who reviews it?
What happens if it is not renewed?
Can deployed systems continue using it?
How does it become permanent?

temporary is safe only when the transition out of temporary is defined

Deprecated Is Not the Same as Deleted

An old assignment may no longer be recommended.

Deleting it completely can be dangerous because old documents and systems may still contain the value.

Better state:

Deprecated — retained for historical compatibility; do not use for new assignments.

The registry preserves the meaning of the past while steering the future elsewhere.

deprecation is memory plus direction

Reassignment Can Corrupt Historical Meaning

Code 23 once means:

OldProtocolFeature

The feature is retired.

Years later, code 23 is assigned to:

NewProtocolFeature

An archived packet containing 23 becomes ambiguous.

Which era’s meaning applies?

Registries often avoid reassignment when historical interpretation matters.

scarce identifier space tempts reuse; archival integrity argues for memory

A Registry Needs Change Control

Entries change.

References are updated.

Contacts move.

Names are corrected.

Status changes.

A mature registry records enough provenance to answer:

what changed;
when;
under which authority;
why;
whether the assigned value itself changed.

The registry is not merely current state.

It is current state with accountable history.

The Registry Must Distinguish Correction from Reassignment

Typo correction:

“Photogrphy” → “Photography”

Same assignment.

Reassignment:

value 71 changes from one semantic owner to another

Very different event.

Change logs should not collapse them.

editing description and changing referent are different identity operations

Registries Can Have Multiple Ranges with Different Rules

RFC 8126 and IANA guidance recognise that registries can divide value space into ranges governed by different policies.

For example:

private-use range;
expert-review range;
standards-action range;
reserved range.

Now one registry contains several governance zones.

The range is part of interpretation.

same registry, different allocation corridor

Private Use Is a Deliberate Escape from Global Coordination

Some registries reserve values for private use.

Two organisations may both use the same private-use value internally without conflict because the value is not expected to carry interoperable public meaning.

This resembles local identifiers inside separate namespaces.

private-use value is safe only while its meaning remains inside the intended private scope

If private values leak into public interchange, collision returns.

A Registry Can Be Complete and Still Be Wrong

Every row has a value.

Every row has a reference.

No duplicates exist.

The registry can still contain:

outdated references;
incorrect descriptions;
assignments approved under weak criteria;
conceptual duplicates with different names.

Structural cleanliness is not factual perfection.

This repeats a recurring How English Works lesson:

formal validity is not the same thing as truth or usefulness

Registry Governance Must Survive the Original Maintainer

If only one person understands why entries exist, the registry is an elaborate personal notebook.

Durable registry governance needs:

published procedures;
defined authority;
documented criteria;
stable storage;
change history;
succession of maintainers.

the registry becomes institutional when its authority can survive personnel change

Registries Are Interfaces Between Standards and Reality

A standard may say:

The field contains one registered media type.

The registry says which media-type names are currently recognised.

The standard defines the mechanism.

The registry supplies evolving assignments.

standard defines the slot
registry maintains the allowed public assignments over time

This separation lets assignment evolve without rewriting the whole standard every time a new value is added.

Primary School: Build a Classroom Equipment Registry

Give each classroom device a number.

Record:

equipment ID;
name;
assigned classroom;
status;
date added.

Then remove one device.

Ask:

Should its number immediately be given to a different device?

The discussion introduces assignment history and reassignment risk.

Lower Secondary: Design Registration Rules

Create a fictional registry of club codes.

Students must decide:

who may request a code;
how duplicates are prevented;
which codes are reserved;
what happens when a club closes;
whether an old code can be reused.

The lesson is that the list is the easy part.

The governance creates the registry.

Upper Secondary: Audit an Authoritative Assignment System

What values or identifiers are registered?
What gives the registry authority?
What registration policies exist?
What evidence must an applicant supply?
Which ranges have different rules?
What does Reserved mean?
What does Temporary mean?
How is deprecation handled?
Can values be reassigned?
Does the history survive changes of maintainer?

Ten Failure Modes of Registry English

List-registry confusion. A collection is called authoritative without admission rules or authority.
Authority ambiguity. Several maintainers claim control with no agreed hierarchy.
Policy opacity. Applicants cannot tell why one entry is admitted and another rejected.
Reference decay. Entries remain while their defining documentation becomes stale or unreachable.
Reserved-unassigned collapse. Intentionally withheld values are mistaken for available space.
Temporary permanence. Provisional assignments never receive review or closure.
Deletion amnesia. Deprecated assignments vanish, breaking historical interpretation.
Reassignment corruption. Old values gain new meanings and make archived records ambiguous.
Change-history loss. The current row exists but nobody can reconstruct how it got there.
Registration-endorsement confusion. Presence in the registry is treated as proof that the design is universally recommended.

How to Build a Better Registry

Define exactly what is being registered.
Define the authority that maintains assignments.
Define the uniqueness scope.
Publish admission and change policies.
Require sufficient references and provenance.
Separate unassigned, reserved, temporary, active and deprecated states.
Control reassignment according to historical risk.
Maintain a visible change history.
Version procedures when governance changes.
Preserve enough institutional knowledge for future maintainers.

Then perform the thirty-year test:

If somebody encounters one registered value thirty years from now, will the registry let them determine what it meant, who assigned it, under what rules, and whether that meaning later changed?

The Deeper Idea: Registries Turn Scarce Shared Meaning into Governed Memory

When many independent actors need the same naming space, private memory is not enough.

Somebody has to remember:

what is taken;

what is reserved;

what is obsolete;

what is temporary;

what document defines each meaning.

shared naming space → governed assignment → published registry → interoperable future use

This is why Registry belongs to How English Works.

It is language used to make a community’s assignment decisions durable enough that strangers can coordinate across time.

Reader Checklist

What is being registered?
Who has authority?
What policy controls admission?
What makes an entry unique?
What reference defines it?
Which statuses exist?
Can values be reassigned?
What is reserved?
How are changes recorded?
Will future readers still understand old assignments?

Research and Further Reading

Final idea: a registry is good when the assignment visible today still explains itself after the people, documents and systems around it have changed.