The TCS 2 Task Group will turn TCS into a form in which it can be maintained. The new version of TCS will be a vocabulary standard like Darwin Core and Audiovisual Core and will complement these other existing TDWG standards.
An identifiable taxonomic position that can be aligned to other such positions through TCS concept mapping relationships.
Usage
A TaxonConcept MUST have taxonName and accordingTo properties.
Comments
A taxonomic position is an opinion about the definition of a taxonomic group. A Taxon Concept is identifiable, because it combines a label – taxonName in TCS – with a source – accordingTo. Both the taxonName and accordingTo properties are required on a tcs:TaxonConcept. When mentioning a taxon concept, the label and the source are combined, separated by 'sec.' (from, 'secundus', meaning 'according to') or 'sensu' (meaning the same). The term dcterms:title has been borrowed from Dublin Core to provide this taxon concept label. Because of the context provided by the source, taxon concepts are in principle also alignable to other Taxon Concepts using TCS concept mapping statements. The concept mapping properties in TCS are isCongruentWith, includes, isIncludedIn, partiallyOverlaps, isDisjointFrom and intersects. These properties can be used directly on a TaxonConcept object or as the value of the tcs:mappingRelation property in a tcs:TaxonConceptMapping object.
The TCS Taxon Concept is applied more broadly than the term is used in science (e.g. Franz & Peet 2009 [franz_perspectives_2009]). On the one hand, things that are not generally considered to be biological taxa, e.g. hybrids and cultivars, can be casted as TCS Taxon Concepts. Also Operational Taxonomic Units (OTUs) [sokal_principles_1963] can be exchanged as Taxon Concepts, if there is a reason to do so, e.g. if one wants to align them with other Taxon Concepts later. On the other hand, entries from treatments that are considered to cite concepts from other treatments can be formulated as Taxon Concepts. Every taxon concept from a treatment that is likely to be referenced as the source of taxonomic context, for example a field guide for a determination of a specimen or a national census for an ecological study, can – and it would be very nice if they would – be stated as a Taxon Concept, so they can be aligned with other Taxon Concepts that may provide more or different taxonomic context.
By contrast, entries in the nomenclature section of treatments ('TaxonomicNameUsage's sensu Senderov et al. 2018 [senderov_openbiodiv-o_2018]) and in lists of nomenclatural types are not Taxon Concepts.
Examples
[] a tcs:TaxonConcept ;
dcterms:title "Dicranoloma blumei sec. Klazenga 1999" ;
tcs:accordingTo <https://www.tropicos.org/reference/9020903>
tcs:taxonName <https://www.tropicos.org/name/35121475> .
<https://www.tropicos.org/name/35121475> a tcs:TaxonName ;
tcs:taxonNameString "Dicranoloma blumei" ;
dwc:scientificNameAuthorship "(Nees) Renauld" .
<https://www.tropicos.org/reference/9020903> a bibo:AcademicArticle ;
dcterms:bibliographicCitation """Klazenga, N. (1999). A revision of the
Malesian species of Dicranoloma (Dicranaceae, Musci). Journal of the
Hattori Botanical Laboratory 87: 1-130.""" .
[] a tcs:TaxonConcept ;
dcterms:title "Calymperes moluccense sec. Yong et al. 2013" ;
tcs:accordingTo <urn:isbn:978-967-5221-99-6> ;
tcs:taxonName <https://www.tropicos.org/name/35153806> .
<https://www.tropicos.org/name/35153806> a tcs:TaxonName ;
tcs:taxonNameString "Calymperes moluccense" ;
dwc:scientificNameAuthorship "Schwägr." .
<urn:isbn:978-967-5221-99-6> a bibo:Book ;
dcterms:bibliographicCitation """Yong, K.T.; Tan, B.C.; Ho, B.C.; Ho, Q.Y.;
Mohamed, H. (2013). A revised Moss Checklist of Peninsular Malaysia
and Singapore. Research Pamphlet no. 133, Forest Research Institute
Malaysia, Kepong, Malaysia.""" .
# Species Hypothesis (SH) from UNITE
<https://doi.plutof.ut.ee/doi/10.15156/BIO/SH1109146.09FU> a tcs:TaxonConcept ;
tcs:taxonName [ a skosxl:Label ;
skosxl:literalForm "SH1109146.09FU" ] ;
tcs:accordingTo <https://unite.ut.ee> ;
tcs:isIncludedIn <https://doi.plutof.ut.ee/doi/10.15156/BIO/TH077737> .
<https://doi.plutof.ut.ee/doi/10.15156/BIO/TH077737> a tcs:TaxonConcept ;
tcs:accordingTo <https://unite.ut.ee> ;
tcs:taxonName <https://www.indexfungorum.org/names/NamesRecord.asp?RecordID=17175> .
<https://www.indexfungorum.org/names/NamesRecord.asp?RecordID=17175> a tcs:TaxonNAme ;
tcs:taxonNameString "Boletus" ;
dwc:scientificNameAuthorship "L" ;
dwc:namePublishedIn "Sp. pl. 2: 1176" ;
dwc:namePublishedInYear "1753" .
<https://unite.ut.ee> a bibo:Website ;
dcterms:title """UNITE: rDNA ITS based identification of Eukaryotes and
their communication via DOIs""" ;
bibo:uri "https://unite.ut.ee" .
TaxonConcept (class)
An identifiable taxonomic position that can be aligned to other such positions through TCS concept mapping relationships.
A
TaxonConcept
MUST havetaxonName
andaccordingTo
properties.Comments
A taxonomic position is an opinion about the definition of a taxonomic group. A Taxon Concept is identifiable, because it combines a label –
taxonName
in TCS – with a source –accordingTo
. Both thetaxonName
andaccordingTo
properties are required on atcs:TaxonConcept
. When mentioning a taxon concept, the label and the source are combined, separated by 'sec.' (from, 'secundus', meaning 'according to') or 'sensu' (meaning the same). The termdcterms:title
has been borrowed from Dublin Core to provide this taxon concept label. Because of the context provided by the source, taxon concepts are in principle also alignable to other Taxon Concepts using TCS concept mapping statements. The concept mapping properties in TCS areisCongruentWith
,includes
,isIncludedIn
,partiallyOverlaps
,isDisjointFrom
andintersects
. These properties can be used directly on aTaxonConcept
object or as the value of thetcs:mappingRelation
property in atcs:TaxonConceptMapping
object.The TCS Taxon Concept is applied more broadly than the term is used in science (e.g. Franz & Peet 2009 [franz_perspectives_2009]). On the one hand, things that are not generally considered to be biological taxa, e.g. hybrids and cultivars, can be casted as TCS Taxon Concepts. Also Operational Taxonomic Units (OTUs) [sokal_principles_1963] can be exchanged as Taxon Concepts, if there is a reason to do so, e.g. if one wants to align them with other Taxon Concepts later. On the other hand, entries from treatments that are considered to cite concepts from other treatments can be formulated as Taxon Concepts. Every taxon concept from a treatment that is likely to be referenced as the source of taxonomic context, for example a field guide for a determination of a specimen or a national census for an ecological study, can – and it would be very nice if they would – be stated as a Taxon Concept, so they can be aligned with other Taxon Concepts that may provide more or different taxonomic context.
By contrast, entries in the nomenclature section of treatments ('TaxonomicNameUsage's sensu Senderov et al. 2018 [senderov_openbiodiv-o_2018]) and in lists of nomenclatural types are not Taxon Concepts.
Examples
[TaxonConcept-example-1.ttl] [TaxonConcept-example-1.jsonld]
[TaxonConcept-example-2.ttl] [TaxonConcept-example-2.jsonld]
[TaxonConcept-example-3.ttl] [TaxonConcept-example-3.jsonld]
[TaxonConcept-example-4.ttl] [TaxonConcept-example-4.jsonld]
[TaxonConcept-example-5.ttl] [TaxonConcept-example-5.jsonld]
[TaxonConcept-example-6.ttl] [TaxonConcept-example-6.jsonld]
[TaxonConcept-example-7.ttl] [TaxonConcept-example-7.jsonld]
Mapping