Changes for page Guidelines on the Versioning of SDMX Artefacts

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

From 1.5 to 1.4 From 1.11 to 1.10

From version 1.10

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

Change comment: There is no comment for this version

To version 1.5

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -63,48 +63,56 @@
  As a general rule insignificant changes (e.g. textual clarifications or typos) will result in an increment of the patch component of the versioning system (i.e. N.M.**+**).
  |(% colspan="3" %)**CODE LIST (CL)**
--|(% style="width:877px" %)**Type of Change**|(% style="width:161px" %)**Impact**|(% style="width:1034px" %)**Comments**
--|(% style="width:877px" %)(((
++|(% style="width:942px" %)**Type of Change**|(% style="width:165px" %)**Impact**|**Comments**
++|(% style="width:942px" %)(((
  **Addition into an existing CL of one or more new codes not having the**
  **CodeList:Code:ParentCode attribute**
--)))|(% style="width:161px" %)**Minor**: **N.,,+,,**^^({{footnote}}The overall impact on compatibility should be assessed when there are several “minor” version impact changes. For example, it may be that the effect of adding several new Code List or HCL codes results in an implicit change in the meaning of existing Code List or HCL codes which may not be completely backward compatible, therefore (depending on the analysis) the overall version impact may be “Major +.0”.{{/footnote}})^^|(% style="width:1034px" %)Data exchanged/disseminated using the old CL can still be exchanged/disseminated using the new CL
--|(% style="width:877px" %)(((
++)))|(% style="width:165px" %)**Minor**: **N.,,+,,**^^({{footnote}}The overall impact on compatibility should be assessed when there are several “minor” version impact changes. For example, it may be that the effect of adding several new Code List or HCL codes results in an implicit change in the meaning of existing Code List or HCL codes which may not be completely backward compatible, therefore (depending on the analysis) the overall version impact may be “Major +.0”.{{/footnote}})^^|Data exchanged/disseminated using the old CL can still be exchanged/disseminated using the new CL
++|(% style="width:942px" %)(((
  **Addition of one or more new hierarchies represented using the**
  **CodeList:Code:ParentCode attribute (not using the Hierarchical Code List artefact)**
--)))|(% style="width:161px" %)**Minor**: **N.,,+,,^^(^^**^^{{footnote}}The overall impact on compatibility should be assessed when there are several “minor” version impact changes. For example, it may be that the effect of adding several new Code List or HCL codes results in an implicit change in the meaning of existing Code List or HCL codes which may not be completely backward compatible, therefore (depending on the analysis) the overall version impact may be “Major +.0”.{{/footnote}})^^|(% style="width:1034px" %)Data exchanged/disseminated using the old CL can still be exchanged/disseminated using the new CL as already existing hierarchies still represent the same aggregations
--|(% style="width:877px" %)**Addition of one or more new codes into existing hierarchies represented using the CodeList:Code:ParentCode attribute (not using the Hierarchical Code List artefact)**|(% style="width:161px" %)**Major**: **+.0**|(% style="width:1034px" %)After the change, the parent code for the changed hierarchy does not represent the same aggregation any more, thus resulting in a break in backward compatibility
--|(% style="width:877px" %)**Aggregation, disaggregation, reorganisation or removal of one or more codes**|(% style="width:161px" %)**Major**: **+.0**|(% style="width:1034px" %)Data exchanged/disseminated using an old version of the CL can no longer be exchanged/disseminated using the new version of the CL
++)))|(% style="width:165px" %)**Minor**: **N.,,+,,^^(^^**^^{{footnote}}The overall impact on compatibility should be assessed when there are several “minor” version impact changes. For example, it may be that the effect of adding several new Code List or HCL codes results in an implicit change in the meaning of existing Code List or HCL codes which may not be completely backward compatible, therefore (depending on the analysis) the overall version impact may be “Major +.0”.{{/footnote}})^^|Data exchanged/disseminated using the old CL can still be exchanged/disseminated using the new CL as already existing hierarchies still represent the same aggregations
++|(% style="width:942px" %)**Addition of one or more new codes into existing hierarchies represented using the CodeList:Code:ParentCode attribute (not using the Hierarchical Code List artefact)**|(% style="width:165px" %)**Major**: **+.0**|After the change, the parent code for the changed hierarchy does not represent the same aggregation any more, thus resulting in a break in backward compatibility
++|(% style="width:942px" %)**Aggregation, disaggregation, reorganisation or removal of one or more codes**|(% style="width:165px" %)**Major**: **+.0**|Data exchanged/disseminated using an old version of the CL can no longer be exchanged/disseminated using the new version of the CL
  |(% colspan="3" %)**HIERARCHICAL CODE LIST (HCL)**
--|**Type of Change**|(% style="width:150px" %)**Impact**|(% style="width:1045px" %)**Comments**
++|**Type of Change**|**Impact**|**Comments**
  |(((
--**Addition of new hierarchies in the HCL. Existing hierarchies are unaffected**
--)))|(% style="width:150px" %)**Minor**: **N.,,+,,**^^({{footnote}}The overall impact on compatibility should be assessed when there are several “minor” version impact changes. For example, it may be that the effect of adding several new Code List or HCL codes results in an implicit change in the meaning of existing Code List or HCL codes which may not be completely backward compatible, therefore (depending on the analysis) the overall version impact may be “Major +.0”.{{/footnote}})^^|(% style="width:1045px" %)Data represented using the old HCL can still be represented using the new HCL
--|**Addition of codes into existing hierarchies in the HCL. Existing hierarchies are thus affected**|(% style="width:150px" %)**Major**: **+.0**|(% style="width:1045px" %)The HCL resulting from this change does not represent the same aggregation any more, thus breaking backward compatibility
--|**Removal of one or more codes in the HCL or removal of one or more codes in the referenced code lists**|(% style="width:150px" %)**Major**: **+.0**|(% style="width:1045px" %)Data represented using the old HCL can no longer be represented using the new HCL, thus resulting in a break in backward compatibility
--|**Addition, modification or removal of one or more hierarchical levels**|(% style="width:150px" %)**Major: +.0**|(% style="width:1045px" %)The reorganisation of codes within hierarchies has a significant impact on the code aggregations
++**Addition of new hierarchies in the HCL.**
++**Existing hierarchies are unaffected**
++)))|**Minor**: **N.,,+,,**^^(3)^^|Data represented using the old HCL can still be represented using the new HCL
++|**Addition of codes into existing hierarchies in the HCL. Existing hierarchies are thus affected**|**Major**: **+.0**|The HCL resulting from this change does not represent the same aggregation any more, thus breaking backward compatibility
++|**Removal of one or more codes in the HCL or removal of one or more codes in the referenced code lists**|**Major**: **+.0**|Data represented using the old HCL can no longer be represented using the new HCL, thus resulting in a break in backward compatibility
++|**Addition, modification or removal of one or more hierarchical levels**|**Major: +.0**|The reorganisation of codes within hierarchies has a significant impact on the code aggregations
++
++
++
  |(% colspan="3" %)**CONCEPT SCHEME (CS)**
--|(% style="width:874px" %)**Type of change**|(% style="width:154px" %)**Impact**|(% style="width:1044px" %)**Comments**
--|(% style="width:874px" %)**Addition of one or more new concepts in an existing CS**|(% style="width:154px" %)**Minor**: **N.+**|(% style="width:1044px" %)(((
--Data exchanged/disseminated using the old version of the CS can still be exchanged/disseminated using the new CS
++|**Type of change**|**Impact**|**Comments**
++|**Addition of one or more new concepts in an existing CS**|**Minor**: **N.+**|(((
++Data exchanged/disseminated using the old version of the
++
++CS can still be exchanged/disseminated using the new CS
  )))
--|(% style="width:874px" %)**Removal of one or more existing concepts**|(% style="width:154px" %)**Major: +.0**|(% style="width:1044px" %)Data exchanged/disseminated using the old version of the CS can no longer be exchanged/disseminated using the new version with less concepts
++|**Removal of one or more existing concepts**|**Major: +.0**|Data exchanged/disseminated using the old version of the CS can no longer be exchanged/disseminated using the new version with less concepts
++
++
  |(% colspan="3" %)**DATA STRUCTURE DEFINITION (DSD)**
--|(% style="width:868px" %)**Type of change**|(% style="width:159px" %)**Impact**|(% style="width:1045px" %)**Comments**
--|(% style="width:868px" %)**Addition of a dimension**|(% style="width:159px" %)**Major**: **+.0**|(% style="width:1045px" %)Adding a new dimension has a strong impact because a dimension represents the identifier of a dataset, thus requiring a remodelling of the data as existing structural validation will fail
--|(% style="width:868px" %)**Addition of a mandatory attribute**|(% style="width:159px" %)**Major**: **+.0**|(% style="width:1045px" %)If the attribute is mandatory, the situation is the same as under point “Addition of a dimension”
--|(% style="width:868px" %)**Addition of a conditional attribute**|(% style="width:159px" %)**Minor**: **N.+**|(% style="width:1045px" %)If the attribute is conditional backward compatibility is maintained
--|(% style="width:868px" %)**Removal of a dimension or attribute**|(% style="width:159px" %)**Major**: **+.0**|(% style="width:1045px" %)Whatever the type of component, the change does not guarantee backward compatibility
++|**Type of change**|**Impact**|**Comments**
++|**Addition of a dimension**|**Major**: **+.0**|Adding a new dimension has a strong impact because a dimension represents the identifier of a dataset, thus requiring a remodelling of the data as existing structural validation will fail
++|**Addition of a mandatory attribute**|**Major**: **+.0**|If the attribute is mandatory, the situation is the same as under point “Addition of a dimension”
++|**Addition of a conditional attribute**|**Minor**: **N.+**|If the attribute is conditional backward compatibility is maintained
++|**Removal of a dimension or attribute**|**Major**: **+.0**|Whatever the type of component, the change does not guarantee backward compatibility
  For concrete examples, see the Appendix.
--= 5. How versioning works for inter-dependent artefacts =
++=== 5. How versioning works for inter-dependent artefacts ===
  This section describes how version changes to inter-dependent or parent/child artefacts affect each other. For example, how a Concept Scheme is affected when one of the Code Lists that it references changes version.
@@ -127,40 +127,51 @@
  The replacement of a reference with a different reference has the same impact for every artefact.
  |(% colspan="3" %)**ALL ARTEFACTS**
--|(% style="width:492px" %)**Type of change**|(% style="width:441px" %)**Impact**|**Comments**
--|(% style="width:492px" %)(((
--**Replacement of a child artefact having a different version, but same id and Agency**
--)))|(% style="width:441px" %)(((
--**The child artefact version change is replicated in the parent artefact**
++|**Type of change**|**Impact**|**Comments**
++|(((
++**Replacement of a child artefact having a different version, but same id and**
++
++**Agency**
  )))|(((
++**The child artefact version change is replicated in the**
++
++**parent artefact**
++)))|(((
  If a child artefact (e.g. a Code List) has a minor version change, then the parent artefact (e.g. a Concept Scheme) should also have a minor version change.
++
  If there are several child artefact version changes, the most severe impact is replicated in the parent artefact. For example, if two Code Lists have minor changes, and one Code List has a major change at the same time, the parent Concept Scheme has a major version change
  )))
--|(% style="width:492px" %)(((
--**Replacement of a referenced child artefact having a different id or Agency**
--)))|(% style="width:441px" %)**The parent artefact version impact depends on the backward/ forward compatibility as shown in the tables above**|Technically, the child artefact is not considered to be related to the previous child artefact. It needs to be checked whether exchange contracts can still be guaranteed (backward/forward compatibility principle)
++|(((
++**Replacement of a referenced child artefact having a**
++**different id or Agency**
++)))|**The parent artefact version impact depends on the backward/ forward compatibility as shown in the tables above**|Technically, the child artefact is not considered to be related to the previous child artefact. It needs to be checked whether exchange contracts can still be guaranteed (backward/forward compatibility principle)
++
  ==== 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.+**
@@ -182,8 +182,10 @@
  |(% 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.
++|(% 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|(((
@@ -190,8 +190,10 @@
 . Pure bred breeding horses, live
 . 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**
  |(((
@@ -221,17 +221,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