The various categories of guidelines are described below.
These guidelines support SDMX design projects which follow the pattern shown in the diagram below.
This introductory document (February 2016 version) provides a general description of the various components of the SDMX Content-Oriented Guidelines, namely: cross-domain concepts, code lists, subject-matter domains, glossary, and implementation-specific guidelines. This material is made available to users to enhance and make more efficient the exchange of statistical data and metadata using the SDMX standard.
Cross-domain concepts in the SDMX framework describe concepts relevant to many, if not all, statistical domains. SDMX recommends using these concepts whenever feasible in SDMX structures and messages to promote the reuse and exchange of statistical information and related metadata between organisations. These cross-domain concepts can be found in the SDMX Glossary below (under attribute “Type: Cross-domain concept”).
Code lists are predefined sets of terms from which some statistical coded concepts take their values. SDMX cross-domain code lists are used to support cross-domain concepts. The use of common code lists will help users to work even more efficiently, easing the maintenance of and reducing the need for mapping systems and interfaces delivering data and metadata to them. Therefore, a choice over code lists has a great impact on the efficiency of data sharing.
Statistical subject-matter domains
A statistical subject-matter domain refers to a statistical activity that has common characteristics with respect to variables, concepts and methodologies for data collection and the whole statistical data compilation process. Examples of statistical domains are price statistics, national accounts, and environment or education statistics. The Classification of Statistical Subject-Matter Domains (January 2009 version) is based on the UN Economic Commission for Europe (UNECE) Classification of International Statistical Activities.
The SDMX Glossary Version 2.0 (published in October 2018) contains concepts and related definitions used in structural and reference metadata of international organisations and national data-producing agencies. This new version contains many new concept definitions which are coded so that they can be used as structural metadata in machine-to-machine statistical exchanges. All existing definitions have been reviewed with improvements to add to clarity and example use cases.
The SDMX Glossary recommends a common terminology that should be used in order to facilitate communication and understanding. The overall message of the SDMX Glossary is: if a term is used, then its precise meaning should correspond to the Glossary definition, and any reference to a particular phenomenon described in the Glossary should use the appropriate term.
Users interested in making direct links to specific terms in the Glossary (e.g. for citations, ease of navigation) are invited to use the html version of the Glossary. Let us assume that you want your users to be directly referred to the concept “Content-oriented guidelines (COG)” without them having to search the whole Glossary. Once the Glossary page is open, go through the table of contents until you spot the entry “Content-oriented guidelines (COG)”. You then have two options: a) if you do not want to check the content of the entry (because you already know that it is the concept you are interested in), just do a right-click and select “Copy link address” in Chrome browser, “Copy Link Location” in Netscape, Opera and Firefox browsers, “Copy shortcut” in Internet Explorer browser, or similar functionality in other browsers; b) if you want to check the content of the entry before taking any action, click on the link; you will then be redirected to the place in the document where the entry “Content-oriented guidelines (COG)” is defined; if the entry meets your needs, simply copy the URL displayed in the address bar of your browser and paste it in your document. In the case of the “Content-oriented guidelines (COG)”, the link will be the following: https://sdmx.org/wp-content/uploads/SDMX_Glossary_Version_2_0_October_2018.htm#_Toc529282104 (the segment “#_Toc529282104” is the part of the address that makes the concept directly referencable).
Please note that the SDMX Glossary is also available as a Cross-Domain Concept Scheme from the SDMX Registry.
- Governance of commonly used SDMX metadata artefacts
- Modelling Statistical Domains in SDMX
- Guidelines for representing methodological changes in Data Structure Definitions
- Guidelines for SDMX Data Structure Definitions
- Guidelines for the Creation and Management of SDMX Code Lists
- Guidelines on the Versioning of SDMX Artefacts
- Guidelines on Non-Calendar Year Reporting of Data
- Possible Ways of Implementing the Observation Status Concept
- Guidelines for Confidentiality and Embargo in SDMX
- Guidelines on coding time transformations in SDMX
- Guidelines for SDMX Concept Roles
- SDMX Global Registry Content Policy
Governance of commonly used SDMX metadata artefacts
The document “Governance of commonly used SDMX metadata artefacts” (Version 1.3, September 2018) describes the SDMX governance model and the governance principles of the artefacts. The latter also deal with maintenance issues related to these artefacts. These guidelines are the basis on which the SDMX standards are implemented in statistical domains.
Modelling Statistical Domains in SDMX (Back to Table of Contents)
The document “Modelling Statistical Domains in SDMX” (Version 2.0, June 2018) outlines general principles on how to design and create SDMX artefacts in a statistical domain, following a step-by-step approach to design based on the SDMX information model and, complementing the existing guidelines on Data Structure Definitions and Codelists.The document includes how to determine the number of Data Structure Definitions (DSDs) for a subject-matter domain and recommends that a decision on this should come after a discussion on all the parameters of the data collection exercise.
Guidelines for representing methodological changes in Data Structure Definitions (Back to Table of Contents)
The document “Guidelines for representing methodological changes in Data Structure Definitions” (Version 1.0, April 2019) provides recommendations on how to represent methodological changes for several use cases. When designing SDMX artefacts for an implementation project, one major design choice is the dimensionality of the Data Structure Definition(s), that is, which and how many dimensions are used to uniquely identify the relevant time series. Various trade-offs related to this design choice, such as between DSD complexity and parsimony, are discussed in the Modelling Guidelines. One aspect that is mentioned in the Modelling Guidelines, but not elaborated in detail, is the one of structural stability in case of methodological changes. In other words, how future-proof is the DSD? How many and what kind of changes to the DSD are required when certain aspects of the underlying data change and the DSD needs to represent both, pre-change and post-change data, in different time series? If certain future changes are already expected when the DSD is originally designed, dimensions (or attributes) covering these changes will be included in the DSD. If the DSD was designed without expecting changes, additional dimensions or attributes will have to be introduced at a later stage.
Guidelines for SDMX Data Structure Definitions (Back to Table of Contents)
The development of SDMX Data Structure Definitions in many statistical domains raised the need for guidance on the design of DSDs. The SDMX initiative now releases such guidelines based on conceptual considerations and first hand experiences with the development of DSDs. The document “Guidelines for SDMX Data Structure Definitions” (Version 1.0, June 2013) outlines general design principles for DSDs such as reuse of existing concepts and code lists, and principles such as keeping the DSDs simple. The guidelines describe the different uses of DSDs, based on different user needs. And discuss the advantages and disadvantages of data structures in different domains. They provide context-specific recommendations instead of prescribing “the best” one-size-fits-all approach. For DSD designers, a step-by-step guide for designing DSDs is also included.
Guidelines for the Creation and Management of SDMX Code Lists (Back to Table of Contents)
The document “Guidelines for the creation and Management of SDMX Code Lists” (Version 3.0, 19 January 2018) is intended to support the creation of code lists to be used all along the statistical business process, in particular when SDMX is implemented in statistical domains. They are strongly recommended when SDMX-compliant data structure definitions (DSDs) are built-up and implemented in statistical domains.
Guidelines on the Versioning of SDMX Artefacts (Back to Table of Contents)
The “Guidelines on the Versioning of SDMX Artefacts” (Version 1.0, November 2015) provide recommendations on how to version SDMX artefacts inspired by “semantic versioning”, i.e. a formal convention for specifying compatibility between the different versions of a “versionable” artefact (a SDMX artefact that has an associated version number). Versioning is central to SDMX because it guarantees the stability of references to SDMX artefacts. This is of the utmost importance given the sometimes strong dependencies between artefacts, especially in Data Structure Definitions (DSDs). The document contains three main recommendations: a) numbering system and syntax; b) types of artefact changes and their versioning impact; c) how versioning works for inter-dependent artefacts. The document’s appendix contains examples of several types of changes and their versioning impact.
Guidelines on Non-Calendar Year Reporting of Data (Back to Table of Contents)
In many cases, data that are exchanged in SDMX data messages do not relate to the calendar year. However, many statistical system implementations require that data are mapped to and stored as the real calendar. The document “Guidelines on Non-Calendar Year Reporting of Data” (Version 1.0, November 2016) provides recommendations for four use cases of such non-calendar year data: a) Reporting year is equal to the calendar year; b) Reporting year starts on the first day of a month different to January; c) Reporting year starts on a given day in the year, and d) Reporting year ends on a given day in the year.
Possible Ways of Implementing the Observation Status Concept (Back to Table of Contents)
The “Observation status” code list has a heterogeneous character as it mixes concepts which are not always mutually exclusive (e.g. a missing value can generate a break in time series). This means that several flags can be allocated to one statistical observation. The document “Possible Ways of Implementing the Observation Status Concept” (Version 2.0, May 2019) describes the possible options for doing that, including the recommended solution, and explains their advantages and disadvantages.
Guidelines for Confidentiality and Embargo in SDMX (Back to Table of Contents)
The “Guidelines for Confidentiality and Embargo in SDMX” (Version 2.0, 19 January 2018) cover the confidentiality aspects in SDMX data exchange, including embargo scenarios. The aim is to provide a consistent and practical way to represent these aspects in SDMX artefacts in order to promote cross-domain consistency and harmonise methodology and processes. The paper presents the use case scenarios related to confidentiality and embargo. Based on the use cases, recommendations are provided on how to represent both elements in the SDMX model.
Guidelines on coding time transformations in SDMX(Back to Table of Contents)
The “Guidelines on coding time transformations in SDMX” (Version 1.0, September 2016) describe two methods that may be used to code a time transformation, defined as a time-related operation performed on a time series, solely involving observations of that time series. Examples of such time transformations are growth rates, cumulative sums over several periods and moving averages. Both of the methods described in the guideline are included as separate use cases. The aim of this document is to demonstrate that guidance and a standard approach is available and promoted for each use case.
Guidelines for SDMX Concept Roles(Back to Table of Contents)
The document “Guidelines for SDMX Concept Roles” (Version 1.0, February 2019) describes SDMX Concept Roles and their use, proposes a cross-domain Concept scheme that defines the set of concept roles (for SDMX 2.1), and gives examples on concept role implementation in both SDMX 2.0 and SDMX 2.1. A concept role gives a particular context to a concept for easy and systematic interpretation by machine processing and visualization tools. For example, the concepts REPORTING_AREA and COUNTERPART_AREA are different concepts but they are both geographical characteristics, therefore they can be associated with the same concept role ID: “GEO”. This allows visualization systems to interpret these concepts as geographical data in order to generate maps. The implementation of concept roles is different in versions 2.0 and 2.1 of the SDMX technical standard. Examples for both versions are included in the appendix. The Concept Roles are available as an SDMX Concept Scheme from the SDMX Global Registry.
SDMX Global Registry Content Policy (Back to Table of Contents)
The document “SDMX Global Registry Content Policy” (Version 1.0, March 2015) proposes a policy for artefacts stored, maintained and disseminated from the SDMX global registry (GR). Defining precisely which artefacts should go into the GR and which ones should not is crucial as the GR will play a central role in providing SDMX implementers with final, reliable, up-to-date, harmonised and validated SDMX artefacts.
This webpage is maintained by the SDMX Statistical Working Group (SWG), comprised of 20 members coming from national and international banking and statistical organisations.
Contact address: firstname.lastname@example.org