Add support for v1.1

[sparkpunkd]

Extend ledger to support proposed changes to support NMOS Discovery and Registration v1.1. New branch veeoneone has been created to track this. Features include:

• Pagination of results.
• Structured queries.
• Extensions of schemas to include multiplexed streams.
• Carriage of technical stream parameters via the API.
• Support for HTTPS.
• Other minor tweaks e.g. add device_id to a flow.
• Support for unicast DNS.

[sparkpunkd]

Decided that this is too much to chew prior to the Wuppertal workshop. Will focus on bug fixes and getting v1.0 stable.

[sparkpunkd]

I've had a couple of goes at implementing the changes and I'm finding it hard to go from where I am to v1.1. There are a lot of changes to the model and the new deep structure of the JSON schemas is, in my opinion, hard to work with. In particular, the way the model is now defined couples syntax and semantics ... it's difficult to stand away from the schema and see the patterns.

Also, it also does not help that this was my first serious attempt at writing a classic object model in Javascript and I probably went to town. I want to avoid a toxic mix of my implementation being too brittle and the NMOS schema design being tied to some specific implementation choices about a way to do validation.

I need to go and have a think about this one. I was hoping to keep a common object core for v1.0 and v1.1 and change the validation/serialization based on the version number in RESTful path. Is that possible from where I am? Two prototypes thrown away - but that can only be a good thing?!?