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

2023-05-05 IISOMI Meeting Minutes

05 May 2023 Leader: Andrea; (Not available: Italo)

12 May 2023 Leader: Nigel; (Not available:)

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

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

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.

• See the Signal compartment in a class topic.

Action items moved:

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

Bernd Zeuner 26 May 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.

Scott Mansfield has asked to the folks he usually contact for questions re Papyrus, but without any answer.

• Clarified that the fact the folks did not answer does not necessarily imply that Papyrus devopment has stopped
  • in fact, Papyrus Releases shows recent deliveries.

• Andrea Mazzini shows that the signal compartment is not available in Eclipse 2019-09 / Papyrus 4.5.0:

• Right after the call Scott Mansfield emails the following screenshot of the 2020-06 version of Papyrus, clarifying that
  • Signals that are attached to a Class show up in the “nested classifiers” compartment.  So the compartment isn’t called signal, there is one compartment that is used for all “nested classifiers” of which signal is one.
    

The conclusion is that Eclipse 2019-09 / Papyrus 4.5.0 has apparently a bug, not showing the Signal in the compartment despite the tic to display the nested classifiers:

Reminded that:

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 

The publication site will be, as before, at https://opennetworking.org/software-defined-standards/models-apis/. 

Andrea Mazzini asks for a clarification regarding Papyrus, how to clone a Git Repository identified by a Tag rather than a Branch.

• Bernd Zeuner answers 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:

Maybe this clarification can be added to the Papyrus Guidelines.