Knowledge Domain Database - Botany
How does the domain work before writing a line of code? Choose a document from the left tree: each page explains part of the model.
Business Rules - Botany
This document lists the fundamental rules of the botany domain, each identified by a unique BR-NNN code. Every rule is technology-independent and describes an invariant constraint on observation, classification, nomenclature and conservation of plants.
> Note: This is a descriptive scientific domain. The rules do not model commercial transactions, but the scientific process of observation, validation and classification.
---
BR-001 - Scientific name validity under the ICN
Code: BR-001
Name: Every Species must have a valid scientific name under the International Code of Nomenclature
Description: A species name must be binomial (genus + specific epithet + author), correctly published and compliant with the ICN (Shenzhen Code 2018, updated Madrid 2024). Unaccepted names are recorded as synonyms, not as distinct species.
Motivation: Ensure uniqueness of the taxonomic reference and avoid duplicating species under different names.
Priority: HIGH
Actors: Taxonomist, Botanist
Traceability: ICN Shenzhen Code 2018; POWO (Kew); classify-species.md.
---
BR-002 - Principle of priority in synonymy
Code: BR-002 Name: Among competing names the oldest correctly published name prevails Description: When two names describe the same taxonomic entity, the ICN principle of priority assigns validity to the name published first (with the basionym in parentheses if recombined). The others become synonyms. Motivation: Stabilize nomenclature and resolve conflicts deterministically. Priority: HIGH Actors: Taxonomist Traceability: ICN (principle of priority); basionym; BR-001.
---
BR-003 - Observation validation before publication
Code: BR-003
Name: An Observation must be validated before entering public datasets
Description: A field observation (date, georeferenced location, species identification, optional herbarium specimen) must be reviewed and validated by an expert before transitioning from DRAFT to VALIDATED and then to PUBLISHED in databases such as GBIF.
Motivation: Prevent the propagation of misidentifications into shared scientific datasets.
Priority: HIGH
Actors: Botanist, Researcher, Taxonomist
Traceability: GBIF data quality; record-observation.md; observation-lifecycle.md.
---
BR-004 - Mandatory georeferencing of the observation
Code: BR-004
Name: Every Observation must record coordinates and date
Description: A valid observation contains geographic coordinates (lat/lon, WGS84 datum), date of sighting and identification at least at genus level. Occurrences without georeferencing are not admitted into distribution datasets.
Motivation: Species distribution and ecological niche models depend on reliable spatial data.
Priority: HIGH
Actors: Botanist, Amateur Naturalist
Traceability: GBIF Darwin Core; WGS84; BR-003.
---
BR-005 - Protection of priority habitats
Code: BR-005
Name: Observations in priority habitats (Directive 92/43/EEC) require conservation caution
Description: When an Observation falls within a Habitat classified as priority (asterisk in the Habitats Directive), the publication of the exact location of threatened species may be obscured or reduced in precision to prevent illegal collection.
Motivation: Protect endemic and threatened species from unauthorized harvesting.
Priority: HIGH
Actors: Researcher, Amateur Naturalist
Traceability: Directive 92/43/EEC; IUCN Red List; Habitat entity.
---
BR-006 - Reporting of invasive alien species
Code: BR-006
Name: Species of Union concern (Reg. EU 1143/2014) must be reported
Description: The sighting of an invasive alien species included in the EU Regulation 1143/2014 list (e.g. _Ailanthus altissima_, _Reynoutria japonica_) generates a priority report to monitoring bodies, distinct from ordinary floristic observations.
Motivation: Enable timely containment of the spread of IAS.
Priority: MEDIUM
Actors: Botanist, Researcher
Traceability: Reg. EU 1143/2014; Species entity (IAS flag).
---
BR-007 - Taxonomic rank consistency
Code: BR-007
Name: The taxonomic hierarchy must be consistent and complete down to genus
Description: A Species is placed in a Taxonomy respecting the hierarchy Kingdom → Division → Class → Order → Family → Genus → Species. Rank skips or placements in families incompatible with the accepted phylogeny are not allowed.
Motivation: Maintain classification consistency and the navigability of the taxonomy.
Priority: MEDIUM
Actors: Taxonomist
Traceability: Taxonomic ranks; POWO; BR-001.
---
BR-008 - Preservation of the herbarium type specimen (typus)
Code: BR-008
Name: A newly described species requires a deposited type specimen
Description: The formal description of a new Species requires depositing a type Specimen (holotype) in a recognized herbarium, with an identifier code (e.g. herbarium acronym + number). The typus is the permanent reference for the species.
Motivation: Guarantee physical verifiability and reproducibility of the taxonomic determination over time.
Priority: HIGH
Actors: Taxonomist, Collector
Traceability: ICN (typification); Index Herbariorum; Specimen entity.