Use case: Statistical compendium

[ChLaaboudi]

The Statistical Compendium is a reference tool for producers of official statistics. The Compendium is organised by Statistical Subject Areas, derived from the CSA (Classification of Statistical Activities). Each subject area is described with the following components:

• Legal Basis
• List of Statistical products (datasets)
• Methodologies
• International cooperation
• Responsible Unit

For some section, a dataset exists (Yellow Circle in the picture).

The Use Case will consist of representing a Statistical Subject Area linked with its components.

[flo7894]

@ChLaaboudi in coos there are classes that could represent datasets and organisations. Legal basis and methodologies could be documents (prov:entity) that would be produced by activities that would probably fall under corporate support or strategy and leadership of GAMSO. how would you model the subject area, some kind of statistical activity area ?

[ChLaaboudi]

@flo7894 Statistical Activity Areas can be modelled in SKOS/XKOS. In XKOS, specifies the coverage of a classification. We could have a similar property in coos that specifies the domain coverage for a methodology, legal act, dataset, organisation.

[ChLaaboudi]

Hi @flo7894, When you'll have time, may I ask you to add the conclusions of our meeting from 19/05? Thanks a lot, Christine

[flo7894]

• Each section of the statistical compendium may be represented as a coos:StatisticalProgram. In some cases there might be several programs for a section.
• Subject Area : This can be seen as the GSIM SubjectField for the coos:StatisticalProgam defined above. Eurostat has a skos:ConceptScheme for the CSA that can be reused. The property to link does not yet exist ( in GSIM: has context of)
• Responsible unit : This can be linked to the program with the generic property prov:wasAttributedTo. Eurostat has a skos:ConceptScheme reprensenting its internal units that can be reused. (the concepts in this concept scheme are also prov:Organization)
• DataSets : Eurostat has a skos:ConceptScheme for the datasets, they might also be typed as coos:Dataset. Some information about datasets found the compendium can be expressed with dcat (e.g. periodicity). Datasets are input of the program and provided by member’s state, both these informations can be expressed with prov properties

• International cooperation : This can also be linked to the program with prov:wasAssociatedWith. To differentiate the roles between responsable unit and international cooperation some prov:Association could be introduced.

[ChLaaboudi]

Thanks @flo7894 for the update.

About Subject Area : CSA. If Eurostat implements the CSA as a ConceptScheme, the resources will be defined in the namespace data.europa.eu. It will be more relevant if the namespace is defined in the COOS, UNECE or UNSD domain.

Responsible Unit: see dataset https://showvoc.op.europa.eu/#/datasets/ESTAT_Statistical_Organisations_Unit/data

In your schema, references to the Legal basis or Methodology are missing.

[flo7894]

Eurostat has a skos:ConceptScheme for Legal Acts and one for Methodologies. In GSIM revision a class has been introduced "Reference Documents". In issue #78 there is a proposition to introduce a property coos:informs. With these we could represent Legal Acts and Methodologies at the program level or dataset level

It is also possible with prov using a prov:Association

[InKyungChoi]

If GSIM class "Reference Document" is to be added in COOS, GSIM currently has following definition and explanatory text:

• definition: documents that are used to support, inform and guide the business processes
• explanatory text: The examples of Reference Documents include: methodological handbooks, standards, legislation, corporate policies/guideline and best practices. Reference Documents are often unstructured and can be translated into Rules (e.g., quality requirements set by legislation can be written as a Rule). Note that documents can be physical (e.g., books) or electronical. The documents can be formal in terms of content (e.g., laws) or in terms of format (e.g., XML).

which is in line with Florian's diagram above

[FranckCo]

Following 9/7 meeting: Florian to write a "COOS use case" document summarizing use case and proposed solution.