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

2023-02-03 IISOMI Meeting notes

03 Feb 2023 Leader: Kam; (Not available: )

10 Feb 2023 Cancelled

17 Feb 2023 Leader: Nigel; (Not available: )

24 Feb 2023 Leader: Scott; (Not available: Kam) (May adjust to 8:00 PST to accommodate Kam)

03 Mar 2023 Leader: ; (Not available: Kam)

10 Mar 2023 Leader: Nigel; (Not available: Kam)

IISOMI Action Items done or past due

Action items done:

• Bernd Zeuner 03 Feb 2023 Create a small project with small example models and include a concrete class/abstraction and abstract class/abstraction, and update the powerpoint to provide the desired tool output. → SpecifyAugmentExample_20230131.zip, specify-augment.pptx

Due dates of the following action items updated:

All

Issue: The main issue is with the tooling not differentiating between abstract and concrete classes when creating the Augment statement in yang.

• Prior to the call, there was email discussion on the issue using the small Papyrus project that Bernd created.
  • Email thread discussion on Abstract vs. Concrete augmentation: See RE_ running xmi2yang on abstract and concrete example.msg
  • The mapping tool that Scott has been using does the same thing regardless of the abstract/concrete property. Thus no container wraps around the concrete augmenting class.
  • The mapping tool that Andrea has been using does wrap the augmenting class with a container. Note that in TAPI, the augmenting class is always concrete.
  • So, both tools are wrong. Abstract should not have containere. Concrete should have container.
• Discussion:
  • Scott explained his investigation.
  • Scott will compare the two tools, to find out where to add the switch in the code. The result will be discussed in the next IISOMI call.
  • Bernd explained the last 4 slides in specify-augment.pptx (version 4), which shows the expected result of mapping.

none