Date

Attendees

Apology

Agenda

Discussion items

#

Time

Item

Who

Notes

15 minAdmin: Call planAll

 Leader: Bernd Zeuner (Not available: Scott)

 Leader: Nigel Davis

 Leader: Andrea Mazzini

 Leader: Scott Mansfield (Not available: Andrea)

 Leader: Hing-Kam Lam (Not available: Nigel, Andrea)

 Cancelled (Not available: Nigel, Andrea, Italo)

 Leader: (Not available: Bernd)

 Leader: (Not available: Bernd)

25  min

Admin: IISOMI Action Items status

All

IISOMI Action Items review (every meeting)

Action item discussed:

  • Nigel Davis : Further updates on issue of "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."
  • Moved the target date from July 23 to 30 July.

No update on the other open action items.

350 min

UML → YANG Mapping Tool:
O-RAN interest and potential redevelopment support

O-RAN Alliance is looking for tooling and may also be able to fund the work on tooling.
Created a small "Tooling Coordination Team" that produced a slide set "WG10 Tooling proposal" on that topic.

Martin presented the slide set:

  • Input from various SDOs into the O-RAN information model (written in Papyrus) which is the "single source of truth"
  • Use Gendoc to create pdf-version of the information model
  • Need to create an O-RAN YANG specification which need to be able to import also existing YANG specifications from other SDOs
  • Not clear if re-engineering of existing YANG specifications to UML is required by O-RAN; e.g., 3GPP is not using Papyrus
  • See also Project proposal for UML-To-YANG
    • Goal: Complete tool supported project lifecycle
  • O-RAN is using Papyrus 2020-06 with the latest profiles
  • O-RAN wants to harmonize terminology/semantic among their teams using UML
  • UML model validation is required
  • O-RAN will provide 4 interfaces
  • Preferred is a Linux Foundation project that works on the tools
  • IISOMI Guidelines shall be used
  • Need to estimate the effort that is required for the tooling (may need to rewrite the mapping tool from scratch because a complete restructuring is necessary)

Further discussion next week when Scott is available

4

Convention of UML property names in document/comment/description

KamNot discussed. Deferred to next call.
5

Gendoc output for Interfaces and Operations and Association

AllNot discussed. Deferred to next call.
6
Papyrus-Model2Doc feature

May 142021-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.)

GenDoc no longer work with Eclipse Papyrus 2020-06. 

May 282021-05-28 IISOMI Meeting notes

June 11: No discussion

July 9: No discussion

July 23: No discussion

7
Papyrus 5.0.0 Version

June 11: No discussion

July 9: No discussion

July 23: No discussion

8

GenDoc Issues

May 142021-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 Mansfield 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.

July 23: No discussion

9
Agenda of next callAll
  • Administrative
  • UML → YANG Mapping Tool update
    • O-RAN co-operation
    • Private GitHub
    • Cleanup of the existing public GitHub (ONF EAGLE), rationalize the forks/branches,
    • Identify different releases, Release management, and release plan; e.g., current ITU-T Q14/15 version and TAPI version are different 
    • How to merge the private GitHub development into the public GitHub (ONF EAGLE)
  • Convention of UML property names in document/comment/description
  • Gendoc output for Interfaces and Operations and Association
  • Papyrus-Model2Doc further investigations?
  • Papyrus 5.0.0 Version (2021-06)
  • Agenda of next call
  • AOB

Action items