Kmohr-soprasteria/issue120

README.md

@@ -37,9 +37,10 @@ DEVICE_PASSWORD=xxx
 #### v1.1.0
 Release v.1.1.0 introduces the integration with a Kafka message broker.  
 
+Notification types:
 - *Controller notifications*: handling of Controller notifications has not been changed. Those are not pushed to Kafka, applications interested in receiving those still need to subscribe to NotificationProxy directly. (This decision is based on the fact, that in the future Controller notifications will not be handed over from Controller to NP directly, but will be managed by future app Controller Domain Manager.)
 - *Device change and alarm notifications*: Handling of device change notifications however has changed - those are now pushed to Kafka.
-- *Proprietary notifications*: those are ignored for now.
+- *Proprietary notifications*: those are not received and managed by NotificationProxy and, thus, out of scope.  
 
 Kafka sends all ONF TR52 device change notifications to Kafka topic *all_notifications* after bringing them into the required format (in regards to the included resource path).  
 Sorting the notifications into separate topics (e.g. *device_change_notifications* and *device_alarm_notifications*) on Kafka, from where consumers then can pull them, will not be done by the NotificationProxy but by other means (e.g. a KafkaStreams application).  

testing/2_functional/completeness/v1.1.0/schema/info.txt

@@ -0,0 +1 @@
+currently all individual NP services return 204, i.e. no schemas needed.