-
Notifications
You must be signed in to change notification settings - Fork 1
property:proParteSynonym #200
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
Comments
This term, despite being a new term, has been included, because we consider that it was included in the The definition according to Franz and Peet (2009):
..., which I based the definition above on, indicates that the name of a |
Not always because of "broader circumscription" but also because of misidentifications/misapplications, often without implying a different taxonomic concept but just careless examination of specimens. The term is difficult to define because it overlaps with taxonomic concepts and scientific names. Definition: Taxonomic Concept including more than one currently recognized taxonomic concept, while only one of those taxonomic concepts is being considered a synonym of the |
I have a suggestion to make. I think TCS really should not allow (or endorse) the exchange of "pro-parte synonyms" and "misapplications" (#199), whatever they are, in this form. These things are really taxon relationships/alignments (cf. #43), not nomenclatural relationships like the labels suggest, and should be exchanged as such. The rational for having these terms in the first place is that people want to exchange the information straight from the page without data entry folk having to do expert interpretations (which would make the assertion theirs and not by the authors of the publication). So lets make that possible under Taxon Alignments (which is what we call Taxon Relationships now), so the data ends up in the place it belongs. We have added a controlled term |
proParteSynonym (property)
The text was updated successfully, but these errors were encountered: