1. Pages
2. …
3. OIMT
4. IISOMI
5. IISOMI Minutes
6. 2021 IISOMI Minutes
7. IISOMI 2021-09-24 Meeting Minutes

Page History

01 Oct 2021 Leader: Bernd

08 Oct 2021 Leader: Nigel

15 Oct 2021 Leader: Scott (Not available: Andrea)

22 Oct 2021 Leader: Scott

All

IISOMI Action Items review (every meeting)

Action items done

• None

Refresh Action Items

•  Nigel Davis  01 Oct 2021 Review proposal for "UML comments often include construct name formatted according to the UML guidelines. When the UML is converted to Yang the construct names are then incorrectly formatted." (in minutes 2021-07-30 IISOMI Meeting Minutes).
•  Scott Mansfield 01 Oct 2021  To take the gendoc examples from the guidelines and perform regression test. 
•  Scott Mansfield 01 Oct 2021  To investigate why none of the <<cond>> is retrieved from the model.
  
•  Hing-Kam Lam 01 Oct 2021  At the meeting, to review ORAN tooling funding status to enable planning for key activities related to guidelines etc. to enable new tooling to be constructed.
  

Andrea Mazzini shows the dump of abstractions:

Driven by the following template statements:

1.1       Abstractions

[for (ab:Abstraction | self.eAllContents(Abstraction)->sortedBy(name))]<drop/>

1.1.1        [ab.name/]

[for (co:Comment | ab.ownedComment)]<drop/>

<dropEmpty>[co._body.clean()/]</dropEmpty>

[/for]<drop/>

[for (st:Stereotype | ab.getAppliedStereotypes())]<drop/>

[for (oa:Property|st.ownedAttribute)]<drop/>

• [if oa.name.contains('target')][name/]: “[ab.getValue(st, oa.name).oclAsType(OclAny)/]” [else]<drop/>[/if]

[/for]<drop/>

[/for]<drop/>

[/for]<drop/>

Andrea Mazzini tried to dump also the end points ofthe abstractions, but unsuccessfully:

Italo Busi asks whether the dump of Realizations was tested. Andrea Mazzini did not, but given that Interface Realizations are dumped as Abstractions, maybe this is valid also for Realizations.

May 14: 2021-05-14 IISOMI Meeting notes  

Scott Mansfield presented the Model2Doc feature from Papyrus

• still in pre-release state
• need to install Model2Doc tool integrated into Eclipse 2021-03 (nightly build) and Papyrus 5.1 (nightly) and Model2Doc (0.8.0 nightly)
• requires Java version greater than 11
• creates Word files
• need to check if Model2Doc provides at least the functionality of Gendoc
• Gendoc does not work with newer Papyrus versions (see below)
  
• Further investigation is required
• Work continues to create a model2doc template that produces the same material as the gendoc template (class/attribute/datatype/stereotype etc.)

Scott Mansfield clarifies that the more recent versions do not include the "package" (see Papyrus Releases)

• 2021-06 (4.20) version, the Gendoc works on MAC but not on PC, hence there is something not working in the environment.
  • Recalled that in the .ini file is possible to address a specific Java version.
• Agreed that SG15, ONF Core IM and ONF TAPI shall converge on version 2020-06 (4.16)
  • Scott Mansfield confirms that moving to 2020-06 (4.16) is not altering the diagrams.
  • Hing-Kam Lam recalls that it is not backward compatible.

August 13:  Updated Papyrus releases page

September 7: No discussion

September 24: Reaffirmed the need to explore 2020-06 (4.16) version

Scott Mansfield clarifies that the private Github for xmi2yang modification is available.

• People interested can ask Scott Mansfield for the access.
• Andrea Mazzini is starting some tests of Scott Mansfield version of uml2yang tool. The differences between yang modules generated by different tool versions are difficult to be evaluated through simple "diff" feature.
  • Scott Mansfield advises to apply pyang and pretty printer to the generated modules, to remove all formal differences (e.g. the order of statements, the blanks/tabs).
  • Nigel Davis and Andrea Mazzini tried to install pyang but unsuccessfully. Scott Mansfield will provide guidance.
  • The target is the alignment of generated Yang modules across different SDOs.

September 7: No discussion

September 24: Scott Mansfield offers to help Andrea Mazzini in evaluating the differences between yang modules generated by different tool versions.

• Currently there are 7 forks of OpenNetworkingFoundation/EagleUmlYang repositiory:

• Scott Mansfield clarifies that the Karthik Sethuraman fork is the base of his developments (carried out in his "private" Github).
• There is an open pull request #15 with some conflicts to be solved.
  
  • Once solved, the main repository OpenNetworkingFoundation/EagleUmlYang (Tapi_v2x branch) will be aligned to Karthik Sethuraman fork.
    • This will allow Scott Mansfield future commits on Karthik Sethuraman fork, to make publicly available the tool improvements.
  • Scott Mansfield suggests to add a new branch to OpenNetworkingFoundation/EagleUmlYang and possibly define an Eagle Release.

September 7: No discussion

September 24: Scott Mansfield clarifies that without the involvement of key folks with authority on Github no progress can be performed. No administrators appear for ONF EAGLE Github.

June 11: No discussion

...

September 7, 24: No discussion

All
Hing-Kam Lam

May 14: 2021-05-14 IISOMI Meeting notes

• GenDoc didn't generate constraint
• GenDoc didn't generate the Interface definitions
• GenDoc didn't generate the Type of pointed external (imported) classes
• GenDoc OstigOTtpSource::txti:EByte multiplicity [64] is not generated correctly
• AI (5/28/2021): Scott Mansfield11 Jun 2021 to look at all GenDoc issues above and try to find solutions

May 28:  2021-05-28 IISOMI Meeting notes

• Discussed possible output formats of interfaces/operations.

September 7, 24:  No discussion