Date
Attendees
- Nigel Davis
- Hing-Kam Lam
- Alex Stancu
- Bernd Zeuner
- Martin Skorupski
- Xiang YUN
- LoreLei Rouvrais
Apologies
- Andrea Mazzini
- Italo Busi (for ITU-T)
- Scott Mansfield
Agenda
- Administrative
- Call plan (schedule, leader)
- Review IISOMI Action Items
- Coding of Target Path
- UML → YANG Mapping Tool funding
- Papyrus Releases
- Consider a plan for convergence of ITU-T Q14/15, ONF Common IM and TAPI to 2020-06 (4.16) version
- Proposals of capturing discussion items
- Feature/condition
- Convention of UML property names in document/comment/description
- Papyrus-Model2Doc further investigations?
- Private GitHub
- Public GitHub cleanup
- Gendoc Issues: output for Interfaces, Operations, Associations, Abstractions
- Modular and decoupled modeling process
- Agenda of next call
- AOB
Discussion items
# | Time | Item | Who | Notes |
|---|---|---|---|---|
| 1 | 5 min | Admin: Call plan | All | Leader: Kam Leader: Bernd Leader: Scott Leader: Martin Leader: Andrea Leader: Nigel |
| 2 | 15 min | Admin: IISOMI Action Items status | All | IISOMI Action Items review (every meeting) Action items done
Refreshed Action Items
Note in Martin Skorupski email from 5 Nov 2021 there is no further action. |
| 3 | 5 min | UML → YANG Mapping Tool funding | Martin | 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.
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.
2022-01-21:
2022-01-28: No update |
| 4 | 10 min | Coding of target path |
2022-01-21:
2022-01-28:
 Extract form email from Italo Busi on 25 Jan
Note that Italo intended to write "Should the value of the name attribute of the RootElement sterotype follow the convention of navigable attribute" The referencing mechanism used in the target path identifies each element in the path by going one step up the path (hierarchy) to find the referencing attribute from the class that references the class to be identified. This works for all but the root entity (where there is clearly nothing one step up the path hierarchy). This is why an artificial role end was used reference the root entity. This is conveyed in the <<RootElement>> stereotype as shown above. It is as if a class Context references the TapiContext via a composition with a navigable attribute _context. The class "Context" does not exist in the model. Both the class name "Context" and its reference are derived from the value of the name in the <<RootElement>> Stereotype (i.e., "_context") where the class name is an upper camel form of the string with the "_" removed. The mechanism should be described more clearly in the modeling guidelines.
On Italo's second question "Should we use the module name (i.e., IetfPtp) or the module prefix (i.e., ptp) or either option?"
| |
| 5 | 10 min | Papyrus Releases | Papyrus Releases
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:
2021-12-03:
2022-01-21:
2022-01-21:
| |
| 6 | 5 min | Proposals for capturing discussion items | Prior discussion: 2021-10-29 IISOMI Meeting Minutes #2 Prior discussion pointed out that:
Proposal wiki page from Bernd for capturing discussion items: 2022-01-07:
2022-01-21:
2022-01-28 No update | |
| 7 | 0 min | Guideline/Tooling wiki page(s) for listing the tasks | Andrea Mazzini | Andrea Mazzini shows Guidelines and Tooling Discussion Items
2022-01-28 No update. |
| 8 | 0 min | Feature/condition | Prior discussion: IISOMI 2021-09-03 Meeting Minutes, #3 | |
| 9 | 0 min | Convention of UML property names in document/comment/description | Prior discussion: 2021-10-29 IISOMI Meeting Minutes #5
2022-01-07:
2022-01-28 No update. | |
| 10 | 0 min | Papyrus-Model2Doc feature | 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:
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. 2022-01-28 No update. | |
| 11 | 0 min | Private GitHub | Prior discussion: IISOMI 2021-09-24 Meeting Minutes #9 and 2021-10-01 IISOMI Meeting Minutes #8 2022-01-28 No update. | |
| 12 | 0 min | Cleanup of the existing public GitHub (ONF EAGLE), rationalize the forks/branches | ||
| 13 | 0 min | GenDoc Issues | All | Prior discussion: 2021-05-28 IISOMI Meeting notes #6
2022-01-28 No update. |
| 14 | 0 min | Modular and decoupled modeling process | 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
First try of "modelling profiles" on CoreModel Target:
Further details: 2022-01-07:
2022-01-28 No update. | |
| 15 | Agenda of next call | All |
|
Overview
Content Tools
Activity