[fixed] wrong assertion in unit test
[updated] config and connections yml from dataservice
[deleted] unused code from the UpdateService
[updated] connections-yml added example for all possible values and some of the values ​​for a better understanding renamed
[updated] connection and subscription all keys unified yml and REST use the same keys from ConnectionKey and SubscriptionKey
[fixed] wrong exception was logged
[fixed] comments in the yml files
[bugfix] when a set is called from a get

Detail: The Properties class do not store between the property values ​​in a map. Is is always worked on the -yml file and so no inconsistencies can occur.
[added] more Properties tests ( the last set bug)
[changed] the order from Connection values in the yml-file
[updated] visualization to the new yaml properties
[changed] YamlReader and YamlWriter ( removed the Constructor and other yaml data type from the method parameter )
[added] new log prints to the Properties.set() (each set makes a debug log)
[changed] Properties.getValue(). If the property path a empty String return the full root map.
[added] abstract base class for future testcase-based classes and tests for an empty graph
[added] factory class for neo4j test databases
[fixed] Neo4JTestDatabaseFactory; now correctly uses the Neo4JTimestampManager
[change] AbstractTestCase now loads external testcases from YAML files
[add] SingleValueMetadataInsertUpdateAndDeleteTestCase; a simple testcase that extends from AbstractTestCase and makes use of external YAML file
[change] implemented JSON tests
[fixed] if the metadata has no properties
[added] changed tests for access-request-device
[added] in AbstractTestCase equals methods for metadata
[added] changed tests for access-request-device with a not empty graph
[added] test for graphs, where delta calculations create multiple subgraphs of updates or deleted graph content