search

Open-Network-Models-and-Interfaces-ONMI / TAPI

LF ONMI Transport API Repository (TAPI)
https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI/wiki
Apache License 2.0
95 stars 80 forks source link

layerProtocolName/Qualifier attributes of Notification #446

Closed amazzini closed 5 months ago

amazzini commented 5 years ago

In case of Object Creation Notification all the object’s attributes are (JSON dump) mapped into additional info, hence including the object's layerProtocolName/Qualifier attributes when foreseen. As far as Notification also includes its own layerProtocolName/Qualifier parameters, there could be a conflict or at best redundancy. E.g. the Node may have more layerProtocols, which to map in Notification attribute? In general, Notification shall include only the attributes common to all notification cases, layerProtocolName/Qualifier seem not. Two possible solutions are: 1) Move layerProtocolName/Qualifier from Notification to applicable augmentations (e.g. AlarmInfo). 2) Keep layerProtocolName/Qualifier in Notification - as they may be useful for filtering purposes - but allowing 1..* multiplicity.

amazzini commented 5 months ago

This issue has been closed due to the lack of activity for more than one year. Please reopen it if follow up is necessary.