Changes for page SDMX 3.1 Standards. Section 1. Framework
Last modified by Helena K. on 2026/06/08 15:16
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -64,7 +64,7 @@ 64 64 65 65 * **[[Reference Metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]]**: In addition to describing and specifying data structures and formats (along with related [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]]), the version 2.0 specification also provides for the exchange of metadata which is distinct from the [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] in the 1.0 version. This [[category>>doc:sdmx:Glossary 2\.1.Category.WebHome]] includes “reference” metadata (regarding data quality, methodology, and similar types – it can be configured by the user to include whatever concepts require reporting); metadata related to data provisioning ([[release calendar>>doc:sdmx:Glossary 2\.1.Release policy - release calendar.WebHome]] information, description of the data and metadata provided, etc.); and metadata relevant to the exchange of categorization schemes. 66 66 * **[[SDMX Registry>>doc:sdmx:Glossary 2\.1.SDMX Registry.WebHome]]**: Provision is made in the 2.0 standard for standard communication with registry services, to support a data-sharing model of statistical exchange. These services include registration of data and metadata, querying of registered data and metadata, and [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]]/[[notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]]. 67 -* **[[Structural Metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]]**: The support for exchange of statistical data and related [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] has been expanded. Some support is provided for qualitative data; data cube structures are described; [[hierarchical code lists>>doc:sdmx:Glossary 2\.1.Hierarchical codelist.WebHome]] are supported; relationships between data structures can be expressed, providing support for extensibility of data structures; and the description of functional dependencies within cubes are supported.67 +* **[[Structural Metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]]**: The support for exchange of statistical data and related [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] has been expanded. Some support is provided for qualitative data; data cube structures are described; [[hierarchical code>>doc:sdmx:Glossary 2\.1.Hierarchical code.WebHome]] lists are supported; relationships between data structures can be expressed, providing support for extensibility of data structures; and the description of functional dependencies within cubes are supported. 68 68 69 69 == 2.2 Major Changes from 2.0 to 2.1 == 70 70 ... ... @@ -78,7 +78,7 @@ 78 78 * **Support for Non-Time-[[Series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] Data in the Generic Format: **One area which has been extended is the ability to express non-time-[[series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] data as part of the generic data message. 79 79 * **Simplification of the [[data structure definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] - specific message types: **Both [[time series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] (version 2.0 Compact) and non-[[time series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] [[data sets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] (version 2.0 Cross Sectional) use the same underlying structure for a structure-specific formatted message, which is specific to the [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] of the [[data set>>doc:sdmx:Glossary 2\.1.Data set.WebHome]]. 80 80 * **Simplification and better support for the metadata structure: **New use cases have been reported and these are now supported by a re-modelled [[metadata structure definition>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]]. 81 -* **Support for partial [[item schemes>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] such as a [[code list>>doc:sdmx:Glossary 2\.1.Codelist.WebHome]]: **The concept of a partial (subset) [[item scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] such as a partial [[codelist>>doc:sdmx:Glossary 2\.1.Codelist.WebHome]] for use in exchange scenarios has been introduced**.**81 +* **Support for partial [[item schemes>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] such as a [[code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] list: **The concept of a partial (subset) [[item scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] such as a partial [[code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] list for use in exchange scenarios has been introduced**.** 82 82 83 83 == 2.3 Major Changes from 2.1 to 3.0 == 84 84 ... ... @@ -137,7 +137,7 @@ 137 137 (% class="wikigeneratedid" id="HInformationModel-1" %) 138 138 **Information Model** 139 139 140 -* Addition of [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] [[Constraint>>doc:sdmx:Glossary2\.1.Constraint.WebHome]]property to a [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]]140 +* Addition of [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] Constraint property to a [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] 141 141 * Addition of evolving structure property to a [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] 142 142 * Remove [[version>>doc:sdmx:Glossary 2\.1.Version.WebHome]] property on [[Categorisation>>doc:sdmx:Glossary 2\.1.Categorisation.WebHome]] 143 143 * Simplification of [[Constraints>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]] ... ... @@ -241,15 +241,15 @@ 241 241 * //**[[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]]. 242 242 * //**[[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]]. 243 243 * //**Metadata Provider: **//An organization which produces [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] is termed a metadata provider. 244 -* //**[[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]]. 244 +* //**[[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 (% 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]]. 245 245 * //**Data [[Constraint>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]]:**// 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 246 246 * //**Metadata [[Constraint>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]]:**// 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 247 247 * //**Available Data [[Constraint>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]]:**// 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. 248 -* //**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. 249 -* //**[[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>>doc:sdmx:Glossary 2\.1.Code.WebHome]] list, value list or be of a certain type such as integer or string. 250 -* //**[[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>>doc:sdmx:Glossary 2\.1.Code.WebHome]] lists 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. 248 +* //**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]] (% 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. 249 +* //**[[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>>doc:sdmx:Glossary 2\.1.Code.WebHome]] list, value list or be of a certain type such as integer or string. 250 +* //**[[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>>doc:sdmx:Glossary 2\.1.Code.WebHome]] lists 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. 251 251 * //**[[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. 252 -* //**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. 252 +* //**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(%%). 253 253 * //**[[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>>doc:sdmx:Glossary 2\.1.Code.WebHome]] lists in which they are maintained. 254 254 * //**[[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]]. 255 255 * //**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 @@ 273 273 274 274 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. 275 275 276 -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]]. 276 +(% 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]]. 277 277 278 278 There are five ‘resources’: 279 279 ... ... @@ -288,17 +288,18 @@ 288 288 289 289 = 4 The SDMX Information Model = 290 290 291 + 291 291 [[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. 292 292 293 -[[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>>doc:sdmx:Glossary 2\.1.Code.WebHome]] lists (enumerations) and other patterns for [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] of data and metadata are also modelled. 294 +[[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>>doc:sdmx:Glossary 2\.1.Code.WebHome]] lists (enumerations) and other patterns for [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] of data and metadata are also modelled. 294 294 295 -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>>doc:sdmx:Glossary 2\.1.Hierarchical code.WebHome]] lists, [[constraints>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]] and structure maps make it possible to more fully model the structure of cubes. 296 +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>>doc:sdmx:Glossary 2\.1.Hierarchical code.WebHome]] lists, [[constraints>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]] and structure (% style="color:#e74c3c" %)maps(%%) make it possible to more fully model the structure of cubes. 296 296 297 -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. 298 +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. 298 298 299 -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. 300 +(% 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. 300 300 301 -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]]. 302 +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]]. 302 302 303 303 A full UML conceptual design of the information model is set out in Section 2 of the Technical Specifications. 304 304 ... ... @@ -306,6 +306,7 @@ 306 306 307 307 == 5.1 SDMX-ML == 308 308 310 + 309 309 [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] is the XML transmission format specification for exchanging [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]], data and [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]], and interacting with [[SDMX registry>>doc:sdmx:Glossary 2\.1.SDMX Registry.WebHome]] services. It is designed as a general-purpose format for all automation and data / metadata exchange tasks, and provides the most complete [[coverage>>doc:sdmx:Glossary 2\.1.Coverage.WebHome]]. 310 310 311 311 There are four distinct types of message: ... ... @@ -320,6 +320,7 @@ 320 320 321 321 == 5.2 SDMX-JSON == 322 322 325 + 323 323 [[SDMX-JSON>>doc:sdmx:Glossary 2\.1.SDMX-JSON.WebHome]] is the JSON transmission format specification for exchanging [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]], data and [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]]. It provides an alternative to [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] and is most suited to applications like web data dissemination. 324 324 325 325 [[SDMX-JSON>>doc:sdmx:Glossary 2\.1.SDMX-JSON.WebHome]] messages serve the same function as those of the XML formats but have a different structure. For data, an important distinction is that they carry both [[component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] [[codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] and labels which provides all the information needed to display the content in a single JSON response. The XML Structure-specific Data format by contrast carries only [[code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] IDs thus requiring applications obtain and hold [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] about the [[data set>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] in order to display the content in human-readable form. ... ... @@ -334,6 +334,7 @@ 334 334 335 335 == 5.3 SDMX-CSV == 336 336 340 + 337 337 [[SDMX-CSV>>doc:sdmx:Glossary 2\.1.SDMX-CSV.WebHome]] is the CSV transmission format specification for exchanging data and [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] only. 338 338 339 339 [[SDMX-CSV>>doc:sdmx:Glossary 2\.1.SDMX-CSV.WebHome]] provides a simple columnar format for data and metadata that can be readily created and interpreted by standard software tools such as Microsoft Excel. Nevertheless, data and metadata can still be converted between the CSV and the JSON / XML formats without loss. ... ... @@ -345,7 +345,7 @@ 345 345 346 346 == 5.4 Formats and Messages Deprecated in Version 3.0 == 347 347 348 -The following formats and messages have been deprecated in version 3.0 to simplify, modernise and rationalise the standard. 352 +The following formats and messages have been deprecated in (% style="color:#e74c3c" %)version(%%) 3.0 to simplify, modernise and rationalise the standard. 349 349 350 350 * [[SDMX-EDI>>doc:sdmx:Glossary 2\.1.SDMX-EDI.WebHome]] 351 351 * [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] 1.0/2.0 Generic (time-[[series>>doc:sdmx:Glossary 2\.1.Series.WebHome]]) data message ... ... @@ -355,7 +355,7 @@ 355 355 * [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] 2.1 Generic ([[Time Series>>doc:sdmx:Glossary 2\.1.Series.WebHome]]) data messages (for observations, time-[[series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] and cross-sectional data) 356 356 * [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] 2.1 Structure Specific [[Time Series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] data message 357 357 358 -The following messages were deprecated in version 3.0 as a consequence of the deprecation of the SOAP web services: 362 +The following messages were deprecated in (% style="color:#e74c3c" %)version(%%) 3.0 as a consequence of the deprecation of the SOAP web services: 359 359 360 360 * [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] Query messages 361 361 * [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] Submit Structure Request messages ... ... @@ -390,7 +390,7 @@ 390 390 391 391 For many years the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] initiative has been fostering and supporting the development of a standard calculation [[language>>doc:sdmx:Glossary 2\.1.Language.WebHome]], called [[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]]). A blueprint for defining calculations was already described in the original [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] 2.1 specifications (package 13 of the Information Model - “Transformations and Expressions”). It was just a basic framework that required further developments to became operational in order to achieve a calculation [[language>>doc:sdmx:Glossary 2\.1.Language.WebHome]] able to manipulate [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]]. 392 392 393 -These developments started in late 2012 and were put in charge of the [[Validation and Transformation Language>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] Task Force ([[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] TF), which included members of the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] Technical Working Group (TWG) and Statistical Working Group (SWG), besides experts coming from the DDI and GSIM communities. The intent was to define a standard [[language>>doc:sdmx:Glossary 2\.1.Language.WebHome]] to be implemented in [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] and applicable also to GSIM and DDI. This brought to the publication of the [[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] 1.0 in 2015. Then new requirements came from a number of proofs of concepts and tests of [[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] 1.0 made by several organisations and triggered a large improvement of the [[language>>doc:sdmx:Glossary 2\.1.Language.WebHome]]. A new provisional version, the [[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] 1.1, was released in public consultation in 2017. The high number of [[comments>>doc:sdmx:Glossary 2\.1.Comment.WebHome]] received triggered another phase of intensive work, with the main goal of achieving a more robust and forward compatible version. Finally, the [[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] 2.0 was published between April and July 2018 (see the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] website). 397 +These developments started in late 2012 and were put in charge of the [[Validation and Transformation Language>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] Task Force ([[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] TF), which included members of the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] Technical Working Group (TWG) and Statistical Working Group (SWG), besides experts coming from the DDI and GSIM communities. The intent was to define a standard [[language>>doc:sdmx:Glossary 2\.1.Language.WebHome]] to be implemented in [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] and applicable also to GSIM and DDI. This brought to the publication of the [[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] 1.0 in 2015. Then new requirements came from a number of proofs of (% style="color:#e74c3c" %)concepts(%%) and tests of [[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] 1.0 made by several organisations and triggered a large improvement of the [[language>>doc:sdmx:Glossary 2\.1.Language.WebHome]]. A new provisional (% style="color:#e74c3c" %)version(%%), the [[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] 1.1, was released in public consultation in 2017. The high number of [[comments>>doc:sdmx:Glossary 2\.1.Comment.WebHome]] received triggered another phase of intensive work, with the main goal of achieving a more robust and forward compatible (% style="color:#e74c3c" %)version(%%). Finally, the [[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] 2.0 was published between April and July 2018 (see the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] website). 394 394 395 395 The implementation of the [[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] 2.0 in [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] started in late 2018 and was published as an incremental revision to the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] 2.1 standards in July 2020. It allows users to write [[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] 2.0 programs for validating and transforming [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] data, to store these programs in a [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] metadata registry and to exchange them through [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] messages, also together the definition of the data structures of the involved data. 396 396