Child pages
  • 2021-05-14 IISOMI Meeting notes

Versions Compared

Key

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

...

#

Time

Item

Who

Notes

15 minAdmin: Call planAll

 Leader Bernd Zeuner  (Kam in CA)

 Leader Andrea Mazzini (Kam may not be available)

 CANCELLED

 Leader Hing-Kam Lam

 Leader Scott Mansfield

10?  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

Actions were assessed and all but one had been dealt with. The action below was extended by 4 weeks.

  •   Scott Mansfield Scott to improve the tool so that to minimize the manual fix


VariousKam

Enum literal (propose allow 12.5GHz)

  • UML model guideline currently prevents "." (and other characters). This prevents "12.5GHz" from being an Enum literal.
  • Yang has exceptions to allow "well-known value" such as "Only lowercase letters, numbers, and dashes SHOULD be used in identifier names. Uppercase characters, the period character, and the underscore character MAY be used if the identifier represents a well-known value that uses these characters."
  • Scott noted that the tooling is not consistent. Some places the tooling converts to Yang format and in others it does not.
  • The tooling is not validating the UML naming convention. 
  • Tooling does no translation of Enum Literals.
  • Changing the guidelines are sufficient.
  • Nigel suggested that a stereotype to identify the rare case where a well known value is being used should be available (not to be used by the tooling). This was not accepted.
  • Agreed to not change the tooling.
  • Agreed to proceed with Enum literals in upper case in Yang (i.e., not strict Yang, but still essentially allowed by "well-known value").
  • Agreed to not add a stereotype.
  • Agreed that we would not follow RFC 8407 on the Enums.
  • Agreed to change the guideline rules to allow for well known terms to be used in the Enum name.
  •    Bernd Zeuner  Update the UML guidelines to reflect the agreements above.
0  minPapyrus-Model2Doc feature

Not discussed on 14 May

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
  • 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. 

0 minUML → YANG mapping issues and enhancements

Not discussed on 14 May

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: 
0minPapyrus 5.0.0 Version
Not discussed on 14 May
2minAgenda of next callAll
  • Administrative
  • Papyrus-Model2Doc further investigations?
  • Handling of the UML → YANG Mapping Tool in GitHub - Still TBD
  • Papyrus 5.0.0 Version
  • Agenda of next call
  • Various issue:
    • GenDoc didn't generate constraint
    • GenDoc didn't generate the Type of pointed external class
    • GenDoc OstigOTtpSource txti multiplicity 64 is not generated correctly.
    • ExtendedComposite association end
    • Property names in UML documentation converted to Yang

...