Skip to content

property:misapplication #199

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

Closed
nielsklazenga opened this issue Jan 21, 2022 · 4 comments
Closed

property:misapplication #199

nielsklazenga opened this issue Jan 21, 2022 · 4 comments
Labels
class:TaxonConcept Organized in the TaxonConcept class new term The 'new term' label is applied to terms that were not in TCS 1. property RDF type of term is 'property'

Comments

@nielsklazenga
Copy link
Member

misapplication(property)

Label Misapplication
Definition Usage of a Taxon Name that does not include its nomenclatural type
Usage notes
Comments The Botanical Code recommends that misapplied names are listed – if they are listed – separately from the synonymy and with 'auct. non' in the authorship.
Required No
Repeatable Yes
Constraints Object
@nielsklazenga nielsklazenga added class:TaxonConcept Organized in the TaxonConcept class new term The 'new term' label is applied to terms that were not in TCS 1. property RDF type of term is 'property' labels Jan 21, 2022
@nielsklazenga
Copy link
Member Author

This term, despite being a new term, has been included, because we consider that it could have been included in the has synonym relationship type in TCS 1. Since we are proposing to break down the Taxon Relationship class, which only leaves Taxon Alignments in a separate class (#43), misapplication is best dealt with as a property of Taxon Concept. Misapplications are best dealt with as a Taxon Alignment, but the mapping is not straightforward and the rationale for including this extra term is to be able to exchange this information without the need for an expert opinion.

@nielsklazenga nielsklazenga added this to the Taxon Concept terms for 01 Feb 2022 meeting milestone Jan 24, 2022
@Archilegt
Copy link

"Usage of a Taxon Name that does not include its nomenclatural type". Observation: The types may be included in the usage of a scientific name, but if the types are incorrectly described or defined, usage may also result in misapplication. Therefore:

Definition: Usage of a scientific name in a manner not in accord with the name-bearing type. (This one should do for all cases)

@nielsklazenga
Copy link
Member Author

nielsklazenga commented Feb 1, 2022

I do not understand the difference, but would be happy with your definition as well. However, although the problems are not quite as big, just as for proParteSynonym (#200), I think we should first consider if we should have the term at all.

[I actually do have a problem with 'name-bearing type'. That might be a thing in zoological nomenclature, but in botany it means nothing. A nomenclatural type fixes the usage of a name, but can bear all names that apply to the taxon it belongs to. Also, "types [that] are incorrectly described or defined" are (by definition) not nomenclatural types.]

@nielsklazenga
Copy link
Member Author

Opened issue #205 to replace this and #200.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
class:TaxonConcept Organized in the TaxonConcept class new term The 'new term' label is applied to terms that were not in TCS 1. property RDF type of term is 'property'
Projects
None yet
Development

No branches or pull requests

2 participants