Child pages
  • 2019-11-08 IISOMI Meeting notes
Skip to end of metadata
Go to start of metadata

Date

Attendees

Apology

Agenda

Discussion items

Time

Item

Who

Notes

15 minCall planAll
  •  Skip. Overlap with TAPI virtual meeting 12:00-18:30 CET
  •   Leader Andrea Mazzini ; Topics:

(1) leafref on non-config data

(2) UML-YANG: Reference Mapping: Use of "Current" in xPath


GuidelinesAll

Kam reported the status of the guidelines documents: IISOMI Deliverables

  • TR-514 UML Modeling Guidelines
    • Published: v1.3 (7/2018),
    • Posted editor draft: v1.3.01 (10/2018), v1.3.02 (12/2018)
    • In progres draft: v1.3.03. Posting date undecided. Topics updated:
      • Clause 7.3.3 "Style Sheets". Should be per papyrus project.
  • TR-515 Papyrus Guidelines
    • Published: v1.3 (7/2018),
    • Posted editor draft: v1.3.01 (8/2018)
    • In progress draft: v1.3.02. Posting date undecided. Topics to update:
      • clauses 5.2 and 5.4 to point to Github for the versions of Eclipse/Papyrus and Gendoc to be installed. 
      • clause 7.4.6 on style sheet file per papyrus project 
  • TR-531 UML-YANG Mapping Guidelines
    • Published: v1.1 (7/2018),
    • Posted editor draft: v1.1.01 (11/2018), v1.1.02 (12/2018)
    • In progress draft: Karthik Sethuramanto provide
  • TR-543 UML-OpenAPI Mapping Guidelines
    • Published: v1.0 (2/2018)
  • TR-544 UML-ProtoBuf Mapping Guidelines
    • Published: v1.0 (2/2018)
 40 min Use of "Current" in xPath

 Deferred to next call on November 22


leafref on non-config dataThorsten Heinze

Thorsten presented an issue that they encounted:

In UML:

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 minAgenda of next callAll
  • leafref on non-config data
  • UML-YANG: Reference Mapping: Use of "Current" in xPath

Action items

  •