Currently Op generation from Javadoc reuses the service loading logic of interrogating the Java class to determine Op information, e.g. optionality of parameters.

If #200 is resolved then the Javadoc path to op registration could fully lean on the YAML.

The Javadoc parsing could then fully stand on its own, with any information coming from the Java method instead being embedded in Javadoc in a way that doesn't require use of scijava-specific dependencies. Current thinking was to make parameter information in parenthetical notes at the end of each @param tag