Changes for page 4 General Notes for Implementers

Summary

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

Details

Page properties

Content

...	...	@@ -544,17 +544,13 @@
544	544
545	545	The production versions of identifiable artefacts are assumed stable, i.e., they do not have an EXTENSION. This is because once in production, an artefact cannot change in any way, or it must change the version. For cases where an artefact is not static, like during the drafting, the version must indicate this by including an EXTENSION. Draft artefacts should not be used outside of a specific system designed to accommodate them. For most purposes, all artefacts should become stable before being used in production.
546	546
547		-1.
548		-11.
549		-111. Legacy-versioned artefacts
	547	+=== 4.3.3 Legacy-versioned artefacts ===
550	550
551	551	Organisations wishing to keep a maximum of backwards compatibility with existing implementations can continue using the previous 2-digit convention for version numbers (MAJOR.MINOR) as in the past, such as '2.3', but without the ‘isFinal’ property. The new SDMX 3.0 standard does not add any strict rules or guarantees about changes in those artefacts, since the legacy versioning rules were rather loose and non-binding, including the meaning of the ‘isFinal’ property, and their implementations were varying.
552	552
553	553	In order to make artefacts immutable or changes truly predictable, a move to the new semantic versioning syntax is required.
554	554
555		-1.
556		-11.
557		-111. Dependency management and references
	553	+=== 4.3.4 Dependency management and references ===
558	558
559	559	New flexible dependency specifications with wildcarding allow for easier data model maintenance and enhancements for semantically versioned SDMX artefacts. This allows implementing a smart referencing mechanism, whereby an artefact may reference:
560	560