Child pages
  • 2021-08-06 IISOMI Meeting Minutes

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Administrative
  • UML → YANG Mapping Tool update
    • O-RAN cooperation
    • 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 (202106)
  • Agenda of next call
  • AOB

Discussion items

#

Time

Item

Who

Notes

15 minAdmin: Call planAll

 Leader: Scott Mansfield (Not available: Andrea)

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

 Cancelled (Not available: Nigel, Andrea, Italo)

 Leader: Nigel Davis (Not available: Bernd)

 Leader: Andrea Mazzini  (Not available: Bernd)

 Leader: Scott Mansfield

220  min

Admin: IISOMI Action Items status

All

IISOMI Action Items review (every meeting)

Bernd Zeuner closed the following action items:

  •  Update the Modelling Guidelines to cover "_classB should not be defined in an ExtendedComposite association (because it is abstract)."
  • Update the UML guidelines to reflect the agreements on Enum Literals.

Italo Busi with reference to navigable associations, in the UML diagrams shall we show the attribute in the class?

  • Nigel Davis there are two cases:
    • The model is defined to specify a management interface: better show the association attribute.
    • The model is defined to specify relationships between classes (conceptual model not oriented to a given implementation): better omit the association attribute.
  • Andrea Mazzini shows an example of TAPI diagram, where association attributes are shown.
    • Recalled that the "strict composite" stereotype is deprecated from UML guidelines, leaving only "extended composite" one.
      • TAPI still uses "strict composite" because it is necessary for the currently used uml2yang tool version.
4
3

Convention of UML property names in document/comment/description

KamNot discussed. Deferred to next call.
5
4

Gendoc output for Interfaces and Operations and Association

AllNot discussed. Deferred to next call.
6
5
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

July 30: No discussion

August 6: No discussion

7
615 min

Papyrus versions

All

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)
8
710 min

Private GitHub

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.
9
840 mins

Cleanup of the existing public GitHub (ONF EAGLE), rationalize the forks/branches

Image Modified

10
9
Papyrus 5.0.0 Version

June 11: No discussion

July 9: No discussion

July 23: No discussion

July 30: No discussion

August 6: No discussion

11
10

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

July 30: No discussion

August 6: No discussion

12
11
Agenda of next callAll
  • Administrative
  • UML → YANG Mapping Tool update
    • O-RAN cooperation
    • Cleanup of the existing public GitHub (ONF EAGLE), rationalize the forks/branches
      • How to merge the private GitHub development into the public GitHub (ONF EAGLE)
    • Consider a plan for convergence of ITU-T Q14/15, ONF Common IM and TAPI to 2020-06 (4.16) version
  • 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 (202106)
  • Agenda of next call
  • AOB

Action items

  •