I’m trying to understand the intended semantics of the /species/{usageKey}/synonyms endpoint.
For example, in the GBIF Backbone I found these three records:
2873991 Aristolochia clematitis ACCEPTED
2874019 Aristolochia rotunda ACCEPTED
7914281 Aristolochia rotunda SYNONYM
Calling:
GET /v1/species/2873991/synonyms
I see 7914281 (Aristolochia rotunda) as a synonym of Aristolochia clematitis.
However, if I try to resolve the name Aristolochia rotunda using:
GET /v2/species/match?genericName=Aristolochia%20rotunda&strict=true
I get the accepted taxon 2874019, which is a completely different species.
This is confusing from a client application’s point of view.
My expectation was that the names returned by /synonyms would represent alternative names for the accepted taxon. In this example, however, the returned synonym name resolves to another accepted species.
Could you explain how the /synonyms endpoint should be interpreted in cases like this?
Is 7914281 intended to represent a historical checklist usage rather than a taxonomic synonym of Aristolochia clematitis? Or should client applications interpret these records in a different way?
Thank you.
