Taxonomic Swap 103109
(Tehty 30-12-2021)
|
|
korvattu seuraavalla: |
|
Kommentit
@apseregin I am deeply sorry to not have discussed before the taxon change.
The main problem is the controversy about Capparis sicula.
POWO sees Capparis sicula as a synonym of Capparis spinosa var. canescens, and Capparis sicula subsp. herbacea is seen as a synonym of Capparis spinosa var. herbacea.
Now the question is, wether all species are variations or subspecies of Capparis spinosa or sicula.
To be honest, I do not wish to spend my time in cumbersome discussions, that's why I'll make a taxon swap with Capparis spinosa var. herbacea, which is accepted by POWO.
Nevertheless I'd like to discuss which sources we're all going to follow on iNat: Capparis spinosa or sicula?
With kindly regards,
Sotirios Liakas
P.S. here's the "right" taxon change https://www.inaturalist.org/taxon_changes/103110
I'm sorry again for the inconvience caused.
Hi Sotiros,
Thanks for the immediate response. I am not an expert in Capparidaceae in general, therefore I have no idea what is C. sicula. However, since there are discrepancies in subordinating C. herbacea (to C. sicula in EuroMed or to C. spinosa in POWO and CoL), but no hesitation that this is a distinct taxon (subspecies or variety), it might be wise and moderately conservative to leave it as a species as an eastern vicariant for the whole Capparis spinosa aggr.
Additionally, removing the species rank of Capparis herbacea will remove it from the computer vision models.
It's so unfortunate that it's removed from the computer vision models. On the other hand, the name is accepted...
This swap was made without any discussion or flagging with a FALSE reference to POWO, where this taxon is actually subordinated to Capparis spinosa (as Capparis spinosa var. herbacea) https://powo.science.kew.org/taxon/urn:lsid:ipni.org:names:77142363-1
The author of the swap have neither observations nor the identifications of this taxon.
The swap should be undone asap with the further precise substantial discussion and clarification of an issue.
@greek_cicada_project @convallaria1128 @kai_schablewski @loarie