/DataSet/TaxonConcepts/TaxonConcept
/DataSet/TaxonNames/TaxonName
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 preferred.
Container for vouchers (representation of specimen) records.
Specimen and location
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.
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.
Container for publication records.
Details of the data source.
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.
Full bibliographic reference as a single formatted string.
Mechanism to allow for the extension of the schema for specific applications.
A container element for TaxonName.
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.
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 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.
Controlled vocabulary to express taxonomic rank of scientific names in biology.
Canonical name enforcing strict inclusion of only nomenclatural information - _not_ taxonomic information with the exception of the necessary placements within Genus or Species.
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 TaxonName that contains the name of the genus.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
The specific epithet for the name. If this is subspecific taxon then this may be a link to another TaxonName 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. omit 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.
Authorship of the name, optionally atomized
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.
Taxonomic authors.
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.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
This represents the authors of the basionym. It is usually displayed in brackets.
Taxonomic authors.
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.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
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).
Taxonomic authors.
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.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
A link to where this name was first published.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
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.
The kind of type this specimen is e.g. paratype, isotype, holotype etc.
A reference to a type specimen for this name.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
A reference to the publication where the lectotype was nominated.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
Specifies any minor reference parts connected to the lectotypification publication e.g. page number
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.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
A reference to the publication where the lectotypes were nominated.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
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 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 illegitimate because homonym the earlier homonym, etc.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
The publication/reference source used to determine the nomenclatural status.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
Specifies any minor reference parts connected to the According to publication e.g. page number
The current name is a recombination (comb nov) of the name pointed to and the name pointed to is not, itself, a recombination.
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 illegitimate because homonym the earlier homonym, etc.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
The publication/reference source used to determine the nomenclatural status.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
Specifies any minor reference parts connected to the According to publication e.g. page number
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 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 illegitimate because homonym the earlier homonym, etc.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
The publication/reference source used to determine the nomenclatural status.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
Specifies any minor reference parts connected to the According to publication e.g. page number
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)
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 illegitimate because homonym the earlier homonym, etc.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
The publication/reference source used to determine the nomenclatural status.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
Specifies any minor reference parts connected to the According to publication e.g. page number
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.
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 illegitimate because homonym the earlier homonym, etc.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
The publication/reference source used to determine the nomenclatural status.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
Specifies any minor reference parts connected to the According to publication e.g. page number
With reference to fungi. ICBN: Articles 13.1d and 15. ICZN: No equivalent term for animals
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 illegitimate because homonym the earlier homonym, etc.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
The publication/reference source used to determine the nomenclatural status.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
Specifies any minor reference parts connected to the According to publication e.g. page number
Current name is replacement for target name. Also called 'Nomen Novum' or 'avowed substitute' ICBN: Article 7.3 ICZN: Article 60.3.
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 illegitimate because homonym the earlier homonym, etc.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
The publication/reference source used to determine the nomenclatural status.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
Specifies any minor reference parts connected to the According to publication e.g. page number
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.
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 illegitimate because homonym the earlier homonym, etc.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
The publication/reference source used to determine the nomenclatural status.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
Specifies any minor reference parts connected to the According to publication e.g. page number
Mechanism to allow for the extension of the schema for specific applications.
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.
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.
A non-unique handle to the concept. This can represent the name as published.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
The taxonomic rank of this concept. Either as a string or as a code for a recognise rank or both.
Controlled vocabulary to express taxonomic rank of scientific names in biology.
Information about the authorship of this concept which uses the Name in their sense (i.e. secundum, sensu).
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.
Taxonomic authors.
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.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
Reference ID or GUID of the original publication in which the concept or relationship was introduced.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
This is an additional qualification to the reference given by 'PublishedIn'. It for holding things such as "page 34" or "tab. 67" etc.
Stores explicit, taxonomic and nomenclatural relationships that are part of the original concept definition.
Type of the relationship
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 TaxonName 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'. This is intended for handling legacy data.
Reference to another TaxonConcept.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
A set of specimens that are used to define the concept.
Link to record of a specimen.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
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.
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.
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 TaxonName 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'. This is intended for handling legacy data.
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.
Information about the authorship of the asserted relationship.
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.
Taxonomic authors.
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.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
Reference ID or GUID of the original publication in which the concept or relationship was introduced.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
This is an additional qualification to the reference given by 'PublishedIn'. It for holding things such as "page 34" or "tab. 67" etc.
Starting point of the directed relationship. A reference to a TaxonConcept.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.
End point of the directed relationship. A reference to a TaxonConcept.
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.
A link to another resource external to the current document that is not in TCS format. e.g. a jpeg, html page or pdf.