Binding for MiOS (Vera) Automation controllers

This binding exposes read, and read-command, access to Devices controlled by a MiOS Home Automation controller, such as those seen at http://getvera.com.

It exposes the ability to do the following things in the MiOS HA Controller
* `Devices` - Read State Variables & Device Attributes, and invoke (single parameter) UPnP Commands to control the Device.
* `Scenes` - Read the current execution state of a Scene, and invoke those Scenes within the remote HA Controller
* `System` - Read System-level Attributes.

It uses the _remote control_ interfaces (aka "UI Simple" JSON Calls, and HTTP Long-polling) of the MiOS HA Controller to keep the _bound_ openHAB Items in sync with their counterparts in the MiOS HA Controller.

The "guts" is outlined in the root-level `README.md` file, along with the JavaDoc that's in the code (although, the `README.md` is better).  

The binding uses the openHAB _Transformation Service_ extensively to "map" the Data & Commands between the two systems.  I provide a set of example MAP transform files in the `examples/transform` directory of the Binding, but these can readily be augmented without needing to tweak the code.

Original code was used from the XBMC Binding, and then heavily modified.  Snippets included from the HTTP Binding for the various datatype mapping functions.

Submitting for early feedback, there will probably be a lot since it's my first binding  ;)
So, I've spent some time chatting in the background with the folks that have been using the Binding for a few months.  None of them had any particular objection with the current form, and/or other suggestions for alternatives.

Previously Thomas has indicated that "2.x" would have a more formalized set of standards/conventions for the functional equivalent of binding-strings.

In absence of any [openHAB] standard in this space, and a strong consensus-based alternatives from those that are actually using it, I'm going to stick with what I have for the first round.  

For 2.x, once Thomas and/or the openHAB core team have defined a standard, then the necessary changes will be made.  At that time I'll also consider what form of Backward compat is needed on the 1.x driver.


PS: I'm from a document-centric background, which is why the Resource-Locator style string, it's a very natural form to me, and also happens to match what you'd do if you ran something like a CoAP Serving device.

PPS: I've also worked extensively with LDAP DN's, which is more similar to the style you're shooting for John.  I found them much more awkward to deal with, in practice, than a well described Document-style tree, but perhaps that's my Document-centric background creeping in ;)