I made this scijava-ops-ext-parser component to create a shorthand convenience for automatically generating large volumes of op definitions in an op.yaml.

However, this is essentially taking a yaml configuration as input and outputting... another yaml configuration file. The input yaml is therefore sufficient for determining the desired ops. We could just revise the Op yaml parser to recognize the syntax defined in the ext-parser, or it could be made an extension to the base yaml parser.

There are other questions:

• do we even want a utility like this?
• If we do, is the shorthand syntax sufficiently convenient? I think class-level configuration fields could be useful (e.g. for author and namespace) in addition to the current "global" or "method" scopes.