1. Pages
2. …
3. OIMT
4. IISOMI
5. IISOMI Minutes
6. 2021 IISOMI Minutes

2021-02-12 IISOMI Meeting notes

19 Feb 2021 Leader Hing-Kam Lam (May not be available: Andrea)

26 Feb 2021 Leader Scott Mansfield

05 Mar 2021 Leader Andrea Mazzini (May not be available: Bernd)

19 Mar 2021 Leader Bernd Zeuner

Enhancement per ITU-T Q14/15 G.875 pruning/refactoring needs

• Evaluate xmi2yang support of ExtendedComposite
  • Scott has received the simple example from Kam
  • Scott reported that the support has been added to the code; now just need to generate the appropriate output. 
• Creates a grouping with uses statement (like Inheritance is supported)
  • Discussion:
    • Normal composite
      • 
      • In the data tree, the container class-d is visible.
    • ExtendedComposite 
      • 
      • In the data tree, no container.
      • This steoreotype indicates a more restrictive form of "StrictComposite" where the "extending" classes will never be explictly instantiated, but that the attributes defined by the “extending” class will be transferred to the class being “extended” at runtime, much like the UML “Generalization” relationship. In other words the "extending" classes are essentially carrying attributes of the “extended” class in a grouping-pack and often referred to as "_Pacs".
    • Difference between normal composition and ExtendedComposition
      • 
    • Strict Composite: This stereotype has been obsoleted in the latest version of the modeling guideline.
      
    • Current mapping in TAPI
      • Not using StrictComposite, produce the following 
        • 
      • Using StrictComposite, produce the following 
        •  

• Scott Mansfield To compare and verify whether Kam, Shu, and Andrea are using the same version of the mapping tool 
• Scott Mansfield To test the mapping of the following cases:  
  • Normal composite, 1..* part
  • Normal composite, 1 part
  • Extended composite, 1..* part (invalid model, throw error)
  • Extended composite, 1 part
  • Strict composite, 1..* part (obsoleted, throw warning)
  • Strict composite, 1 part (obsoleted, throw warning)

• Profiles: https://github.com/OpenNetworkingFoundation/EagleUmlCommon
  

• Consider how to support/parse the Condition statement

Analyses of the current code

• Written in NodeJS using node_modules
  • fs
  • loadsh
  • minimist
  • miment
  • xmlreader
• app.js reads the XMI file and converts it into an internal format
• Parse the internal format
• Generators read from the internal format

AGREEMENT

For the mid term timeframe we continue using the current tool and update this (this is not waste of effort).

Mapping of the references

• Scott enhanced the tool to return in a first step the references defined for the leafs (9 files were modified)
•  Is it also possible to extract more than one reference for the same artefact (this is used in ITU)?
• The namespace and prefix issues (inserting dashes) is also solved

Generation of references in GenDoc

Bernd presented (based on the itut-eth-oam model example from g8052.1_v0.15_uml@2020.09.16.zip)

• The updated gdITUTemplate-8052.1_bz.docx Gendoc script which returns also the references. See yellow marked changes in the script.
• A new Gendoc script (started from scratch) which only extracts the references for the classes/data types and their attributes; see References_gd.docx.

Not discussed

Papyrus 2020-06 uses a new version of Eclipse GMF Runtime 1.13.0 which makes diagrams not backward compatible to the previous versions; see also: Papyrus Releases.
Papyrus version review information is provieded here: 2021-01-22 IISOMI Meeting Notes

Model2Doc analyses ...

Need still to check if Papyrus 5.0.0 provides relevant advantages to justify the move to this version.