-
Notifications
You must be signed in to change notification settings - Fork 0
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
property: vernacularName #10
Comments
The definition is tautological, and vernaculars are not "alternative to" but "opposed to". New The Comment does not apply. Vernaculars exist also in absence of scientific names. |
We are defining the We could try to provide a definition of 'vernacular name' and move the requirement that it is used alongside and as an alternative to the To use an analogy with SKOS:
To deal with different kinds of names the |
I have done what I said two-and-a-half years ago I did not want to do and changed the definition. |
See tdwg/dwc#524 (comment) for a suggestion for another definition. Thanks @qgroom. |
vernacularName (property)
Name for an organism or organisms in a language used for general purposes.
vernacularName
is an IRI term; a Taxon Concept can have more than onevernacularName
.Comments
The
vernacularName
property can be used when a vernacular name is used alongside a scientific name, which is thetaxonName
. If a vernacular name is the only name, thetaxonName
property should be used. The object of thevernacularName
property can be a Taxon Name, but another label object, such as the GBIF Vernacular Name, might be preferrable, especially if there can be multiple vernacular names for a concept.Examples
[TaxonConcept-vernacularName-example-1.ttl] [TaxonConcept-vernacularName-example-1.jsonld]
[TaxonConcept-vernacularName-example-2.ttl] [TaxonConcept-vernacularName-example-2.jsonld]
[TaxonConcept-vernacularName-example-3.ttl] [TaxonConcept-vernacularName-example-3.jsonld]
Mapping
DataSet/TaxonRelationshipAssertions/TaxonRelationshipAssertion[@type="has vernacular"]
The text was updated successfully, but these errors were encountered: