Skip to Content
Last modified by Artur K. on 2026/05/29 14:28
From version 1.16
edited by Helena K.
on 2026/01/15 15:20
Change comment: There is no comment for this version
To version 2.1
edited by Artur K.
on 2026/05/29 14:28
Change comment: Copied from sdmxsrlocalization:Methodology.Guidelines on the Versioning of SDMX Artefacts.WebHome

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.helena
1 +xwiki:XWiki.arturkryazhev
Content
... ... @@ -247,47 +247,38 @@
247 247  
248 248  **Example 7.1 – Dependencies between artefacts: Concept Scheme and Code List. Minor impact: N.+**
249 249  
250 -|**Id:Artefact Type:Details**|**Change type**|**Version Impact**|**Old version**|(((
251 -**New**
252 -
253 -**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**
254 254  )))
255 -|**CL_OBS_STATUS:Code List**|Addition of a new code X|**Minor: N.+**|**1.0**|**1.1**
256 -|**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" %)(((
257 257  Adoption of new code X
258 258  
259 -**//Change type//**: Replacement of a child artefact having a different version, but the same id and
260 -
261 -Agency
262 -)))|(((
257 +**//Change type//**: Replacement of a child artefact having a different version, but the same id and Agency
258 +)))|(% style="width:558px" %)(((
263 263  **Minor: N.+**
260 +The child version impact is replicated in the parent artefact
261 +)))|(% style="width:139px" %)**2.0**|(% style="width:151px" %)**2.1**
264 264  
265 -The child version impact is replicated in the parent
266 -
267 -artefact
268 -)))|**2.0**|**2.1**
269 -
270 270  **Example 7.2 – Dependencies between artefacts: Concept Scheme and Code List. Major impact: +.0**
271 271  
272 -|**Id:Artefact Type:Details**|**Change type**|**Version Impact**|**Old version**|(((
273 -**New**
274 -
275 -**version**
265 +|(% style="width:489px" %)**Id:Artefact Type:Details**|(% style="width:734px" %)**Change type**|(% style="width:562px" %)**Version Impact**|**Old version**|(((
266 +**New version**
276 276  )))
277 -|**CL_OBS_STATUS:Code List**|Removal of code U|**Major: +.0**|**1.0**|**2.0**
278 -|(((
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" %)(((
279 279  **CS_TRADE:Concept**
280 280  
281 281  **Scheme:References**
282 282  
283 283  **CL_OBS_STATUS v1.0 above**
284 -)))|(((
275 +)))|(% style="width:734px" %)(((
285 285  Adoption of new CL_OBS_STATUS without U.
286 286  
287 287  **//Change type//**: Replacement of a child artefact having a different version, but the same id and
288 288  
289 289  Agency
290 -)))|(((
281 +)))|(% style="width:562px" %)(((
291 291  **Major: +.0**
292 292  
293 293  The child version impact is replicated in the parent artefact.
... ... @@ -295,51 +295,41 @@
295 295  
296 296  **Example 7.3 – Dependencies between artefacts: Concept Scheme and Code List. Variable impact (see below)**
297 297  
298 -|**Id:Artefact Type:Details**|**Change type**|**Version Impact**|**Old version**|(((
299 -**New**
300 -
301 -**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**
302 302  )))
303 -|(% rowspan="3" %)**CL_XYZ: Code List**|(((
292 +|(% rowspan="3" style="width:489px" %)**CL_XYZ: Code List**|(% style="width:736px" %)(((
304 304  a) Maintenance agency changes from A to B for governance reasons.
305 -
306 306  Nothing else changes in the code list.
307 -)))|(% rowspan="3" %)**New artefact**|(% rowspan="3" %)(((
295 +)))|(% rowspan="3" style="width:555px" %)**New artefact**|(% rowspan="3" style="width:146px" %)(((
308 308  **CL_XYZ**
309 309  
310 310  **(Agency A)**
311 -)))|(% rowspan="3" %)(((
299 +)))|(% rowspan="3" style="width:146px" %)(((
312 312  **CL_XYZ**
313 313  
314 -**(Agency B)**
315 -
316 -**(new maintenance agency)**
302 +**(Agency B)
303 +(new maintenance agency)**
317 317  )))
318 -|b) Maintenance agency changes from A to B and at the same time new codes are added
319 -|c) Maintenance agency changes from A to B. Since B has different coding rules, the code list itself changes as well.
320 -|(% rowspan="3" %)(((
321 -**CS_TRADE: Concept Scheme: References**
322 -
323 -**CL_XYZ (Agency A) **
324 -)))|(% rowspan="3" %)(((
325 -Replacement of a child artefact having a different Agency.
326 -
305 +|(% style="width:736px" %)b) Maintenance agency changes from A to B and at the same time new codes are added
306 +|(% style="width:736px" %)c) Maintenance agency changes from A to B. Since B has different coding rules, the code list itself changes as well.
307 +|(% rowspan="3" style="width:489px" %)(((
308 +**CS_TRADE: Concept Scheme: References CL_XYZ (Agency A) **
309 +)))|(% rowspan="3" style="width:736px" %)(((
310 +Replacement of a child artefact having a different Agency.
327 327  CL_XYZ (Agency A) changes to CL_XYZ (Agency B).
328 -)))|(((
312 +)))|(% style="width:555px" %)(((
329 329  **Case a): Patch: N.M.+**
330 -
331 331  There is no impact on data exchange
332 -)))|**2.0**|**2.0.1**
333 -|(((
315 +)))|(% style="width:146px" %)**2.0**|(% style="width:146px" %)**2.0.1**
316 +|(% style="width:555px" %)(((
334 334  **Case b): Minor: N. +**
335 -
336 336  The impact is the same as a new minor version of the code list
337 -)))|**2.0**|**2.1**
338 -|(((
319 +)))|(% style="width:146px" %)**2.0**|(% style="width:146px" %)**2.1**
320 +|(% style="width:555px" %)(((
339 339  **Case c) Major: +.0**
340 -
341 341  The impact is the same as a new major version of the code list.
342 -)))|**2.0**|**3.0**
323 +)))|(% style="width:146px" %)**2.0**|(% style="width:146px" %)**3.0**
343 343  
344 344  **Example 7.4 – Dependencies between artefacts: Concept Scheme and DSD. Variable impact (see below)**
345 345  
... ... @@ -346,44 +346,36 @@
346 346  |**Id:Artefact Type:Details**|**Change type**|**Version Impact**|**Old version**|**New version**
347 347  |**CS_TRADE: Concept Scheme containing Concepts C1, C2, C3**|Addition of new Concept C4|**Minor: N.+**|**1.4**|**1.5**
348 348  |(((
349 -**TRADE: Data Structure Definition:**
350 -
351 -**references Concepts C1 and C2**
330 +**TRADE: Data Structure Definition:
331 +references Concepts C1 and C2**
352 352  )))|(((
353 353  None
354 -
355 355  Concept C3 is not used
356 356  )))|**None**|**1.0**|**1.0**
357 357  |** **| |** **|** **|** **
358 358  |**CS_TRADE: Concept Scheme containing Concepts C1, C2, C3**|Change of description in Concept C3 (typo)|**Patch: N.M.+**|**1.4**|**1.4.1**
359 359  |(((
360 -**TRADE: Data Structure Definition:**
361 -
362 -**references Concepts C1 and C2**
339 +**TRADE: Data Structure Definition:
340 +references Concepts C1 and C2**
363 363  )))|(((
364 364  None
365 -
366 366  Concept C3 is not used
367 367  )))|**None**|**1.0**|**1.0**
368 368  |(% colspan="5" %)
369 369  |**CS_TRADE: Concept Scheme containing Concepts C1, C2, C3**|Removal of Concept C3|**Major: +.0**|**1.4**|**2.0**
370 370  |(((
371 -**TRADE: Data Structure Definition:**
372 -
373 -**references Concepts C1 and C2**
348 +**TRADE: Data Structure Definition:
349 +references Concepts C1 and C2**
374 374  )))|None concept C3 is not used|**None**|**1.0**|**1.0**
375 375  |(% colspan="5" %)**Remark: **Once a new version of the DSD is needed for some other reasons (e.g. a change in a code list), it is recommended to update all concept references to the newest available concept scheme if possible: i.e. DSD version 1.1 would then update its concept scheme references from 1.4 to 2.0.
376 376  |(% colspan="5" %)
377 377  |**CS_TRADE: Concept Scheme containing Concepts C1, C2, C3**|Change of description in Concept C2 (typo)|**Patch: N.M.+**|**1.4**|**1.4.1**
378 378  |(((
379 -**TRADE: Data Structure Definition:**
380 -
381 -**references Concepts C1 and C2**
355 +**TRADE: Data Structure Definition:
356 +references Concepts C1 and C2**
382 382  )))|Correction should be taken into account, concept C2 is used|(((
383 -**Patch: N.M.+**
384 -
385 -**//or//**
386 -
358 +**Patch: N.M.+
359 +//or //**
387 387  **None**
388 388  )))|**1.0**|(((
389 389  **1.0.1 //or//**
... ... @@ -392,8 +392,6 @@
392 392  )))
393 393  |(% colspan="5" %)**Remark: **Since the change of a typo in a Concept of the Concept Scheme does not have a direct impact on the DSD itself (the link is by reference), there is strictly speaking no need to update the DSD. Both DSDs (1.0 and 1.0.1) will have exactly the same syntax. However, if maintainers want to highlight the correction for users of the DSD or for some other reason the DSD is updated anyway; it should reference the newer Concept Scheme.
394 394  
395 -**~ **
396 -
397 397  ----
398 398  
399 399  {{putFootnotes/}}
© Semantic R&D Group, 2026