That's true, but I don't understand why we need to hook up names, types, actions, etc. to these sorts of results, when they are not needed (nor used) by optparse to construct / provide an interface- that is all taken care of in ```inputs```.

I'm likely misunderstanding how you're wanting to use this meta-information at the optparse level, because I thought we were going to use result metadata at the Command level to construct workflows, drag-n-drop interfaces, etc.. I think the optparse config files are already a bit complicated and would like to avoid making them even more so. I think keeping ```OptparseResult``` similar to the way it was before will keep the config files simpler and still let us do everything we need to.