require-instance==false at object-creation- and attribute-value-changed-notification manually corrected

[openBackhaul]

Currently, shared associations in UML get translated into leafref with require-instance==false as a standard. This is not correct for a subset of cases.

Defining the value of the require-instance statement in YANG should be made available in UML.

This Problem has already been raised in Synchronization Issue#16. This issue is just for documenting that the VlanInterface model is also affected.

In meantime, the require-instance==false statements have been manually changed to true for the following attributes in the YANG:

• object-creation-notification :: object-id-ref
• attribute-value-changed-notification :: object-id-ref

[demx8as6]

Proposal to the 5G-xhaul call on 14th of June 2023:

The issue will be rejected, because the asynchrous implementation of the NETCONF server can not guarantee the exactions of an instance. This will simplify the implementation and causes no harm on application implementation.

As a consequence all open issues in this regard can be "rejected" as there is no change in UML and UML2YANG needed. 

All leafrefs will be tagged with "required-instance = false". 

[openBackhaul]

Decision made at the 5Gxhaul call on 5th of July 2023: The shared associations between the object-creation-notification/attribute-value-changed-notification and the LTP (represented also by _objectIdRef attributes) shall be marked with Stereotype "LifecycleAggregate" for triggering the UML2YANG tool to add a required-instance = true statement to the leaf-ref in YANG.

[openBackhaul]

Notifications have been removed from the modelings.