From discussions at 2021 CF and a subsequent Zoom meeting it emerged that biological_taxon_name and Darwin Core scientificName are not exact synonyms (the latter is broader because it doesn't require association with an identifier). Likewise biological_taxon_lsid is broader than scientific_name_id because there are other identification schemes. This relationship has been documented in the Standard Name description.
It also became clear that CF - a standard developed for global climate model data and based on text-unfriendly NetCDF - might not be the most appropriate standard for low-volume biological datasets that are usually handled in spreadsheets. Should the use case for going into CF be strong enough then they can be accommodated, but not as easily as encoding into Darwin Core. The sorts of biological dataset well-matched to CF are high volume data like model output, satellite images and data syntheses.
Consequently, it is proposed that no further action be taken on this ticket.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.