1. Pages
2. …
3. OIMT
4. IISOMI
5. IISOMI Minutes
6. 2021 IISOMI Minutes
7. 2021-10-01 IISOMI Meeting Minutes

Page History

01 Oct 2021 Leader: Bernd (Not available: Nigel, Scott)

08 Oct 2021 Leader: Nigel

15 Oct 2021 Leader: Scott (Not available: Andrea)

22 Oct 2021 Leader: Scott

All

IISOMI Action Items review (every meeting)

Action items done

• None

Refresh Action Items

•  Nigel Davis  08 Oct 2021 Review proposal for "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." (in minutes 2021-07-30 IISOMI Meeting Minutes).
•  Scott Mansfield 08 Oct 2021  To take the gendoc examples from the guidelines and perform regression test. 
•  Scott Mansfield 08 Oct 2021  To investigate why none of the <<cond>> is retrieved from the model.

Bernd Zeuner 

Bernd proposed to capture the discussion items in GitHub Issues than in the IISOMI Meeting Minutes and just provide a link to the GitHubIssue in the minutes. This prevents that the same discussion minutes appear many times in the minutes. Two draft Issues are contained in https://github.com/samans/iisomi-private/issues/1 and https://github.com/samans/iisomi-private/issues/2 and have been presented at the meeting.

At the discussion it was pointed out that

• a private repository is not the appropriate place for the items since not everyone has access to this
• the ONF GitHub is publicly available but not all participants are allowed to contribute to it
• there is no single ONF repository which could host such Issues; IISOMI is spread over many repositories
• it might be possible to cover the discussions in Wiki pages
• new discussions should be captured in the Meeting Minutes and then copied to the Wiki pages

•  Bernd Zeuner 08 Oct 2021 Draft an example Wiki page that capture an discussion item

Andrea Mazzini

Italo Busi Hing-Kam Lam

https://github.com/samans/iisomi-private/issues/2

Not discussed. Defer to next call

• Extended composition in UML (including object classes and interfaces)
  • See 8/16-17 email thread: RE Questions about the extended composition in UML.msg
• Also look at the 2021-08-13 IISOMI Meeting Minutes on the discussion of how to display Association information using Gendoc
  • Two examples
    • TapiConnectivity.docx (See section 1.2.2)
    • TapiConnectivitySimple.docx (See section 1.3)
  • Modeling guidelinesTR-514 (draft)
    • See Figure 5.26 in section 5.4.2.1 for ExtendedComposite information
    • See section 5.4.3 for information on Role Type

September 7, 24: No discussion

October 1:

Agreement: Extended composition should also be available for Interfaces and Signals.

Question: Can one extension class (Class, Interface, Signal) extend more than one base class (Class, Interface, Signal)? → Yes

•  Italo Busi 08 Oct 2021 To verify and confirm that an "Extended composition" can also be used with Interfaces and Signals.

Hing-Kam Lam

September 7, 24: No discussion

October 1:

Mentioning of UML artefact names (UCC) in YANG descriptions creates problems.
E.g., TerminationPoint (object class) is converted in YANG to termination-point (statement) but if "TerminationPoint" appears in the related YANG description it is remains TerminationPoint.

Agreement: The Mapping Tool should convert also the artefact names within the descriptions to YANG style (i.e., kebab-case). The list of names to be converted in the descriptions is limited to the UML artefact names.

•  Bernd Zeuner 15 Oct 2021 Update the Mapping Guidelines with a rule that artefact names within the descriptions should be converted to YANG style.

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

Consider a plan for convergence of ITU-T Q14/15, ONF Common IM and TAPI to 2020-06 (4.16) version

September 24: Reaffirmed the need to explore 2020-06 (4.16) release

October 1: No discussion

Just for information; was not discussed October 1:

Scott Mansfield created reengineer-private Github repository and added the reengineered IEEE and IETF YANG models from Februrary 12, 2020 to it.
People interested can ask Scott Mansfield for the access.

• Currently there are 7 forks of OpenNetworkingFoundation/EagleUmlYang repositiory:

• Scott Mansfield clarifies that the Karthik Sethuraman fork is the base of his developments (carried out in his "private" Github).
• There is an open pull request #15 with some conflicts to be solved.
  
  • Once solved, the main repository OpenNetworkingFoundation/EagleUmlYang (Tapi_v2x branch) will be aligned to Karthik Sethuraman fork.
    • This will allow Scott Mansfield future commits on Karthik Sethuraman fork, to make publicly available the tool improvements.
  • Scott Mansfield suggests to add a new branch to OpenNetworkingFoundation/EagleUmlYang and possibly define an Eagle Release.

September 7: No discussion

September 24: Scott Mansfield clarifies that without the involvement of key folks with authority on Github no progress can be performed. No administrators appear for ONF EAGLE Github.

October 1: No discussion

All
Hing-Kam Lam

Gendoc output for Interfaces, Operations, Associations, Abstractions

How to dump endpoints of abstractions?

Italo Busi Dump of Realizations possible?
Andrea Mazzini Given that Interface Realizations are dumped as Abstractions, maybe this is valid also for Realizations.

Other Gendoc Issues

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.

September 7, 24, October 1:  No discussion

Martin Skorupski

O-RAN cooperation

October 1:

O-RAN policy has changed collaboration rules. (O-RAN Alliance is registered in Germany)

•  Martin Skorupski 15 Oct 2021 check with O-RAN the tooling funding status.