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

2021-12-03 IISOMI Meeting Minutes

10 Dec 2021 Cancelled (Not available: Kam, Scott, Xiang & Italo - in SG15 meeting)

17 Dec 2021 Cancelled  (Not available: Kam, Scott, Xiang & Italo - in SG15 meeting)

24 Dec 2021 Cancelled – Holiday

31 Dec 2021 Cancelled – New Year Eve

07 Jan 2022 Leader: Nigel 

14 Jan 2022 Leader: Scott? - candidate

21 Jan 2022 Leader: Andrea

28 Jan 2022 Leader: Nigel

All

IISOMI Action Items review (every meeting)

Action items done

• --

Refresh Action Items

• Nigel Davis  19 Nov 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).
  • Current state: The Yang has UML formatted names in it. The user is required to simply deal with this. There have not been any specific complaints, but clearly the comments are confusing. It may be beneficial to add notes to the read-me or similar to explain the formatting transition.
    • "The 'description' text often includes names of properties, classes etc. that are in 'camel case' as opposed to 'hyphen-case' as used for yang labels. The names can be converted by simply ensuring the first letter is lower case and that any intermediate upper case letters are turned into lower case preceeded by a hyphen (e.g., HyphenCase → hyphen-case)."
  • November 19 discussion: Agreed to turn the above decision into a UML-to-YANG mapping guideline tooling task (roadmap item). 
    • Andrea Mazzini 07 Jan 2022 Create a Guideline/Tooling wiki page(s) for listing the tasks 

• Scott Mansfield 07 Jan 2022  To take the gendoc examples from the guidelines and perform regression test. 
• Scott Mansfield 07 Jan 2022  To investigate why none of the <<cond>> is retrieved from the model.
  • Andrea indicated the had attempted to apply analogous rules to member-end to include other properties. Andrea tried various techniques to get client and supplier but with no success 
    • Probably need to review the UML metadata
  • Andrea was able to print the target string

• Scott Mansfield 07 Jan 2022   To investigate how to get client and server values for an abstraction.

• Use of git may be problematic as we have multiple repositories.
  • Nigel Davis 07 Jan 2022  determine whether ONF can create IISOMI Jira.

Finished Actions

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
  

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 

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

Q: can we remove this item from next meetings agenda in 2022-01?

A: no - waiting for feedback - we keep it until Bernd Zeuner  is back

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.

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