object-id-ref datatype (UML and YANG)

openBackhaul / airInterface

Technology specific interface definition for microwave air interfaces

Apache License 2.0

3 stars 0 forks source link

object-id-ref datatype (UML and YANG) #19

Closed openBackhaul closed 4 years ago

openBackhaul commented 4 years ago

The datatype of

object-creation-notification::object-id-ref
object-deletion-notification::object-id-ref
attribute-value-changed-notification::object-id-ref
problem-notification::object-id-ref has been changed from String to yang:uuid. This might be wrong, because "ref" might indicate a reference on an already existing uuid. The value of such reference can by definition not be unique. So String might be the correct datatype.

Proposal: Changing the datatype in the UML and the YANG back to String.

alexandrustancu commented 4 years ago

Why is this not a leafref, which points exactly to the UUID of the affected object ?

openBackhaul commented 4 years ago

Common decision on 21.11.2019:

All *Notification::objectIdRef attributes will become _objectIdRef attributes generated from shared associations to LTP class in UML. This applies on all notifications.

All *notification::object-id-ref leaf will become leafref to LTP.

Only object-deletion-notification::object-id-ref : leafref will be "require-instance false;"

openBackhaul commented 4 years ago

Shared associations between *Notifications and LTP added. Resulting attributes named "_objectIdRef".

UML done. YANG still open.

openBackhaul commented 4 years ago

data type of all object-id-ref attributes changed towards leafref.

    leaf object-id-ref {
      type leafref {
        path "/core-model:control-construct/core-model:logical-termination-point/core-model:uuid";
      }
      config false;
    }

In case of object-deletion-notification, "require-instance false;" added.