Child pages
  • 2022-06-17 IISOMI Meeting Minutes
Skip to end of metadata
Go to start of metadata




Discussion items






110 minAdmin: Call planAll

Leader: Scott (Not available: Bernd, Nigel)

Leader: Nigel (Not available: Bernd, Andrea)

Leader: TBD (Not available: Scott, Andrea)

Leader: Scott (Not available: Andrea)

Leader: Bernd (Not available: Scott)

Leader: Kam (Not available: )

Leader: TBD (IETF 114 week Not available: Scott, Italo)

245 min

Admin: IISOMI Action Items status


IISOMI Action Items review (every meeting)

Action Items with due date today/done/discussed

Create and issue, close it, and move it closed discussion items page Hing-Kam Lam

Nigel Davis   Determine what Jira form structure etc. ONF can create for IISOMI. Provide example/detail etc. for discussion.

  • The group decided to close (supersede) this action item and, instead, the group agreed to try the proposal of using the IISOMI Discussions confluence page (and sub pages) to capture the IISOMI discussion items (open/active and closed/concluded). 
    • The IISOMI Discussions confluence page will have two sub-pages, one for the open/active items and one for the closed/concluded items. Each of the sub-pages will have further sub-pages for each item.
    • The minutes page will have pointer to the item(s) being discussed and capture the discussion/decision/agreement/etc. of the discussed item in the meeting. 
    •  The IISOMI Discussions confluence page and sub-pages will also be updated to sync up with the minutes.
    • Bernd and Kam will make the initial update to the IISOMI Discussions page(s) and clean up the remaining part of the minutes page.

New Action Items

  • Scott Mansfield Andrea Mazzini Discuss xmi2yang tooling regarding to the translation of UML stereotype «Cond» (condition) into (if/when) feature statements.

Refreshed Action Items

  • Italo Busi  Coding of target path: Provide an update to the diagram and propose text for the mapping guidelines.
  • Italo presented his proposals of updating the guideline documents. See the next roll of this minutes. Due to short of time, the discussion will continue in the July 1 IISOMI call.

Andrea Mazzini Scott Mansfield   Review the proposed Gendoc script from Scott on retrieving the «Cond» properties of an association. 

Closed the gendoc portion of this action and created a new action to address the xmi2yang issue related to feature statements.

move this issue to closed discussion items page Hing-Kam Lam

    • Andrea considered yang translation
      • «Cond» on attributes is translated into if-feature statement but with limits (e.g., OR/AND is not supported)
      • «Cond» on associations usage is limited to abstractions and conditional augmentations. This is not translated into Yang.
      • Reference by value translation loses the condition statement in the yang translation. This will have to be done by hand.
        • Many of the property conditions could be on groups of properties that are in packages and hence referenced by value and hence on member end and hence lost.
      • Note that the «Cond» works on containers and leaves.
    • Noted that «OpenModelClass» has a condition.
    • Firstly, explore all condition statement that are in other stereotypes (not just «Cond»). Fix if statements as necessary. Consider any place where stereotype information is to be printed (this requires this code). Consider code for (perhaps using several separate runs):

            • Loop over all stereotypes and print all attributes that are NOT empty/default
            • Selecting specific stereotype list
            • Printing all

Action items