-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TaxonRank #159
Comments
Standardized according to what taxonomic authority? Do you want to go down
this road?
…On Sat, Sep 1, 2018 at 12:46 AM, Arthur Chapman ***@***.***> wrote:
I was asked by someone at TDWG (and there was some discussion in one of
the SPNHC meetings) if we had a test for taxonRank. What do you think
people? Should we add:
VALIDATION_TAXONRANK_EMPTY,
VALIDATION_TAXONRANK_NOTSTANDARD
AMENDMENT_TAXONRANK_STANDARDIZED
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#159>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAcc7DnNo1NT_MTQ0voD8cv0EiBbnqGSks5uWhE3gaJpZM4WWEv8>
.
|
Don't each of the Codes have a standard list of Ranks? I know there are other ranks that are used - but if they are ones not in the Code. The Standardizing would change ssp. to subsp. or (vice versa, I can't remember) and things like that. If it was one that can't be changed, then an assertion is made to say it could not be so amended, |
I think we definitely want this test, and I do not think it depends on any taxonomic authority, but rather on the codes. |
My understanding of the botanical code at least is that there are Code-mandated ranks, but the Code allows inter-ranks to be created more or less willy-nilly: From https://en.wikipedia.org/wiki/Taxonomic_rank#Ranks_in_botany: "There is an indeterminate number of ranks, as a taxonomist may invent a new rank at will, at any time, if they feel this is necessary. In doing so, there are some restrictions, which will vary with the nomenclature code which applies." I'm not sure if these non-Code ranks would be regarded as NOTSTANDARD. |
Note with this comment I'm not saying this is a good idea! Personally, I reckon we should retract to only the Linnaean ranks, then use rank-free taxa (or better still, a phylogeny) for anything else. But that's another conversation. |
Looking through the Botanical Code - ranks are not actually mandated 2.1. Every individual organism is treated as belonging to an indefinite number of taxa at consecutively subordinate ranks, among which the rank of species is basic. These terms are all well covered by the GBIF Vocabulary at http://rs.gbif.org/vocabulary/gbif/rank.xml The Zoological Code doesn't say much at all about Ranks - and what they do say doesn't contradict the Botanical Code. Similarly for the Virus Code By creating a Test for NON_STANDARD - if it does not fit one of those Ranks (in the GBIF doc) an annotation is made - it is not saying it is Wrong - just that it is not one of those Standard Ranks. For the STANDARDIZED test - GBIF includes a number of other language equivalents that could be amended. At TDWG2018 - the issue of taxonRank was raised in several discussions and several people recommended including such a test. |
Yup, I agree that this would be good test to include. The annotation would include the authority that scientificName is checked/standardized against. |
I also agree. As part of cleaning a data set one might want to use services to fill in missing ranks. |
I don't think so - the GBIF reference includes all the relevant terms in the Vocabulary - and several people want the tests. I wrote the tests with the knowledge of what I wrote above, so I don't think any change is needed. |
I was asked by someone at TDWG (and there was some discussion in one of the SPNHC meetings) if we had a test for taxonRank. What do you think people? Should we add:
VALIDATION_TAXONRANK_EMPTY,
VALIDATION_TAXONRANK_NOTSTANDARD
AMENDMENT_TAXONRANK_STANDARDIZED
The text was updated successfully, but these errors were encountered: