Changes for page Guidelines on the Versioning of SDMX Artefacts

Summary

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

Details

Page properties

Content

...	...	@@ -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**
	130	+|**Type of change**|**Impact**|**Comments**
	131	+|(((
	132	+**Replacement of a child artefact having a different version, but same id and**
	133	+
	134	+**Agency**
135	135	)))|(((
	136	+**The child artefact version change is replicated in the**
	137	+
	138	+**parent artefact**
	139	+)))|(((
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.
	141	+
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)
	144	+|(((
	145	+**Replacement of a referenced child artefact having a**
142	142
	147	+**different id or Agency**
	148	+)))|**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)
	149	+
143	143	==== b. Addition or removal of referenced artefacts ====
144	144
145	145	| |(% colspan="2" %)**CONCEPT SCHEME (CS)**