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.18
edited by Helena K.
on 2026/01/15 15:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -142,29 +142,25 @@
142 142  
143 143  ==== b. Addition or removal of referenced artefacts ====
144 144  
145 -| |(% colspan="2" %)**CONCEPT SCHEME (CS)**
146 -|**Type of change**|**Impact**|**Comments**
147 -|(((
148 -**Addition or removal of a child**
145 +|(% colspan="3" style="width:876px" %)**CONCEPT SCHEME (CS)**
146 +|(% style="width:845px" %)**Type of change**|(% style="width:156px" %)**Impact**|(% style="width:1071px" %)**Comments**
147 +|(% style="width:845px" %)(((
148 +**Addition or removal of a child Code List**
149 +)))|(% 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
149 149  
150 -**Code List**
151 -)))|**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
152 152  
153 153  
154 -
155 -| |(% colspan="2" %)**DATA STRUCTURE DEFINITION (DSD)**
153 +|(% colspan="3" %)**DATA STRUCTURE DEFINITION (DSD)**
156 156  |**Type of change**|**Impact**|**Comments**
157 157  |**Addition or removal of a child Code List**|(((
158 -**If same id and Agency, then the child artefact version change is replicated in the parent artefact.**
159 -
160 -**If different id or Agency, impact wil depend on the backward/forward compatibility as shown in the tables above**
156 +**If same id and Agency, then the child artefact version change is replicated in the parent artefact.
157 +If different id or Agency, impact wil depend on the backward/forward compatibility as shown in the tables above**
161 161  )))|(((
162 162  If a child Code List has a minor version change, then the DSD should also have a minor version change.
163 -
164 164  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
165 165  )))
166 166  
167 -=== 6. Appendix - Examples ===
163 += 6. Appendix - Examples =
168 168  
169 169  **Example 1 – Change to a Code List name, for clarification purposes**. **Patch Impact: N.M.+**
170 170  
... ... @@ -185,36 +185,29 @@
185 185  
186 186  |(% colspan="2" %)**AGGREGATION OF EXISTING CODES**
187 187  |**Old version**|**New version**
188 -|**2011** Heifers (female bovine that never calved), live **2012** Cows, live|**2010** Heifers and cows, live
189 -|(% 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.
184 +|**2011** Heifers (female bovine that never calved), live
185 +**2012** Cows, live|**2010** Heifers and cows, live
186 +|(% 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.
190 190  
191 -
192 -
193 193  |(% colspan="2" %)**DISAGGREGATION OF EXISTING CODES**
194 194  |**Old version**|**New version**
195 195  |**1010** Live horses|(((
196 -1. Pure bred breeding horses, live
197 -1. Other horses, live
191 +1011 Pure bred breeding horses, live
192 +1012 Other horses, live
198 198  )))
199 -|(% 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.
194 +|(% 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.
200 200  
201 -
202 -
203 203  |(% colspan="2" %)**REORGANISATION OF EXISTING CODES**
204 204  |**Old version**|**New version**
205 205  |(((
206 206  **3010** Fowls, weighing ≤ 185 g
207 -
208 208  **3020** Ducks, , weighing ≤ 185 g
209 -
210 210  **3030** Other poultry, weighing ≤ 185 g
211 -
212 212  **3040** Fowls, weighing > 185 g
213 -
214 214  **3050** Ducks, , weighing > 185 g
215 -
216 216  **3060** Other poultry, weighing > 185 g
217 -)))|**3025** Poultry, weighing ≤ 175 g **3045** Poultry, weighing > 175 g
205 +)))|**3025** Poultry, weighing ≤ 175 g
206 +**3045** Poultry, weighing > 175 g
218 218  |(% colspan="2" %)Codes **3010**, **3020**, **3030**, **3040**, **3050** and **3060** are fully removed and replaced with two brand new codes; furthermore the criterion for the classification used in the old version has been changed in the new version (185 g criterion versus 175 g criterion), so that it is not possible to exactly aggregate the codes from the old version to the codes of the new version (e.g. a part of **3010** goes to **3025**, another part to **3045**). In this case there is a m to n correspondence between the two sets of codes
219 219  
220 220  **Example 5 – Changes to hierarchies in a Code List. Major impact: +.0**
... ... @@ -221,7 +221,16 @@
221 221  
222 222  |(% colspan="2" %)**ADDING A NEW CODE IN AN EXISTING HIERARCHY – CODE LIST**
223 223  |**Old version**|**New version**
224 -|• 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**
213 +|(((
214 +* 0213 - Beer
215 +** 02131 - Lager beer
216 +** 02132 - Other alcoholic beer
217 +)))|(((
218 +* 0213 - Beer
219 +** 02131 - Lager beer
220 +** 02132 - Other alcoholic beer
221 +* **02133 - Low and non-alcoholic beer**
222 +)))
225 225  |(% colspan="2" %)Code 02133 has been added to hierarchy 0213
226 226  
227 227  **Example 6 – Changes to hierarchies in a Hierarchical Code List. Major impact: +.0**
... ... @@ -229,69 +229,58 @@
229 229  |(% colspan="2" %)**ADDING A NEW CODE IN AN EXISTING HIERARCHY – HIERARCHICAL CODE LIST**
230 230  |**Old version**|**New version**
231 231  |(((
232 -• A1 - World (codelist ref. ECB@CL_AREAS@1.0) o E1 - Europe (ECB@CL_COUNTRIES@1.0)
233 -
234 - ES - Spain FR - France
235 -
236 -GR - Greece
237 -
238 -IT - Italy o E4 - Africaetc.
230 +* A1 - World (codelist ref. ECB@CL_AREAS@1.0)
231 +** E1 - Europe (ECB@CL_COUNTRIES@1.0)
232 +*** ES - Spain FR - France
233 +*** GR - Greece
234 +*** IT - Italy
235 +** E4 - Africa
236 +*** etc.
239 239  )))|(((
240 -• A1=World (codelist ref. ECB@CL_AREAS@1.0) o E1 =Europe (ECB@CL_COUNTRIES@1.0)
241 -
242 - ES = Spain FR = FranceGR = Greece
243 -
244 -IT = Italy
245 -
246 -**DE= Germany**
247 -
248 -o E4 =Africaetc.
238 +* A1=World (codelist ref. ECB@CL_AREAS@1.0)
239 +** E1 =Europe (ECB@CL_COUNTRIES@1.0)
240 +** ES = Spain FR = FranceGR = Greece
241 +** IT = Italy
242 +** **DE= Germany**
243 +* E4 =Africa
244 +** etc.
249 249  )))
250 250  |(% colspan="2" %)The id of the hierarchical codes are assumed to be equal to those of the code lists referenced. The code DE has been added to hierarchy E1
251 251  
252 252  **Example 7.1 – Dependencies between artefacts: Concept Scheme and Code List. Minor impact: N.+**
253 253  
254 -|**Id:Artefact Type:Details**|**Change type**|**Version Impact**|**Old version**|(((
255 -**New**
256 -
257 -**version**
250 +|(% style="width:492px" %)**Id:Artefact Type:Details**|(% style="width:732px" %)**Change type**|(% style="width:558px" %)**Version Impact**|(% style="width:139px" %)**Old version**|(% style="width:151px" %)(((
251 +**New version**
258 258  )))
259 -|**CL_OBS_STATUS:Code List**|Addition of a new code X|**Minor: N.+**|**1.0**|**1.1**
260 -|**CS_TRADE:Concept Scheme: References CL_OBS_STATUS v1.0 above**|(((
253 +|(% style="width:492px" %)**CL_OBS_STATUS:Code List**|(% style="width:732px" %)Addition of a new code X|(% style="width:558px" %)**Minor: N.+**|(% style="width:139px" %)**1.0**|(% style="width:151px" %)**1.1**
254 +|(% style="width:492px" %)**CS_TRADE:Concept Scheme: References CL_OBS_STATUS v1.0 above**|(% style="width:732px" %)(((
261 261  Adoption of new code X
262 262  
263 -**//Change type//**: Replacement of a child artefact having a different version, but the same id and
264 -
265 -Agency
266 -)))|(((
257 +**//Change type//**: Replacement of a child artefact having a different version, but the same id and Agency
258 +)))|(% style="width:558px" %)(((
267 267  **Minor: N.+**
260 +The child version impact is replicated in the parent artefact
261 +)))|(% style="width:139px" %)**2.0**|(% style="width:151px" %)**2.1**
268 268  
269 -The child version impact is replicated in the parent
270 -
271 -artefact
272 -)))|**2.0**|**2.1**
273 -
274 274  **Example 7.2 – Dependencies between artefacts: Concept Scheme and Code List. Major impact: +.0**
275 275  
276 -|**Id:Artefact Type:Details**|**Change type**|**Version Impact**|**Old version**|(((
277 -**New**
278 -
279 -**version**
265 +|(% style="width:489px" %)**Id:Artefact Type:Details**|(% style="width:734px" %)**Change type**|(% style="width:562px" %)**Version Impact**|**Old version**|(((
266 +**New version**
280 280  )))
281 -|**CL_OBS_STATUS:Code List**|Removal of code U|**Major: +.0**|**1.0**|**2.0**
282 -|(((
268 +|(% style="width:489px" %)**CL_OBS_STATUS:Code List**|(% style="width:734px" %)Removal of code U|(% style="width:562px" %)**Major: +.0**|**1.0**|**2.0**
269 +|(% style="width:489px" %)(((
283 283  **CS_TRADE:Concept**
284 284  
285 285  **Scheme:References**
286 286  
287 287  **CL_OBS_STATUS v1.0 above**
288 -)))|(((
275 +)))|(% style="width:734px" %)(((
289 289  Adoption of new CL_OBS_STATUS without U.
290 290  
291 291  **//Change type//**: Replacement of a child artefact having a different version, but the same id and
292 292  
293 293  Agency
294 -)))|(((
281 +)))|(% style="width:562px" %)(((
295 295  **Major: +.0**
296 296  
297 297  The child version impact is replicated in the parent artefact.
... ... @@ -299,51 +299,48 @@
299 299  
300 300  **Example 7.3 – Dependencies between artefacts: Concept Scheme and Code List. Variable impact (see below)**
301 301  
302 -|**Id:Artefact Type:Details**|**Change type**|**Version Impact**|**Old version**|(((
303 -**New**
304 -
305 -**version**
289 +|(% style="width:489px" %)**Id:Artefact Type:Details**|(% style="width:736px" %)**Change type**|(% style="width:555px" %)**Version Impact**|(% style="width:146px" %)**Old version**|(% style="width:146px" %)(((
290 +**New version**
306 306  )))
307 -|(% rowspan="3" %)**CL_XYZ: Code List**|(((
292 +|(% rowspan="3" style="width:489px" %)**CL_XYZ: Code List**|(% style="width:736px" %)(((
308 308  a) Maintenance agency changes from A to B for governance reasons.
309 309  
310 310  Nothing else changes in the code list.
311 -)))|(% rowspan="3" %)**New artefact**|(% rowspan="3" %)(((
296 +)))|(% rowspan="3" style="width:555px" %)**New artefact**|(% rowspan="3" style="width:146px" %)(((
312 312  **CL_XYZ**
313 313  
314 314  **(Agency A)**
315 -)))|(% rowspan="3" %)(((
300 +)))|(% rowspan="3" style="width:146px" %)(((
316 316  **CL_XYZ**
317 317  
318 -**(Agency B)**
319 -
320 -**(new maintenance agency)**
303 +**(Agency B)
304 +(new maintenance agency)**
321 321  )))
322 -|b) Maintenance agency changes from A to B and at the same time new codes are added
323 -|c) Maintenance agency changes from A to B. Since B has different coding rules, the code list itself changes as well.
324 -|(% rowspan="3" %)(((
306 +|(% style="width:736px" %)b) Maintenance agency changes from A to B and at the same time new codes are added
307 +|(% style="width:736px" %)c) Maintenance agency changes from A to B. Since B has different coding rules, the code list itself changes as well.
308 +|(% rowspan="3" style="width:489px" %)(((
325 325  **CS_TRADE: Concept Scheme: References**
326 326  
327 327  **CL_XYZ (Agency A) **
328 -)))|(% rowspan="3" %)(((
312 +)))|(% rowspan="3" style="width:736px" %)(((
329 329  Replacement of a child artefact having a different Agency.
330 330  
331 331  CL_XYZ (Agency A) changes to CL_XYZ (Agency B).
332 -)))|(((
316 +)))|(% style="width:555px" %)(((
333 333  **Case a): Patch: N.M.+**
334 334  
335 335  There is no impact on data exchange
336 -)))|**2.0**|**2.0.1**
337 -|(((
320 +)))|(% style="width:146px" %)**2.0**|(% style="width:146px" %)**2.0.1**
321 +|(% style="width:555px" %)(((
338 338  **Case b): Minor: N. +**
339 339  
340 340  The impact is the same as a new minor version of the code list
341 -)))|**2.0**|**2.1**
342 -|(((
325 +)))|(% style="width:146px" %)**2.0**|(% style="width:146px" %)**2.1**
326 +|(% style="width:555px" %)(((
343 343  **Case c) Major: +.0**
344 344  
345 345  The impact is the same as a new major version of the code list.
346 -)))|**2.0**|**3.0**
330 +)))|(% style="width:146px" %)**2.0**|(% style="width:146px" %)**3.0**
347 347  
348 348  **Example 7.4 – Dependencies between artefacts: Concept Scheme and DSD. Variable impact (see below)**
349 349  
© Semantic R&D Group, 2026