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

2022-07-01 IISOMI Meeting Minutes

01 Jul 2022 Leader: Kam; (Not available: Scott, Andrea, Nigel)

08 Jul 2022 Leader: Scott; (Not available: Andrea, Nigel)

15 Jul 2022 Leader: Bernd; (Not available: Scott)

22 Jul 2022 Leader: Scott; (Not available: Bernd)

29 Jul 2022 Leader: Andrea?/Cancel?; (IETF 114 week Not available: Scott, Italo, Nigel)

05 Aug 2022 Leader: Kam; (Not available: Nigel)

12 Aug 2022 Leader: TBD; (Not available: Nigel)

19 Aug 2022 Leader: TBD; (Not available: Nigel)

26 Aug 2022 Leader: Nigel; (Not available: Kam )

All

IISOMI Action Items review (every meeting)

Action Items with due date today/done/discussed

• Hing-Kam Lam Bernd Zeuner 01 Jul 2022 Need to clean up other pages, such as Guidelines and Tooling Discussion Items and move material to IISOMI Discussions
  • Cleaned-up performed, reviewed and agreed as follows:
    • #1 (Yang mapping of UML construct names) has been moved to → Closed Discussed Items "Mapping of UML construct names in UML Comment"
    • #2 (Abstractions: How to dump the properties.) has been moved to → Gendoc related items "Abstractions: How to dump the properties". 
    • #3 (Abstractions: The stereotype "Cond" is not managed) is considered as part of  the UML-YANG Mapping Guidelines related items "Use of Feature/Condition"
    • #4 (Yang Identity lost in yang2oas mapping) has been moved to → YANG-OAM Mapping related items "Yang Identity Lost in yang2oas"
    • #5 (Tool handling of Inter-module identities) has been moved to → UML-YANG Mapping Guidelines related items "Tool handling of Inter-module Identities"
  • This action item is done.
• Hing-Kam Lam Bernd Zeuner 15 Jul 2022 Assess 2022-05-27 IISOMI Meeting Minutes and extract all discussion items into IISOMI Discussions as appropriate
  • KL and BZ will do in an off-line session on 07 Jul 2022 
• Italo Busi 01 Jul 2022 Coding of target path: Provide an update to the diagram and propose text for the mapping guidelines. (see Coding of target path)
  • Figure 5.30 in <Draft_TR-514_UML_Modeling_Guidelines_v1.3.04 - ib-00.docx> from Italo's 13 May 2022 email to BZ, AM, & KL
  • 
  • Clarification made in the discussion
    • The OMG UML abstraction: When there is the abstraction dependency between ClassA and ClassB, attributes of ClassB will be instantiated in instance of ClassA, instead of in instance of ClassB. But there could be instance of ClassB instantiated independent of ClassA. This is why ClassB needs not to be an abstract class. 
    • The IISOMI «Specify»: ClassB is abstract class. Never have ClassB instance.
    • Difference between «Specify» and «ExtendedComposite»: «Specify» has a path, which allows inter-module referencing. «ExtendedComposite» doesn't have a path and is used for classes within the same module. So, for classes within the same module, no need to use «Specify».
      • Question: Should «Specify» be used for classes between Aggregates, even the Aggregates are within the same module?
  • Will continue the discussion in the next call.

New Action Items

Refreshed Action Items

Plan

• 08 Jul 2022 
  
  • Action items
    • July 15 due (KL/BZ): Assess 2022-05-27 IISOMI Meeting Minutes and extract all discussion items into IISOMI Discussions as appropriate
    • July 1 due (IB): Coding of target path: Provide an update to the diagram and propose text for the mapping guidelines. (see Coding of target path)
  • Discuss UML-YANG translation related questions from academic researchers.
  • Check if there needs any editing instruction for updating the three guideline documents due to the Closed Discussion Items.
  • Follow up on discussion items
  • Clean-up or disposition of the wiki page [Historic] Versions of UML Models and Modeling Tools (Overview)