Skip to content

Glossary Update

Reference maintenance — instantiates Schema Update Protocol

Revises the authoritative definitions of terms — not the category structure — recording the old baseline, why each meaning changed, and how users should read affected records.

Version
v1 · 2026-08-24 · History
Mechanism #
3867
Type
Reference Maintenance
Form family
Intervention, Treatment & Transformation
Solution family
Representation & Modeling
Problem family
Adaptation, Variation & Context Misfit
Problem subfamily
Stale Response Under Changed Conditions
Origin domain
Library & Information Science
Also from
Linguistics & Semiotics
Instantiates
Schema Update Protocol

A Glossary Update revises the definitions of terms that a shared schema depends on, while leaving the category structure itself in place. Its defining feature is that the payload is meaning, not shape: no category is split, merged, or reparented — instead the sanctioned definition of a term is tightened, broadened, or corrected because the words have drifted from what people now do with them. That sounds minor and is often anything but: two teams reporting the same "active user" against silently divergent definitions will produce contradictory numbers and never know why. The update's job is to re-pin a term to a single authoritative meaning, preserve what the old meaning was, and tell everyone who relied on the term how to read records created under the previous definition.

Example

A bank's data-governance team maintains a business glossary — the authoritative dictionary of terms used across risk reports, dashboards, and regulatory filings. The term small-business customer has quietly become ambiguous: originally it meant "annual revenue under $5M," but three departments have each been reading it differently since a new lending product launched, and a regulator's question exposes the gap. A Glossary Update is opened on this term alone. First it captures the current definition exactly as written, with the date and the reports that cite it, so the prior meaning is not lost the moment it is overwritten. Then it sets the corrected definition (revenue under $5M and fewer than 50 employees, resolving the drift) and records in the rationale log why the change was made, what ambiguity it fixes, and which regulatory question prompted it. Finally it publishes a transition note telling report owners that figures produced before the change used the looser definition and must be footnoted when compared across the boundary. The category "small-business customer" still exists in exactly the same place in the schema; only its meaning has been re-pinned.

How it works

A glossary update is definition maintenance with memory, so its distinctive steps are about preserving and communicating meaning rather than restructuring:

  • Snapshot the term as-was. Record the outgoing definition verbatim, dated, with its citations, before editing — the baseline that lets anyone reconstruct what old records meant.
  • Re-pin to one authoritative meaning. Write the corrected definition tightly enough that two readers cannot diverge, and mark any deprecated synonyms.
  • Log the why. Capture the rationale — what drift or ambiguity is being fixed and what evidence prompted it — so the change is defensible and not mistaken for cosmetic wording.
  • Publish the reading rule. Tell downstream users how to interpret records that predate the change, especially where old and new figures might be compared.

Tuning parameters

  • Definition tightness — how narrowly the term is pinned; tighter kills ambiguity but may exclude legitimate edge readings, looser stays flexible but invites the drift again.
  • Snapshot retention depth — whether every prior definition is versioned or only the immediately preceding one; deeper history aids audit but grows the glossary.
  • Rationale rigor — a one-line note versus a full justification with evidence links; heavier is defensible under scrutiny but slows routine edits.
  • Announcement reach — a quiet changelog entry versus an active notice to every report owner; louder prevents silent misreads but has a cost in attention.

When it helps, and when it misleads

Its strength is cheapness and precision: when the problem is genuinely a word rather than a structure, re-pinning the definition fixes the misfit without the cost and risk of restructuring anything. It is the standing defense against semantic drift — the slow, unnoticed slippage of a term's working meaning away from its documented one — which is the specific decay a glossary exists to arrest.[n1]

Its failure mode is using a definition edit to paper over a structural problem: if a term is ambiguous because it is genuinely two things, redefining the word just relocates the confusion, and the schema still needs a split. The classic misuse is the silent redefinition — quietly broadening "active user" so a metric improves, with no snapshot and no rationale, which corrupts every historical comparison that touches it. The guarding discipline is to require a dated before-snapshot and a logged rationale for every change, and to escalate to a structural mechanism the moment a definition edit starts wanting to carve the category in two rather than merely describe it more precisely.

How it implements the components

  • current_schema_snapshot — the verbatim, dated capture of each term's outgoing definition and citations, so prior meanings survive the edit.
  • change_rationale_log — the record of why each definition changed and what ambiguity or drift it resolves, keeping the change defensible and non-cosmetic.
  • user_transition_path — the published reading rule that tells downstream users how to interpret records created under the old definition.

A Glossary Update deliberately does not touch structure: it performs no category_revision (that is Taxonomy Revision) and renders no split-or-merge revision_decision (that is Category Split/Merge Review). Its nearest twin is Knowledge-Base Retagging, with which it shares the user-transition-path role; the difference is that retagging physically relabels stored items to match a changed structure, whereas this changes only the words that define a term and leaves every item where it sits.

Editorial Notes

Form Classification

Form family: Intervention, Treatment & Transformation

Rationale: The mechanism directly changes authoritative term definitions, records how meanings moved, and updates how affected records should be read.

Nearest alternative: Protocol, Workflow & Routine — Reference maintenance can follow a procedure, but success is the transformed semantic baseline.

Review outcome: Adjudicated after independent review; high confidence.

Origin Attribution

Primary origin: Library & Information Science

Origin pattern: Cross-disciplinary synthesis

Present-day reach: Universal

Rationale: Lexicography and historical semantics supply explicit management of changing word senses.

Related originating lineages:

  • Linguistics & Semiotics — Lexicography and historical semantics supply analysis of changing senses and definition boundaries.

Review resolution: NISO standards explicitly cover controlled-vocabulary maintenance and management, and Library of Congress authority practice maintains standardized terms and variants. That makes library_information_science primary. Linguistics materially supplies semantic-change analysis. The mechanism’s versioned baseline, change reason, and reader-impact packaging is an encyclopedia synthesis with universal reach.

Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.

Review outcome: Researched adjudication after independent review; high confidence.

Sources consulted:

Notes

[n1] Semantic drift is the gradual, unremarked change in the working meaning of a term while its documented definition stays fixed — the reason two teams can use the same word for years and mean subtly different things. A versioned glossary with dated snapshots is the standard instrument for detecting and arresting it. ↩