Open Information Model & Tooling
Space shortcuts
Expand all   Collapse all
Child pages
  • 2022-09-02 IISOMI Meeting Minutes
Skip to end of metadata
Go to start of metadata

Date

Attendees

Apology

Agenda

  • Administrative
    • Call plan (schedule, leader)
  • Action items due/done
    • Navigable attribute to ExtendedComposite
  • xmi2yang follow-up and next steps
  • Check the progress of the ExtendedComposite updates
  • Coding of target path 
  • AOB

Discussion items

Time

Item

Who

Notes

5 minAdmin: Call planAll

 Leader: Bernd

    • xmi2yang follow-up and next steps
    • Check the progress of the ExtendedComposite updates
    • Coding of target path 

 Leader: Kam; (Not available: Andrea)

    • Check the progress of the ExtendedComposite updates
      • Workaround regarding the modelling of the «ExtendedComposite» for YANG mapping
      • Different gendoc script styles in IISOMI and ITU-T
      • What information on «ExtendedComposite» relationships is meaningful?
    • xmi2yang follow-up and next steps
    • Coding of target path

 Leader: Scott; (Not available: )

 Leader: Andrea; (Not available: Kam, Scott, Italo, Yun Xiang)

 Leader: Nigel; (Not available: Kam, Scott, Italo, Yun Xiang)

Leader:  Bernd; (Not available: Kam)

 15 minAction items due/doneAll

IISOMI Action Items done or past due

  • The owner of the past due items, in particular the 2021 ones, are reminded to check the progress and will be reported in the next call.

Dealing with action items:

Add new action items to the minutes; after the meeting copy the action item together with the whole discussion to the related Discussion item and check the action item in the minutes.

min

xmi2yang follow-up and next steps

All

no discussion, deferred to next week.

40 min

Check the progress of the «ExtendedComposite» updates

All

Scott provided the gendoc script for extracting the «ExtendedComposite» relationships.

Issues/Questions:

  1. The loop over ALL associations sorted by name does not extract any association if at least one association does not have a name.
    All associations should have names in the model.
  2. Scott's gendoc script fragments are not in line with the current fragments contained in the Papyrus Guidelines.
    Scott's gendoc is used in ITU-T "for ages"; the gendoc in the Papyrus Guidelines is quite old. → Continue the discussion next week.
  3. What information on «ExtendedComposite» relationships is meaningful? → Continue the discussion next week.
  • Scott Mansfield Update the gendoc script to loop only over the associations that have a name.

This topic is added to IISOMI Discussions / Papyrus Guidelines related items / Navigable attribute to ExtendedComposite


Not discussed:

Bernd provided a proposal for the UML modelling guidelines decribing the workaround regarding the «ExtendedComposite» relationships when the model needs to be mapped to YANG by the UML to YANG mapping tool.

Note: The modelling of the the «ExtendedComposite» aggregation needs to be adapted in case the UML model needs to be mapped to YANG by the UML to YANG mapping tool [5].
Knowing that this workaround will create an unnecessary attribute in the extended class, but the correct YANG can only be generated when the navigable association end at the extending class is owned by the classifier (expressed by the black dot at the arrow as shown in the diagram below).


 min

Coding of target path

All

IISOMI Discussions / Papyrus Guidelines related items / Coding of target path 

no discussion, deferred to next week.