Meeting notes Feb 22, 2023 #42

unece-stat · 2023-03-03T13:35:51Z

unece-stat
Mar 3, 2023
Maintainer

Participants: Francine Kalonji, Flavio Rizzolo, Jenny Linnerud, Andrea Petres, Juan Munoz, Raul Mejia, Christopher Jones

Action: To use GSIM classes Process Step and Process Control instead of “task” and “control logic” in the definition of new class Software Agent
Action: Not to make attribute "Type of Role", move it in the explanatory text (e.g., we can define controlled vocabulary for the type, e.g., RASCI, and maintain in the organisation)
Action: To name association between Change Event and Process Step “trigger”
Action: Not to add association between Role and Business Process. Role is not just for a process, it can be associated with, for example, Data Sets, Statistical Classification (e.g., Maintainer of Statistical Classification), we can pull that association from the existing association between Agent In Role and Identifiable Artefact (IA), we can think of how to do this more thoroughly later.
There are two Referential Metadata Subjects in the diagram
To close this issue

There are internal uses for Data Provider and Data Consumer, e.g., data hubs that maintain data sets internally and share them with downstream activities, Agents can play the role of consumer and provider internally.
Action: to accept the proposals from Flavio and to fix “Exchange Channel” in the explanatory text
To close this issue

Referential Metadata (RM) Subject itself is an information class. So when we instantiate, it becomes IA
Action: to move “refers to” association with IA from RM Subject to RM Subject Item. For example, RM Subject is Data Set and RM Subject Item is a particular (instantiated) Data Set. Question remains as to how we link it to GSIM objects, how do we say a certain GSIM class is the RM Subject, we need a place to write that down
Action: add an attribute to indicate that it is any information class
We can have RM Subject Item without having Subject, we can still get structure through the set.
Action: change cardinality RM Subject to RM Subject Item from 1 - 0..many to 0, 1 - 0..many.
To close this issue

Action: Not to remove the association between Business Process (and Statistical Program Design) and Business Service. If we delete, we need to delete the lower level, not higher level. We also still need a way of saying Business Service is associated with Business Process (without needing to have Process Steps).