New actions are added to the minutes of the current meeting and dated using the "task list" control
Do not copy actions from previous minutes, just add bullet version to reference the source minutes
In every IISOMI meeting, check the action item list and check for tasks that have passed their due date
If the due date is past, determine if the issue is still active
If the task is active, mark the over-due task as completed, and create a new task with a new due date in the minutes
If the task is not active, (i.e. not going to be progressed at this time), simply close the task and make a note in the minutes that the task was closed.
Action item discussed
Action item updates:(no changes to action, just changing date)
Extended Composite
_classB should not be defined in an ExtendedComposite association
Bernd Zeuner Update the Modelling Guidelines to cover "_classB should not be defined in an ExtendedComposite association (because it is abstract)."
Enum literal (propose allow 12.5GHz)
UML model guideline currently prevents "." (and other characters). This prevents "12.5GHz" from being an Enum literal.
Yang has exceptions to allow "well-known value" such as "Only lowercase letters, numbers, and dashes SHOULD be used in identifier names. Uppercase characters, the period character, and the underscore character MAY be used if the identifier represents a well-known value that uses these characters."
Scott noted that the tooling is not consistent. Some places the tooling converts to Yang format and in others it does not.
The tooling is not validating the UML naming convention.
Tooling does no translation of Enum Literals.
Changing the guidelines are sufficient.
Nigel suggested that a stereotype to identify the rare case where a well known value is being used should be available (not to be used by the tooling). This was not accepted.
Agreedto not change the tooling.
Agreedto proceed with Enum literals in upper case in Yang (i.e., not strict Yang, but still essentially allowed by "well-known value").
Agreedto not add a stereotype.
Agreedthat we would not follow RFC 8407 on the Enums.
Agreedto change the guideline rules to allow for well known terms to be used in the Enum name.
Bernd Zeuner Update the UML guidelines to reflect the agreements on Enum Literals.
3
30 min
Gendoc
Andrea
Is there a way to publish, in a tabular form, the stereotypes on associations?
For example, <<ExtendedComposite>> is used by the UML-Yang tool. There is no mechanism to publish this in the documentation (other than on the diagrams).
Property names etc. in UML comments not converted to Yang
Nigel
UML comments often include construct name formatted according to the UML guidelines. When the UML is converted to Yang the construct names are then incorrectly formatted.
Agreed that this is an issue.
It was suggested that:
The construct names be marked in some way so that tooling could identify the strings to convert. The marking could be two single quotes (e.g., ''xyz''), two curly brackets (e.g., {{xyz}}) or similar. The comment could be:
Processed by the UML-Yang tool
Post processed after Yang generation to generate a Yang with corrected comments
The reader will just have to deal with it
But a Yang reader will question the correctness of the comments
The construct names could be changed to be less rigorous, e.g., ConnectivityService becomes connectivity service (which is somewhere between the UML and Yang form (connectivity-service)
But both the UML reader and the Yang reader will question the correctness of the comments
Nigel Davis Further updates on issue of "UML comments often include construct name formatted according to the UML guidelines. When the UML is converted to Yang the construct names are then incorrectly formatted."
Editor's note: Papyrus should enable comments to include links to class names etc. via xmi-id that should be selectable from list etc.
3
10 min
Gendoc
Scott
June 11: Gendoc output for Interfaces and Operations
Reviewed the generatedInterface and Operationtable from Gendoc
Discussed table numbering
Table 1 Operation of AcAction
Table 1.1 Parameters for Operation createClientContext
Discussed case where there is no parameter
Still have table for operation which does not have parameter, with a row for heading and the second row with N/A
Discussed Interface meta data to be displayed in the GenDoc output
