we compared the current NotificationProxy v1.0.1 outbound callbacks (for delivering subscriber notifications) with the current MWDI (tag test_v1.0.9) "regard*"-service endpoints and found some differences in the expected notification structure.
/v1/regard-device-attribute-value-change
->expects "resource" attribute in notification, currently NP delivers "object-path"
/v1/regard-device-object-creation
->expects "resource" and "object-type" in notification, currently NP delivers only "object-path"
/v1/regard-device-object-deletion
->expects "resource" attribute in notification, currently NP delivers "object-path"
These differences cause "bad request"-errors when we try to deliver NP-notifications to MWDI. Is there a MWDI-spec-update planned to address these differences?
Questions from implementers