Skip to Content
Last modified by Artur on 2025/09/30 12:30
From version 15.5
edited by Helena
on 2025/06/06 17:31
Change comment: There is no comment for this version
To version 13.4
edited by Helena
on 2025/06/06 17:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -153,27 +153,6 @@
153 153  
154 154  The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards specified here are designed to support the requirements of all of these automation processes and technologies.
155 155  
156 -= 3 Processes and Business Scope =
157 -
158 -== 3.1 Process Patterns ==
159 -
160 -[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] identifies three basic process patterns regarding the exchange of statistical data and metadata. These can be described as follows:
161 -
162 -1. //**Bilateral exchange**~:// All aspects of the exchange process are agreed between counterparties, including the mechanism for exchange of data and metadata, the formats, the frequency or schedule, and the mode used for communications regarding the exchange. This is perhaps the most common process pattern.
163 -1. //**Gateway exchange**~:// Gateway exchanges are an organized set of bilateral exchanges, in which several data and metadata collecting organizations or individuals agree to exchange the collected information with each other in a single, known format, and according to a single, known process. This pattern has the effect of reducing the burden of managing multiple bilateral exchanges (in data and metadata collection) across the sharing organizations/individuals. This is also a very common process pattern in the statistical area, where communities of institutions agree on ways to gain efficiencies within the scope of their collective responsibilities.
164 -1. //**Data-sharing exchange**~:// Open, freely available data formats and process patterns are known and standard. Thus, any organization or individual can use any counterparty’s data and metadata (assuming they are permitted access to it). This model requires no bilateral agreement, but only requires that data and metadata providers and consumers adhere to the standards.
165 -
166 -== 3.2 SDMX and Process Automation ==
167 -
168 -Statistical data and metadata exchanges employ many different automated processes, but some are of more general interest than others. There are some common information technologies that are nearly ubiquitous within information systems today. [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] aims to provide standards that are most useful for these automated processes and technologies.
169 -
170 -Briefly, these can be described as:
171 -
172 -1. //**Batch Exchange of Data and Metadata**~:// The transmission of whole or partial databases between counterparties, including incremental updating.
173 -1. //**Provision of Data and Metadata on the Internet**~:// Internet technology - including its use in private or semi-private TCP/IP networks - is extremely common. This technology includes XML, JSON and REST web services as primary mechanisms for automating data and metadata provision, as well as the more traditional static HTML and database-driven publishing.
174 -1. //**Generic Processes**~:// While many applications and processes are specific to some set of data and metadata, other types of automated services and processes are designed to handle any type of statistical data and metadata whatsoever. This is particularly true in cases where portal sites and data feeds are made available on the Internet.
175 -1. //**Presentation and Transformation of Data**~:// In order to make data and metadata useful to consumers, they must support automated processes that transform them into application-specific processing formats, other standard formats, and presentational formats. Although not strictly an aspect of exchange, this type of automated processing represents a set of requirements that must be supported if the information exchange between counterparties is itself to be supported.
176 -
177 177  == 3.3 Statistical Data and Metadata ==
178 178  
179 179  To avoid confusion about which "data" and "metadata" are the intended content of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] formats specified here, a statement of scope is offered. Statistical "data" are sets of often numeric observations which typically have time associated with them. They are associated with a set of metadata values, representing specific (% style="color:#e74c3c" %)concepts(%%), which act as identifiers and descriptors of the data. These metadata values and (% style="color:#e74c3c" %)concepts(%%) can be understood as the named [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] of a multi-dimensional co-ordinate system, describing what is often called a "cube" of data.
... ... @@ -204,8 +204,25 @@
204 204  
205 205  It is important to note that [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] is primarily focused on the //exchange// and //dissemination// of statistical data and metadata. There may also be many uses for the standard model and formats specified here in the context of internal processing of data that are not concerned with the exchange between organizations and users, however. It is felt that a clear, standard formatting of data and metadata for the purposes of exchange and dissemination can also facilitate internal processing by organizations and users, but this is not the focus of the specification.
206 206  
207 -[[image:SDMX%203.1%20Section%201.png]]
186 +== 3.2 SDMX and Process Automation ==
208 208  
188 +Statistical data and metadata exchanges employ many different automated processes, but some are of more general interest than others. There are some common information technologies that are nearly ubiquitous within information systems today. [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] aims to provide standards that are most useful for these automated processes and technologies.
189 +
190 +Briefly, these can be described as:
191 +
192 +//Batch Exchange of Data and Metadata~:// The transmission of whole or partial databases between counterparties, including incremental updating. //Provision of Data and Metadata on the Internet~:// Internet technology - including its use in private or semi-private TCP/IP networks - is extremely common. This technology includes XML, JSON and REST web services as primary mechanisms for automating data and metadata provision, as well as the more traditional static HTML and database-driven publishing. //Generic Processes~:// While many applications and processes are specific to some set of data and metadata, other types of automated services and processes are designed to handle any type of statistical data and metadata whatsoever. This is particularly true in cases where portal sites and data feeds are made available on the Internet. //Presentation and Transformation of Data~:// In order to make data and metadata useful to consumers, they must support automated processes that transform them into application-specific processing formats, other standard formats, and presentational formats. Although not strictly an aspect of exchange, this type of automated processing represents a set of requirements that must be supported if the information exchange between counterparties is itself to be supported.
193 +
194 += 3 Processes and Business Scope =
195 +
196 +== 3.1 Process Patterns ==
197 +
198 +[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] identifies three basic process patterns regarding the exchange of statistical data and metadata. These can be described as follows:
199 +
200 +//Bilateral exchange~:// All aspects of the exchange process are agreed between counterparties, including the mechanism for exchange of data and metadata, the formats, the frequency or schedule, and the mode used for communications regarding the exchange. This is perhaps the most common process pattern. //Gateway exchange~:// Gateway exchanges are an organized set of bilateral exchanges, in which several data and metadata collecting organizations or individuals agree to exchange the collected information with each other in a single, known format, and according to a single, known process. This pattern has the effect of reducing the burden of managing multiple bilateral exchanges (in data and metadata collection) across the sharing organizations/individuals. This is also a very common process pattern in the statistical area, where communities of institutions agree on ways to gain efficiencies within the scope of their collective responsibilities. //Data-sharing exchange~:// Open, freely available data formats and process patterns are known and standard. Thus, any organization or individual can use any counterparty’s data and metadata (assuming they are permitted access to it). This model requires no bilateral agreement, but only requires that data and metadata providers and consumers adhere to the standards.
201 +
202 +
203 +[[image:SDMX 3.1 Section 1.png]]
204 +
209 209  **Figure 1: High Level Schematic of Major Artefacts in the SDMX 3.0 Information Model**
210 210  
211 211  == 3.4 The SDMX View of Statistical Exchange ==
... ... @@ -242,15 +242,15 @@
242 242  * //**[[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] (Metadata [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]):**// The set of information which describes the way in which [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] are provided by a data/metadata provider. A [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] can be constrained in much the same way as a data or [[metadata flow>>doc:sdmx:Glossary.Metadataflow.WebHome]] definition. Thus, a [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]] can express the fact that it provides a particular [[data flow>>doc:sdmx:Glossary.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.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.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.Provision agreement.WebHome]] and data [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] are two separate artefacts.
243 243  * //**Data (% style="color:#e74c3c" %)Constraint(%%):**// Used to restrict content (such as enumerations) and are used by [[provision agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]], [[data flows>>doc:sdmx:Glossary.Dataflow.WebHome]], [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]] in order to provide a set of reporting restrictions in the context of a collection
244 244  * //**Metadata (% style="color:#e74c3c" %)Constraint(%%):**// Used to restrict content (such as enumerations) and are used by metadata [[provision agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]], [[metadata flows>>doc:sdmx:Glossary.Metadataflow.WebHome]], [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] in order to provide a set of reporting restrictions in the context of a collection
245 -* //**Available Data (% style="color:#e74c3c" %)Constraint(%%):**// Used to report the set of [[Component>>doc:sdmx:Glossary.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.
246 -* //**Structure (% style="color:#e74c3c" %)Map(%%): **//Structure (% style="color:#e74c3c" %)maps(%%) describes a mapping between [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] for the purpose of transforming a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] into a different structure. The mapping rules are defined using one or more [[component>>doc:sdmx:Glossary.Component.WebHome]] (% style="color:#e74c3c" %)maps(%%) which each (% style="color:#e74c3c" %)map(%%) in turn describes how one or more [[components>>doc:sdmx:Glossary.Component.WebHome]] from the source [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] (% style="color:#e74c3c" %)map(%%) to one or more [[components>>doc:sdmx:Glossary.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.
247 -* //**[[Representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)Map(%%):**// [[Representation>>doc:sdmx:Glossary.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.Code list.WebHome]], value list or be of a certain type such as integer or string.
248 -* //**[[Item Scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] (% style="color:#e74c3c" %)Map(%%):**// An [[item scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] (% style="color:#e74c3c" %)map(%%) describes mapping rules between any [[item scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] with the exception of [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] and value lists which use [[representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)maps(%%). The (% style="color:#e74c3c" %)version(%%) 3.0 information model provides four [[item scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] (% style="color:#e74c3c" %)maps(%%): organisation scheme (% style="color:#e74c3c" %)map(%%), [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] (% style="color:#e74c3c" %)map(%%), [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] (% style="color:#e74c3c" %)map(%%) and [[reporting taxonomy>>doc:sdmx:Glossary.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.
249 -* //**[[Reporting Taxonomy>>doc:sdmx:Glossary.Reporting taxonomy.WebHome]]: **//A [[reporting taxonomy>>doc:sdmx:Glossary.Reporting taxonomy.WebHome]] allows an organisation to link (possibly in a hierarchical way) a number of cube or [[data flow>>doc:sdmx:Glossary.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.
250 -* //**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.Reference metadata.WebHome]] sets which describe processes-related (% style="color:#e74c3c" %)concepts(%%).
251 -* //**[[Hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]**//: Describes complex [[code>>doc:sdmx:Glossary.Code.WebHome]] [[hierarchies>>doc:sdmx:Glossary.Hierarchy.WebHome]] principally for data discovery purposes. The [[codes>>doc:sdmx:Glossary.Code.WebHome]] themselves are referenced from the [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] in which they are maintained.
252 -* //**[[Hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] Association**//: A [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] association links a [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] to something that needs it like a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]. Furthermore, the linking can be specified in the context of another object such as a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] in the context of a [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]. Thus, a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] in a [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] could have different [[hierarchies>>doc:sdmx:Glossary.Hierarchy.WebHome]] depending on the [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]].
253 -* //**Transformation Scheme:**// A transformation scheme is a set of [[Validation and Transformation Language>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] ([[VTL>>doc:sdmx:Glossary.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.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.Validation and transformation language.WebHome]] ‘program’.
241 +* • //**Available Data (% style="color:#e74c3c" %)Constraint(%%):**// Used to report the set of [[Component>>doc:sdmx:Glossary.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.
242 +* • //**Structure (% style="color:#e74c3c" %)Map(%%): **//Structure (% style="color:#e74c3c" %)maps(%%) describes a mapping between [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] for the purpose of transforming a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] into a different structure. The mapping rules are defined using one or more [[component>>doc:sdmx:Glossary.Component.WebHome]] (% style="color:#e74c3c" %)maps(%%) which each (% style="color:#e74c3c" %)map(%%) in turn describes how one or more [[components>>doc:sdmx:Glossary.Component.WebHome]] from the source [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] (% style="color:#e74c3c" %)map(%%) to one or more [[components>>doc:sdmx:Glossary.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.
243 +* • //**[[Representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)Map(%%):**// [[Representation>>doc:sdmx:Glossary.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.Code list.WebHome]], value list or be of a certain type such as integer or string.
244 +* • //**[[Item Scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] (% style="color:#e74c3c" %)Map(%%):**// An [[item scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] (% style="color:#e74c3c" %)map(%%) describes mapping rules between any [[item scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] with the exception of [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] and value lists which use [[representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)maps(%%). The (% style="color:#e74c3c" %)version(%%) 3.0 information model provides four [[item scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] (% style="color:#e74c3c" %)maps(%%): organisation scheme (% style="color:#e74c3c" %)map(%%), [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] (% style="color:#e74c3c" %)map(%%), [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] (% style="color:#e74c3c" %)map(%%) and [[reporting taxonomy>>doc:sdmx:Glossary.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.
245 +* • //**[[Reporting Taxonomy>>doc:sdmx:Glossary.Reporting taxonomy.WebHome]]: **//A [[reporting taxonomy>>doc:sdmx:Glossary.Reporting taxonomy.WebHome]] allows an organisation to link (possibly in a hierarchical way) a number of cube or [[data flow>>doc:sdmx:Glossary.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.
246 +* • //**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.Reference metadata.WebHome]] sets which describe processes-related (% style="color:#e74c3c" %)concepts(%%).
247 +* • //**[[Hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]**//: Describes complex [[code>>doc:sdmx:Glossary.Code.WebHome]] [[hierarchies>>doc:sdmx:Glossary.Hierarchy.WebHome]] principally for data discovery purposes. The [[codes>>doc:sdmx:Glossary.Code.WebHome]] themselves are referenced from the [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] in which they are maintained.
248 +* • //**[[Hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] Association**//: A [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] association links a [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] to something that needs it like a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]. Furthermore, the linking can be specified in the context of another object such as a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] in the context of a [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]. Thus, a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] in a [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] could have different [[hierarchies>>doc:sdmx:Glossary.Hierarchy.WebHome]] depending on the [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]].
249 +* • //**Transformation Scheme:**// A transformation scheme is a set of [[Validation and Transformation Language>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] ([[VTL>>doc:sdmx:Glossary.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.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.Validation and transformation language.WebHome]] ‘program’.
254 254  
255 255  == 3.5 SDMX Registry Services ==
256 256  
... ... @@ -308,13 +308,13 @@
308 308  
309 309  There are four distinct types of message:
310 310  
311 -1. //**Structure Definition**~:// For the exchange of [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. A [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] structure message can carry details of any number and combination of [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] like DSDs, [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] and (% style="color:#e74c3c" %)constraints(%%).
312 -1. //**Structure-specific Data**~:// For the exchange of data. This format is specific to the [[Data Structure Definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]] of the [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] (in other terms, it is [[DSD>>doc:sdmx:Glossary.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.Data set.WebHome]] in XML format, provides strict validation of conformance with the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] using a generic XML parser, and supports the transmission of partial [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] ([[incremental updates>>doc:sdmx:Glossary.Incremental update.WebHome]]) as well as whole [[data sets>>doc:sdmx:Glossary.Data set.WebHome]].
307 +1. //Structure Definition~:// For the exchange of [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. A [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] structure message can carry details of any number and combination of [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] like DSDs, [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] and (% style="color:#e74c3c" %)constraints(%%).
308 +1. //Structure-specific Data~:// For the exchange of data. This format is specific to the [[Data Structure Definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]] of the [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] (in other terms, it is [[DSD>>doc:sdmx:Glossary.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.Data set.WebHome]] in XML format, provides strict validation of conformance with the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] using a generic XML parser, and supports the transmission of partial [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] ([[incremental updates>>doc:sdmx:Glossary.Incremental update.WebHome]]) as well as whole [[data sets>>doc:sdmx:Glossary.Data set.WebHome]].
313 313  
314 314  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.
315 315  
316 -1. //**Generic Metadata**~:// For the exchange of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] sets. ‘Generic’ means the XML elements and XML [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] are the same regardless of the metadata set.
317 -1. //**Registry**~:// All of the possible interactions with the [[SDMX registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] services are supported using [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] interfaces and REST API calls. Submission of [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] content, data registrations and [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] is performed by a synchronous exchange of documents – a “request” message answered by a “response” message.
312 +1. //Generic Metadata~:// For the exchange of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] sets. ‘Generic’ means the XML elements and XML [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] are the same regardless of the metadata set.
313 +1. //Registry~:// All of the possible interactions with the [[SDMX registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] services are supported using [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] interfaces and REST API calls. Submission of [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] content, data registrations and [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] is performed by a synchronous exchange of documents – a “request” message answered by a “response” message.
318 318  
319 319  == 5.2 SDMX-JSON ==
320 320  
... ... @@ -326,8 +326,8 @@
326 326  
327 327  There are three distinct message types:
328 328  
329 -1. //**Structure**~:// For the exchange [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] structure messages follow the same principles as for [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] in that a single message can transmit any number and combination of [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]]. While the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] messages are structured differently, it is possible to freely convert between them.
330 -1. //**Data**: //For the exchange of data. Unlike [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]], the structure of a [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] data message is not specific to the DSDs of the [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] so schema validation will not check for compliance of the data with the DSDs.
325 +1. //Structure~:// For the exchange [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] structure messages follow the same principles as for [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] in that a single message can transmit any number and combination of [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]]. While the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] messages are structured differently, it is possible to freely convert between them.
326 +1. //Data: //For the exchange of data. Unlike [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]], the structure of a [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] data message is not specific to the DSDs of the [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] so schema validation will not check for compliance of the data with the DSDs.
331 331  1. //Metadata//: For the exchange of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] sets.
332 332  
333 333  == 5.3 SDMX-CSV ==
... ... @@ -372,8 +372,10 @@
372 372  
373 373  The Metadata Common Vocabulary is an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] guideline which provides definition of terms to be used for the comparison and mapping of terminology found in [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]] and in other aspects of statistical metadata management. Essentially, it provides ISOcompliant definitions for a wide range of statistical terms, which may be used directly, or against which other terminology systems may be (% style="color:#e74c3c" %)mapped(%%). This set of terms is inclusive of the terminology used within the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Technical Standards.
374 374  
375 -The MCV provides definitions for terms on which the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Cross-Domain Metadata (% style="color:#e74c3c" %)Concepts(%%) work is built.
371 +The MCV provides definitions for terms on which the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Cross-Domain Metadata
376 376  
373 +(% style="color:#e74c3c" %)Concepts(%%) work is built.
374 +
377 377  == 6.3 Statistical Subject-Matter Domains ==
378 378  
379 379  The [[Statistical Subject-Matter Domains>>doc:sdmx:Glossary.Statistical subject-matter domain.WebHome]] is a listing of the breadth of statistical information for the purposes of organizing widespread statistical exchange and categorization. It acts as a standard scheme against which the categorization schemes of various counterparties can be (% style="color:#e74c3c" %)mapped(%%), to facilitate interoperable data and metadata exchange. It serves another useful purpose, however, which is to allow an organization of corresponding “domain groups”, each of which could define standard [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]], (% style="color:#e74c3c" %)concepts(%%), etc. within their domains. Such groups already exist within the international community. [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] would use the [[Statistical Subject-Matter Domains>>doc:sdmx:Glossary.Statistical subject-matter domain.WebHome]] list to facilitate the efforts of these groups to develop the kinds of content standards which could support the interoperation of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-conformant technical systems within and across [[statistical domains>>doc:sdmx:Glossary.Statistical subject-matter domain.WebHome]]. The organisation of the content of such schemes is supported in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] as a [[Category>>doc:sdmx:Glossary.Category.WebHome]] Scheme.
SDMX%203.1%20Section%201.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -101.7 KB
Content