Log (to be updated by Thérèse Lalor only)

Can we do an example like we have an example for quality?

Chris says he could have an example from Eurostat - Metadata Structure Definition.

Following agreements made:

** have to make changes with a good business case**

** not going to leave it as it is **

**balance of simple to understand and not leading down the wrong path **

--> Go to Sprint for elaboration

What is the outcome here? Is it a change or an acknowledgement?

depends on result of decision at #35

Input from Arofan and Chris given. Need a resolution based on that advice

depends on result of decision at #35

Channel Activity Specification, Channel Design Specification?

Relationship to Data Resource

Objects related to acquisition decided

Jenny has provided an improved definition.

Related to issue #31 and #7

unit data

dimensional data

We agree to the tenet of it and exact changes - in terms of relationships and definitions - to be worked out at sprint. We also need to tighten up all the definitions of dataset related objects.

GSIM should add a mention of Statistical Service either to the description or examples of a Business Service

Review text at Sprint to ensure alignment

16 Aug

Are we ready to resolve this? Is this something for GSIM version after this one?

Categorized as future work. Is this something other groups could solve? eg Data without Boundaries or Stats Network

 Action: fix the table....

Action: Change definition. Better explanatory text around this. 

Action: Rename instrument implementation to represented instrument. It has the advantage of linguistic consistency

#1

A new object will be added called Unit Type

Action: Definition, relationships and attributed need to be drafted

All subtypes of population will be removed

All subtypes of Unit will be remove

Node Sets

Code vs Code List

Category vs Category Set

Provide clearer explanation of the differences

Code is kept in the model with better explanation

Action: Text needs to be drafted from examples in discussion forum

#8

Change the diagrams to include Level in the next release.

Action: New diagrams to be created

22 Apr

Classification Scheme (Statistical Classification) has Mandatory Level

Action: Change the definition of (Statistical Classification) such that it must contain at least one Level.

(Statistical Classification) 1..* Level (Mandatory, Many)

Fixed in Neuchatel changes

Change according to proposal

Action:

Remove Classification Version from model

Remove Classification Variant from model

Change Classification to Classification Series

Change Classification Scheme to Statistical Classification

Revise relationships according to proposal

Add attributes according to proposal

Revise definitions

Business Service

Dissemination Service

Dissemination Service to be a subtype of Business Service

Action: Text needs to be drafted and attributes aligned

Information about how states of data "could be done" should go into the next version of the User Guide, rather than trying to fit into the model

Input to be given by countries using states of data may be done.

Action: Text needs to be drafted

Data Channel stays in model

Action: Review definition of Data Channel

Change name of Representation to Presentation

Action: Name changed in documentation and model

Example in glossary to be fixed (Proposal 1)

Action: Fix Example

 Remove all subtypes of Process Input

Remove all subtypes of Process Output

Definition to be improved

Action: Fix definition

No change to model required. Although perhaps clarification in text would help future users?

Action: clarification in text would help future users?