Versioning of structural metadata artefacts - Revision history

Vmurrell: /* Overview */

2024-05-13T14:08:07Z

‎Overview

2022-08-25T14:49:44Z

2022-08-25T14:48:52Z

‎Overview

2022-08-17T12:44:42Z

2022-08-17T12:43:01Z

2022-08-17T12:42:18Z

2022-08-17T12:15:28Z

2021-03-15T18:03:27Z

2021-02-01T18:02:20Z

‎Overview

2021-01-20T12:01:34Z

@@ Line 8: / Line 8: @@
 The version number defaults to 1.0.
-The combination of the structure type, Agency ID, structure ID and version are used to uniquely identify any Maintainable structure using its [[URN]].
+The combination of the structure type, Agency ID, structure ID and version are used to uniquely identify any Maintainable structure using its [[URN V11]].
 Examples of URN illustrating the use of version numbers:<br>

@@ Line 2: / Line 2: @@
 [[Category:Concepts_Reference_V11]]
 =Overview=
-All [[Maintainable_V10|Maintainable]] structures have a mandatory version number of the form <strong>[major number].[minor number]</strong>.
+All Maintainable structures have a mandatory version number of the form <strong>[major number].[minor number]</strong>.
 Examples: 1.0, 1.1, 2.3
@@ Line 10: / Line 10: @@
 The combination of the structure type, Agency ID, structure ID and version are used to uniquely identify any Maintainable structure using its [[URN]].
-Examples of [[URN V10|URNs]] illustrating the use of version numbers:<br>
+Examples of URN illustrating the use of version numbers:<br>
 <code><nowiki>urn:sdmx:org.sdmx.infomodel.codelist.Codelist=SDMX:CL_TIME_PER_COLLECT(1.11)</nowiki></code><br>
 <code><nowiki>urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=IMF:ECOFIN_CONCEPTS(2.0).INDICATOR</nowiki></code><br>

@@ Line 2: / Line 2: @@
 [[Category:Concepts_Reference_V11]]
 =Overview=
-All [[Maintainable]] structures have a mandatory version number of the form <strong>[major number].[minor number]</strong>.
+All [[Maintainable_V10|Maintainable]] structures have a mandatory version number of the form <strong>[major number].[minor number]</strong>.
 Examples: 1.0, 1.1, 2.3
@@ Line 10: / Line 10: @@
 The combination of the structure type, Agency ID, structure ID and version are used to uniquely identify any Maintainable structure using its [[URN]].
-Examples of [[URN|URNs]] illustrating the use of version numbers:<br>
+Examples of [[URN V10|URNs]] illustrating the use of version numbers:<br>
 <code><nowiki>urn:sdmx:org.sdmx.infomodel.codelist.Codelist=SDMX:CL_TIME_PER_COLLECT(1.11)</nowiki></code><br>
 <code><nowiki>urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=IMF:ECOFIN_CONCEPTS(2.0).INDICATOR</nowiki></code><br>

@@ Line 1: / Line 1: @@
 [[Category:Concepts_Reference_V10]]
 =Overview=
 All [[Maintainable]] structures have a mandatory version number of the form <strong>[major number].[minor number]</strong>.

@@ Line 1: / Line 1: @@
-[[Category:Concepts_Reference]]
+[[Category:Concepts_Reference_V10]]
 =Overview=
 All [[Maintainable]] structures have a mandatory version number of the form <strong>[major number].[minor number]</strong>.

← Older revision	Revision as of 12:44, 17 August 2022
(No difference)

← Older revision	Revision as of 12:43, 17 August 2022
(No difference)

← Older revision		Revision as of 18:03, 15 March 2021
Line 39:		Line 39:
	\|}		\|}

−	For Item Schemes such as Codelists and Concept Schemes, it is generally recommended <strong>not</strong> to increment the version number when new codes are added. The reason being that Codelists are linked to Data Structure ~~Defintions~~ at a particular version, for example CL_REF_AREA(1.0). If significant changes are made to a Codelist like a complete redesign of a classification scheme, consideration should be given to incrementing the minor or major version. Thus a user may infer that CL_REF_AREA(2.0) is ~~signficantly~~ different to CL_REF_AREA(1.0), and not just because it carries some additional codes.	+	For Item Schemes such as Codelists and Concept Schemes, it is generally recommended <strong>not</strong> to increment the version number when new codes are added. The reason being that Codelists are linked to Data Structure Definitions at a particular version, for example CL_REF_AREA(1.0). If significant changes are made to a Codelist like a complete redesign of a classification scheme, consideration should be given to incrementing the minor or major version. Thus a user may infer that CL_REF_AREA(2.0) is significantly different to CL_REF_AREA(1.0), and not just because it carries some additional codes.