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  ;)
It seems to me that it would make sense to completely isolate the binding string syntax from the semantic purposes that binding strings serve.  In other words, just have your syntax be a distinguished name.  Every element would be a `key:value` pair, separated from others by either a comma or a slash.  Which ones you provided in the string would follow your binding's domain-specific rules that determine what you are binding to.  So you would have binding strings like
```
unit=<unitName>/device=<deviceId>/service=<serviceURN>/variable=<serviceVariable>
device=<deviceId>/service=<serviceURN>/action=<actionName>
scene=<sceneId>/attribute=<attributeName>
unit=<unitName>/systemAttribute=<attributeName>
```
Or whatever combinations are needed in order to address some aspect of the Vera.  Your binding provider would just assemble a Dictionary out of a binding string, and then determine, based on the keys, what you are trying to address.   The syntax is independent of current or future needs.