Root element of the data set. Information associated with the creation of the dataset in human-readable form. A summary of the metadata for this document. A place holder for an external schema giving details of the metadata for this document. A meta data schema is provided with the TCS release for this purpose should no other schema be prefered. Container for vouchers (representation of specimen) records. Specimen and location Information about the location of the specimen. The PlaceholderType represents a placeholder for optionally extending the schema with a schema element defined in another standard. The PlaceholderType represents a placeholder for optionally extending the schema with a schema element defined in another standard. Identifier for the specimen used within the collection. Physical object the voucher is referring to. The PlaceholderType represents a placeholder for optionally extending the schema with a schema element defined in another standard. Unique identifier (key) of the element. It can be local to the data set or a GUID in which case it can be resolved to a location on the internet where the record is stored. Container for publication records. Details of the data source. Full bibliographic reference as a single formatted string. Mechanism to allow for the extension of the schema for specific applications. Unique identifier (key) of the element. It can be local to the data set or a GUID in which case it can be resolved to a location on the internet where the record is stored. A container element for NameObjects. An object that represents a single scientific biological name that either is, or appears to be, governed by one of the biological codes of nomenclature. These are not taxa. Taxa, whether accepted or not, are represented by TaxonConcept objects. Vernacular names are also dealt with under taxon concepts. Container for TaxonConcept records. Representation of a TaxonConcept. Various types of concept can be represented, including a reference to the GUID of an existing Concept. A non-unique handle to the concept. This can represent the name as published. The taxonomic rank of this concept. Either as a string or as a code for a recognise rank or both. Information about the authorship of this concept which uses the Name in their sense (i.e. secundum, sensu). Stores explicit, taxonomic and nomenclatural relationships that are part of the original concept definition. Type of the relationship Reference to another TaxonConcept. A set of specimens that are used to define the concept. Link to record of a specimen. A set of taxonomic descriptions used to define this concept. May potentially hold descriptions according to the TDWG SDD schema, or any other, format. Mechanism to allow for the extension of the schema for specific applications. Unique identifier (key) of the element. It can be local to the data set or a GUID in which case it can be resolved to a location on the internet where the record is stored. The optional enumerated type of the Concept may reflect which data elements are provided. If primary='true' the concept is the first level response to a query. If 'false' the concept may be a secondary concept linked directly or indirectly to the definition of a primary concept. Flag as to sexual form or parentage. List of options may extend in future but are mutually exclusive. Container for taxonomic assertion records. Relationships between two concepts which are not part of the original definition of either of these concepts; possibly by a third party. Information about the authorship of the asserted relationship. Starting point of the directed relationship. A reference to a TaxonConcept. End point of the directed relationship. A reference to a TaxonConcept. Unique identifier (key) of the element. It can be local to the data set or a GUID in which case it can be resolved to a location on the internet where the record is stored. Elements of this type are used to refer to other resources. They can be used in the following ways. 1) With text content and no attributes - a simple text representation of the resource. 2) With no text content but a ref attribute pointing to the location or the resource. 3) A combination of the two above. The text content is a summary or the resource referenced to in the ref attribute. The location of the resource. If the linkType attribute is not supplied agents should first presume this refers to the id of an element within the current document and then try to interpret it as a link to a resource available elsewhere on the network. Defines the meaning of the contents of the ref attribute. This is the id of another element within this document. A link to a resource in another document. It is presumed that the target will be returned as a valid TCS instance. A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf. Describes the origin of the concept or assertion. Unstructured string as used in the data source describing the origin of the concept (e.g. AuthorTeam and year). Details provided by the data source about the concept or relationship authors. This field should contain the authors of the concept. Note that the Simple sub element of this element is a signature field and should have the following content. For TCS signatures two situations are envisaged, one where concepts appear in printed publications and the other where concepts are published on-line. When representing a printed concept the field should contain the unabbreviated surnames of the authors in the order they appear in the publication separated by spaces. Initials and any punctuation marks should be omitted. If there are more than three authors only the first two author names should be included and they should be followed by the words “et al”. The full authorship of the concept will always be available via the <PublishedIn> element. Transliteration of names should be avoided unless they can't be represented in UTF-8 encoding. If the concept is being published on line, and does not exist in a paper form, then the DNS name of the institution publishing the concept should be used. A policy should be formulated for how many sub-domains should be cited and this should be stuck to. It is recommended that the “www” sub-domain should not be used (e.g. ipni.org not www.ipni.org). These DNS names are not expected to resolve to anything now or in future and so artificial sub-domains could be created to represent publishing authorities within larger organisation if required. If the concept is version sensitive then the DNS name should be followed by a space and then the versioning information. Reference ID or GUID of the original publication in which the concept or relationship was introduced. This is an additional qualification to the reference given by 'PublishedIn'. It for holding things such as "page 34" or "tab. 67" etc. Type attribute describe the type of relationship Any of an enumerated list of possible taxonomic relationships that may be expressed between two TaxonConcepts. Set Relationship: The extent of Concept 1 is (essentially) identical to Concept 2 Set Relationship: The extent of Concept 1 is not identical to Concept 2 Set Relationship: Concept 2 is a subset of Concept 1 Set Relationship: Concept 2 is not a subset of Concept 1 Set Relationship: Concept 1 does not overlap or include Concept 2 Set Relationship: Concept 1 is a subset of Concept 2 Set Relationship: Concept 1 is not a subset of Concept 2 Set Relationship: Concepts 1 and 2 share members/children in common Set Relationship: Concepts 1 and 2 have no members/children in common Hierarchical Relationship: Concept 1 is a member of lower taxonomic rank of Concept 2 Hierarchical Relationship: Taxon Concept 1 includes Concept 2 as a lower-ranked member. Concept 1 is the asexual or mitotic reproductive stage in a pleomorphic life cycle in which Concept 2 is the teleomorph or meiotic reproductive stage . Concept 1 is the teleomorph or meiotic reproductive stage in a pleomorphic life cycle in which Concept 2 is the asexual or mitotic reproductive stage. Hybrid Relationship: Concept 1 is genetic parent (2) of Concept 2 . Hybrid Relationship: Concept 1 is genetic mother of Concept 2 Hybrid Relationship: Concept 1 is genetic parent (1) of Concept 2 Hybrid Relationship: Concept 1 is genetic father of Concept 2 Hybrid Relationship: Concept 1 is genetic parent of Concept 2 Hybrid Relationship: Concept 2 is a genetic parent of Concept 1 Concepts have only a single scientific name. This name is governed by a single nomenclatural code. If an organism falls into two codes (not a desirable or frequent situation) then two TaxonConcepts should be created and linked with this relationship. e.g. a concept for the organism as an animal and a concept of it as a plant. The current concept is used as a vernacular concept, at least in part, for the target concept. This kind of relationship should not be used to express any form of set relationship (e.g. overlaps, is congruent with, includes). Consider using vernacular type relationships along with set type relationships to avoid any ambiguity. The target concept is used as a vernacular concept, at least in part, for the current concept. This kind of relationship should not be used to express any form of set relationship (e.g. overlaps, is congruent with, includes). Consider using vernacular type relationships along with set type relationships to avoid any ambiguity. The target concept is considered a synonym of the current concept. This is an ambiguous relationship. It can mean: 1) a nomenclatural relationship where all that is implied is that the type of the target concept is included in the current circumscription. This is more precisely expressed as a SpecimenCircumscription (for heterotypic synonyms) or as NameObject basionym relationships (for homotypic synonyms) 2) a concept relationship where some part of (or all of) the target concept is included in the current circumscription. This is more precisely expressed using the set relationships such as 'is congruent to'. Placeholder for other schema standards A full (non-atomized) name, including nomenclatural citation (authors/year in the form mandated by the relevant code). The name should be normalized (removing optional infrageneric or infraspecific hierarchy, author given only for the lowest nomenclatural rank) human readable and unique representation of the nomenclatoral name object. Where available, this should be generated from the canonical name and authorship plus Name extensions. In combination with the ID this constitutes the lowest abstraction a of name. Any other information is optional. The taxonomic rank of this name. Either as a string or as a code for a recognise rank or both. The code attribute is a TCS signature field. Canonical name enforcing strict inclusion of only nomenclatural information - _not_ taxonomic information with the exception of the necessary placements within Genus or Species. Authorship of the name, optionally atomized A link to where this name was first published. The year of publication of the name as it would appear in the publication. This is the publication year for THIS name combination not for the basionym should this be a comb nov. This is a TCS signature field. Specifies any minor reference parts connected to the name publication e.g. page number A container for type specimens and other vouchers. Names at species and below are typified by specimens. A reference to a type specimen for this name. A reference to the publication where the lectotype was nominated. Specifies any minor reference parts connected to the lectotypification publication e.g. page number The kind of type this specimen is e.g. paratype, isotype, holotype etc. Names above species level are typified by the NAME of a lower taxon. A reference to the name object that typifies this name. e.g. species for genus or genus for family etc. A reference to the publication where the lectotypes were nominated. Specifies any minor reference parts connected to the lectotypification publication e.g. page number The current name is a spelling correction of the name that is pointed to. The current name is a recombination (comb nov) of the name pointed to and the name pointed to is not, itself, a recombination. The current name is the validation of a that was not fully published before. Covers the use of ex in botanical author strings. ICBN Art. 46.4: e.g. if this name object represents G. tomentosum Nutt. ex Seem. then the pointer should point to G. tomentosum Nutt. The current name is conserved against the name pointed to. ICBN: Conservation is covered under Article 14 and Appendix II and Appendix III (this name is nomina conservanda). ICZN: Conservation is covered under Article 23.9 (this name is nomen protectum and the target name is nomen oblitum) Current name has same spelling as target name but was published later and has priority over it (unless conserved or sanctioned). See ICBN: Article 53, ICZN: Chapter 12, Article 52. With reference to fungi. ICBN: Articles 13.1d and 15. ICZN: No equivelent term for animals Current name is replacement for target name. Also called 'replacement name' or 'avowed substitute' ICBN: Article 7.3 ICZN: Article 60.3. Note concerning the publication status of the name. e.g. whether it is validly published. THIS SHOULD NOT BE USED TO IMPLY WHETHER THE NAME IS CONSIDERED TO REPRESENT AN ACCEPTED TAXON. An accepted taxon can only be represented as a TaxonConcept. Mechanism to allow for the extension of the schema for specific applications. Some fungal names under ICBN are termed anamorphic. This is because they have asexual types and aren't available for use for teleomorphic or holomorphic taxa. Use this flag to indicate that the name is anamorphic. The nomenclatural code that governs the construction and use of this name. This is a TCS signature field. A label containing the canonical name without authors. For the purposes of a TCS signature this field should contain nothing but the text strings representing the name itself with no indication of rank or any other qualifiers. Family, genus, infrafamilial or suprafamilial name The name of the genus. If this name is below the rank of genus then this may also be reference to a NameObject that contains the name of the genus. The specific epithet for the name. If this is subspecific taxon then this may be a link to another NameObject that contains the species. The name of the Cultivar, Cultivar Group, grex, convar or graft chimera. Under the ICNCP. Just include here the string of the name. i.e. ommit the single quotes around cultivar names, the word Group that denotes cultivar group and the + sign used in chimeras. These symbols can be added in later on the basis of the rank of the name. The user of Group for example is language dependant. The full code-appropriate author team string for this name at this rank. If author is not known, enter the literal "-" (element is not optional!). Examples: 'L.'; '(L.) Smith & Jones ex Brown, Green & Black'. Where atomized citation data exist, this text should be derived from them. This represents the authors of the basionym. It is usually displayed in brackets. This represents the authors of the new combination of this name. The authors who come after the brackets in the traditional way of citing botanical names. These authors are not usually cited in zoology though the ICZN recommends that they should be included (Art.51G). A collection (seq) of name strings, used for publication authors or editors and for collectors, i. e. whenever the identity of an Agent is doubtful and can not associated with an Agent without doubt Authors or Editors expressed only as string, e.g. in publications where the identity of creators can often not be discovered. Optionally, the ref attribute may refer to an agent if the relation between string and Agent can be assessed. A list of authors with a year if required. Taxonomic authors. The "ex" and ":" used in botanical names should be treated as special author names. Note that document order is important here! Taxonomic ranks can be represented as either a plain text string in the body of the element or an attribute from a controlled vocabulary. It is highly recommended that the attribute is used where ever possible. Controlled vocabulary to express taxonomic rank of scientific names in biology.

Enumerated codes to express the rank of a taxon (scientific organism name) in a taxonomic hierarchy. The list is intended to be interoperable between name providers for bacteria, viruses, fungi, plants, and animals. It is not assumed that in each taxonomic group all ranks have to be used. Individual applications may select appropriate subsets (which may be based on information given inside the enumerated values, see Specifications/BioCode-, Botany-, Zoology-, and BacteriaStatus). The enumeration attempts to strike a balance between listing all possible rank terms, and remaining comprehensible. For example, the "infra-" ranks specifically mentioned in BioCode have been included (although very rarely used), but the additional intermediate zoological ranks (micro, nano, pico, etc.) are not included. Whether the selection of infraspecific ranks (some informal ranks, esp. from bacteriology, may be missing!) probably needs some discussion. However, it is believed that this list may help to start developing data sets that can easily be integrated across the barriers of Language and taxonomic traditions.

Not included in the list are the botanical "notho-" ranks, which are used to designate hybrids (nothospecies, nothogenus). It is assumed they can be generated from separate information that the taxon is a hybrid. ICBN §4.4 states: "The subordinate ranks of nothotaxa are the same as the subordinate ranks of non-hybrid taxa, except that nothogenus is the highest rank permitted".

The following publications have been consulted to determine the number of type terms that should be included and to prepare the semantic definitions:

  • The Berlin Taxonomic Information Model, MoReTax view (Berendsohn & al., http://www.bgbm.org/scripts/ASP/BGBMModel/Catalogues.asp?Cat=MT
  • DiversityTaxonomy model version 0.7 (G. Hagedorn & T. Gräfenhan 2002, http://160.45.63.11/Workbench/Taxonomy/Model/InformationModels.html)
  • ABCD version 1.44, types HigherTaxonRankType and RankAbbreviationType, by W. Berendsohn, reviewed by D. Hobern
  • TaxCat2 - Database of Botanical Taxonomic Categories by Jörg Ochsmann, IPK Gatersleben; http://mansfeld.ipk-gatersleben.de/TaxCat2/default.htm

A separate enumeration and several ranks have been added to the original list to better accomodate names from ICNCP. (RDH).

Many thanks for review and help go to Dr. Walter Gams.

Note: the list of all ranks is implemented as a union of all following rank subsets. Note that although BioCode has been used to define the partition into subsets, the ranks are not limited to BioCode but should be an interoperable superset of ranks used in Virology, Bacteriology, Botany and Zoology.

 Subset of ranks; equivalent to BioCode "infra-subspecfic", i.e. below the species group [cand.] -- candidate -- Candidatus' rank is proposed in bacteriology for putative taxa, which could not yet be studied sufficiently to warrant the creation of a name with a known rank. (Murray, R.G.E. & Schleifer, K.H.: Taxonomic notes: a proposal for recording the properties of putative taxa of procaryotes. Int. J. Syst. Bacteriol., 1994, 44, 174-176). cand. - - - - - - - Proposed - - [tax. infrasp.] -- infraspecific tax. of undefined rank -- Undefined ranks (using either no rank identifier in botany, or using greek letters or symbols like stars, crosses) occur in very old publications. Most frequently these are to be interpreted as varieties, but occasionally they are forms or subspecies (see Stearn, W.T. 1957: Species plantarum (Facsimile); Introduction. 1. London, p. 90-95, 160-161, 163). The interpretation of these cases requires taxonomic knowledge that may not be available at the time when data are parsed. Such lack of knowledge can be expressed using this rank identifier. tax. infrasp. - - - - - - - - - - [f. sp.] -- special form -- The ICBN does not formally cover formae specialis (art. 4, note 3). However, because of the economic importance of pathogenic f. sp., and since it is common practice to handle them as if the code would apply (i. e. priority usually observed, name quoted with author), they are included here. f. sp. forma sp.; fsp.; fm. sp.; f. spec.; fm. spec.; forma spec. - - - - - - used, but all ranks below subsp. are not covered by ICNP/ICNB, see Rules 5d and 14a. ##Check whether this rank is used indeed. none - [subsubfm.] -- subsubform subsubfm. subsubf. - - - - - - - additional(?) - [subfm.] -- subform subfm. subf. - - - - - additional - additional - [fm.] -- form -- Form, race, variety are not subject to regulation in zoology; see ICZN Article 1.3.4 fm. f. - - - - - secondary - secondary - [subsubvar.] -- sub-sub-variety subsubvar. subsubv. - - - - - additional - additional - [subvar.] -- sub-variety subvar. subv. - - - - - additional - additional - [var.] -- variety -- Form, race, variety are not subject to regulation in zoology; see ICZN Article 1.3.4 Examples: Pinus nigra var. caramanica (= "P. nigra subsp. nigra var. caramanica"; Taxus baccata var. variegata var. v. - - - - - secondary used, but all ranks below subsp. are not covered by ICNP/ICNB, see Rules 5d and 14a. ##Check whether this rank is used indeed. secondary - [pathovar.] -- patho-variety pathovar. pv. - - - - - - used, but all ranks below subsp. are not covered by ICNP/ICNB, see Rules 5d and 14a. ##Check whether this rank is used indeed. - - [biovar.] -- bio-variety biovar. bv. - - - - - - used, but all ranks below subsp. are not covered by ICNP/ICNB, see Rules 5d and 14a. ##Check whether this rank is used indeed. - - [infrasp.] -- infraspecies infrasp. infrasp.; infraspec. - - - - - additional - - - Subset of ranks; equivalent to BioCode "species group", i.e. only species and subspecies [aggr.] -- subspecific aggregate (= group, complex) -- A loosely defined group of subspecies. Zoology: "Aggregate - a group of subspecies within a species. An aggregate may be denoted by a group name interpolated in parentheses." aggr. - - - - - - - - - [ssp.] -- subspecies -- Examples: Pinus nigra subsp. nigra Homo sapiens sapiens ssp. subsp.; subspec. - - - - - secondary covered additional additional [sp.] -- species -- Examples: Taxus baccata, Homo sapiens sp. spec. - - - - - primary covered principal principal Subset of ranks; equivalent to BioCode ""subdivision of a genus" ", i.e. all ranks between genus and species group (i.e. not including subgenus and species) [aggr.] -- species aggregate (= species group, species complex) -- A loosely defined group of species. Zoology: "Aggregate - a group of species, other than a subgenus, within a genus. An aggregate may be denoted by a group name interpolated in parentheses." -- The Berlin/MoreTax model notes: "[these] aren't taxonomic ranks but cirumscriptions because on the one hand they are necessary for the concatenation of the fullname and on the other hand they are necessary for distinguishing the aggregate or species group from the microspecies." Compare subspecific aggregate for a group of subspecies within a species! aggr. - - - - - - - - - [tax. infragen.] -- infrageneric tax. of undefined rank -- A name that appear between a genus name and a species epitheton and is not clearly marked as series or section, or other may be assigned to this rank until the true rank can be assigned by a taxonomic expert. tax. infragen. - - - - - - - - - - [subser.] -- subseries subser. * - - - - - additional - additional - [ser.] -- series ser. * - - - - - secondary - secondary - [subsect.] -- subsection subsect. * - - - - - additional - additional - [sect.] -- section sect. * - - - - - secondary - secondary - Subset of ranks; equivalent to BioCode "genus group", i.e. infragenus to genus [infragen.] -- infragenus infragen. * - - - - - additional - - - [subgen.] -- subgenus subgen. * - - - - - secondary covered additional additional [gen.] -- genus -- Examples: Magnolia Homo gen. - - - - - - primary covered principal principal Subset of ranks; equivalent to BioCode "subdivision of a family", i.e. ranks between genus group and family group [infratrib.] -- infratribe infratrib. - - - - - - additional - - - [subtrib.] -- subtribe subtrib. - -inae -inae -inae -inae -ina additional covered (but probably not in current use) additional - [trib.] -- tribe trib. - -eae -eae -eae -eae -ini secondary covered (but probably not in current use) secondary - [supertrib.] -- supertribe supertrib. - - - - - - additional - additional - Subset of ranks; equivalent to BioCode "family group", i.e. infrafamily to superfamily [infrafam.] -- infrafamily infrafam. - - - - - - additional - - - [subfam.] -- subfamily -- Examples: Magnolioideae subfam. - -oideae -oideae -oideae -oideae -inae secondary covered additional additional [fam.] -- family -- Examples: Magnoliaceae Hominidae fam. - -aceae -aceae -aceae -aceae -idae principal covered principal principal [superfam.] -- superfamily -- Examples: Magnoliacea superfam. - - -acea -acea -acea -oidea; -acea secondary - additional - Subset of ranks; equivalent to BioCode "suprafamilial". This rank group includes all ranks higher than superfamily (class, phylum/division, kingdom, domain) [infraord.] -- infraorder infraord. - - - - - - additional - - - [subord.] -- suborder -- Examples: Magnolineae Catarrhini subord. - -ineae -ineae -ineae -ineae - additional covered additional additional [ord.] -- order -- Examples: Magnoliales Primates ord. - -ales -ales -ales -ales - principal covered principal principal [superord.] -- superorder -- Examples: Magnolianae superord. - - -anae -anae -anae - additional - additional additional [infracl.] -- infraclass infracl. - - - - - - additional - - - [subcl.] -- subclass -- Examples: Magnoliidae Eutheria subcl. - -idae [proposed; Stackebrandt, E., Rainey, F.A. & Ward-Rainey, N.L.: Proposal for a new hierarchic classification system, Actinobacteria classis nov. Int. J. Syst. Bacteriol., 1997, 47, 479-491.] -idae -phycidae -mycetidae - additional covered additional additional [cl.] -- class -- Examples: Magnoliopsida Mammalia cl. - -ia [proposed; Stackebrandt, E., Rainey, F.A. & Ward-Rainey, N.L.: Proposal for a new hierarchic classification system, Actinobacteria classis nov. Int. J. Syst. Bacteriol., 1997, 47, 479-491.] -opsida -phyceae -mycetes - principal covered principal principal [supercl.] -- superclass supercl. - - - - - - additional - additional - [infraphyl./div.] -- infraphylum (= infradivision) infraphyl./div. - - - - - - additional - - - [subphyl./div.] -- subphylum (= subdivision) -- Examples: Magnoliophytina Vertebrata subphyl./div. - - -phytina -phytina -mycotina - additional - - additional [phyl./div.] -- phylum (= division) -- Examples: Magnoliophyta Chordata phyl./div. - - -phyta -phyta -mycota - principal used, but all ranks above class are not covered by ICNP/ICNB - principal [superphyl./div.] -- superphylum (= superdivision) superphyl./div. - - - - - - additional - - additional [infrareg.] -- infrakingdom infrareg. - - - - - - additional - - - [subreg.] -- subkingdom subreg. - - - - - - additional - additional additional [reg.] -- kingdom -- Examples: Plantae Animalia reg. - - - - - - principal used, but all ranks above class are not covered by ICNP/ICNB principal principal [superreg.] -- super kingdom -- Examples: Eucaryota superreg. - - - - - - additional - additional additional [dom.] -- domain (= empire) -- Examples: Archaea (= Archaeobacteria), Bacteria (= Eubacteria), Eukarya (= Eukaryota) dom. - - - - - - secondary used, but all ranks above class are not covered by ICNP/ICNB - - [tax. supragen.] -- suprageneric tax. of undefined rank -- This value indicates that the rank of a name is unknown. Compare "incertae sedis" which is commonly used as a replacement for a taxon to group all taxa whose position in the classification or phylogenetic tree is uncertain. tax. supragen. - - - - - - - - - - Subset of ranks used spefically for cultivated plants [cult.] -- cultivar -- The epithet is usually output in single quotes and may contain multiple words, see ICBN §28. Examples: Taxus baccata 'Variegata', Juniperus ×pfitzeriana 'Wilhelm Pfitzer'; Magnolia 'Elizabeth' (= a hybrid, no species epithet). cult. - - - - - - - - Reference to 'Internat. code of nomenclature for cultivated plants' - [convar.] -- convar -- Used in cultivated plants (ICNCP), but deprecated, see 'Some notes on problems of taxonomy and nomenclature of cultivated plants' by J. Ochsmann, http://www.genres.de/IGRREIHE/IGRREIHE/DDD/22-08.pdf convar. cv. - - - - - - - - - [grex] -- a rank equivalent to cultivar group used principly for artificial hybrid swams in Orchidaceae. grex grex - - - - - - - Reference to ICNCP - [cultivar. group] -- cultivar-group cultivar. group - - - - - - - - - - [graft-chimaera] -- graft-chimaera graft-chimaera - - - - - - - - - - Denomination classes are constructs under ICNCP for defining the scope within which a cultivar or Group epithet must be unique. denomination-class - - - - - - - - - -

This list is a first version of a constrained vocabulary to express typifying relations between taxonomic names and units (specimens or objects preserved in collections). Beyond those type categories explicitly governed by nomenclatural codes (Zoology, Botany, Bacterioloy, Virology), the list also includes some additional type status terms. These categories may be helpful when interpreting the original circumscription (topotypes, ex-types), but do not have the same binding status as terms governed by the nomenclatural codes. The enumeration attempts to strike a balance between listing all possible terms, and remaining comprehensible. In general, including too many terms was considered less problematic than omitting terms. Applications may easily select a subset for presentation in their user interface.

This list is intended as a first version and it is hoped that in the review process through TDWG it will achieve sufficient maturity to be truly useful. It is expected that over time revisions will have to be made. Please use the WIKI (http://efgblade.cs.umb.edu/twiki/bin/view/UBIF/NomenclaturalTypeStatusOfUnitsDiscussion) to discuss the current list and the lists of synonymous, doubtful, or excluded type terms provided therein.

Some background information: A type provides the objective standard of reference to determine the application of a taxon name. The type status of a unit (specimen) is only meaningful in combination with the name that is being typified (a unit may have been designated type for multiple names in different publications). The type status of an object may be designated in the original description of a scientific name (original designation), or - under rules layed out in the respective nomenclatural codes - at a later time (subsequent designation). -- For taxa above species rank the type is always a lower rank taxon (e. g., species for genus, genus for family). The type terms for this situation are not included in the enumeration. Ultimately, typication of all taxa goes back to physical type units, but this should not be recorded as such in data sets. The indirect type reference in higher taxa means that typification changes to the lower taxon automatically affect the higher taxon.

The exact definitions of type status differ between nomenclatural codes (ICBN, ICZN, ICNP/ICNB, etc.). The term definitions are intended to be informative and generally applicable across the different codes. The should not be interpreted as authoritative; in nomenclatural work the exact definitions in the respective codes have to be consulted. A duplication of status codes (bot-holo, zoo-holo, bact-holo, etc.) is not considered desirable or necessary. Since the application of the type status terms is constrained by the relationship of the typified name with a specific code, the exact definition can always be unambiguously retrieved.

The following publications have been consulted to determine the number of type terms that should be included and to prepare the semantic definitions:

  • Nomenclatural Glossary for Zoology (January 18 2000; ftp://ftp.york.biosis.org/sysgloss.txt; verified 17. June 2004)
  • ICBN St. Louis Code (http://www.bgbm.fu-berlin.de/iapt/nomenclature/code/SaintLouis/0013Ch2Sec2a009.htm; verified 17. June 2004)
  • Draft BioCode 4th version (Greuter et al., 1997; http://www.rom.on.ca/biodiversity/biocode/biocode1997.html)
  • Glossary of 'type' terminology (Ronald H. Petersen; http://fp.bio.utk.edu/mycology/Nomenclature/nom-type.htm)
  • Dictionary of Ichthyology (Brian W. Coad and Don E. McAllister, 2004; http://www.briancoad.com/Dictionary/introduction.htm)
  • A useful resource that was not available when writing this proposal might be: Hawksworth, D.L., W.G. Chaloner, O. Krauss, J. McNeill, M.A. Mayo, D.H. Nicolson, P.H.A. Sneath, R.P. Trehane and P.K. Tubbs. 1994. A draft Glossary of terms used in Bionomenclature. (IUBS Monogr. 9) International Union of Biological Sciences, Paris. 74 pp.

Many thanks for review and help to Dr. Miguel A. Alonso-Zarazaga and Dr. Walter Gams. Gregor Hagedorn, 13.7.2004

 Allotype -- A paratype specimen designated from the type series by the original author that is the opposite sex of the holotype. The term is not regulated by the ICZN. [Zoo.] Allolectotype -- A paralectotype specimen that is the opposite sex of the lectotype. The term is not regulated by the ICZN. [Zoo.] Alloneotype -- A paraneotype specimen that is the opposite sex of the neotype. The term is not regulated by the ICZN. [Zoo.] Cotype -- A deprecated term no longer recognized in the ICZN; formerly used for either syntype or paratype [see ICZN Recommendation 73E]. [Zoo.] Epitype -- An epitype is a specimen or illustration selected to serve as an interpretative type when any kind of holotype, lectotype, etc. is demonstrably ambiguous and cannot be critically identified for purposes of the precise application of the name of a taxon (see Art. ICBN 9.7, 9.18). An epitype supplements, rather than replaces existing types. [Bot./Bio.] Ex-Type -- A strain or cultivation derived from some kind of type material. Ex-types are not regulated by the botanical or zoological code. [Zoo./Bot.] Ex-Epitype -- A strain or cultivation derived from epitype material. Ex-types are not regulated by the botanical or zoological code. [Bot.] Ex-Holotype -- A strain or cultivation derived from holotype material. Ex-types are not regulated by the botanical or zoological code. [Zoo./Bot.] Ex-Isotype -- A strain or cultivation derived from isotype material. Ex-types are not regulated by the botanical or zoological code. [Zoo./Bot.] Ex-Lectotype -- A strain or cultivation derived from lectotype material. Ex-types are not regulated by the botanical or zoological code. [Zoo./Bot.] Ex-Neotype -- A strain or cultivation derived from neotype material. Ex-types are not regulated by the botanical or zoological code. [Zoo./Bot.] Ex-Paratype -- A strain or cultivation derived from paratype material. Ex-types are not regulated by the botanical or zoological code. [Zoo./Bot.] Ex-Syntype -- A strain or cultivation derived from neotype material. Ex-types are not regulated by the botanical or zoological code. [Zoo./Bot.] Hapantotype -- One or more preparations of directly related individuals representing distinct stages in the life cycle, which together form the type in an extant species of protistan [ICZN Article 72.5.4]. A hapantotype, while a series of individuals, is a holotype that must not be restricted by lectotype selection. If a hapantotype is found to contain individuals of more than one species, however, components may be excluded until it contains individuals of only one species [ICZN Article 73.3.2]. [Zoo.] Holotype -- The one specimen or other element used or designated by the original author at the time of publication of the original description as the nomenclatural type of a species or infraspecific taxon. A holotype may be 'explicit' if it is clearly stated in the originating publication or 'implicit' if it is the single specimen proved to have been in the hands of the originating author when the description was published. [Zoo./Bot./Bio.] Iconotype -- A drawing or photograph (also called 'phototype') of a type specimen. Note: the term "iconotype" is not used in the ICBN, but implicit in, e. g., ICBN Art. 7 and 38. [Zoo./Bot.] Isotype -- An isotype is any duplicate of the holotype (i. e. part of a single gathering made by a collector at one time, from which the holotype was derived); it is always a specimen (ICBN Art. 7). [Bot.] Isolectotype -- A duplicate of a neotype, compare lectotype. [Bot.] Isoneotype -- A duplicate of a neotype, compare neotype. [Bot.] Isosyntype -- A duplicate of a syntype, compare isotype = duplicate of holotype. [Bot.] Lectotype -- A specimen or other element designated subsequent to the publication of the original description from the original material (syntypes or paratypes) to serve as nomenclatural type. Lectotype designation can occur only where no holotype was designated at the time of publication or if it is missing (ICBN Art. 7, ICZN Art. 74). [Zoo./Bot.] -- Note: the BioCode defines lectotype as selection from holotype material in cases where the holotype material contains more than one taxon [Bio.]. Neotype -- A specimen designated as nomenclatural type subsequent to the publication of the original description in cases where the original holotype, lectotype, all paratypes and syntypes are lost or destroyed, or suppressed by the (botanical or zoological) commission on nomenclature. In zoology also called "Standard specimen" or "Representative specimen". [Zoo./Bot./Bio.] Paratype -- All of the specimens in the type series of a species or infraspecific taxon other than the holotype (and, in botany, isotypes). Paratypes must have been at the disposition of the author at the time when the original description was created and must have been designated and indicated in the publication. Judgment must be exercised on paratype status, for only rarely are specimens explicitly cited as paratypes, but usually as "specimens examined," "other material seen", etc. [Zoo./Bot.] Paralectotype -- All of the specimens in the syntype series of a species or infraspecific taxon other than the lectotype itself. Also called "lectoparatype". [Zoo.] Paraneotype -- All of the specimens in the syntype series of a species or infraspecific taxon other than the neotype itself. Also called "neoparatype". [Zoo.] Plastotype -- A copy or cast of type material, esp. relevant for fossil types. Not regulated by the botanical or zoological code (?). [Zoo./Bot.] Plastoholotype -- A copy or cast of holotype material (compare Plastotype). Plastoisotype -- A copy or cast of isotype material (compare Plastotype). Plastolectotype -- A copy or cast of lectotype material (compare Plastotype). Plastoneotype -- A copy or cast of neotype material (compare Plastotype). Plastoparatype -- A copy or cast of paratype material (compare Plastotype). Plastosyntype -- A copy or cast of syntype material (compare Plastotype). Secondary type -- A referred, described, measured or figured specimen in the original publication (including a neo/lectotypification publication) that is not a primary type. Supplementary type -- A referred, described, measured or figured specimen in a revision of a previously described taxon. Syntypes -- The series of specimens used to describe a species or infraspecific taxon when neither a single holotype by the original author, nor a lectotype in a subsequent publication has been designated. The syntypes collectively constitute the name-bearing type. [Zoo./Bot.] Topotype -- One or more specimens collected at the same location as the type series (type locality), regardless of whether they are part of the type series. Topotypes are not regulated by the botanical or zoological code. Also called "locotype". [Zoo./Bot.] Type -- a) A specimen designated or indicated any kind of type of a species or infraspecific taxon. If possible more specific type terms (holotype, syntype, etc.) should be applied. b) the type name of a name of higher rank for taxa above the species rank. [General] not a type -- For specimens erroneously labelled as types an explicit negative statement may be desirable. [General] Enumeration of the nomenclatural code under which a name is considered valid. (Source: comparison of enumerations in ABCD 1.49 and initial LinneanCore.) International Code of Botanical Nomenclature, ICBN International Code of Zoological Nomenclature, ICZN International Code of cultivated plants, ICNCP Examples: ambiregnally named taxa can not be fixed to a code; to express the (pre-starting point) names on which the sanctioning mechanism of fungal names is based. A base object that defines a common structure for a number of elements within NameObject. The article/note/recommendation in the code in question that is commented on below Comment concerning this name. If status is conservation, the rejected name and vice versa, if illegitmate because homonym the earlier homonym, etc. The publication/reference source used to determine the nomenclatural status. Specifies any minor reference parts connected to the According to publication e.g. page number