# | Time | Item | Who | Notes | |
---|---|---|---|---|---|
1 | 5 min | Admin: Call plan | All | US/Canada: Daylight Savings Starts 13 March. Eastern Daylight Time is UTC-4 Leader: Kam Leader: Scott (IETF meeting) Europe: European Summer Time Starts 27 March CEST is UTC+2 Leader: Martin (ooo Nigel) cancelled (ooo Bernd, Nigel) cancel(l)ed (public holiday in Germany: Bernd, Martin, Nigel) Leader: Bernd Leader: Nigel (ooo Kam) Leader: (ooo Kam) | |
2 | 5 min | Admin: IISOMI Action Items status | All | IISOMI Action Items review (every meeting) Action Items done/discussed
Refreshed Action Items
| |
3 | 1 min | Add values to an existing core-model enumeration | Martin | the ONF OTCC 5G-xHaul group would like to get guidance how to add microwave specific layer-protocol-names to core-model:layer-protocol-names (e.g. microwave-physical-section, microwave-section, ....). More abstract: How can a conditional package add values to an existing (extensible) core-model enumeration? To demonstrate, create a enum and then extend the enum using either specify or generalization. Determine how to display this in GenDoc. Determine the guidelines needed to convert this structure to YANG. Initial thoughts are to ensure isLeaf = false so Identity is used in YANG. For example the core model enum would be the base and the specify or generalization would extend the base identity. Scott Mansfield Demonstrate small example of enums with gendoc 2022-03-18:
| |
4 | 0 min | UML modeling guidelines questions from ITU-T Q14/15 | Italo | <specify> Decision expected from IISOMI Concern on augment rules UML/YANG Guidelines should be improved(?) keep text in UML to YANG Guidelines UML Guidelines RootElement
Update in mapping Guidelines expected Discussion to be continued ....
Examples about RootElement representation in YANG (thanks Italo)
2022-03-18: | |
5 | 50 min | UML modeling guidelines | Italo | UML modeling guidelines
2022-02-04: No discussion. Deferred to 2022-02-11 2022-03-18: Discussed.
To be discussed on next week 2022-03-25:
| |
6 | 0 min | Coding of target path |
2022-01-21:
2022-01-28: See 2022-01-28 IISOMI Meeting Minutes #4 for details of discussion
2022-02-04:
Post call email from Italo: 2022-02-11: In order to be able to compose the target path of the two «Specify» relationships the class diagram below has been extended with the greyed out "non existing" object class and composition relationships. Andrea Mazzini will draft rules for the UML Modelling Guidelines for creating the target paths; this is part of the existing action item "Improve explanation of target sterotype string content formation in the UML Guidelines". Discussion will continue in two weeks. 2022-03-04: Italo Busi presents an UML diagram with abstraction examples and related translations into Yang augment statements.
augment "/tapi-common:context/tapi-connectivity:connectivity-context/tapi-connectivity:connectivity-service/tapi-connectivity:end-point" { Which is then an additional node in the Yang tree: +--rw context Italo Busi highlights that current translation does not allow distinct labels for the container and for the used class. By always specifying as abstract the augmenting class we may allow both ways. Post meeting note: Italo Busi provides the updated diagram with a summary of the agreements-
module base-model-example { grouping model-root { grouping model-element { grouping class-b { grouping class-c { grouping class-d { container root {
augment /b:root/b:element:
module augment-model-example { import base-model-example { grouping class-a { grouping class-b { grouping class-c { grouping class-c-pac { grouping class-d { augment "/b:root/b:element" { augment "/b:root/b:element" { augment "/b:root/b:element" { augment "/b:root/b:element" { 2022-03-18: | ||
7 | 0 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:
2022-02-04: No discussion. Deferred to 2022-02-11 2022-03-18: | ||
8 | 0 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-02-04: No discussion. Deferred to 2022-02-11 2022-03-18: | ||
9 | 0 min | Guideline/Tooling wiki page(s) for listing the tasks | Andrea Mazzini shows Guidelines and Tooling Discussion Items
2022-01-28 No update. 2022-02-04: No discussion. Deferred to 2022-02-11 2022-03-18: | ||
10 | 0 min | Feature/condition | Prior discussion: IISOMI 2021-09-03 Meeting Minutes, #3 2022-02-04: No discussion. Deferred to 2022-02-11 2022-03-18: | ||
11 | 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. 2022-02-04: No discussion. Deferred to 2022-02-11 2022-03-18: | ||
12 | 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. 2022-02-04: No discussion. Deferred to 2022-02-11 2022-03-18: | ||
13 | 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. 2022-02-04: No discussion. Deferred to 2022-02-11 2022-03-18: | ||
14 | 0 min | Cleanup of the existing public GitHub (ONF EAGLE), rationalize the forks/branches | Prior discussion: IISOMI 2021-09-24 Meeting Minutes #10 2022-01-28 No update. 2022-02-04: No discussion. Deferred to 2022-02-11 2022-03-18: | ||
15 | 0 min | GenDoc Issues | All | Prior discussion: 2021-05-28 IISOMI Meeting notes #6
2022-01-28 No update. 2022-02-04: No discussion. Deferred to 2022-02-11 2022-03-18: | |
16 | 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. 2022-02-04: No discussion. Deferred to 2022-02-11 2022-03-18: | ||
17 | Agenda of next call | All |
|