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

2022-01-21 IISOMI Meeting notes

28 Jan 2022 Leader: Nigel

04 Feb 2022 Leader: Kam

11 Feb 2022 Leader: Bernd

18 Feb 2022 Leader: Scott

25 Feb 2022 Leader: Martin

04 Mar 2022 Leader: Andrea

11 Mar 2022 Leader: Nigel

All

IISOMI Action Items review (every meeting)

Action items done

• Andrea Mazzini 21 Jan 2022 Create a Guideline/Tooling wiki page(s) for listing the tasks

Refreshed Action Items

• Nigel Davis 28 Jan 2022 Try to move TR-512 v1.5 core model to 2020-06 (4.16) Eclipse
• Nigel Davis 28 Jan 2022 determine what Jira form structure etc. ONF can create IISOMI. Provide example/detail etc. for discussion.
• Martin Skorupski 04 Feb 2022 To update on the progress in O-RAN of getting approval of an O-RAN project on UML-YANG tooling
  INFO: Tracy van Brakle publish a document as proposal for O-RAN TSC 
  https://oranalliance.atlassian.net/wiki/download/attachments/2211414051/ATT.2021.11.30-WG10-IM-DM_Tooling_Informational_Report-v00.02.docx?api=v2

O-RAN cooperation

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

October 15: Martin Skorupski checked with O-RAN the tooling funding status.  There is hope, not dead, but not moving either. 

• Martin Skorupski 19 Nov 2021 Get a written statement from O-RAN leadership on state of tooling funding's

November 19 discussion: Martin reported on the progress of requesting funding from O-RAN for UML-YANG tooling. The proposal will be up for voting in O-RAN.  

• Martin Skorupski 21 Jan 2022 To update on the progress in O-RAN of getting approval of an O-RAN project on UML-YANG tooling
  INFO: Tracy van Brakle publish a document as proposal for O-RAN TSC 
  https://oranalliance.atlassian.net/wiki/download/attachments/2211414051/ATT.2021.11.30-WG10-IM-DM_Tooling_Informational_Report-v00.02.docx?api=v2
  

2022-01-21:

• Martin Skorupski has informed that the proposal reached the next level and moved from O-RAN TSC to O-RAN Executive Committee (EC). Discussion in O-RAN EC will start.

Papyrus Releases

• • Consider a plan for convergence of ITU-T Q14/15, ONF Common IM and TAPI to 2020-06 (4.16) version
  • Prior discussion: IISOMI 2021-09-24 Meeting Minutes
    • Reaffirmed the need to explore 2020-06 (4.16) version

November 19 discussion: The TR-512 v1.5 Core model was developed using Eclipse 2019-09. It the model can migrate to 2020-06 seamlessly, Q14/15 might move G.7711 v4.0 (12/2021 consent) also to Eclipse 2020-06. To verify the seamless migration: 

• Nigel Davis 14 Jan 2022 Try to move TR-512 v1.5 core model to 2020-06 (4.16) Eclipse
• Hing-Kam Lam Try to move TR-512 v1.5 core model to 2020-06 (4.16) Eclipse

2021-12-03: 

• from Kam - diagrams from TR-512 v1.5 core model on 2020-06 (4.16) Eclipse looks fine
• proposal for next week ITU-T: IISOMI moves to 2020-06, because gen-doc works find 
• TAPI will follow after some tests will be done by Andrea Mazzini
• Nigel Davis 21 Jan 2022 Try to move TR-512 v1.5 core model to 2020-06 (4.16) Eclipse

2022-01-21:

• Scott Mansfield clarifies that the Gendoc application depends on Papyrus version, and not on Eclipse version.
• Hing-Kam Lam in ITU-T SG15 we plan to migrate to 2020-06 (4.16) version by the end of February.
• Scott Mansfield and Andrea Mazzini agree to create a wiki page dedicated to the examples of Gendoc templates.
• Scott Mansfield model2doc should dump every UML construct, to be checked.

Prior discussion: 2021-10-29 IISOMI Meeting Minutes #2

Prior discussion 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

Proposal wiki page from Bernd for capturing discussion items:

• IISOMI Discussions

2022-01-07:

• Follow-up after progress made with Jira ( 14 Jan 2022 ) as per action for Nigel Davis 

2022-01-21:

• Scott Mansfield informs that IETF is not using JIRA, but Github and its Issues. But as highlighted above, relying on Github for IISOMI seems not feasible.

Andrea Mazzini shows Guidelines and Tooling Discussion Items

• Martin Skorupski adds two columns, Reporter and Rough Effort Estimation.
• Scott Mansfield until there is no investment, there will be no progress.

Andrea Mazzini

Hing-Kam Lam

Prior discussion: 2021-10-29 IISOMI Meeting Minutes #5

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

2022-01-07:

• Bernd will upload the draft (IISOMI Deliverables)
  • Bernd Zeuner 14 Jan 2022  Upload latest mapping guidelines to IISOMI Deliverables
    → Done: IISOMI 531 UML to YANG Mapping Guidelines (new editor Karthik)

Prior discussion: 2021-05-28 IISOMI Meeting notes #3

2022-01-21 post meeting notes:

Scott Mansfield found the following links to various update sites and performed some tests:

• (model2doc 2019 version 0.7.0): https://download.eclipse.org/modeling/mdt/papyrus/components/model2doc/releases/0.7.0/
• (model2doc 2021 version 0.8.0): https://download.eclipse.org/modeling/mdt/papyrus/components/model2doc/2021-12/
• (model2doc 2022 bleeding edge):  https://download.eclipse.org/modeling/mdt/papyrus/components/model2doc/releases/0.8.0/p2/
• (model2doc 2022 last successful build): https://ci.eclipse.org/papyrus/job/Papyrus-Model2Doc/lastSuccessfulBuild/artifact/repository/

The last successful build (model2doc 0.8.0) works fine in 2021-12 (4.22) (Eclipse 4.22 and Papyrus 6.0).

Regarding 2020-06 (4.16), none of the found Model2Doc versions works.

Even with Eclipse 2021-12 (4.22) but Papyrus 4.8, Model2Doc does not work.

The conclusion so far is that only version 2021-03 (4.19) - Papyrus 5.1 and later seem to work with the 0.8.0 Model2Doc version.

Prior discussion: IISOMI 2021-09-24 Meeting Minutes #9 and 2021-10-01 IISOMI Meeting Minutes #8

Prior discussion: IISOMI 2021-09-24 Meeting Minutes #10

All
Hing-Kam Lam

Prior discussion: 2021-05-28 IISOMI Meeting notes #6

• Scott Mansfield  18 Feb 2022  Provide  gendoc  examples  to  implement  the  first  two bullets
  • 2021-05-28 IISOMI Meeting notes #6
  • GenDoc didn't generate constraint
  • GenDoc OstigOTtpSource::txti:EByte multiplicity [64] is not generated correctly
  • Discussion Needed:  To agree on a specific format for operation, then implement

2021-12-03

from OIMT

CoreModel FD - to of the tree

Composed FC-Switch .... with no sense if independent

.

Driver of Model structure (arrangement)

usage of stereo-types

• aggregate
• leaf
• admin relationships
• Chris has nice ideas - but needs to be further analyzed.

First try of "modelling profiles" on CoreModel

Target:

• Split CoreModel in "smaller" parts - decoupling 
• Rules needs to be described/defined/documented.

Further details:

• https://wiki.opennetworking.org/download/attachments/266141701/ONF_T64_DddAggregates.pptx?api=v2

2022-01-07:

• Nigel Davis noted that OIMT have agreed to develop the profile and apply to a part of the core as an example. This can be presented to IISOMI in February.
• Nigel Davis 18 Feb 2022 Provide an overview of the DDD trial profile and show application to the core model.

Andrea Mazzini Italo Busi 

• In particular, if I understand correctly, for the root element object class (i.e., red element), the format is actually not “[/<ModelName>:<ClassName>:<navigable association end role name>]” as indicated in the UML guidelines v1.3.03 but it is in the format of “[/<ModelName>:<ClassName>:<name of the RootElement stereotype>]”
• Model Name or Prefix

2022-01-21:

• Italo Busi indicates that the UML guideline is not requiring the undescore in the name of the RootElement stereotype, while the examples in the UML to YANG guideline include the undescore (e.g. TAPI currently has "_context"). It is recommendable to clarify and align the guidelines.

• In particular, for the root element object class (i.e., red element), the format is actually not “[/<ModelName>:<ClassName>:<navigable association end role name>]” as indicated in the UML guidelines v1.3.03 but it is in the format of “[/<ModelName>:<ClassName>:<name of the RootElement stereotype>]”, e.g. 

  • PtpTlpDefaultDsSpecSpecifiesPtpDefaultDs: /ptp:Ptp:_ptp/ptp:Ptp:_instanceList/ptp:PtpInstance:_defaultDs

  • PtpTlpPortDsSpecSpecifiesPtpPortDs: /ptp:Ptp:_ptp/ptp:Ptp:_instanceList/ptp:PtpInstance:_portDsList

  • PtpTlpTcDefaultDsSpecSpecifiesPtpTcDefaultDsPac: /ptp:Ptp:_ptp/ptp:Ptp:_instanceList/ptp:Ptp:_transparentClockDefaultDs