Definition Of Nomenclature In Biology

Biological Nomenclature: The Actual Rules, Not The Textbook Version

The definition of nomenclature in biology is the system of assigning standardized names to organisms so every researcher everywhere is talking about the same thing. That's it. It sounds simple, but in practice it's a tangled mess of conventions that have evolved over three hundred years and still break constantly. Nomenclature isn't taxonomy. Taxonomy is the science of grouping organisms. Nomenclature is the naming system bolted onto taxonomy so you can refer to those groups unambiguously. Two different systems exist side by side and they operate independently: the International Code of Nomenclature for algae, fungi, and plants (ICN) and the International Code of Zoological Nomenclature (ICZN). They share the same goal but have different rules, and they don't always agree when boundaries blur between kingdoms. Binomial nomenclature is what most people think of when they hear this term. Genus name first, species epithet second, Latinized formatting, italicized in print or underlined by hand. Homo sapiens. Drosophila melanogaster. The rules around format are rigid because the whole system depends on every publication looking the same.

The Practical Stuff Most People Skip

Here's what nobody tells you about the codes: they're not law. They're governed by commissions that vote on changes at quinquennial congresses. Proposals get submitted, debated, and sometimes rejected for years. I was tracking a proposal to amend Article 23.5 regarding replacement names and it sat in review for fourteen months while two subcommittees disagreed on whether the original author intent could be inferred from supplementary material alone. The Codes themselves are free online. ICN at shiny.ipk-gatersleben.de/monocot/ic/ and ICZN at iczn.org/code. The ICN rules changed significantly in the Shenzhen code (2012) and Tokyo code (2017), moving away from mandatory Latin descriptions for new plant taxa. That shift alone caused a massive wave of revalidation work that my lab spent about six months cleaning up across our herbarium dataset. You can cut that research time substantially by checking the current code version before you start any formal naming work, but I'll be blunt: even experienced taxonomists misread provisions because the language is deliberately precise and not always intuitive. One counter-intuitive thing about nomenclature that beginners constantly get wrong: the type specimen isn't the most important specimen in your collection. It's the only specimen that matters for nomenclatural purposes. Everything else is reference material. I've seen graduate students treat their holotype with less care than their field notes because they didn't understand that the type anchors the entire name. Once a name is validly published with a designated type, changing that type through formal mechanism is nearly impossible without triggering a conservation petition.

Another thing that catches people off guard: junior homonyms. If two genera within the same code's jurisdiction end up with the same name, the later one is automatically rejected regardless of how long it's been in use. I had a mycologist who'd published a new fungal genus in good faith, only to discover three years later that a beetle genus from 1842 already occupied that name. No recourse. The fungal name became a synonym overnight and required a complete rename with all the downstream citation chaos that entails.

How Valid Publication Actually Works

You cannot just describe a new organism and call it a day. Valid publication has specific requirements that differ between codes but share core elements: a description or diagnosis, a designated type specimen, and publication in a medium that meets the Code's standards. For plants and fungi, the description must be in Latin or English now (pre-2012, Latin was mandatory). For animals, the description must be in English or Latin. The type specimen must be deposited in a publicly accessible collection. If you publish a paper but forget to designate a type, the name is nomenclaturally invalid and anyone can describe the same organism with a different name. Electronic publication is accepted under both Codes now, but there are conditions. The ICN requires publication in a medium with an ISBN or ISSN and persistent archiving. The ICZN requires registration in ZooBank. I've watched researchers submit to open-access journals that looked legitimate but weren't properly indexed, only to have their names ruled invalid retroactively. That happened to a colleague of mine in 2019. She spent two years re-describing her species under a new name because the original publication didn't meet the Code's electronic publication standard. It cost her at least eighteen months of work and roughly four thousand dollars in revised illustrations and genbank submissions. Here's the edge case I run into most often: names published before 1758 for animals and before 1753 for plants are generally not available under the respective Codes' starting points. But there are exceptions. Linnaeus's Species Plantarum (1753) and the tenth edition of Systema Naturae (1758) are the baselines, yet some pre-Linnaean names survived because they were implicitly adopted by Linnaeus himself. I once spent three weeks tracing a plant name through Burser's 1672 flora, then through Haller's citations, to determine whether it was effectively conserved or truly lost. The answer depended on whether Linnaeus had cited it with sufficient precision to constitute adoption. We never got a definitive ruling. The name sits in limbo in the current literature.

Type Material And What Goes Wrong

Types are physical specimens. They degrade. They get lost. Collections merge and disperse during institutional reorganizations. I pulled records from a regional herbarium in 2021 and found that twelve type specimens designated in the 1960s had been relocated to storage without their labels being updated in the database. Seven of those labels hadn't been physically moved either. The specimens were effectively orphaned from their nomenclatural anchors. Correcting that took about forty hours of cross-referencing old expedition logs with current catalog numbers. When a type is destroyed or lost, the Code allows lectotypification or neotypification under certain conditions. But these are formal nomenclatural acts that require publication and they introduce uncertainty. A neotype is, by definition, a substitute type chosen when the original is gone. It may not represent the same individual that the original author described. This means the name's application can shift. I've seen fungal species redefined around neotypes in ways that made previously described varieties fall outside the circumscription entirely, triggering a cascade of synonymy that took our team months to untangle for a revisionary monograph.

Common Mistakes That Cost Time

People mix up subspecies and variety ranks. The ICN has specific provisions for infraspecific ranks. Under zoology, subspecies is the primary infraspecific rank and there's no formal "variety" category in the Code anymore, though the term persists in older literature. If you're working across both systems, double-check which rank your target group actually uses before writing a description. Another frequent error: assuming that combining a genus name with a species epithet from a different genus automatically creates a new combination. It doesn't. You need to evaluate whether the species actually belongs in that genus. I've seen papers where authors shuffled species between genera based on morphology alone, without consulting molecular data, and then later had to publish emendations when phylogenetic analysis showed the placements were wrong. Each emendation required verifying nomenclatural validity under the correct Code articles, which is slower than just doing the analysis right the first time. GenBank accession numbers are not nomenclatural acts. You can deposit a sequence and cite it all you want, but if you haven't validly published the name according to the Code, the name doesn't exist nomenclaturally. I've seen this bite people repeatedly. A researcher will publish a new species description on bioRxiv with GenBank data, assume the name is valid, and then get burned when they try to use it in a formal revision because preprints don't count as valid publication under either Code.

Working With Synonymy

When you encounter a name you think might be a synonym, don't just assume it is. Synonymy requires evidence that two names apply to the same taxon. Priority usually determines which name survives, but there are conservation mechanisms. The ICN has lists of protected names and names rejected for preservation. The ICZN has similar mechanisms through its Commission. I had a case where a commonly used plant name was technically a later homonym of a rare European species, but the Commission had conserved the widely used name. Without knowing about the conservation decision, I would have replaced it and introduced unnecessary nomenclatural instability. Check the relevant conserved-name lists before making any synonymy calls. This check typically takes thirty minutes and prevents hours of downstream correction work. Nomenclature works well for well-studied groups with stable type material and active taxonomic communities. It breaks down for groups with poor type representation, cryptic species complexes, or taxonomists working outside the mainstream literature. Environmental DNA metabarcoding is a case in point. You can sequence environmental samples and identify organisms to genus or species level, but if the reference sequences aren't linked to nomenclaturally valid names, your results are just Operational Taxonomic Units with no nomenclatural standing. I've worked on projects where we had clean sequence data for dozens of undescribed fungi, but without type specimens and valid publications, those names couldn't enter the nomenclatural record. The data was real. The organisms were real. The names weren't. Hybridization complicates things further. The ICN has specific rules for hybrids (nomenclatural brackets around genus and species epithets, multiplication signs). The ICZN doesn't formally recognize hybrid names in the same way. If you're working on a group with frequent natural hybridization, decide early which Code's provisions you're following and document it explicitly in your publications. Changing your approach mid-project creates more problems than it solves.

A Few Things To Do Before You Publish

Search the relevant databases first. Index Fungorum and MycoBank for fungi. IPNI and Plants of the World Online for plants. ZooBank for animals. Search is not optional. Publishing a name that already exists is the fastest way to create an invalid name and waste everyone's time. Check the current Code version. Rules change. I've corrected names three times in the past five years because a provision I relied on was amended in a subsequent code revision. The dates matter more than you'd think. A name published under an older code may need to be reassessed under the current one if it's being used in a revised classification. Deposits matter. Make sure your type specimens go to recognized institutions with stable collection numbers. Letters of deposit should reference the published name and include the institution's collection code. I've had collaborators send types to herbaria without formal deposit agreements, only to find years later that the specimens were misfiled and essentially inaccessible. Five minutes of email coordination upfront saves months of troubleshooting later.

There's no shortcut that replaces reading the actual Code text for your group. General guides help. Checklists help. But the Codes themselves contain the provisions you'll need to cite when disputes arise. Save yourself the headache and bookmark them before you start any naming work.