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

From version 36.23
edited by Helena K.
on 2026/06/08 13:29
Change comment: There is no comment for this version
To version 36.22
edited by Helena K.
on 2026/06/08 13:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -249,7 +249,7 @@
249 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 list>>doc:sdmx:Glossary 2\.1.Code list.WebHome]], value list or be of a certain type such as integer or string.
250 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 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.
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 lists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] 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||rel="noopener noreferrer" target="_blank"]].
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||rel="noopener noreferrer" target="_blank"]].
277 277  
278 278  There are five ‘resources’:
279 279  
... ... @@ -290,7 +290,7 @@
290 290  
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 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.
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-(% 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.
294 294  
295 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 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.
296 296  
© Semantic R&D Group, 2026