Skip to Content
Last modified by Artur K. on 2026/05/29 14:28
From version 1.9
edited by Helena K.
on 2026/01/15 15:12
Change comment: There is no comment for this version
To version 1.6
edited by Helena K.
on 2026/01/15 15:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -88,23 +88,29 @@
88 88  |**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
89 89  |**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
90 90  
91 +
92 +
91 91  |(% colspan="3" %)**CONCEPT SCHEME (CS)**
92 -|(% style="width:874px" %)**Type of change**|(% style="width:154px" %)**Impact**|(% style="width:1044px" %)**Comments**
93 -|(% style="width:874px" %)**Addition of one or more new concepts in an existing CS**|(% style="width:154px" %)**Minor**: **N.+**|(% style="width:1044px" %)(((
94 -Data exchanged/disseminated using the old version of the CS can still be exchanged/disseminated using the new CS
94 +|**Type of change**|**Impact**|**Comments**
95 +|**Addition of one or more new concepts in an existing CS**|**Minor**: **N.+**|(((
96 +Data exchanged/disseminated using the old version of the
97 +
98 +CS can still be exchanged/disseminated using the new CS
95 95  )))
96 -|(% 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
100 +|**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
97 97  
102 +
103 +
98 98  |(% colspan="3" %)**DATA STRUCTURE DEFINITION (DSD)**
99 -|(% style="width:868px" %)**Type of change**|(% style="width:159px" %)**Impact**|(% style="width:1045px" %)**Comments**
100 -|(% 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
101 -|(% 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”
102 -|(% 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
103 -|(% 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
105 +|**Type of change**|**Impact**|**Comments**
106 +|**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
107 +|**Addition of a mandatory attribute**|**Major**: **+.0**|If the attribute is mandatory, the situation is the same as under point “Addition of a dimension”
108 +|**Addition of a conditional attribute**|**Minor**: **N.+**|If the attribute is conditional backward compatibility is maintained
109 +|**Removal of a dimension or attribute**|**Major**: **+.0**|Whatever the type of component, the change does not guarantee backward compatibility
104 104  
105 105  For concrete examples, see the Appendix.
106 106  
107 -= 5. How versioning works for inter-dependent artefacts =
113 +=== 5. How versioning works for inter-dependent artefacts ===
108 108  
109 109  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.
110 110  
... ... @@ -127,19 +127,26 @@
127 127  The replacement of a reference with a different reference has the same impact for every artefact.
128 128  
129 129  |(% colspan="3" %)**ALL ARTEFACTS**
130 -|(% style="width:492px" %)**Type of change**|(% style="width:441px" %)**Impact**|**Comments**
131 -|(% style="width:492px" %)(((
132 -**Replacement of a child artefact having a different version, but same id and Agency**
133 -)))|(% style="width:441px" %)(((
134 -**The child artefact version change is replicated in the parent artefact**
136 +|**Type of change**|**Impact**|**Comments**
137 +|(((
138 +**Replacement of a child artefact having a different version, but same id and**
139 +
140 +**Agency**
135 135  )))|(((
142 +**The child artefact version change is replicated in the**
143 +
144 +**parent artefact**
145 +)))|(((
136 136  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.
147 +
137 137  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
138 138  )))
139 -|(% style="width:492px" %)(((
140 -**Replacement of a referenced child artefact having a different id or Agency**
141 -)))|(% 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)
150 +|(((
151 +**Replacement of a referenced child artefact having a**
142 142  
153 +**different id or Agency**
154 +)))|**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)
155 +
143 143  ==== b. Addition or removal of referenced artefacts ====
144 144  
145 145  | |(% colspan="2" %)**CONCEPT SCHEME (CS)**
© Semantic R&D Group, 2026