Release v0.9.0-rc · camaraproject/QualityOnDemand

This is the release candidate of v0.9.0 - the (third alpha (tbc)) release of the Quality-On-Demand (QoD) API

Please note:

This release contains significant changes compared to v0.8.1, and it is not backward compatible
- Especially a lot of the parameter names changed in line with the agreed glossary within CAMARA Commonalities
This is only the pre-release, it should be considered as a draft of the upcoming release v0.9.0
The pre-release is meant for implementors, but it is not recommended to use the API with customers in productive environments.

Introduced qosStatus and corresponding notification event to fix issue #38 by @emil-cheung in #67
Added basic tests with Cucumber framework using Java and Maven implementation by @mdomale in #134
Added new methods to get service provider defined QoS Profile by @RandyLevensalor in #138
Scopes specified and OAuth2 authorizationCode flow added as security mechanism, for operations dealing with QoD sessions by @jlurien in #163
Added new model EventQosStatus by @jlurien in #167

Aligned error format with CAMARA design guidelines by @jlurien in #104
Renamed properties to new terms agreed in CAMARA Commonalitites by @jlurien in #129
Updated method for identifying devices by IPv4 address by @eric-murray in #139
Updated of the notification event related fields based on the CAMARA design guideline by @akoshunyadi in #155
CAMARA documentation is now embedded within the OAS definition, and not separate by @jlurien in #151

Removed format lines from Datatypes Ipv4Address and Ipv6Address by @tlohmar in #153
Removed markdown documentation (now embedded within the OAS definition, see above)

Full Changelog: v0.8.1...v0.9.0-rc