Skip to Content
Last modified by Artur on 2025/09/30 12:30
From version 14.4
edited by Helena
on 2025/06/06 17:27
Change comment: There is no comment for this version
To version 13.2
edited by Helena
on 2025/06/06 17:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -98,7 +98,7 @@
98 98  (% class="wikigeneratedid" id="HVersioningofStructuralMetadataArtefacts" %)
99 99  **Versioning of Structural Metadata Artefacts**
100 100  
101 -Adoption of the three-number semantic versioning standard for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] ([[__https:~~/~~/semver.org__>>https://https:semver.org]])
101 +* Adoption of the three-number semantic versioning standard for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] ([[__https:~~/~~/semver.org__>>https://https:semver.org]])
102 102  
103 103  (% class="wikigeneratedid" id="HRESTWebServicesApplicationProgrammingInterface28API29" %)
104 104  **REST Web Services Application Programming Interface (API)**
... ... @@ -108,60 +108,39 @@
108 108  * Improvements to [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] queries
109 109  * Support for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] maintenance using HTTP PUT, POST and DELETE verbs
110 110  
111 -(% class="wikigeneratedid" id="HSOAPWebServicesAPI" %)
112 -**SOAP Web Services API**
113 113  
114 -* The SOAP web services API has been deprecated with (% style="color:#e74c3c" %)version(%%) 3.0 standardising on REST
115 115  
116 -(% class="wikigeneratedid" id="HXML2CJSON2CCSVandEDITransmissionformats" %)
117 -**XML, JSON, CSV and EDI Transmission formats**
113 +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.
118 118  
119 -The [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]], [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] and [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-CSV specifications have been extended and modified where needed to support the new features and changes such as [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] and microdata Obsolete [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] data message variants including Generic, Compact, Utility and Cross-sectional have been deprecated standardising on Structure Specific Data as the sole XML format for data exchange The [[SDMX-EDI>>doc:sdmx:Glossary.SDMX-EDI.WebHome]] transmission format for structures and data has been deprecated The organisation of structures into ‘collections’ in [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] structure messages has been flattened and simplified The option to reference structures in [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] messages using Agency, ID and (% style="color:#e74c3c" %)Version(%%) has been deprecated with URN now exclusively used for all non-local referencing purpose
115 +== 3.3 Statistical Data and Metadata ==
120 120  
121 -Several of the changes are ‘breaking’ meaning that, in specific cases, the (% style="color:#e74c3c" %)version(%%) 3.0 specification is not backwardly compatible with earlier (% style="color:#e74c3c" %)versions(%%) of the Standard.
117 +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.
122 122  
123 -The principle breaking changes are:
119 +[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] identifies a standard technique for modelling, expressing, and understanding the structure of this multi-dimensional "cube", allowing automated processing of data from a variety of sources. This approach is widely applicable across types of data and attempts to provide the simplest and most easily comprehensible technique that will support the exchange of this broad set of data and related metadata.
124 124  
125 -* REST API – The REST API is not backwardly compatible due to modifications to the URLs and query parameters resulting in breaking changes in four of the five main resources.
126 -* SOAP API – Deprecation of the SOAP API means that existing systems designed to use SOAP will not work with (% style="color:#e74c3c" %)version(%%) 3.0 registries.
127 -* [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] – [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 and earlier structure, data and metadata XML messages are not valid in (% style="color:#e74c3c" %)version(%%) 3.0. Specifically: legacy data messages including Generic, Compact and Utility are no longer supported. The remaining Structure Specific data message has been changed to support new features such as reporting of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] as part of the [[dataset>>doc:sdmx:Glossary.Data set.WebHome]], Structure messages have a number of breaking changes, principally modification to the information model, removal of the agency-(% style="color:#e74c3c" %)version(%%)-id option for referencing [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] and changes to the way the structures are organised into ‘collections’ within the message.
128 -* [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] – [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 structure, data and metadata JSON messages are not valid in (% style="color:#e74c3c" %)version(%%) 3.0. The data message has been changed to support the improved REST data queries, in particular the ability to retrieve in one operation data from multiple [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] with potentially different [[Data Structure Definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]]. Breaking changes similar to those for the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] transmission format have been made to the structure message.
129 -* [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-CSV - The CSV data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] messages are not backwardly compatible with those under (% style="color:#e74c3c" %)version(%%) 2.1 due to changes to the structure of the messages needed to support new features such as the improved REST API data queries.
130 -* [[SDMX-EDI>>doc:sdmx:Glossary.SDMX-EDI.WebHome]] – Deprecation of the EDI transmission format means that existing systems designed to send or receive structures or data in EDI will not work with (% style="color:#e74c3c" %)version(%%) 3.0 registries.
131 -* Information Model – Several structures have been changed in the (% style="color:#e74c3c" %)version(%%) 3.0 model and three removed. For these reasons the (% style="color:#e74c3c" %)version(%%) 3.0 model is not directly compatible with (% style="color:#e74c3c" %)version(%%) 2.1 or earlier, although conversion of specific [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] is possible under some circumstances. Loss of information during the conversion process however means that in cases like structure mapping, the conversion is not reversible i.e. it is not possible to recreate the 2.1 structure once it has been converted to the 3.0 model.
121 +The term "metadata" is very broad indeed. A distinction can be made between “structural” metadata – those (% style="color:#e74c3c" %)concepts(%%) used in the description and identification of statistical data and metadata – and “reference” metadata – the larger set of (% style="color:#e74c3c" %)concepts(%%) that describe and qualify statistical [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and processing more generally, and which are often associated not with specific observations or series of data, but with entire collections of data or even the institutions which provide that data.
132 132  
133 -The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 3.0 Major Changes document provides more information including an analysis of the breaking changes.
123 +The [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] provides for the structuring not only of data, but also of “reference” metadata. While these [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] structures exist independent of the data and its [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]], they are often linked. The [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] provides for the attachment of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] to any part of the data or [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]], as well as for the reporting and exchange of the [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] and its structural descriptions. This function of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards supports many aspects of data quality initiatives, allowing as it does for the exchange of metadata in its broadest sense, of which quality-related metadata is a major part.
134 134  
135 -== 2.4 Major Changes from 3.0 to 3.1 ==
125 +Metadata are associated not only with data, but also with the process of providing and managing the flow of data. The [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] provides for a set of metadata concerned with “data provisioning” – metadata which are useful to those who need to understand the content and form of a [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]]’s output. Each [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]] can describe in standard fashion the content of and dependencies within the data and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] which they produce, and supply information about the scheduling and mechanism by which their data and metadata are provided. This allows for automation of some validation and control functions, as well as supporting management of data reporting.
136 136  
137 -(% class="wikigeneratedid" id="HInformationModel-1" %)
138 -**Information Model**
127 +[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] also recognizes the importance of classification schemes in organizing and managing the exchange and dissemination of data and metadata. It is possible to express information about classification schemes and domain [[categories>>doc:sdmx:Glossary.Category.WebHome]] in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], along with their relationships to data and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], as well as to categorize other objects in the model.
139 139  
140 -* Addition of [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)Constraint(%%) property to a Dataflow
141 -* Addition of evolving structure property to a Data Structure Definition
142 -* Remove (% style="color:#e74c3c" %)version(%%) property on Categorisation
143 -* Simplification of (% style="color:#e74c3c" %)Constraints
144 -** Removal of Advanced Release Calendar
145 -** Removal of Role, Data (% style="color:#e74c3c" %)Constraints(%%) only restrict data that can be reported
146 -** Restrict (% style="color:#e74c3c" %)constraint(%%) targets to Identifiable structures (not URLs)
147 -** Addition of Availability (% style="color:#e74c3c" %)Constraint(%%) to define actual data
129 +The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards offer a common model, a choice of syntax and, for XML, a choice of data formats which support the exchange of any type of statistical data meeting the definition above; several optimized formats are specified based on the specific requirements of each implementation, as described below in the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] section.
148 148  
149 -(% class="wikigeneratedid" id="HDocumentation" %)
150 -**Documentation**
131 +The formal objects in the information model are presented schematically in Figure 1, and are discussed in more detail elsewhere in this document.
151 151  
152 -* Registering [[Reference Metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] removed from documentation, to align with XML Registration object which is unable to reference a Metadata Provision, and REST API which is unable to query for registered [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] sources.
133 +This document specifies the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards designed to facilitate exchanges based on any of these process patterns, and shows how [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] offers advantages in all cases. It is possible to agree bilaterally to use a standard format (such as [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] or [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]]); it is possible for data senders in a gateway process to use a standard format for data exchange with each other, or with any [[data providers>>doc:sdmx:Glossary.Data provider.WebHome]] who agree to do so; it is possible to agree to use the full set of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards to support a common data-sharing process of exchange, whether based on an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-conformant registry or some other architecture.
153 153  
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.
135 +The standards specified here specifically support a data-sharing process based on the use of central registry services. Registry services provide visibility into the data and metadata existing within the community, and support the access and use of this data and metadata by providing a set of triggers for automated processing. The data or metadata itself is not stored in a central registry – these services merely provide a useful set of metadata about the data (and additional metadata) in a known location, so that users/applications can easily locate and obtain whatever data and/or metadata is registered. The use of standards for all data, metadata, and the registry services themselves is ubiquitous, permitting a high (% style="color:#e74c3c" %)level(%%) of automation within a data-sharing community.
155 155  
156 -= 3 Processes and Business Scope =
137 +It should be pointed out that these different process models are not mutually exclusive – a single system capable of expressing data and metadata in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-conformant formats could support all three scenarios. Different standards may be applicable to different processes (for example, many registry services interfaces are used only in a data-sharing scenario) but all have a common basis in a shared information model.
157 157  
158 -== 3.1 Process Patterns ==
139 +In addition to looking at collection and reporting, it is also important to consider the dissemination of data. Data and metadata – no matter how they are exchanged between counterparties in the process of their development and creation – are all eventually supplied to an end user of some type. Often, this is through specific applications inside of institutions. But more and more frequently, data and metadata are also published on websites in various formats. The dissemination of data and its accompanying metadata on the web is a focus of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards. Standards for statistical data and metadata allow improvements in the publication of data – it becomes more easily possible to process a standard format once the data is obtained, and the data and metadata are linked together, making the comprehension and further processing of the data easier.
159 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:
141 +In discussions of statistical data, there are many aspects of its dissemination which impact data quality: data discovery, ease of use, and [[timeliness>>doc:sdmx:Glossary.Timeliness.WebHome]]. [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards provide support for all of these aspects of data dissemination. Standard data formats promote ease of use, and provide links to relevant metadata. The (% style="color:#e74c3c" %)concept(%%) of registry services means that data and metadata can more easily be discovered. [[Timeliness>>doc:sdmx:Glossary.Timeliness.WebHome]] is improved throughout the data lifecycle by increases in efficiency, promoted through the availability of metadata and ease of use.
161 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.
143 +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.
165 165  
166 166  == 3.2 SDMX and Process Automation ==
167 167  
... ... @@ -169,43 +169,50 @@
169 169  
170 170  Briefly, these can be described as:
171 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.
151 +//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.
176 176  
177 -== 3.3 Statistical Data and Metadata ==
153 +o Removal of Role, Data (% style="color:#e74c3c" %)Constraints(%%) only restrict data that can be reported// //o Restrict (% style="color:#e74c3c" %)constraint(%%) targets to Identifiable structures (not URLs) o Addition of Availability (% style="color:#e74c3c" %)Constraint(%%) to define actual data
178 178  
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.
155 +(% class="wikigeneratedid" id="HDocumentation" %)
156 +**Documentation**
180 180  
181 -[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] identifies a standard technique for modelling, expressing, and understanding the structure of this multi-dimensional "cube", allowing automated processing of data from a variety of sources. This approach is widely applicable across types of data and attempts to provide the simplest and most easily comprehensible technique that will support the exchange of this broad set of data and related metadata.
158 +• Registering [[Reference Metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] removed from documentation, to align with XML Registration object which is unable to reference a Metadata Provision, and REST API which is unable to query for registered [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] sources.
182 182  
183 -The term "metadata" is very broad indeed. A distinction can be made between “structural” metadata – those (% style="color:#e74c3c" %)concepts(%%) used in the description and identification of statistical data and metadata – and “reference” metadata – the larger set of (% style="color:#e74c3c" %)concepts(%%) that describe and qualify statistical [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and processing more generally, and which are often associated not with specific observations or series of data, but with entire collections of data or even the institutions which provide that data.
160 += 3 Processes and Business Scope =
184 184  
185 -The [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] provides for the structuring not only of data, but also of “reference” metadata. While these [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] structures exist independent of the data and its [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]], they are often linked. The [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] provides for the attachment of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] to any part of the data or [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]], as well as for the reporting and exchange of the [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] and its structural descriptions. This function of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards supports many aspects of data quality initiatives, allowing as it does for the exchange of metadata in its broadest sense, of which quality-related metadata is a major part.
162 +== 3.1 Process Patterns ==
186 186  
187 -Metadata are associated not only with data, but also with the process of providing and managing the flow of data. The [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] provides for a set of metadata concerned with “data provisioning” – metadata which are useful to those who need to understand the content and form of a [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]]’s output. Each [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]] can describe in standard fashion the content of and dependencies within the data and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] which they produce, and supply information about the scheduling and mechanism by which their data and metadata are provided. This allows for automation of some validation and control functions, as well as supporting management of data reporting.
164 +[[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:
188 188  
189 -[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] also recognizes the importance of classification schemes in organizing and managing the exchange and dissemination of data and metadata. It is possible to express information about classification schemes and domain [[categories>>doc:sdmx:Glossary.Category.WebHome]] in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], along with their relationships to data and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], as well as to categorize other objects in the model.
166 +//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.
190 190  
191 -The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards offer a common model, a choice of syntax and, for XML, a choice of data formats which support the exchange of any type of statistical data meeting the definition above; several optimized formats are specified based on the specific requirements of each implementation, as described below in the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] section.
168 +The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 3.0 Major Changes document provides more information including an analysis of the breaking changes.
192 192  
193 -The formal objects in the information model are presented schematically in Figure 1, and are discussed in more detail elsewhere in this document.
170 +== 2.4 Major Changes from 3.0 to 3.1 ==
194 194  
195 -This document specifies the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards designed to facilitate exchanges based on any of these process patterns, and shows how [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] offers advantages in all cases. It is possible to agree bilaterally to use a standard format (such as [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] or [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]]); it is possible for data senders in a gateway process to use a standard format for data exchange with each other, or with any [[data providers>>doc:sdmx:Glossary.Data provider.WebHome]] who agree to do so; it is possible to agree to use the full set of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards to support a common data-sharing process of exchange, whether based on an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-conformant registry or some other architecture.
172 +(% class="wikigeneratedid" id="HInformationModel-1" %)
173 +**Information Model**
196 196  
197 -The standards specified here specifically support a data-sharing process based on the use of central registry services. Registry services provide visibility into the data and metadata existing within the community, and support the access and use of this data and metadata by providing a set of triggers for automated processing. The data or metadata itself is not stored in a central registry – these services merely provide a useful set of metadata about the data (and additional metadata) in a known location, so that users/applications can easily locate and obtain whatever data and/or metadata is registered. The use of standards for all data, metadata, and the registry services themselves is ubiquitous, permitting a high (% style="color:#e74c3c" %)level(%%) of automation within a data-sharing community.
175 +Addition of [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)Constraint(%%) property to a Dataflow Addition of evolving structure property to a Data Structure Definition Remove (% style="color:#e74c3c" %)version(%%) property on Categorisation Simplification of (% style="color:#e74c3c" %)Constraints(%%) o Removal of Advanced Release Calendar
198 198  
199 -It should be pointed out that these different process models are not mutually exclusive – a single system capable of expressing data and metadata in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-conformant formats could support all three scenarios. Different standards may be applicable to different processes (for example, many registry services interfaces are used only in a data-sharing scenario) but all have a common basis in a shared information model.
177 +Several of the changes are ‘breaking’ meaning that, in specific cases, the (% style="color:#e74c3c" %)version(%%) 3.0 specification is not backwardly compatible with earlier (% style="color:#e74c3c" %)versions(%%) of the Standard.
200 200  
201 -In addition to looking at collection and reporting, it is also important to consider the dissemination of data. Data and metadata – no matter how they are exchanged between counterparties in the process of their development and creation – are all eventually supplied to an end user of some type. Often, this is through specific applications inside of institutions. But more and more frequently, data and metadata are also published on websites in various formats. The dissemination of data and its accompanying metadata on the web is a focus of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards. Standards for statistical data and metadata allow improvements in the publication of data – it becomes more easily possible to process a standard format once the data is obtained, and the data and metadata are linked together, making the comprehension and further processing of the data easier.
179 +The principle breaking changes are:
202 202  
203 -In discussions of statistical data, there are many aspects of its dissemination which impact data quality: data discovery, ease of use, and [[timeliness>>doc:sdmx:Glossary.Timeliness.WebHome]]. [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards provide support for all of these aspects of data dissemination. Standard data formats promote ease of use, and provide links to relevant metadata. The (% style="color:#e74c3c" %)concept(%%) of registry services means that data and metadata can more easily be discovered. [[Timeliness>>doc:sdmx:Glossary.Timeliness.WebHome]] is improved throughout the data lifecycle by increases in efficiency, promoted through the availability of metadata and ease of use.
181 +REST API – The REST API is not backwardly compatible due to modifications to the URLs and query parameters resulting in breaking changes in four of the five main resources. SOAP API – Deprecation of the SOAP API means that existing systems designed to use SOAP will not work with (% style="color:#e74c3c" %)version(%%) 3.0 registries. [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] – [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 and earlier structure, data and metadata XML messages are not valid in (% style="color:#e74c3c" %)version(%%) 3.0. Specifically: legacy data messages including Generic, Compact and Utility are no longer supported. The remaining Structure Specific data message has been changed to support new features such as reporting of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] as part of the [[dataset>>doc:sdmx:Glossary.Data set.WebHome]], Structure messages have a number of breaking changes, principally modification to the information model, removal of the agency-(% style="color:#e74c3c" %)version(%%)-id option for referencing [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] and changes to the way the structures are organised into ‘collections’ within the message. [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] – [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 structure, data and metadata JSON messages are not valid in (% style="color:#e74c3c" %)version(%%) 3.0. The data message has been changed to support the improved REST data queries, in particular the ability to retrieve in one operation data from multiple [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] with potentially different [[Data Structure Definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]]. Breaking changes similar to those for the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] transmission format have been made to the structure message. [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-CSV - The CSV data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] messages are not backwardly compatible with those under (% style="color:#e74c3c" %)version(%%) 2.1 due to changes to the structure of the messages needed to support new features such as the improved REST API data queries. [[SDMX-EDI>>doc:sdmx:Glossary.SDMX-EDI.WebHome]] – Deprecation of the EDI transmission format means that existing systems designed to send or receive structures or data in EDI will not work with (% style="color:#e74c3c" %)version(%%) 3.0 registries. Information Model – Several structures have been changed in the (% style="color:#e74c3c" %)version(%%) 3.0 model and three removed. For these reasons the (% style="color:#e74c3c" %)version(%%) 3.0 model is not directly compatible with (% style="color:#e74c3c" %)version(%%) 2.1 or earlier, although conversion of specific [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] is possible under some circumstances. Loss of information during the conversion process however means that in cases like structure mapping, the conversion is not reversible i.e. it is not possible to recreate the 2.1 structure once it has been converted to the 3.0 model.
204 204  
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.
183 +(% class="wikigeneratedid" id="HSOAPWebServicesAPI" %)
184 +**SOAP Web Services API**
206 206  
207 -[[image:SDMX%203.1%20Section%201.png]]
186 +• The SOAP web services API has been deprecated with (% style="color:#e74c3c" %)version(%%) 3.0 standardising on REST
208 208  
188 +(% class="wikigeneratedid" id="HXML2CJSON2CCSVandEDITransmissionformats" %)
189 +**XML, JSON, CSV and EDI Transmission formats**
190 +
191 +The [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]], [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] and [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-CSV specifications have been extended and modified where needed to support the new features and changes such as [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] and microdata Obsolete [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] data message variants including Generic, Compact, Utility and Cross-sectional have been deprecated standardising on Structure Specific Data as the sole XML format for data exchange The [[SDMX-EDI>>doc:sdmx:Glossary.SDMX-EDI.WebHome]] transmission format for structures and data has been deprecated The organisation of structures into ‘collections’ in [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] structure messages has been flattened and simplified The option to reference structures in [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] messages using Agency, ID and (% style="color:#e74c3c" %)Version(%%) has been deprecated with URN now exclusively used for all non-local referencing purpose
192 +
193 +[[image:SDMX 3.1 Section 1.png]]
194 +
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 ==
... ... @@ -316,7 +316,7 @@
316 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 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.
318 318  
319 -== 5.2 SDMX-JSON ==
305 +== ​​​​​​​5.2 SDMX-JSON ==
320 320  
321 321  [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] is the JSON transmission format specification for exchanging [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]], data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. It provides an alternative to [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] and is most suited to applications like web data dissemination.
322 322  
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