Representing Taxon relationships in a Checklist

[LordFlashmeow]

Representing Taxon relationships in a Checklist

[deepreef]

My interpretation of originalNameUsage in this case is that it should represent the original combination of the secondary homonym, not the senior homonym. DwC Taxon terms are not sufficient to confer both nomenclatural and taxonomic information, so statements about secondary homonymy aren't directly supported. This is why there is a fair bit of effort focused on the Taxon Names and Concepts Interest Group to allow more robust exchange of this kind of taxonomic and nomenclatural information.

In the case of a secondary homonym, I would use acceptedNameUsage to represent whatever name is deemed by the content provider or represented Reference to represent the "correct" scientific name. I interpret the word "correct" in this context to mean both nomenclaturally correct name (replacement names, objective senior synonyms, correct original spelling, etc.) and the taxonomically correct name (subjective synonymy, classification including genus placement, etc.).

For example, assuming we have:

Aus bus Smith 1850
Xus bus Jones 1900
Aus bus (Jones 1900)
Aus cus Pyle 2000 (replacement name for Jones' bus)

The record for Aus bus Smith 1850 would have the same value ("Aus bus Smith 1850") for scientificName, originalNameUsage and acceptedNameUsage (assuming the name is still regarded by the Reference/Provider as representing a valid species, within the genus Aus).

The record for Aus bus Smith 1850 would have these values:
scientificName: Aus bus (Jones 1900)
originalNameUsage: Xus bus Jones 1900
acceptedNameUsage: Aus cus Pyle 2000

Again, this is how I would represent it. DarwinCore terms do not define it with this level of precision (hence the ongoing work of the Taxon Names and Concepts Interest Group).