That's an interesting idea, though I'm not sure if we should push the code all the way up into ```InterfaceInputOption```, mainly because that is meant to be very general and not specific to optparse, argparse, HTML, etc.. Shouldn't this mapping be the job of the option's ```Handler``` (which translates an interface input into the type expected by the Command)?

@wasade what do you think?