1. Pages
2. …
3. OIMT
4. IISOMI
5. IISOMI Minutes
6. 2021 IISOMI Minutes

2021-07-02 IISOMI Meeting Notes

09 Jul 2021 Leader ; Hing-Kam Lam

16 Jul 2021 CANCELLED (Not available: Scott, Italo, Andrea)

23 Jul 2021 Leader ; Bernd Zeuner (Not available: Scott, Andrea)

All

IISOMI Action Items review (every meeting)

• NOTE: Administration of IISOMI action items

  • New actions are added to the minutes of the current meeting and dated using the "task list" control
  • Do not copy actions from previous minutes, just add bullet version to reference the source minutes 
  • In every IISOMI meeting, 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.

Action item discussed

Action item updates: (no changes to action, just changing date)

•  Extended Composite

_classB should not be defined in an ExtendedComposite association

Bernd Zeuner13 Aug 2021 Update the Modelling Guidelines to cover "_classB should not be defined in an ExtendedComposite association (because it is abstract)."

• 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  13 Aug 2021Update the UML guidelines to reflect the agreements on Enum Literals.

2 July: Reviewed Andrea's suggestions for association formatting.

• Agreed:  The version that has the attribute table that includes the attribute description will be used.  And want to ensure the template includes the description of the association.  Will use this to complete the existing action item.

Scott Mansfield 13 Aug 2021 Explore Gendoc generation of associations (to cover stereotypes such as <<ExtendedComposite>> etc.) - See https://wiki.onap.org/display/DW/ONAP+Information+Model+-+Gendoc+Examples

Discussed need for collection of Gendoc material.

Scott Mansfield 13 Aug 2021 Update IISOMI Tooling with Gendoc template material.

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.

Agreed that this is an issue. 

It was suggested that:

• The construct names be marked in some way so that tooling could identify the strings to convert. The marking could be two single quotes (e.g., ''xyz''), two curly brackets (e.g., {{xyz}}) or similar. The comment could be:
  • Processed by the UML-Yang tool
  • Post processed after Yang generation to generate a Yang with corrected comments
• The reader will just have to deal with it
  • But a Yang reader will question the correctness of the comments
• The construct names could be changed to be less rigorous, e.g., ConnectivityService becomes connectivity service (which is somewhere between the UML and Yang form (connectivity-service)
  • But both the UML reader and the Yang reader will question the correctness of the comments

• Nigel Davis 09 Jul 2021 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."

Editor's note: Papyrus should enable comments to include links to class names etc. via xmi-id that should be selectable from list etc.

June 11: Gendoc output for Interfaces and Operations

• Reviewed the generated Interface and Operation table from Gendoc
  • 
• Discussed table numbering
  • Table 1 Operation of AcAction
  • Table 1.1 Parameters for Operation createClientContext
• Discussed case where there is no parameter  
  • Still have table for operation which does not have parameter, with a row for heading and the second row with N/A
• Discussed Interface meta data to be displayed in the GenDoc output
  • Qualified name
  • Description
  • Abstract
  • Applied stereotype
• Discussed columns 
  • Operation table
  • Parameter table

• Action item recreated: GenDoc didn't generate constraint
  • Scott Mansfield 13 Aug 2021 To investigate why none of the constraints is retrieved from the model.

E.g., 

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

May 14: 2021-05-14 IISOMI Meeting notes

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

• Issue: 
  • Feature/when (condition statement); Mandatory/multiplicity; Do not print the blank reference (fixed in Scott's version of the tool)  
  • GitHub issues list: https://github.com/OpenNetworkingFoundation/EagleUmlYang/issues  
    
• 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: 

June 11:

• Action item recreated: Tool improvement
  • Scott Mansfield 13 Aug 2021 Scott to improve the tool so that to minimize the manual fix
  • Scott Mansfield 13 Aug 2021 Scott to create a private Github for xmi2yang modification

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.

All
Hing-Kam Lam

May 14: 2021-05-14 IISOMI Meeting notes

•  AI (5/28/2021): Bernd Zeuner04 Jun 2021 Update the Modelling Guidelines accordingly

June 11: No discussion

All
Hing-Kam Lam