Child pages
  • 2020-05-29 IISOMI Meeting minutes
Skip to end of metadata
Go to start of metadata

Date

| 6am PDT | 9am EDT | 13:00 UTC | 15:00 CEST | 

Zoom: https://www.zoom.us/j/853336915

Attendees

Agenda

  • Administrative
    • Call plan (schedule, leader, topics)
    • Does contribution to IISOMI need CLA?
  • Check status of update to UML Modelling Guidelines
  • Check status of suggested action for resolving the G.8052.1 UML to Yang mapping issues
  • Updating the installation part of the Papyrus Guidelines; how to deal with changed URLs for the downloads
  • Papyrus version: Which version is recommended
  • Guideline on the Reference stereotype
  • Agenda of next call
  • AOB

Discussion items

Time

Item

Who

Notes

5 minCall planAll
2 min

Does contribution to IISOMI need CLA?

Since IISOMI is a multi SDO initiative, people from other SDOs should not be required to sign the CLA.

3 x Nigel

min

UML Modelling Guidelines: Use of "is leaf" property 

Bernd analyzed the allowed usage of the "is leaf" property and proposed the following change:

UML Artefactcurrentproposed
Object Classallowednot used
Attributeallowednot used
Interfacenot usednot used
Operationnot usednot used
Notificationnot usednot used
DataTypenot usedonly for enumerations
  • Current Definition: Is Leaf:  If true the object class must not be extended (class can not be inherited from).
    • Modify the guidelines to say that IsLeaf on a class means that the class can not be redefined (for example: via inheritance). 
  • Keep IsLeaf for Object Classes and Attributes
  • The semantics of IsLeaf could be useful in some situations.
  • Bernd Zeuner ADD to the uml modeling guidelines that artifact properties not discussed in the uml modeling guidelines must be ignored
  • Bernd Zeuner Update the definition of IsLeaf for attribute.  The datatype/enum IsLeaf is distinct from the attribute IsLeaf usage.
50 min

Check status of suggested action for resolving the G.8052.1 UML to Yang mapping issues

Scott Mansfield

Hing-Kam Lam

Issues listed in 2020-02-28 IISOMI Meeting Minutes:

iisomi2020.KL.003_g8052.1_v0.13_yang-result-n-modification.zip

  • Object key with the "config false"; see Issues 1 & 3 in the "itut-g-8052dot-1@2020-01-27_modified.yang" file, (contained in iisomi2020.KL.003_g8052.1_v0.13_yang-result-n-modification.zip)
    • TR-514 UML Modeling Guidelines, section 5.3.4 says that 
      • "UML provides a Boolean property called “readOnly”. Since this is not enough to describe all required cases “readOnly” is not used and two additional properties isInvariant and writeAllowed are defined."
    • G.8052.1's ThresholdProfile object class has the attribute localId, which is defined as
      • partOfObjectKey=1
      • is read only = true
      • isInvariant = true
      • writeAllowed = CREATE_ONLY
    • RFC7950 section 7.2.1 
      • If a node has "config" set to "false", no node underneath it can have "config" set to "true".
    •  Issue:
      • The uml2yang mapping tool maps the localId with config=false. 
      • Yang validation throws an error on config=false because because ThresholdProfile has attributes that are config=true (i.e., the threshold values of LM and DM etc).
        • Scott MansfieldTo raise this issue with the YANG doctors
          • During the last IISOMI call we were reviewing the UML – YANG Mapping tool.

            In our UML models we have two meta-data attributes that are related to setting an attribute’s value.

            isInvariant true or false.  If true the attribute can’t be changed after it is initially set.

            writeAllowed:  has four options:

               create_only: value can be set only during instance creation

               update_only: value can be changed, but the initial value comes from somewhere else

              create_and_update: value can be set and changed

               write_not_allowed:  value can’t be set, ever.

            We are trying to determine how best to map this to YANG constructs.

            We have been getting confused between the interaction of config vs. state data concept in YANG and the isInvariant/writeAllowed semantics in UML.

            The config vs. state data concept in YANG is not the same as isInvariant or writeAllowed.

            I don’t see anything in YANG (that I can find anyway) that would have the semantics of invariant.

            I also don’t see anything in YANG that would differentiate between create_only, upate_only, create_and_update, and write_not_allowed.

            The semantics related to config vs. state in YANG helps, but is not sufficient to capture all the semantics from the UML.

            Thoughts?

0 minPapyrus version: Which version is recommended to install

TR-515 Papyrus Guidelines (v1.3.01)

Applied tool versions for the guideline:

  • Eclipse version 4.7.2 “Oxygen”
  • Papyrus version 3.2.0 RC4
  • Gendoc version 0.6.0

Papyrus versions since then:

Release Name

Release Number

Windows Platform

Eclipse Version

Comments

Oxygen

3.x.032 bit / 64 bit4.7.2Used for writing the Papyrus Guidelines
Photon4.0.032 bit / 64 bit4.8Never used
2018-094.1.x32 bit / 64 bit4.9Currently used
2018-124.2.x64 bit only4.10
2019-034.3.x64 bit only4.11
2019-064.4.x64 bit only4.12
2019-094.5.x64 bit only4.13
2019-124.6.x64 bit only4.14
2020-034.7.x64 bit only4.15
2020-064.8.x64 bit only4.16Not released yet
2020-09

4.17Not released yet

Latest version of Gendoc is 0.7.2 from 2018-10


Not discussed. Deferred to next call

0 minUpdating the installation part of the Papyrus Guidelines; how to deal with changed URLs for the downloads

TR-515 Papyrus Guidelines

Not discussed. Deferred to next call

0 minGuideline on the Reference stereotype

TR-514 UML Modelling Guidelines

Not discussed. Deferred to next call

0 minAgenda of next callAll

Call plan for

  • Check status of suggested action for resolving the G.8052.1 UML to Yang mapping issues
    • Object key with the "config false"; see Issues 1 & 3 in the "itut-g-8052dot-1@2020-01-27_modified.yang" file
    • Missing typedef, such as alarm-severity-code, csf-config, etc.; see "Issue 4" in the "itut-g-8052dot-1@2020-01-27_modified.yang" file
  • Papyrus version: Which version is recommended
  • Updating the installation part of the Papyrus Guidelines; how to deal with changed URLs for the downloads
  • Guideline on the Reference stereotype
0 minAOBAllNone

Action items

  •