Taxacom: nomen nudum and synonymy question

[Adam Cotton]

Replies interspersed:

On 28/01/2023 00:03, John Grehan via Taxacom wrote:
> Thank you to everyone who responded and helped clarify the situation. First
> clarification is that the name in question is not a nomen nudum as it was
> described in the first published article of that year.

Correct.

> Second question I would like to clarify here is that since the name is
> designated an aberration, it does not fall within the Code - that it is
> 'unavailable' as a taxon within the code. I am fine with that, but if such
> a name is 'unavailable', does this mean that one does not recognize the
> name as a 'synonym'? For example, Nielsen et al (2000) list of
> Hepialdiae include many infrasubspecies names under the applicable species
> names. Should that not have done that? Or can one list infrasubspecies
> names, but not treat them as synonyms? Could I list them as 'unavailable'?

All relevant names can be included in a taxon synonymy, and it is useful 
to add the status of the name after it as well. I use '[IFS]' for 
infrasubspecific names, and similarly it is worth including other types 
of status too, eg. JOS (junior objective synonym), JS (junior synonym), 
JH (junior homonym), NN (nomen nudum), PS (published in synonymy) etc.
Note that a JOS is an unavailable name, since it is based on the same 
individual type specimen (species-group), or the same type species 
(genus group); whereas a JS is a subjective opinion, and the name is 
still available.
Don't forget to include a list of abbreviations. I recommend NOT using 
'NP' for homonyms as nomen praeoccupatum, and nomen protectum are 
different but have the same initials.

> This question arises as I finalize a revised Hepialidae catalog, and had
> followed Nielsen et al in listing infrasubspecies name. In the current list
> I include information on type locality and type depository only for species
> and subspecies names (when known). For infrasubspecies names I have just
> noted the locality (i.e. not as a type locality), and collection depository
> (but, again, not as a type collection).
>
> Thanks,
>
> John Grehan

Good luck!
Adam.