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

2023-05-12 IISOMI Meeting Minutes

12 May 2023 Leader: Kam; (Not available: Nigel, Scott)

19 May 2023 Leader: Nigel; (Not available: Bernd?)

26 May 2023 Leader:  Bernd; (Not available: )

02 Jun 2023 Leader: Andrea; 

09 Jun 2023 Leader: ; (Not available: Bernd?)

16 Jun 2023 Leader: ; (Not available: Bernd, Scott)

23 Jun 2023 Leader: ; (Not available: Scott)

30 Jun 2023 Leader: Scott; (Not available: Andrea)

Guidelines documents:

The IISOMI experts should review the latest drafts

• Draft_TR-514_UML_Modeling_Guidelines_v1.3.04.docx (2/2023)
• Draft_TR-515_Papyrus_Guidelines_v1.3.02.docx (1/2023) 
• Draft_TR-531_UML-YANG_Mapping_Gdls_v1.1.03.docx (2/2023)

Deadline of providing feedback: 26 May 2023 

Publication site: It will be, as before, at https://opennetworking.org/software-defined-standards/models-apis/, i.e.,

• From ONF home page https://opennetworking.org/ → RESOURCES tag → MODEL & APIs

IISOMI Action Items done or past due

Action items done:

Scott Mansfield 05 May 2023Determine from Papyrus contacts whether removal of the opportunity to have a signal compartment in a class was intentional.

• Right after last week's IISOMI call, Scott Mansfield emailed a screenshot of the 2020-06 version of Papyrus, clarifying that
  • Signals of a Class now show up in the “nested classifiers” compartment.  So the compartment for signal isn’t called signal anymore, there is one compartment that is used for all “nested classifiers” of which signal is one.
    
• Should this be documented in the Papyrus Guidelines?
  • Yes. Only in the Papyrus Guidelines document. Not in the UML modeling Guidelines document. The UML modeling guidelines still recommends defining signals (notifications) in a Signal class, i.e., not in a Object class.
  • Bernd will do that.

Action items (to be) moved:

Nigel Davis 19 May 2023 Provide Bernd with ONF Style converted script from Scott related to associations (See action from 2022-08-12).

Bernd Zeuner 02 Jun 2023 To create a sub-section 8.xx "Adding ExtendedComposite associations" in TR-515 Papyrus guidelines document. Is dependent on outcome of discussion on ITU-T vs. ONF Gendoc Style.

Done

Regarding how to clone a Git Repository identified by a Tag rather than a Branch, will the Papyrus Guidelines document be updated? to clarify that:

• It is enough to Check Out the required Tag, and the repository content identified by the Tag will be downloaded to the local project directory, replacing all previous content.
  • 
• Should this be documented in the Papyrus Guidelines?
  • Yes. Bernd will do that.

Post meeting note:

During the meeting the integer elementary type was discussed.

Andrea Mazzini confirms that

• the uml2yang tool version used by TAPI is not managing the stereotype OpenModelAttribute/unsigned boolean, always translating all integers into uint64 Yang type.
• the uml2yang tool version updated by Scott Mansfield correctly manages the stereotype.