You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously, taxonomic units (TU) were identified based on the properties they had: a TU with a scientific name referred to a taxon, one with an occurrence ID referred to a specimen, and so on. A single TU was also allowed to have multiple scientific names or multiple occurrence IDs. This meant that you could represent a huge variety of taxonomic units, but it also meant that figuring out what a particular TU actually meant could be really complicated. Designing a user interface that could handle all this complexity was also a challenge.
Instead, I propose that we simplify taxonomic units so that each taxonomic unit must have a single type (stored in the JSON-LD @type property), indicating whether they are taxon concepts (with or without a citation) or specimens. This will also make it easier to add taxonomic units for apomorphies and phylorefs later on.
In the Phyx and the OWL/JSON-LD file, this will look like this:
One nice this about this approach is that this is pretty readable both as annotations and in the class expression in Protege.
(This example doesn't have the nomenclatural code, since I need to figure out how to add that on the phylogeny!)
You can also provide a more detailed description if you need to using the TDWG Taxon Concept ontology, such as including original descriptions or circumscription information (i.e. the accordingTo, sensu or sec):
This PR cleans up taxonomic units in several ways:
- Taxonomic units have clear types (stored in the `@type` property), indicating whether they are taxon concepts (with or without a citation) or specimens, allowing us to more easily add taxonomic units for apomorphies and phylorefs later on. (closes#20).
- RDF properties used by taxon concepts and names have been rewritten to bring them more into line with the TDWG ontologies TaxonConcept and TaxonName, including the use of `TaxonName:nameComplete` instead of `dwc:scientificName` (closes#8).
- External references are stored in the `@id` element rather than in a separate property.
- Added support for nomenclatural codes in scientific names (as per phyloref/klados#143). Note that this PR includes an earlier version of the nomenclature code system; this is updated and improved in #26.
This PR also introduces a new `TaxonConceptWrapper` as an analogue to `SpecimenWrapper` and renames the `ScientificNameWrapper` to the shorter `TaxonNameWrapper`.
Previously, taxonomic units (TU) were identified based on the properties they had: a TU with a scientific name referred to a taxon, one with an occurrence ID referred to a specimen, and so on. A single TU was also allowed to have multiple scientific names or multiple occurrence IDs. This meant that you could represent a huge variety of taxonomic units, but it also meant that figuring out what a particular TU actually meant could be really complicated. Designing a user interface that could handle all this complexity was also a challenge.
Instead, I propose that we simplify taxonomic units so that each taxonomic unit must have a single type (stored in the JSON-LD
@type
property), indicating whether they are taxon concepts (with or without a citation) or specimens. This will also make it easier to add taxonomic units for apomorphies and phylorefs later on.In the Phyx and the OWL/JSON-LD file, this will look like this:
One nice this about this approach is that this is pretty readable both as annotations and in the class expression in Protege.
(This example doesn't have the nomenclatural code, since I need to figure out how to add that on the phylogeny!)
You can also provide a more detailed description if you need to using the TDWG Taxon Concept ontology, such as including original descriptions or circumscription information (i.e. the
accordingTo
, sensu or sec):What do you think?
The text was updated successfully, but these errors were encountered: