Changes for page Guidelines on the Versioning of SDMX Artefacts

Last modified by Artur K. on 2026/05/29 14:28

From 1.9 to 1.8 From 1.12 to 1.11

From version 1.11

edited by Helena K.
on 2026/01/15 15:16

Change comment: There is no comment for this version

To version 1.9

edited by Helena K.
on 2026/01/15 15:12

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -142,25 +142,29 @@
  ==== b. Addition or removal of referenced artefacts ====
--|(% colspan="3" style="width:876px" %)**CONCEPT SCHEME (CS)**
--|(% style="width:845px" %)**Type of change**|(% style="width:156px" %)**Impact**|(% style="width:1071px" %)**Comments**
--|(% style="width:845px" %)(((
--**Addition or removal of a child Code List**
--)))|(% style="width:156px" %)**Minor: N.+**|(% style="width:1071px" %)The child Code Lists in a Data Structure Definition have priority over those referenced in a Concept Scheme. Child Code Lists added to or removed from a Concept Scheme do not have a direct impact on the data exchange. Backward/forward compatibility depends on the way Code Lists are referenced in Data Structure Definitions referencing the concept scheme. This needs to be taken into account when creating a new version of a DSD accordingly
++| |(% colspan="2" %)**CONCEPT SCHEME (CS)**
++|**Type of change**|**Impact**|**Comments**
++|(((
++**Addition or removal of a child**
++**Code List**
++)))|**Minor: N.+**|The child Code Lists in a Data Structure Definition have priority over those referenced in a Concept Scheme. Child Code Lists added to or removed from a Concept Scheme do not have a direct impact on the data exchange. Backward/forward compatibility depends on the way Code Lists are referenced in Data Structure Definitions referencing the concept scheme. This needs to be taken into account when creating a new version of a DSD accordingly
--|(% colspan="3" %)**DATA STRUCTURE DEFINITION (DSD)**
++
++| |(% colspan="2" %)**DATA STRUCTURE DEFINITION (DSD)**
  |**Type of change**|**Impact**|**Comments**
  |**Addition or removal of a child Code List**|(((
--**If same id and Agency, then the child artefact version change is replicated in the parent artefact.
--If different id or Agency, impact wil depend on the backward/forward compatibility as shown in the tables above**
++**If same id and Agency, then the child artefact version change is replicated in the parent artefact.**
++
++**If different id or Agency, impact wil depend on the backward/forward compatibility as shown in the tables above**
  )))|(((
  If a child Code List has a minor version change, then the DSD should also have a minor version change.
++
  If there are several Code List version changes, the most severe impact is replicated in the DSD. For example, if two Code Lists have minor changes, and one Code List has a major change at the same time, the parent DSD has a major version change
  )))
--= 6. Appendix - Examples =
++=== 6. Appendix - Examples ===
  **Example 1 – Change to a Code List name, for clarification purposes**. **Patch Impact: N.M.+**
@@ -181,18 +181,21 @@
  |(% colspan="2" %)**AGGREGATION OF EXISTING CODES**
  |**Old version**|**New version**
--|**2011** Heifers (female bovine that never calved), live
--**2012** Cows, live|**2010** Heifers and cows, live
--|(% colspan="2" %)Codes **2011** and **2012** are fully{{footnote}}i.e. without integration into or combination with another existing code.{{/footnote}} __**removed**__ and replaced with one __**brand new**__ code. In this case there is a many to 1 correspondence between the codes.
++|**2011** Heifers (female bovine that never calved), live **2012** Cows, live|**2010** Heifers and cows, live
++|(% colspan="2" %)Codes **2011** and **2012** are fully{{footnote}}i.e. without integration into or combination with another existing code.{{/footnote}} **removed** and replaced with one **brand new** code. In this case there is a many to 1 correspondence between the codes.
++
++
  |(% colspan="2" %)**DISAGGREGATION OF EXISTING CODES**
  |**Old version**|**New version**
  |**1010** Live horses|(((
--1011 Pure bred breeding horses, live
--1012 Other horses, live
++1. Pure bred breeding horses, live
++1. Other horses, live
  )))
--|(% colspan="2" %)Code __**1010**__ is fully __**removed**__ and replaced with two __**brand new**__ codes. In this case there is a 1 to m correspondence between the codes.
++|(% colspan="2" %)Code **1010** is fully **removed** and replaced with two **brand new** codes. In this case there is a 1 to m correspondence between the codes.
++
++
  |(% colspan="2" %)**REORGANISATION OF EXISTING CODES**
  |**Old version**|**New version**
  |(((
@@ -214,8 +214,7 @@
  |(% colspan="2" %)**ADDING A NEW CODE IN AN EXISTING HIERARCHY – CODE LIST**
  |**Old version**|**New version**
--|• 0213 - Beer o02131 - Lager beer o02132 - Other alcoholic beer|0213 - Beer o02131 - Lager beer o 02132 - Other alcoholic beer
--**02133 - Low and non-alcoholic beer**
++|• 0213 - Beer o02131 - Lager beer o02132 - Other alcoholic beer|• 0213 - Beer o02131 - Lager beer o 02132 - Other alcoholic beer o **02133 - Low and non-alcoholic beer**
  |(% colspan="2" %)Code 02133 has been added to hierarchy 0213
  **Example 6 – Changes to hierarchies in a Hierarchical Code List. Major impact: +.0**
@@ -223,17 +223,17 @@
  |(% colspan="2" %)**ADDING A NEW CODE IN AN EXISTING HIERARCHY – HIERARCHICAL CODE LIST**
  |**Old version**|**New version**
  |(((
-- A1 - World (codelist ref. ECB@CL_AREAS@1.0) o E1 - Europe (ECB@CL_COUNTRIES@1.0)
++• A1 - World (codelist ref. ECB@CL_AREAS@1.0) o E1 - Europe (ECB@CL_COUNTRIES@1.0)
--ES - Spain FR - France
++ ES - Spain FR - France
  GR - Greece
  IT - Italy o E4 - Africaetc.
  )))|(((
--A1=World (codelist ref. ECB@CL_AREAS@1.0) o E1 =Europe (ECB@CL_COUNTRIES@1.0)
++• A1=World (codelist ref. ECB@CL_AREAS@1.0) o E1 =Europe (ECB@CL_COUNTRIES@1.0)
--ES = Spain FR = FranceGR = Greece
++ ES = Spain FR = FranceGR = Greece
  IT = Italy