|15 min||Call plan||All|
Kam reported the status of the guidelines documents: IISOMI Deliverables
|40 min||Use of "Current" in xPath|
Deferred to next call on November 22
|leafref on non-config data||Thorsten Heinze|
Thorsten presented an issue that they encounted:
We define a read-only Class (e.g. TransmissionMode) that hold several attributes (e.g. center frequency, channel bandwidth, modulation)
We reference this datatype in read-only classes (Capability) for vendors to list the combinations of values, which are supported by the hardware
We reference this datatype in read-write classes (Configuration) for operators to select one of the supported combinations of values
It looks like this in the class diagram (unfortunately the referencing _attributes in the Capability and Configuration classes are not shown in Papyrus):
The “shared” associations from the Configuration class to the TransmissionMode are very well translated into leafref statements in the YANG.
But unfortunately, we get the following error messages during compiling the resulting YANG:
… error: the node is config, but refers to a non-config leaf 'transmission-mode-name' in module …
We would have thought that this is a very reasonable appliance of leafref, and are surprised about the error message.
Do you have an idea about what we have to correct in the YANG, respectively the UML? Note that the error message doesn’t show up, when the leafref is complemented with a require-instance==false statement, but we are not sure about the side effect of this amendment.
Willcontinue the discussion on the Nov. 22 IISOMI call.
Bernd gave the following link on "require-instnce false" when pulling leafref definitions from grouping.
|5 min||Agenda of next call||All|