Changes for page SDMX 3.1 Standards. Section 1. Framework

Last modified by Helena K. on 2026/06/08 15:16

From 36.20 to 36.19 From 36.26 to 36.25

From version 36.25

edited by Helena K.
on 2026/06/08 13:30

Change comment: There is no comment for this version

To version 36.20

edited by Helena K.
on 2026/06/08 13:27

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -241,15 +241,15 @@
  * //**[[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]] Definition:**// A [[metadata flow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]] definition is very similar to a [[data flow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] definition, but describes, categorises, and constrains [[metadata sets>>doc:sdmx:Glossary 2\.1.Metadata set.WebHome]].
  * //**[[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]]: **//An organization which produces data is termed a [[data provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]].
  * //**Metadata Provider: **//An organization which produces [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] is termed a metadata provider.
--* //**[[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] (Metadata [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]]):**// The set of information which describes the way in which [[data sets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary 2\.1.Metadata set.WebHome]] are provided by a data/metadata provider. A [[provision agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] can be constrained in much the same way as a data or [[metadata flow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]] definition. Thus, a [[data provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] can express the fact that it provides a particular [[data flow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] covering a specific set of countries and topics, Importantly, the actual source of registered data or metadata is attached to the [[provision agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] (in terms of a URL). The term “agreement” is used because this information can be understood as the basis of a “service-level agreement”. In [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]], however, this is informational metadata to support the technical systems, as opposed to any sort of contractual information (which is outside the scope of a technical specification). In version 3.0, metadata [[provision agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] and data [[provision agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] are two separate [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]].
--* //**Data Constraint:**// Used to restrict content (such as enumerations) and are used by [[provision agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]], [[data flows>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]], [[data structure definitions>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] in order to provide a set of reporting restrictions in the context of a collection
--* //**Metadata Constraint:**// Used to restrict content (such as enumerations) and are used by metadata [[provision agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]], [[metadata flows>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]], [[metadata structure definitions>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]] in order to provide a set of reporting restrictions in the context of a collection
--* //**Available Data Constraint:**// Used to report the set of [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] values that have data reported against them in the context of a Data Query. This structure allows a user to know what valid filters can be applied to a cube of data, such that the resulting cube will contain data.
--* //**Structure Map: **//Structure maps describes a mapping between [[data structure definitions>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] or [[dataflows>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] for the purpose of transforming a [[data set>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] into a different structure. The mapping rules are defined using one or more [[component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] maps which each map in turn describes how one or more [[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] from the source [[data structure definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] map to one or more [[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] in that of the target. Represent maps act as lookup tables and specific provision is made for mapping dates and times.
--* //**[[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] Map:**// [[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] maps describe mappings between source value(s) and target value(s) where the values are restricted to those in a [[code list>>doc:sdmx:Glossary 2\.1.Code list.WebHome]], value list or be of a certain type such as integer or string.
--* //**[[Item Scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] Map:**// An [[item scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] map describes mapping rules between any [[item scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] with the exception of [[code lists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] and value lists which use [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] maps. The version 3.0 information model provides four [[item scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] maps: organisation scheme map, [[concept scheme>>doc:sdmx:Glossary 2\.1.Concept scheme.WebHome]] map, [[category scheme>>doc:sdmx:Glossary 2\.1.Category scheme.WebHome]] map and [[reporting taxonomy>>doc:sdmx:Glossary 2\.1.Reporting taxonomy.WebHome]] map. Organisation scheme map and reporting scheme map have been omitted from the information model schematic in Figure 1.
++* //**[[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] (Metadata [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]]):**// The set of information which describes the way in which [[data sets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary 2\.1.Metadata set.WebHome]] are provided by a data/metadata provider. A [[provision agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] can be constrained in much the same way as a data or [[metadata flow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]] definition. Thus, a [[data provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] can express the fact that it provides a particular [[data flow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] covering a specific set of countries and topics, Importantly, the actual source of registered data or metadata is attached to the [[provision agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] (in terms of a URL). The term “agreement” is used because this information can be understood as the basis of a “service-(% style="color:#e74c3c" %)level(%%) agreement”. In [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]], however, this is informational metadata to support the technical systems, as opposed to any sort of contractual information (which is outside the scope of a technical specification). In (% style="color:#e74c3c" %)version(%%) 3.0, metadata [[provision agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] and data [[provision agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] are two separate [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]].
++* //**Data (% style="color:#e74c3c" %)Constraint(%%):**// Used to restrict content (such as enumerations) and are used by [[provision agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]], [[data flows>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]], [[data structure definitions>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] in order to provide a set of reporting restrictions in the context of a collection
++* //**Metadata (% style="color:#e74c3c" %)Constraint(%%):**// Used to restrict content (such as enumerations) and are used by metadata [[provision agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]], [[metadata flows>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]], [[metadata structure definitions>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]] in order to provide a set of reporting restrictions in the context of a collection
++* //**Available Data (% style="color:#e74c3c" %)Constraint(%%):**// Used to report the set of [[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] values that have data reported against them in the context of a Data Query. This structure allows a user to know what valid filters can be applied to a cube of data, such that the resulting cube will contain data.
++* //**Structure (% style="color:#e74c3c" %)Map(%%): **//Structure (% style="color:#e74c3c" %)maps(%%) describes a mapping between [[data structure definitions>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] or [[dataflows>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] for the purpose of transforming a [[data set>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] into a different structure. The mapping rules are defined using one or more [[component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] (% style="color:#e74c3c" %)maps(%%) which each (% style="color:#e74c3c" %)map(%%) in turn describes how one or more [[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] from the source [[data structure definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] (% style="color:#e74c3c" %)map(%%) to one or more [[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] in that of the target. Represent (% style="color:#e74c3c" %)maps(%%) act as lookup tables and specific provision is made for mapping dates and times.
++* //**[[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] (% style="color:#e74c3c" %)Map(%%):**// [[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] (% style="color:#e74c3c" %)maps(%%) describe mappings between source value(s) and target value(s) where the values are restricted to those in a [[code list>>doc:sdmx:Glossary 2\.1.Code list.WebHome]], value list or be of a certain type such as integer or string.
++* //**[[Item Scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] (% style="color:#e74c3c" %)Map(%%):**// An [[item scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] (% style="color:#e74c3c" %)map(%%) describes mapping rules between any [[item scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] with the exception of [[code lists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] and value lists which use [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] (% style="color:#e74c3c" %)maps(%%). The (% style="color:#e74c3c" %)version(%%) 3.0 information model provides four [[item scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] (% style="color:#e74c3c" %)maps(%%): organisation scheme (% style="color:#e74c3c" %)map(%%), [[concept scheme>>doc:sdmx:Glossary 2\.1.Concept scheme.WebHome]] (% style="color:#e74c3c" %)map(%%), [[category scheme>>doc:sdmx:Glossary 2\.1.Category scheme.WebHome]] (% style="color:#e74c3c" %)map(%%) and [[reporting taxonomy>>doc:sdmx:Glossary 2\.1.Reporting taxonomy.WebHome]] (% style="color:#e74c3c" %)map(%%). Organisation scheme (% style="color:#e74c3c" %)map(%%) and reporting scheme (% style="color:#e74c3c" %)map(%%) have been omitted from the information model schematic in Figure 1.
  * //**[[Reporting Taxonomy>>doc:sdmx:Glossary 2\.1.Reporting taxonomy.WebHome]]: **//A [[reporting taxonomy>>doc:sdmx:Glossary 2\.1.Reporting taxonomy.WebHome]] allows an organisation to link (possibly in a hierarchical way) a number of cube or [[data flow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] definitions which together form a complete “report” of data or metadata. This supports primary reporting which often comprises multiple cubes of heterogeneous data, but may also support other collection and reporting functions. It also supports the specification of publications such as a yearbook, in terms of the data or metadata contained in the publication.
--* //**Process:**// The process class provides a way to model statistical processes as a set of interconnected //process steps.// Although not central to the exchange and dissemination of statistical data and metadata, having a shared description of processing allows for the interoperable exchange and dissemination of [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] sets which describe processes-related concepts.
++* //**Process:**// The process class provides a way to model statistical processes as a set of interconnected //process steps.// Although not central to the exchange and dissemination of statistical data and metadata, having a shared description of processing allows for the interoperable exchange and dissemination of [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] sets which describe processes-related (% style="color:#e74c3c" %)concepts(%%).
  * //**[[Hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]]**//: Describes complex [[code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] [[hierarchies>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] principally for data discovery purposes. The [[codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] themselves are referenced from the [[code lists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] in which they are maintained.
  * //**[[Hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] Association**//: A [[hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] association links a [[hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] to something that needs it like a [[dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]]. Furthermore, the linking can be specified in the context of another object such as a [[dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] in the context of a [[dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]]. Thus, a [[dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] in a [[data structure definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] could have different [[hierarchies>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] depending on the [[dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]].
  * //**Transformation Scheme:**// A transformation scheme is a set of [[Validation and Transformation Language>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] ([[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]]) transformations aimed at obtaining some meaningful results for the user (e.g., the validation of one or more [[data sets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]]). The set of transformations is meant to be executed together (in the same run) and may contain 597 any number of transformations in order to produce any number of results. Thus, a transformation scheme can be considered as a [[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] ‘program’.
@@ -273,7 +273,7 @@
  Web services allow computer applications to exchange data directly over the Internet, essentially allowing modular or distributed computing in a more flexible fashion than ever before. In order to allow web services to function, however, many standards are required: for requesting and supplying data; for expressing the enveloping data which is used to package exchanged data; for describing web services to one another, to allow for easy integration into applications that use other web services as data resources.
--Version 3.1 has standardized on RESTful web services with a OpenAPI specification published on the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] Technical Working Group’s GitHub repository  [[__https:~~/~~/github.com/sdmx-twg__>>https://https:github.comsdmx-twg||rel="noopener noreferrer" target="_blank"]].
++(% style="color:#e74c3c" %)Version(%%) 3.1 has standardized on RESTful web services with a OpenAPI specification published on the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] Technical Working Group’s GitHub repository  [[__https:~~/~~/github.com/sdmx-twg__>>https://https:github.comsdmx-twg||rel="noopener noreferrer" target="_blank"]].
  There are five ‘resources’:
@@ -290,15 +290,15 @@
  [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] provides a way of modelling statistical data, and defines the set of metadata constructs used for this purpose. Because [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] specifies a number of transmission formats for expressing data and [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]], the model is used as a mechanism for guaranteeing that transformation between the different formats is lossless. In this sense, all of the formats are syntax-bound expressions of the common information model.
--[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] recognizes that statistical data is structured; in [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] this structure is termed a [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]]. “[[Data sets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]]” are made up of one or more lower-level “groups”, based on their degrees of similarity. Each group is in turn comprised of one or more “[[series>>doc:sdmx:Glossary 2\.1.Series.WebHome]]” of data. Each [[series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] or section has a “key” - values for each of a cluster of concepts, also called "[[dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]]" - which identifies it, and one or more “observations”, which typically combine the time of the observation, and the value of the observation (e.g., measurement). Additionally, metadata may be attached at any level of this structure as descriptive “[[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]]”. [[Code lists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] (enumerations) and other patterns for [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] of data and metadata are also modelled.
++[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] recognizes that statistical data is structured; in [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] this structure is termed a [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]]. “[[Data sets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]]” are made up of one or more lower-(% style="color:#e74c3c" %)level(%%) “groups”, based on their degrees of similarity. Each group is in turn comprised of one or more “[[series>>doc:sdmx:Glossary 2\.1.Series.WebHome]]” of data. Each [[series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] or section has a “key” - values for each of a cluster of (% style="color:#e74c3c" %)concepts(%%), also called "[[dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]]" - which identifies it, and one or more “observations”, which typically combine the time of the observation, and the value of the observation (e.g., measurement). Additionally, metadata may be attached at any (% style="color:#e74c3c" %)level(%%) of this structure as descriptive “[[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]]”. [[Code lists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] (enumerations) and other patterns for [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] of data and metadata are also modelled.
--There is some similarity between “cube” structures commonly used to process statistical data, and the [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] idea in the [[SDMX Information Model>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]]. It is important to note that the data as structured according to the [[SDMX Information Model>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]] is optimized for exchange, potentially with partners who may have no ability to process a “cube” of data coming from complex statistical systems. [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] [[time series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] can be understood as “slices” of the cube. Such a slice is identified by its key. A "[[series>>doc:sdmx:Glossary 2\.1.Series.WebHome]]" key consists of the values for all [[dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] specified by the key family except time. Thus, it is possible to reconstruct and describe data cubes from [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]-structured data, and to exchange such databases using the interfaces and formats provided for that purpose in the standard. Additional objects such as [[hierarchical code lists>>doc:sdmx:Glossary 2\.1.Hierarchical code list.WebHome]], [[constraints>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]] and structure maps make it possible to more fully model the structure of cubes.
++There is some similarity between “cube” structures commonly used to process statistical data, and the [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] idea in the [[SDMX Information Model>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]]. It is important to note that the data as structured according to the [[SDMX Information Model>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]] is optimized for exchange, potentially with partners who may have no ability to process a “cube” of data coming from complex statistical systems. [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] [[time series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] can be understood as “slices” of the cube. Such a slice is identified by its key. A "[[series>>doc:sdmx:Glossary 2\.1.Series.WebHome]]" key consists of the values for all [[dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] specified by the key family except time. Thus, it is possible to reconstruct and describe data cubes from [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]-structured data, and to exchange such databases using the interfaces and formats provided for that purpose in the standard. Additional objects such as [[hierarchical code lists>>doc:sdmx:Glossary 2\.1.Hierarchical code list.WebHome]], (% style="color:#e74c3c" %)constraints(%%) and structure (% style="color:#e74c3c" %)maps(%%) make it possible to more fully model the structure of cubes.
--The information model also provides a view of [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]]: a mechanism for referencing the meaningful “objects” within the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] view of statistical exchange processes ([[data providers>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]], structures, [[provisioning agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]], [[dataflows>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]], [[metadata flows>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]], etc.) to which metadata is attached; a mechanism for describing a set of meaningful concepts, of organizing them into a presentational structure, and of indicating how their values are represented. This is based on a simple, hierarchical view of [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] which is common to many metadata systems and [[classification>>doc:sdmx:Glossary 2\.1.Statistical Classification.WebHome]]/categorization schemes. [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] provides a model (and XML and JSON formats) for both describing [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] structures, and of reporting [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] according to those structures.
++The information model also provides a view of [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]]: a mechanism for referencing the meaningful “objects” within the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] view of statistical exchange processes ([[data providers>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]], structures, [[provisioning agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]], [[dataflows>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]], [[metadata flows>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]], etc.) to which metadata is attached; a mechanism for describing a set of meaningful (% style="color:#e74c3c" %)concepts(%%), of organizing them into a presentational structure, and of indicating how their values are represented. This is based on a simple, hierarchical view of [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] which is common to many metadata systems and [[classification>>doc:sdmx:Glossary 2\.1.Statistical Classification.WebHome]]/categorization schemes. [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] provides a model (and XML and JSON formats) for both describing [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] structures, and of reporting [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] according to those structures.
--Version 2.0/2.1 introduced support for metadata related to the process aspects of statistical exchange. A step-by-step process can be modelled; information about who is providing data and [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] and how they are providing it can be expressed; and the technical aspects of service-level agreements (and similar types of [[provisioning agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]]) can be represented.
++(% style="color:#e74c3c" %)Version(%%) 2.0/2.1 introduced support for metadata related to the process aspects of statistical exchange. A step-by-step process can be modelled; information about who is providing data and [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] and how they are providing it can be expressed; and the technical aspects of service-(% style="color:#e74c3c" %)level(%%) agreements (and similar types of [[provisioning agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]]) can be represented.
--Support for the [[Validation and Transformation Language>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] ([[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]]) in the [[SDMX Information Model>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]] was introduced in the July 2020 revision of 2.1 and is retained in version 3.0 with minimal changes. This allows reusable [[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] ‘programs’ (a cohesive set of transformation statements designed to be executed together) and their associated constructs such as validation rulesets and user-defined operators to be managed and exchanged as [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]]. Mappings between objects such as [[data sets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] referenced in [[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] programs and the actual [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] to which they relate is essential when it comes to actually executing programs, and this information can also be defined. Chapter 7 has more information on [[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] and its integration with [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]].
++Support for the [[Validation and Transformation Language>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] ([[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]]) in the [[SDMX Information Model>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]] was introduced in the July 2020 revision of 2.1 and is retained in (% style="color:#e74c3c" %)version(%%) 3.0 with minimal changes. This allows reusable [[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] ‘programs’ (a cohesive set of transformation statements designed to be executed together) and their associated constructs such as validation rulesets and user-defined operators to be managed and exchanged as [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]]. Mappings between objects such as [[data sets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] referenced in [[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] programs and the actual [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] to which they relate is essential when it comes to actually executing programs, and this information can also be defined. Chapter 7 has more information on [[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] and its integration with [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]].
  A full UML conceptual design of the information model is set out in Section 2 of the Technical Specifications.
@@ -310,7 +310,7 @@
  There are four distinct types of message:
--1. //**Structure Definition**~:// For the exchange of [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]]. A [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] structure message can carry details of any number and combination of [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] like DSDs, [[code lists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] and [[constraints>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]].
++1. //**Structure Definition**~:// For the exchange of [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]]. A [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] structure message can carry details of any number and combination of [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] like DSDs, [[code lists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] and (% style="color:#e74c3c" %)constraints(%%).
 . //**Structure-specific Data**~:// For the exchange of data. This format is specific to the [[Data Structure Definitions>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] of the [[data sets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] (in other terms, it is [[DSD>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]]-specific) and is created by following mappings between the metadata constructs defined in the Structure Definition message and the technical specification of the format. It supports the exchange of large [[data sets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] in XML format, provides strict validation of conformance with the [[DSD>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] using a generic XML parser, and supports the transmission of partial [[data sets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] ([[incremental updates>>doc:sdmx:Glossary 2\.1.Incremental update.WebHome]]) as well as whole [[data sets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]].
  Many XML tools and technologies have expectations about the functions performed by an XML schema, one of which is a very direct relationship between the XML constructs described in the XML schema and the tagged data in the XML instance. Strong data typing is also considered normal, supporting full validation of the tagged data. These message types are designed to support validation and other expected XML schema functions.