Taxonomy Revision¶
Hierarchy revision — instantiates Schema Update Protocol
Re-lays a subsumption hierarchy — reparenting, regrouping, and re-leveling its branches — against a recorded baseline so the tree fits the domain without breaking historical comparability.
A Taxonomy Revision reorganizes a subsumption hierarchy — a tree of broader-and-narrower categories, each a kind-of its parent — when the branching no longer reflects the domain. Its defining feature is that the object is a tree structured by is-a-kind-of, and the operations are about placement: reparenting a node under a different genus, promoting or demoting a level, regrouping siblings, collapsing a redundant tier. Unlike a single split/merge, a revision works across the branches at once, re-laying the shape of the tree; unlike an ontology refactor, it moves within one subsumption dimension rather than restructuring typed relations and constraints. Because a taxonomy is usually long-lived and things have been counted under its old branches for years, the revision's hardest obligation is comparability: it must record the tree as it was and preserve the ability to compare across the change.
Example¶
A natural-history museum maintains a taxonomy of its specimen collection built decades ago. Molecular evidence has shown that one traditional grouping is paraphyletic — it gathers organisms that look alike but do not share a most-recent common ancestor, while excluding one that does — so specimens are shelved and searched under a branch that no longer reflects the real tree of relationships. A Taxonomy Revision addresses the whole affected subtree. It first snapshots the current hierarchy exactly — every node, parent, and rank — with the date and the catalogs that cite it, so the prior arrangement is recoverable and old labels remain interpretable. It then re-lays the branches: the paraphyletic group is dissolved, its members reparented under the genera the evidence supports, and one over-deep tier collapsed. Throughout, a continuity commitment governs the change: historical specimen counts and old catalog references must remain comparable, so the revision publishes a mapping from each retired branch to where its members now sit and retains the old rank names as historical cross-references. The tree now mirrors the domain; a researcher comparing a fifty-year-old census to today's can still align them.
How it works¶
A taxonomy revision is tree surgery disciplined by a baseline and a comparability rule, so its distinctive steps are about placement and preservation:
- Snapshot the tree first. Record the full hierarchy — nodes, parents, ranks — dated and cited, before any branch moves, so nothing is lost and old records stay readable.
- Re-lay branches, not just one node. Reparent, regroup, promote, demote, and collapse tiers across the affected subtree so the shape reflects the domain.
- Preserve cross-change comparability. Publish where each retired branch's members now live and keep old branch names as historical references, so counts and citations align across the revision.
- Keep the tree navigable. Check that the re-leveled hierarchy is still shallow and even enough for people to traverse.
Tuning parameters¶
- Revision breadth — one subtree versus the whole hierarchy; broader fixes systemic misplacement but disturbs more downstream references and habits.
- Depth/granularity — how many levels the tree carries; more levels sharpen distinctions but make traversal and consistent placement harder.
- Comparability rigor — from a light where-did-it-go note to an audited old-branch-to-new mapping; heavier preserves historical analysis but costs effort.
- Snapshot retention — whether every prior tree state is versioned or only the last; deeper history supports long-run comparison but grows the record.
When it helps, and when it misleads¶
Its strength is that it repairs structural misplacement — categories filed under the wrong parent, tiers that hide or over-split real distinctions — while protecting the historical comparability that a long-lived tree accumulates. The discipline it leans on is monophyly: the principle that a well-formed group should contain an ancestor and all its descendants, which in cladistics is the test that separates a defensible branch from a convenient but paraphyletic one.[n1]
Its failure mode is legacy meaning loss: a revision that reparents branches into a cleaner tree but silently strands every record and count filed under the old arrangement, so historical comparisons quietly break. The classic misuse is re-laying the hierarchy for tidiness — a more elegant tree that no longer aligns to anything previously measured under it. The guarding discipline is to snapshot the old tree before touching it and to publish the old-branch-to-new mapping as part of the change, so that a revision improves fit and keeps the past legible, rather than trading one for the other.
How it implements the components¶
current_schema_snapshot— the dated, cited capture of the full hierarchy before any branch moves, the baseline that keeps old records interpretable.category_revision— the tree surgery itself: reparenting, regrouping, promoting, demoting, and collapsing tiers across the affected subtree.continuity_constraint— the commitment that historical counts and citations stay comparable, honored through the retired-branch-to-new mapping and preserved old names.
A Taxonomy Revision re-lays the hierarchy but does not adjudicate a lone split/merge or hear stakeholders: it renders no isolated revision_decision on a single node (that is Category Split/Merge Review) and stands up no schema_owner governance (that is Schema Change Review Board). Its nearest twin is Ontology Refactoring, with which it shares the category-revision role; the separator is that this reorganizes a single subsumption tree while ontology refactoring restructures a graph of typed relations and logical constraints, and it leaves the backward_compatibility_map and schema_mismatch framing to that page.
Related¶
- Instantiates: Schema Update Protocol — the revision is the schema-change step specialized to reorganizing a subsumption hierarchy.
- Consumes: Category Split/Merge Review supplies decided node-level split/merge verdicts that the broader re-lay incorporates.
- Sibling mechanisms: Classification Audit · Category Split/Merge Review · Coding-Frame Revision · Glossary Update · Knowledge-Base Retagging · Ontology Refactoring · Schema Change Review Board · Schema Migration Workflow
Editorial Notes¶
Form Classification¶
Form family: Intervention, Treatment & Transformation
Rationale: Taxonomy Revision operates as a direct treatment or transformation applied to a target to change its state or condition because it re-lays a subsumption hierarchy — reparenting, regrouping, and re-leveling its branches — against a recorded baseline so the tree fits the domain without breaking historical comparability.
Independent corroboration: The frozen evidence defines Taxonomy Revision as 'Re-lays a subsumption hierarchy — reparenting, regrouping, and re-leveling its branches — against a recorded baseline so the tree fits the domain without breaking historical comparability', so its operative form is Intervention, Treatment & Transformation.
Nearest alternative: Representation, Specification & Plan — Taxonomy Revision includes features of a static representation, map, specification, schema, or prospective plan that externalizes information, but its defining operation is a direct treatment or transformation applied to a target to change its state or condition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Library & Information Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Taxonomy revision derives most directly from library and information science's classification, provenance, and retrieval tradition; its defining operation is to re-lays a subsumption hierarchy — reparenting, regrouping, and re-leveling its branches — against a recorded baseline so the tree fits the domain without breaking historical comparability.
Related originating lineages:
- Biology & Ecology — Biological and ecological research supplies a parallel or contributing lineage for the mechanism's defining operation: re-lays a subsumption hierarchy — reparenting, regrouping, and re-leveling its branches — against a recorded baseline so the tree fits the domain without breaking historical….
- Computer Science & Software Engineering — Computer science and software-engineering practice supplies a parallel or contributing lineage for the mechanism's defining operation: re-lays a subsumption hierarchy — reparenting, regrouping, and re-leveling its branches — against a recorded baseline so the tree fits the domain without breaking historical….
- Linguistics & Semiotics — Linguistics and semiotics' terminology, meaning, and sign-system tradition provides a formative adjacent lineage for the same taxonomy revision operation.
Review resolution: Both blind reviewers independently select library_information_science as the primary historical origin for the concrete operation—Re-lays a subsumption hierarchy — reparenting, regrouping, and re-leveling its branches — against a recorded baseline so the tree fits the domain without breaking historical comparability. The queued differences concern alternate origin disagreement, origin mode disagreement, domain reach disagreement, encyclopedia synthesis disagreement, not the primary lineage. I retain every alternate that either reviewer explains, without a numeric cap, and choose origin_mode=cross_disciplinary_synthesis because the reviewers' combined evidence identifies material construction from multiple disciplines. domain_reach=universal records later portability rather than multiplying historical origins; confidence=high is the conservative shared evidentiary level, and encyclopedia_synthesis=true preserves either reviewer's affirmative synthesis finding.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] In cladistics a monophyletic group (a clade) contains a common ancestor and all of its descendants; a paraphyletic group omits some descendants and so misrepresents the true branching of relationships. Monophyly is the formal test a taxonomy revision uses to tell a defensible regrouping from a merely traditional one. ↩