Meeting notes -January 11, 2023

[InKyungChoi]

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

Issue #17 Registers in statistical production: their roles and types, and how to model them in GSIM

• Final definition and explanatory text are proposed.
• Current relationship we have with Register (“has” relationship with Information Set) is enough for now (don’t want to go into details yet)
• Action: To add an example of using Register for administrative register (current examples are all for statistical register)
• Action: to record as a backlog of the case where administrative data that are collected for statistical purposes but are not registers.

Issue #10 GSIM Implementation Guide

• GSIM Specification (last updated in 2013) is still valid and contains examples we want for the user guide (detailed explanation for classes with examples) => Jenny, Flavio and InKyung to work on together.
• Implementation guide (how to go from conceptual model to implementation model) is still missing
• A reader guide (different user groups need different documents, some documents might be too technical) => to create a simple table mapping documents and target audience
• Communication paper might need some updates, but would be minimal
• Design principle of GSIM: we need to bring this up front again. They are robust against time, it is very important as they guide GSIM and understand the rationale
• Other documents needed: glossary, EA file, clickable
• Decision: new version will be numbered as GSIM 2.0

Issue #6 Missing GSIM class – quality indicators

• No action yet, InKyung to create a sub-group

Issue #31 GSIM Exchange Group definition / explanatory text update

• Currently, Information Consumer is defined as "Agent that consumes data" but model says it is a sub-type of Role (not Agent which definition seems to suggest). We need to fix either definition or model
• If Maintainer is a sub-type of Role, should its name be written as more like responsibility rather than Agent (e.g., "Maintaining"?)
• Also, current model says Information Consumer “agrees to Provision Agreement”, so it seems they are an Agent (or at least Agent In Role) as Role does not agree to Provision Agreement
• Having various sub-types of Role is important because Agent can play different Roles
• If we want to keep Information Provider as sub-types of Role, we need to change the association as passive (currently it is active "agrees to")