Nigel Davis Try to move TR-512 v1.5 core model to 2020-06 (4.16) Eclipse
Having problems with Gendoc (but Scott has managed to get Gendoc work so closing this action)
Scott Mansfield Confirm that Gendoc works reliably with Papyrus 2020-06
Refreshed Action Items
Nigel Davisdetermine what Jira form structure etc.ONF can create IISOMI. Provide example/detail etc. for discussion.
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 Skorupskichecked with O-RAN the tooling funding status. There is hope, not dead, but not moving either.
Martin SkorupskiGet 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 Skorupskihas 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.
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 Busiindicates that theUML guidelineis not requiring the undescore in thenameof theRootElementstereotype, while the examples in theUML to YANG guidelineinclude 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.
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.
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 Try to move TR-512 v1.5 core model to 2020-06 (4.16) Eclipse
Hing-Kam LamTry 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 Try to move TR-512 v1.5 core model to 2020-06 (4.16) Eclipse
2022-01-21:
Scott Mansfieldclarifies that the Gendoc application depends on Papyrus version, and not on Eclipse version.
Scott Mansfieldmodel2docshould dump every UML construct, to be checked.
2022-01-21:
Brief discussion on 2020-06 (4.16)noting that Papyrus appeared to be OK (but Nigel Davis noted that in his environment Gendoc was still not working due to memory apparently).
Nigel Davisnoted 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 DavisProvide an overview of the DDD trial profile and show application to the core model.
