azoxy in Web Service
Original report by DK (Bitbucket: anonopsin, ).
azoxy methane, azoxy ethane, azoxy benzene and their relatives work without throwing any warning. However, alkanes, alkenes, and alkynes (and maybe other moieties) from "prop-" prefixes and upwards do throw an "APPEARS_AMBIGUOUS" Warning. Interestingly, adding the "cyclo-" prefix to larger hydrocarbons do not generate the warning (e.g. "azoxy pentane" throws the warning, but "azoxy cyclopentane" does not).
Original comment by Daniel Lowe (Bitbucket: dan2097, GitHub: dan2097).
The reason for this is that there are multiple isomers possible for alkane chanes longer than 2, and hence there are multiple structures that are consistent with the name. For example azoxypropane could be either https://pubchem.ncbi.nlm.nih.gov/compound/1-Azoxypropane or https://pubchem.ncbi.nlm.nih.gov/compound/2-Azoxypropane. azoxyethane has to be https://pubchem.ncbi.nlm.nih.gov/compound/azoxyethane as there are no other isomers of ethane. The fact that all 5 atoms in cyclopentane are equivalent means that there is only structure consistent with the name azoxycyclopentane.
Original comment by DK (Bitbucket: anonopsin, ).
Thank you for the clarification. Now I wonder how I missed that.
A side question: As an example, are 1-azoxypropane and 2-azoxypropane not supported nomenclature ? - they throw errors in the web service.