Date

Attendees

Agenda

Discussion items

#

Time

Item

Who

Notes

15 minAdmin: Call planAll

 CANCELLED

 Leader Hing-Kam Lam

 Leader Scott Mansfield

 Leader Nigel Davis

 Leader Bernd Zeuner

21  min

Admin: IISOMI Action Items status

All

IISOMI Action Items review (every meeting)

Note:

  • Do not copy actions from previous minutes, just reference minutes (or add bullet versions of the actions as reminders)
  • New actions are added to the minutes of the current meeting and dated using the "task list" control

Note: Check the action item list and check for tasks that have passed their due date.

  • If the due date is past, determine if the issue is still active
    • If the task is active, mark the over-due task as completed, and create a new task with a new due date in the minutes
    • If the task is not active, (i.e. not going to be progressed at this time), simply close the task and make a note in the minutes that the task was closed.

Actions discussed

  • Moved the deadline of Bernd Zeuner " Update the Modelling Guidelines accordingly" to as next week the IISOMI call is cancelled.
  • Scott Mansfield clarifies that Gendoc tool and uml2yang tool are independent issues.
    • Scott Mansfield needs some more time to recover the development environment to continue on uml2yang tool improvements.
3
Papyrus-Model2Doc feature

Not discussed on May 21st 

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. 

Updates on May 28:

4
UML → YANG mapping issues and enhancements

Not discussed on May 21st 

Logged issues: https://github.com/OpenNetworkingFoundation/EagleUmlYang/issues

  • Issue: 
  • Finalize discussion on xmi2yang support of ExtendedComposite, StrictComposite
  • Check enumerations not following guidelines
  • Management of possible dedicated branch where to store new versions (UML → YANG Tool release process)
    • Dedicated call: 
5
Papyrus 5.0.0 Version
Not discussed on May 21st 
649 min

GenDoc Issues

  • GenDoc didn't generate constraint
    • None of the constraints is retrieved from the model
    • E.g., 
  • GenDoc didn't generate the Interface definitions
    • None of the Interfaces and its operations are retrieved from the model
  • GenDoc didn't generate the Type of pointed external (imported) classes
    • External class means a class imported from another model and used as the type of a navigable attribute (association end)
    • E.g., 
    • The external model should be imported in a proper way
    • This is not a GenDoc issue
  • GenDoc OstigOTtpSource::txti:EByte multiplicity [64] is not generated correctly
    • Solution: [if(p.lower=p.upper)][p.lower/][else][p.lower/]..[if(p.upper=-1)]*[else][p.upper/][/if][/if]
  • Scott Mansfield to look at all GenDoc issues above and try to find solutions

Updates on May 28:

  • Scott Mansfield presents some examples of possible output formats of interfaces/operations.
  • Discussion whether is preferable
    • a top table listing all operations, followed by the tables dedicated to the parameters of each operation, or
    • interleave the operations and their parameters, i.e.
      1. operation 1
      2. general properties of operation 1
      3. table with the parameters of operation 1
      4. operation 2
      5. etc.
    • Hing-Kam Lam prefers the top table listing all operations.
    • Scott Mansfield will take Bernd Zeuner examples to see how the result of interleaving is.
  • Italo Busi points out that the table with the operation parameters risks to be too dense.
    • We could explore a split of the parameters table with
      1. table with all parameters and their main characteristics, followed by
      2. tables expanding all the other properties of each single parameter
  • Andrea Mazzini shows an example (from MEF draft) where the template drives an operation format similar to class format.
  • Agreed to keep the name of the stereotypes in the output format.
  • No final agreement on a specific format, discussion to be continued.
7 5 min

ExtendedComposite association end

_classB should not be defined in an ExtendedComposite association

  • Bernd Zeuner Update the Modelling Guidelines accordingly

8


Property names in UML documentation converted to Yang

Not discussed on May 21st
9
Agenda of next callAll
  • Administrative
  • Papyrus-Model2Doc further investigations?
  • Handling of the UML → YANG Mapping Tool in GitHub - Still TBD
  • Papyrus 5.0.0 Version
  • Property names in UML documentation converted to Yang
  • Agenda of next call
  • AOB

Action items