1. Agenda Item 3.3 - SDMX 2.1 for LCI - Denis.Leythienne@ec.europa.eu
LAMAS October 2017
Agenda Item 3.3
- SDMX 2.1 for LCI -

2. OUTLINE
I. Background II. State of play III. SDMX 2.1 IV. Implementation V. STRUVAL (Structural Validation) VI. Proposal

3. I. Background - SDMX, the new standard for data transmissions …
- Promotes the use of common "dictionnaries" …
i.e. dimensions and code lists
- Across NSIs and international organisations …
- Being updated by the owning institution …
e.g. Estat, IMF, ECB
- But accessible by all stakeholders through the
SDMX Registry

4. II. State of play
- All countries except Turkey and Serbia use SDMX 2.0
- Still some errors detected:
in both indices and weights (CZ, DK, EE, LV, MT and NO)
in indices only (BE, HR, NL, RO and FI)
in weights only (LU)
- That may delay the production process
=> It will be soon possible to check SDMX syntax through the STRUVAL (Structural Validation)

5. III. SDMX 2.1 Reasons for the SDMX 2.0 => SDMX 2.1 upgrade:
- Harmonisation at international level
(e.g. UNIT_MEASURE instead of 'UNIT')
- Need expressed by our main institutional user (ECB)
- Opportunity to improve the definitions provided in
the guidelines

6. III. SDMX 2.1 Very limited changes: - 1 Dimension: CL_ADJUSTMENT
(changed to include "_Z")
- 3 Attributes:
UNIT_MEASURE (changed)
EMBARGO_TIME (added)
BASE_PER (changed)

7. III. SDMX 2.1 Also an opportunity:
- To improve definitions (see guidelines)
- To enable the transmission of Labour Cost Levels
data in SDMX (AT, DK, ES, FR, HU, NL, RO and CZ)
- By including the corresponding indicators:
HLC_O, HLC_T, HLC_TXB and HLC_WAG

8. IV. Implementation
- October 2017: SDMX 2.1 in test for LCI (2017Q2) - December 2017: SDMX 2.1 in prod. for LCI (2017Q3)

9. IV. Implementation
- January 2018: SDMX 2.1 in test for Labour Cost Levels estimates (AT, DK, ES, FR, HU, NL, RO and CZ) - 23 March 2018: SDMX 2.1 in prod. for Labour Cost Levels estimates (AT, DK, ES, FR, HU, NL, RO and CZ) - From April 2018 onwards: SDMX 2.1 in prod. for weights

10. V. STRUVAL (Structural Validation)
No error, no warning
A few minutes after data transmission
An error report will be delivered to the data sender
A warning report will be delivered to the concerned actor (data sender or data receiver)
Compliance to DSDs and DSDs restrictions. Examples:
Activity code must be a valid code listed in the DSD.
Confidentiality flag (conf_status) must be one of the values listed in the restriction list.

11. V. STRUVAL (Structural Validation)
Validation of the data transmissions (feedback received in EDAMIS)
A validation report is made available over the EDAMIS feedback mechanism to the sender of the SDMX-ML file.
The structure of SDMX-ML files (file with the extension .xml) is validated :
- against the data structure definition (DSD)
- against the dataflow specific constraints, e.g. CR_LCI_WEIGHT_A (see "Cube Regions" in the Euros SDMX Registry: for acceptable values)

12. V. STRUVAL (Structural Validation)
Errors (blocking issues)
Warnings (issues to be further analysed)

13. VI. Proposal LAMAS is invited to take note of / comment on:
- The (limited) changes introduced in SDMX 2.1
compared with SDMX 2.0;
- The proposal to test SDMX2.1 transmissions this month
(for LCI) and in January 2018 (for labour costs levels);
- The proposal to use SDMX2.1 in production from ref.
quarter 2017Q3 (for LCI); ref. year 2017 (for labour
cost levels estimates) and from April 2018 for weights.