Yes - this class defines the general interface that in an ideal world would be defined as part of openHAB itself and not defined in the binding. Ultimately, I think it would be the goal to have such an admin interface implemented in all/most bindings to facilitate admin, so it would need to be defined in the openHAB core.
However, I think it's difficult to define such an interface without implementing something and getting some experience. I spent some time  working out what I thought was needed, so this could be considered an initial design proposal, but I'm sure we'll find features that need to be added. 

The interface is basically a list of config items and values, but the items are specified in a hierarchical way. I did look around for a better (more flexible) standard, but couldn't find one (if you find one, I'd be very happy to use it). I also see that we may want to define our own though as openHAB has some specific requirements. Again, looking at 420, I would like to see a way for bindings to describe their configuration, and ideally their item configuration format. I suspect that a standard config interface may not quite fit, but maybe I'm wrong (again, I did spend some time looking, but you might have better luck).

I considered it was easier, and maybe better, to implement this initially as part of the zwave binding since this binding (in my opinion at least) really needs some sort of admin interface. This allows "us" (the openHAB collective) to get some experience with this interface in a controlled and limited way (ie not just rolling it out to 50 bindings).

My thoughts anyway... :)