Meeting notes - March 22, 2023

[InKyungChoi]

Participants: Francine Kalonji, Flavio Rizzolo, Jenny Linnerud, Andrea Petres, Juan Munoz, Raul Mejia, Zoltan Vereczkei, Florian Vucko and InKyung Choi

Finalisation of Exchange Group

• Action: to change “Dissemination Component” to “Dissemination Instrument” to align better with its super-class name (“Exchange Instrument”)
• Action: to use “uses” between Information Structure and Output Specification
• Action: to remove “specifies” between Dissemination Instrument and Output Specification. Output Specification is about specification of Product, not Dissemination Instrument (specification of this is already covered by Exchange Specification). It is true that Dissemination Instrument has impact on the Output Specification (e.g., how we present data is affected by whether we use paper, mobile or web), but we cannot capture all dependencies in the model. This can be mentioned in the user-guide.

Finalisation of Structure Group

• Action: to use “collection of Data Points related to a given Unit or Population” for the definition, to use “….(as proposed in the github postl).. For the case of unit data, it can be structured by Logical Record” for the explanatory text
• Referential metadata area: will be made clearer after user-guide drafting

Finalisation of Business Group

• Action: to remove relationship between Process Pattern and Business Function. Process Pattern has at least one Process Design, and Process Design already specifies delivery of Business Function, so relationship between Process Pattern and Business Function is not needed.
• Action: to remove relationship between Change Definition and Population. No reason Population should be highlighted.
• Action: to keep the relationship between Business Process and Process Design. Business Process doesn’t have to have Process Step (optional), so we need to use this relationship (make it “specifies”) between Business Process and Process Design. Also, remove “implemented by” relationship between Process Design and Process Step (there is already “specifies” relationship between two).
• Action: to remove “has context of” relationship between Assessment and Subject Field.

Finalisation of Concept Group

• Category Item is an element in Category Set while Category Set is a list of Categories, shouldn’t Category Set be a list of Category Items? -> Category Item is a use of Category in a Category Set, rather than an element, you bring Category into a Category Set. The definition of Category Item and Category Set are circular (Category Set is a set of Categories and Category Item is an element of Category Set). Category Item should not be defined as an element in the set, taking Category and making it a part of a set, that is what makes it as an item.
• Action: to discuss about Category-Category Item-Category Set until 31st March
• Action: to let InKyung know if you disagree with any proposal made by Metadata Glossary task team from the UML list (otherwise they will be accepted).