Mandatory Attributes

[PrathibaJee]

The latest UML2YANG tool will include mandatory substatement to attributes that has "Multiplicity 1 + no default values defined". The following attributes which are formerly optional will be changed to mandatory in the upcoming YANG.

grouping attribute-value-changed-notification 1.referenced-severity-configuration-identifier

grouping alarm-event-notification

2. alarm-event-sequence-number
3. alarm-type-id
4. alarm-type-qualifier
5. resource

grouping alarm-kind-type

6. alarm-type-id
7. alarm-type-qualifier

grouping severity-configuration-type

8. severity-configuration-identifier
9. alarm-type-id
10. alarm-type-qualifier
11. resource-group-description

grouping current-alarm-type

12. current-alarm-identifier
13. alarm-type-id
14. alarm-type-qualifier
15. resource

grouping alarm-event-record-type

16. alarm-event-sequence-number
17. alarm-type-id
18. alarm-type-qualifier
19. resource

[openBackhaul]

Withdrawn proposal:

The following attributes will be equipped with a mandatory statement in YANG:

grouping attribute-value-changed-notification 1.referenced-severity-configuration-identifier

grouping alarm-event-notification

2. alarm-event-sequence-number
3. alarm-type-id
4. alarm-type-qualifier
5. resource

grouping alarm-kind-type

6. alarm-type-id
7. alarm-type-qualifier

grouping severity-configuration-type

8. severity-configuration-identifier
9. alarm-type-id
10. alarm-type-qualifier
11. resource-group-description

grouping current-alarm-type

12. current-alarm-identifier
13. alarm-type-id
14. alarm-type-qualifier
15. resource

grouping alarm-event-record-type

16. alarm-event-sequence-number
17. alarm-type-id
18. alarm-type-qualifier
19. resource

(Vendors to please check, whether their devices are able to associate a proper value in all cases. Otherwise adding a default value (for indicating an attribute not being supported) shall be considered in such case.)

[michbin]

IMO the following attributes should not be mandatory:

alarm-event-notification

• alarm-type-id, alarm-type-qualifier: The attributes together identify an alarm. So one of them might not be present (in most cases the qualifier).
• resource: There might be cases where the resource is not provided or cannot be given because the affected object is not covered by the information models.

severity-configuration-type

• alarm-type-id, alarm-type-qualifier: see above.
• resource-group-description: A human-readable description does not always exist.

current-alarm-type

• alarm-type-id, alarm-type-qualifier: see above.
• resource: see above.

alarm-event-record-type

• alarm-type-id, alarm-type-qualifier: see above.
• resource: see above.

[openBackhaul]

Decision made during the 5G-xhaul call on 26th of July 2023:

The following attributes will be equipped with a mandatory statement in YANG:

grouping attribute-value-changed-notification 1.referenced-severity-configuration-identifier

grouping alarm-event-notification

2. alarm-event-sequence-number
3. alarm-type-id
4. resource (if no concrete resource could be named, the control-construct should be referenced)

grouping alarm-kind-type

6. alarm-type-id
7. alarm-type-qualifier

grouping severity-configuration-type

8. severity-configuration-identifier
9. alarm-type-id
10. resource-group-description (if no concrete resource could be named, the control-construct should be referenced)

grouping current-alarm-type

12. current-alarm-identifier
13. alarm-type-id
14. resource (if no concrete resource could be named, the control-construct should be referenced)

grouping alarm-event-record-type

16. alarm-event-sequence-number
17. alarm-type-id
18. resource (if no concrete resource could be named, the control-construct should be referenced)

The following attributes shall change for multiplicity [0..1] and the following default values:

grouping alarm-event-notification

4. alarm-type-qualifier : String = ""

grouping severity-configuration-type

10. alarm-type-qualifier : String = ""

grouping current-alarm-type

14. alarm-type-qualifier : String = ""

grouping alarm-event-record-type

18. alarm-type-qualifier : String = ""