How to markup biodiversity-related resources
The resources may span a large spectrum of domains, ranging from academic biodiversity databases such as taxonommic registries, species check lists and scientific literature repositories, to private companies concerned with regulations and directives related to endangered species, to associations of citizens praticing birdwatching or sea fishing.
The main goal of marking up these resources is to improve their Findability on the Web, in accordance with the goals of Bioschemas themselves, while connecting them together thus helping to weave a broad biodiversity web.
The Taxon and TaxonName profiles
These two profiles can be used together or separately depending on the use case.
A taxon is a group of organisms with common characteristics, identified by taxonomists to form a certain unit. If your resources deal with groups of biological organisms like animals, plants, fungi or bacteria, then you may want to use the Taxon profile. The least you would need to know to describe a Taxon is:
- its full scientific name including authorship and date (property
schema:name), also called accepted name in botanics or valid name in zoology,
- its taxonomimc rank (property
schema:taxonRank) such as species, genus, family etc.
Additional names can be provided:
- synonyms of the accepted/valid scientific name (property
schema:alternateName) keep track of the taxonomic changes and thus reflect the way biologists think of a given taxon, that is, its circumscription.
- vernacular names can also be provided using a property borrowed from Darwin Core terms:
For instance, the taxon representing the Beluga species has a valid scientific name which is Delphinapterus leucas (Pallas, 1776), a synonym name is Balaena albicans Muller, 1776 (note that typographic elements such as parentheses, comma, the use of uppercase vs. lowercase letters etc., are normalized by the Codes of nomenclature), and its rank is species. This is illustrated by the simple example below:
Other recommended or optional information can be added to the description. In particualr, it is recommended to link a Taxon to its parent taxon by means of the
schema:parentTaxon property, and optionally to its child taxa with
schema:isBasedOn property can be used to refer to an article that described the taxon.
Furthermore, a good pratice is to link a Taxon to its counterparts in third-party taxonomic registers like the NBCI taxonomy, or data agregators like GBIF or Catalog of Life, using the
schema:sameAs property and/or
schema:identifier property with a
schema:PropertyValue as an object, such that people would know exactly what taxon you refer to.
Some databases (e.g. Zoobank, IPNI and Mycobank) describe specifically scientific names but do not keep track of how names are assigned to taxa, such that they would be poorly supported by the use of the Taxon profile. In such cases, the TaxonName profile is more relevant to markup the resources of these taxonomic names registries.
A TaxonName essentially consists of the scientific name (
schema:name) without authorship nor date that are specified separately (
It is also recommended that a TaxonName be assigned a taxonomic rank (property
Similarly to the description of a Taxon, a good pratice is to link a TaxonName to its counterpart in third-party projects like Zoobank or IPNI using the
schema:sameAs property and/or
schema:identifier property with a
Furthermore, the TaxonName profile may be used jointly with the Taxon profile when one wants to describe a taxon while giving details about the scientific names. To do so, properties
schema:alternateScientificName are the counterparts of
schema:alternateName, but they take a TaxonName object.
A simple example would look like this:
Additional information could be provided, in particular the article that proposed the name (
How to decide whether to use Taxon or TaxonName?
If you are unsure whether your resources deal with taxa or taxon names, just follow this simple rule:
- When your resources are primarily about biology in the broad sense, organisms, biological features, life traits, phenotypes etc., then most likely you should use the Taxon profile.
- When your resources relate to the publication and typification of scientific names, specifically when this pertains to the application of a Code of nomenclature, then you should use the TaxonName profile.
How to denote taxonomic ranks?
In both Taxon and TaxonName profiles, a taxonomic rank is given with property
schema:taxonRank that may take either a string or a URI.
A simple string would typically be “species, “genus” or family”. This is easy to read but leaves room for multiple wordings with respect, for instance, to the case or the use of singluar or plural etc.
By contrast, a URI from a controlled vocabulary is well defined but multiple choices exist and consumers of the markup data may not know about them all. Some candidates are Wikidata, TDWG TaxonRank ontology, NCBI taxonomy.
Therefore, a recommended practice is to provide at least one string and one URI to denote the rank, as illustrated below:
Cross-references to other databases
So that people understand exactly what taxon or taxon name your resource describes, it is a good practice to link the descriptions to their counterparts in third-party databases.
A simple way to do that is to link to a web page that describes the same entity with property
For instance, a Taxon could link to the GBIF page for taxon Delphinapterus leucas (Pallas, 1776) in this way:
An even better option is to provide the identifier of the entity within other databases using property
schema:identifier and an object of type
schema:propertyID is the URI of a property and
schema:value is the value of the identifier.
Continuing on the same example, the GBIF identifier could be provided this way:
The interest of this approach is that a consumer of the Taxon markup data could, later on, use this identifier to query GBIF’s API and retrieve additional information.
Joint use of Taxon and TaxonName
Keywords: schemaorg, markup, structured data, bioschemas, biodiversity
- (Markup provider, Markup consumer) People interested in adding Bioschemas markup to their own biodiversity-related resources
License: CC-BY 4.0
Last Modified: 09 January 2023