The Domain Anchoring layer is the switchyard where every name becomes a provable object by binding to a concrete anchor. Here’s exactly how each code docks into that layer — same schema for all: Anchor → Validity Gate → Registry/Record → Priority/Change → Cross-links.
ICNafp (algae, fungi, plants)
- Anchor: Type specimen (or sanctioned illustration in limited botanical cases).
- Validity gate: Effective publication + typification; fungi additionally require registration.
- Registry/record: MycoBank, Index Fungorum, Fungal Names (fungi); herbaria accession for specimens.
- Priority/change: Principle of Priority; Conservation/Rejection actions via the Nomenclature Section (Chapter F for fungi).
- Cross-links:
- Up to Language Units via Latinized morphology (binomial grammar).
- Side to ICNCP (cultivars attach under the botanical name).
- Into Governance via conservation lists (synonymy resolution).
ICZN (animals)
- Anchor: Name-bearing type (holotype, syntypes, lectotype, neotype).
- Validity gate: Effective publication; ZooBank registration required for e-only works; availability criteria.
- Registry/record: ZooBank + museum/catalog accessions.
- Priority/change: Principle of Priority; ICZN Opinions/Declarations can conserve or suppress names.
- Cross-links:
- Binomial grammar aligns with ICNafp; parallel specimen-anchored semantics.
- Governance layer consumes Commission Opinions for stability graph updates.
ICNP (prokaryotes)
- Anchor: Type strain (living culture), typically deposited in ≥2 culture collections.
- Validity gate: Publication in IJSEM or via Validation Lists + proof of type-strain deposition.
- Registry/record: Culture collection accessions (DSMZ, ATCC, etc.); IJSEM/Validation List IDs.
- Priority/change: Principle of Priority; ICSP Judicial Commission opinions.
- Cross-links:
- Bridges to ICTV when genomic sequences drive discovery (sequence ↔ strain).
- Clean mapping to UCLS “anchor_kind: type strain (culture)”.
ICTV / ICVCN (viruses)
- Anchor: Exemplar isolate/sequence (reference sequence + metadata).
- Validity gate: Inclusion in the ICTV Master Species List under current Code rules.
- Registry/record: ICTV Taxonomy, Virus Metadata Resource (sequence, isolate, host, etc.).
- Priority/change: ICTV-governed precedence through MSL updates (not classic “priority” by date).
- Cross-links:
- Harmonizes with ICNP on genomic evidence but remains sequence-centric.
- Perfect for UCLS machine joins (stable IDs, FASTA/GenBank cross-refs).
ICNCP (cultivated plants)
- Anchor: Cultivar description & registration record (diagnostic characters; denomination class).
- Validity gate: Published denomination + ICRA check/registration.
- Registry/record: ICRA network (by crop) under ISHS; trade catalogs/docs.
- Priority/change: Denomination priority within cultivar class; ICRA determinations.
- Cross-links:
- Always under an ICNafp botanical name (scientific name + ‘cultivar epithet’).
- Bridges scientific taxonomy ↔ commerce/legal naming.
ICPN (phytosociological nomenclature — plant communities)
- Anchor: Type relevé (plot-based vegetation record) serving as a community holotype.
- Validity gate: Published description + type relevé per ICPN rules.
- Registry/record: Journal articles/monographs; vegetation databases that store relevés.
- Priority/change: Priority within syntaxon rules; IAVS Working Group decisions.
- Cross-links:
- Lifts organismal names into ecosystem-level tokens (community categories).
- Recurses upward into UCLS “structures above taxa.”
PhyloCode (clades)
- Anchor: Phylogenetic specifier set (node-, branch-, or apomorphy-based definition).
- Validity gate: Published definition + RegNum registration.
- Registry/record: RegNum (clade name + formal definition + specifiers).
- Priority/change: Definition-based stability; registration ensures uniqueness (date priority is secondary).
- Cross-links:
- Provides definition-exact names that track trees as data improve.
- Interlocks with ICN/ICZN/ICNP species names as specifiers.
One-screen matrix (copy-paste friendly)
| Code | Anchor (what “proves” the name) | Validity Gate | Registry/Record | Priority/Change | UCLS “anchor_kind” |
|---|---|---|---|---|---|
| ICNafp | Type specimen / illustration (fungi: +registration) | Effective publication + typification (+registration for fungi) | MycoBank • Index Fungorum • Fungal Names • Herbaria | Priority; Conservation/Rejection | Type specimen (botanical) |
| ICZN | Name-bearing type (specimen/series) | Effective publication; ZooBank for e-only; availability criteria | ZooBank • Museum accessions | Priority; ICZN Opinions | Name-bearing type (zoological) |
| ICNP | Type strain (living culture) | IJSEM or Validation Lists + deposition | Culture collections • IJSEM • Validation Lists | Priority; ICSP Opinions | Type strain (culture) |
| ICTV | Exemplar isolate/sequence | Inclusion in Master Species List | ICTV Taxonomy • Virus Metadata Resource | ICTV-managed precedence | Exemplar sequence |
| ICNCP | Cultivar record (diagnosis + denomination) | Published denomination + ICRA check | ICRA registers (ISHS) | Denomination priority | Cultivar registration |
| ICPN | Type relevé (community record) | Published description + type relevé | Vegetation data/journals | Priority within syntaxa | Type relevé |
| PhyloCode | Phylogenetic specifiers (definition) | Published definition + RegNum registration | RegNum | Definition-first stability | Phylo specifiers |
The plug-in flow (each code follows this pipeline)
Token → Anchor → Validity → Registry → Priority/Change → UCLS Graph
- Token(name string; binomial/clade/cultivar/syntaxon)
- Anchor(specimen, strain, sequence, record, relevé, specifiers)
- Validity(code-specific gates: publication/registration/deposition)
- Registry(the auditable ledger)
- Priority/Change(who decides disputes; how stability is enforced)
- UCLS Graph(typed node with edges to Language Units, Governance, and Cross-Recursion)
Key terms in plain language
Open a term for a concise explanation of language used on this page.
Fiber Internet
Internet delivered through strands of glass using light. Fiber commonly supports high capacity, low latency, and strong upload performance, but availability must be confirmed for the exact address.
Broadband
A general term for always-on, high-speed Internet access. Broadband can be delivered over fiber, cable, DSL, fixed wireless, cellular, or satellite networks.
Bandwidth
The amount of data a connection can carry in a given time, usually measured in Mbps or Gbps. More bandwidth supports more users, devices, and simultaneous applications.
Latency
The time it takes data to travel between two points. Lower latency improves voice, video meetings, cloud applications, gaming, and other real-time services.
Dedicated Internet Access (DIA)
A business-grade Internet connection with capacity dedicated to the customer rather than shared in the same way as typical consumer broadband. It often includes symmetrical speeds and an SLA.
SD-WAN
Software-defined wide area networking. It manages multiple connections and chooses paths based on application needs, performance, and policy to improve resilience and control.