Last modified by Artur on 2025/09/10 11:19

From version 6.2
edited by Helena
on 2025/05/22 14:57
Change comment: There is no comment for this version
To version 11.3
edited by Elena
on 2025/06/17 17:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.helena
1 +xwiki:XWiki.elenasemanticproorg
Tags
... ... @@ -1,0 +1,1 @@
1 +Artefact|Attribute|Category|Category scheme|Code|Code list|Comment|Concept scheme|Cross-domain concept|Data consumer|Data provider|Data set|Data source|Data structure definition|Dataflow|Dimension|Hierarchical code list|Hierarchy|Incremental update|Item scheme|Maintenance agency|Measure|Metadata repository|Metadata set|Metadata structure definition|Metadataflow|Notification|Provision agreement|Reference metadata|Release policy - release calendar|Representation|SDMX Information Model|SDMX Registry|SDMX Technical Specification|SDMX-EDI|SDMX-ML|Statistical data and metadata exchange|Statistical subject-matter domain|Structural metadata|Structure set|Subscription|Time period|Timeliness|Validation and transformation language
Content
... ... @@ -12,9 +12,9 @@
12 12  Added the Section 10 –Validation and Transformation Language (VTL(% style="background-color:transparent" %))
13 13  )))
14 14  
15 -= {{id name="_Toc38908"/}}1. Introduction =
15 += Introduction =
16 16  
17 -The [[Statistical Data and Metadata Exchange>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] ([[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]) initiative (http:~/~/www.[[sdmx>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]].org) sets standards that can facilitate the exchange of statistical data and metadata using modern information technology, with an emphasis on aggregated data.
17 +The [[Statistical Data and Metadata Exchange>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] ([[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]) initiative (http:~/~/www.sdmx.org) sets standards that can facilitate the exchange of statistical data and metadata using modern information technology, with an emphasis on aggregated data.
18 18  
19 19  There are several sections to the [[SDMX Technical Specification>>doc:sdmx:Glossary.SDMX Technical Specification.WebHome]]:
20 20  
... ... @@ -30,59 +30,59 @@
30 30  
31 31  Please note also that the SOAP and REST specifications are not maintained any more in the section 7 (Web Service Guidelines), the link to these specifications can be found on the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] website
32 32  
33 -= {{id name="_Toc38909"/}}2. Changes from Previous Version =
33 += Changes from Previous Version =
34 34  
35 35  The 2.0 version of this standard represented a significant increase in scope, and also provided more complete support in those areas covered in the version 1.0 specification. Version 2.0 of this standard is backward-compatible with version 1.0, so that existing implementations can be easily migrated to conformance with version 2.0.
36 36  
37 -The 2.1 version of this standard represents a set of changes resulting from several years of implementation experience with the 2.0 standard. The changes do not represent a major increase in scope or functionality, but do correct some bugs, and add functionalities in some cases. Major changes in SDMX-ML include a much stronger alignment of the XML Schemas with the Information Model, to emphasize inheritance and object-oriented features, and increased precision and flexibility in the attachment of metadata reports to specific objects in the SDMX Information Model.
37 +The 2.1 version of this standard represents a set of changes resulting from several years of implementation experience with the 2.0 standard. The changes do not represent a major increase in scope or functionality, but do correct some bugs, and add functionalities in some cases. Major changes in [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] include a much stronger alignment of the XML Schemas with the Information Model, to emphasize inheritance and object-oriented features, and increased precision and flexibility in the attachment of metadata reports to specific objects in the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]].
38 38  
39 -Note that the idea of backward-compatibility in the standards is based on the information model. In both releases, some non-backward-compatible changes have been made to the SDMX-ML formats. The same set of information required to use version 1.0 of the specification will permit the use of the same features in the version 2.0 specifications, however. Thus, a Data Structure Definition is easily translated from version 1.0 to version 2.0, without requiring any new information regarding structures, etc. There have been no changes to the SDMX-EDI format.
39 +Note that the idea of backward-compatibility in the standards is based on the information model. In both releases, some non-backward-compatible changes have been made to the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] formats. The same set of information required to use version 1.0 of the specification will permit the use of the same features in the version 2.0 specifications, however. Thus, a [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] is easily translated from version 1.0 to version 2.0, without requiring any new information regarding structures, etc. There have been no changes to the [[SDMX-EDI>>doc:sdmx:Glossary.SDMX-EDI.WebHome]] format.
40 40  
41 41  The major changes from 1.0 to 2.0 can be briefly summarized:
42 42  
43 -* **Reference Metadata**: In addition to describing and specifying data structures and formats (along with related structural metadata), the version 2.0 specification also provides for the exchange of metadata which is distinct from the structural metadata in the 1.0 version. This category 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 information, description of the data and metadata provided, etc.); and metadata relevant to the exchange of categorization schemes.
44 -* **SDMX Registry**: 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/notification.
45 -* **Structural Metadata**: The support for exchange of statistical data and related structural metadata has been expanded. Some support is provided for qualitative data; data cube structures are described; hierarchical code 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.
43 +* **[[Reference Metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]**: In addition to describing and specifying data structures and formats (along with related [[structural metadata>>doc:sdmx:Glossary.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.Structural metadata.WebHome]] in the 1.0 version. This [[category>>doc:sdmx:Glossary.Category.WebHome]] includes “reference” metadata (regarding data quality, methodology, and similar types – it can be configured by the user to include whatever [[concepts>>doc:sdmx:Glossary.Concept.WebHome]] require reporting); metadata related to data provisioning ([[release calendar>>doc:sdmx:Glossary.Release policy - release calendar.WebHome]] information, description of the data and metadata provided, etc.); and metadata relevant to the exchange of categorization schemes.
44 +* **SDMX Registry**: 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.Subscription.WebHome]]/notification.
45 +* **[[Structural Metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]**: The support for exchange of statistical data and related [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] has been expanded. Some support is provided for qualitative data; data cube structures are described; [[hierarchical code lists>>doc:sdmx:Glossary.Hierarchical code list.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.
46 46  
47 47  The major changes from 2.0 to 2.1 can be briefly summarized:
48 48  
49 -* **Web-Services-Oriented Changes:** Several organizations have been implementing web services applications using SDMX, and these 106 implementations have resulted in several changes to the specifications. Because the nature of SDMX web services could not be anticipated at the time of the original drafting of the specifications, the web services guidelines have been completely re-developed.
50 -* **Presentational Changes: **Much work has gone into using various technologies for the visualization of SDMX data and metadata, and some changes have been proposed as a result, to better leverage this graphical visualization. These changes are largely to leverage the Cross-domain Concepts of the Content Oriented Guidelines.
49 +* **Web-Services-Oriented Changes:** Several organizations have been implementing web services applications using [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], and these 106 implementations have resulted in several changes to the specifications. Because the nature of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] web services could not be anticipated at the time of the original drafting of the specifications, the web services guidelines have been completely re-developed.
50 +* **Presentational Changes: **Much work has gone into using various technologies for the visualization of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] data and metadata, and some changes have been proposed as a result, to better leverage this graphical visualization. These changes are largely to leverage the [[Cross-domain Concepts>>doc:sdmx:Glossary.Cross-domain concept.WebHome]] of the Content Oriented Guidelines.
51 51  * **Consistency Issues:** There have been some areas where the draft specifications were inconsistent in minor ways, and these have been addressed.
52 52  * **Clarifications in Documentation:** In some cases it has been identified that the documentation of specific fields within the standard needed clarification and elaboration, and these issues have been addressed.
53 -* **Optimization for XML Technologies:** Implementation has shown that it is possible to better organize the XML schemas for use within common technology development tools which work with XML. These changes are primarily focused on leveraging the object-oriented features of W3C XML Schema to allow for easier processing of SDMX data and metadata.
54 -* **Consistency between the SDMX-ML and the SDMX Information Model: **Certain aspects of the XML schemas and UML model have been more closely aligned, to allow for easier comprehension of the SDMX model.
53 +* **Optimization for XML Technologies:** Implementation has shown that it is possible to better organize the XML schemas for use within common technology development tools which work with XML. These changes are primarily focused on leveraging the object-oriented features of W3C XML Schema to allow for easier processing of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] data and metadata.
54 +* **Consistency between the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] and the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]: **Certain aspects of the XML schemas and UML model have been more closely aligned, to allow for easier comprehension of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] model.
55 55  * **Technical Bugs:** Some minor technical bugs have been identified in the registry interfaces and elsewhere. These bugs have been addressed.
56 56  * **Support for Non-Time-Series Data in the Generic Format: **One area which has been extended is the ability to express non-time-series data as part of the generic data message.
57 -* **Simplification of the data structure definition - specific message types: **Both time series (version 2.0 Compact) and non-time series data sets (version 2.0 Cross Sectional) use the same underlying structure for a structure-specific formatted message, which is specific to the Data Structure Definition of the data set.
57 +* **Simplification of the [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] - specific message types: **Both time series (version 2.0 Compact) and non-time series [[data sets>>doc:sdmx:Glossary.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.Data structure definition.WebHome]] of the data set.
58 58  * **Simplification and better support for the metadata structure: **New use 140 cases have been reported and these are now supported by a re-modelled metadata structure definition.
59 -* **Support for partial item schemes such as a code list: **The concept of a 143 partial (sub-set) item scheme such as a partial code list for use in exchange scenarios has been introduced**.**
59 +* **Support for partial [[item schemes>>doc:sdmx:Glossary.Item scheme.WebHome]] such as a [[code list>>doc:sdmx:Glossary.Code list.WebHome]]: **The concept of a 143 partial (sub-set) [[item scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] such as a partial [[code list>>doc:sdmx:Glossary.Code list.WebHome]] for use in exchange scenarios has been introduced**.**
60 60  
61 -= {{id name="_Toc38910"/}}3. Processes and Business Scope =
61 += Processes and Business Scope =
62 62  
63 -== {{id name="_Toc38911"/}}3.1 Process Patterns ==
63 +== 3.1 Process Patterns ==
64 64  
65 -SDMX identifies three basic process patterns regarding the exchange of statistical data and metadata. These can be described as follows:
65 +[[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:
66 66  
67 67  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.
68 68  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.
69 69  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.
70 70  
71 -This document specifies the SDMX standards designed to facilitate exchanges based on any of these process patterns, and shows how SDMX offers advantages in all cases. It is possible to agree bilaterally to use a standard format (such as SDMX-EDI or SDMX-ML); 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 who agree to do so; it is possible to agree to use the full set of SDMX standards to support a common data-sharing process of exchange, whether based on an SDMX-conformant registry or some other architecture.
71 +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-EDI>>doc:sdmx:Glossary.SDMX-EDI.WebHome]] or [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.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.
72 72  
73 73  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 level of automation within a datasharing community.
74 74  
75 75  It should be pointed out that these different process models are not mutually exclusive – a single system capable of expressing data and metadata in SDMXconformant 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.
76 76  
77 -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 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.
77 +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.
78 78  
79 -In discussions of statistical data, there are many aspects of its dissemination which impact data quality: data discovery, ease of use, and timeliness. SDMX 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 concept of registry services means that data and metadata can more easily be discovered. Timeliness is improved throughout the data lifecycle by increases in efficiency, promoted through the availability of metadata and ease of use.
79 +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 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.
80 80  
81 -It is important to note that SDMX 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.
81 +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.
82 82  
83 -== {{id name="_Toc38912"/}}3.2 SDMX and Process Automation ==
83 +== 3.2 SDMX and Process Automation ==
84 84  
85 -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 aims to provide standards that are most useful for these automated processes and technologies.
85 +[[Statistical data and metadata exchanges>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 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.
86 86  
87 87  Briefly, these can be described as:
88 88  
... ... @@ -91,23 +91,23 @@
91 91  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.
92 92  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.
93 93  
94 -The SDMX standards specified here are designed to support the requirements of all of these automation processes and technologies.
94 +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.
95 95  
96 -== {{id name="_Toc38913"/}}3.3 Statistical Data and Metadata ==
96 +== 3.3 Statistical Data and Metadata ==
97 97  
98 -To avoid confusion about which "data" and "metadata" are the intended content of the SDMX 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 concepts, which act as identifiers and descriptors of the data. These metadata values and concepts can be understood as the named dimensions of a multi-dimensional co-ordinate system, describing what is often called a "cube" of data.
98 +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>>doc:sdmx:Glossary.Concept.WebHome]](%%), which act as identifiers and descriptors of the data. These metadata values and (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) 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.
99 99  
100 -SDMX 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.
100 +[[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.
101 101  
102 -The term "metadata" is very broad indeed. A distinction can be made between “structural” metadata – those concepts used in the description and identification of statistical data and metadata – and “reference” metadata – the larger set of concepts that describe and qualify statistical data sets 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.
102 +The term "metadata" is very broad indeed. A distinction can be made between “structural” metadata – those (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) used in the description and identification of statistical data and metadata – and “reference” metadata – the larger set of (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) 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.
103 103  
104 -The SDMX Information Model provides for the structuring not only of data, but also of “reference” metadata. While these reference metadata structures exist independent of the data and its structural metadata, they are often linked. The SDMX Information Model provides for the attachment of reference metadata to any part of the data or structural metadata, as well as for the reporting and exchange of the reference metadata and its structural descriptions. This function of the SDMX 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.
104 +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.
105 105  
106 -Metadata are associated not only with data, but also with the process of providing and managing the flow of data. The SDMX Information Model 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’s output. Each data provider can describe in standard fashion the content of and dependencies within the data and metadata sets 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.
106 +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.
107 107  
108 -SDMX 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 in SDMX, along with their relationships to data and metadata sets, as well as to categorize other objects in the model.
108 +[[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.
109 109  
110 -The SDMX 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 section.
110 +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.
111 111  
112 112  The formal objects in the information model are presented briefly below, but are also discussed in more detail elsewhere in this specification.
113 113  
... ... @@ -115,185 +115,188 @@
115 115  
116 116  **Figure 1: High Level Schematic of Major Artefacts in the SDMX Information Model**
117 117  
118 -== {{id name="_Toc38914"/}}3.4 The SDMX View of Statistical Exchange ==
118 +== 3.4 The SDMX View of Statistical Exchange ==
119 119  
120 -Version 1.0 of ISO/TS 17369 SDMX covered statistical data sets and the metadata related to the structure of these data sets. This scope was useful in supporting the different models of statistical exchange (bilateral exchange, gateway exchange, and data-sharing) but was not by itself sufficient to support them completely. Versions 2.0 and 2.1 provide a much more complete view of statistical exchange, so that an open data-sharing model can be fully supported, and other models of exchange can be more completely automated. In order to produce technical standards that will support this increased scope, the SDMX Information Model provides a broader set of formal objects which describe the actors, processes, and resources within statistical exchanges.
120 +Version 1.0 of ISO/TS 17369 [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] covered statistical [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and the metadata related to the structure of these [[data sets>>doc:sdmx:Glossary.Data set.WebHome]]. This scope was useful in supporting the different models of statistical exchange (bilateral exchange, gateway exchange, and data-sharing) but was not by itself sufficient to support them completely. Versions 2.0 and 2.1 provide a much more complete view of statistical exchange, so that an open data-sharing model can be fully supported, and other models of exchange can be more completely automated. In order to produce technical standards that will support this increased scope, the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] provides a broader set of formal objects which describe the actors, processes, and resources within statistical exchanges.
121 121  
122 122  It is important to understand the set of formal objects not only in a technical sense, but also in terms of what they represent in the real-world exchange of statistical data and metadata.
123 123  
124 -The first version of SDMX provided for data sets - specific statistical data reported according to a specific structure, for a specific time range - and for data structure definitions - the metadata which describes the structure of statistical data sets. These are important objects in statistical exchanges, and are retained and enhanced in the second version of the standards in a backward-compatible form. A related object in statistical exchanges is the "data flow" - this supports the concept of data reporting or dissemination on an ongoing basis. "Data flows" can be understood as data sets which are not bounded by time. Data structures are owned and maintained by agencies - in a similar fashion, data flows are owned by maintenance agencies.
124 +The first version of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] provided for [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] - specific statistical data reported according to a specific structure, for a specific time range - and for [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]] - the metadata which describes the structure of statistical [[data sets>>doc:sdmx:Glossary.Data set.WebHome]]. These are important objects in statistical exchanges, and are retained and enhanced in the second version of the standards in a backward-compatible form. A related object in statistical exchanges is the [[data flow>>doc:sdmx:Glossary.Dataflow.WebHome]] - this supports the concept of data reporting or dissemination on an ongoing basis. [[Data flows>>doc:sdmx:Glossary.Dataflow.WebHome]] can be understood as [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] which are not bounded by time. Data structures are owned and maintained by agencies - in a similar fashion, [[data flows>>doc:sdmx:Glossary.Dataflow.WebHome]] are owned by maintenance agencies.
125 125  
126 -Versions 2.0 and 2.1 – like version 1.0 – allow for the publication of statistical data (and the related structural metadata) but also provide for the standard, systematic representation of reference metadata. Reference metadata are reported not as an integral part of a data set, but independent of the statistical data. SDMX provides for reference "metadata sets", "metadata structure definitions", and "metadata flows". These objects are very similar to data sets, data structure definitions, and data flows, but they concern reference metadata rather than statistical observations. In the same way that data providers may publish statistical data, they may also publish reference metadata. Metadata structural definitions are maintained by agencies in a fashion similar to the way that agencies maintain data structure definitions, the structural definitions of data sets.
126 +Versions 2.0 and 2.1 – like version 1.0 – allow for the publication of statistical data (and the related [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]) but also provide for the standard, systematic [[representation>>doc:sdmx:Glossary.Representation.WebHome]] of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. [[Reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] are reported not as an integral part of a [[data set>>doc:sdmx:Glossary.Data set.WebHome]], but independent of the statistical data. [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] provides for [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] sets", [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]", and [[metadata flows>>doc:sdmx:Glossary.Metadataflow.WebHome]]". These objects are very similar to [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]], and [[data flows>>doc:sdmx:Glossary.Dataflow.WebHome]], but they concern [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] rather than statistical observations. In the same way that [[data providers>>doc:sdmx:Glossary.Data provider.WebHome]] may publish statistical data, they may also publish [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. Metadata structural definitions are maintained by agencies in a fashion similar to the way that agencies maintain [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]], the structural definitions of [[data sets>>doc:sdmx:Glossary.Data set.WebHome]].
127 127  
128 -The structural definitions of both data and reference metadata associate specific statistical concepts with their representations, whether textual, coded, etc. In SDMX version 2.0/2.1, these concepts are taken from a "concept scheme" which is maintained by a specific agency. Concept schemes group a set of concepts, provide their definitions and names, and allow for semantic relationships to be expressed, when some concepts are specializations of others. It is possible for a single concept scheme to be used both for data structures - key families - and for reference metadata structures.
128 +The structural definitions of both data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] associate specific statistical [[concepts>>doc:sdmx:Glossary.Concept.WebHome]] with their [[representations>>doc:sdmx:Glossary.Representation.WebHome]], whether textual, coded, etc. In [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] version 2.0/2.1, these [[concepts>>doc:sdmx:Glossary.Concept.WebHome]] are taken from a [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] which is maintained by a specific agency. [[Concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]] group a set of [[concepts>>doc:sdmx:Glossary.Concept.WebHome]], provide their definitions and names, and allow for semantic relationships to be expressed, when some [[concepts>>doc:sdmx:Glossary.Concept.WebHome]] are specializations of others. It is possible for a single [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] to be used both for data structures - key families - and for [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] structures.
129 129  
130 -Inherent in any statistical exchange – and in many dissemination activities - is a concept of "service level agreement", even if this is not formalized or made explicit. SDMX incorporates this idea in objects termed "provision agreements". Data providers may provide data to many different data flows. Data flows may incorporate data coming from more than one data provider. Provision agreements are the objects which tell you which data providers are supplying what data to which data flows. The same is true for metadata flows.
130 +Inherent in any statistical exchange – and in many dissemination activities - is a concept of "service level agreement", even if this is not formalized or made explicit. [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] incorporates this idea in objects termed [[provision agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]]". [[Data providers>>doc:sdmx:Glossary.Data provider.WebHome]] may provide data to many different [[data flows>>doc:sdmx:Glossary.Dataflow.WebHome]]. [[Data flows>>doc:sdmx:Glossary.Dataflow.WebHome]] may incorporate data coming from more than one [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]]. [[Provision agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]] are the objects which tell you which [[data providers>>doc:sdmx:Glossary.Data provider.WebHome]] are supplying what data to which [[data flows>>doc:sdmx:Glossary.Dataflow.WebHome]]. The same is true for [[metadata flows>>doc:sdmx:Glossary.Metadataflow.WebHome]].
131 131  
132 -Provision agreements allow for a variety of information to be made available: the schedule by which statistical data or metadata is reported or published, the specific topics about which data or metadata is reported within the theoretically possible set of data (as described by a data structure definition or reference metadata structure definition), and the time period covered by the statistical data and metadata. This set of information is termed "constraint" in the SDMX Information Model.
132 +[[Provision agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]] allow for a variety of information to be made available: the schedule by which statistical data or metadata is reported or published, the specific topics about which data or metadata is reported within the theoretically possible set of data (as described by a [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] structure definition), and the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the statistical data and metadata. This set of information is termed [[constraint>>doc:Glossary.Constraint.WebHome]] in the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]].
133 133  
134 134  A brief summary of the objects described in the information model includes:
135 135  
136 -* //**Data Set:**// Data is organized into discrete sets, which include particular observations for a specific period of time. A data set can be understood as a collection of similar data, sharing a structure, which covers a fixed period of time.
137 -* //**Data Structure Definition (DSD, also known as Key Family in Version 2.0): **//Each data set has a set of structural metadata. These descriptions are referred to in SDMX as Data Structure Definitions, which include information about how concepts are associated with the measures, dimensions, and attributes of a data “cube,” along with information about the representation of data and related identifying and descriptive (structural) metadata. In Version 2.1, the term "Key Family" is replaced by "Data Structure Definition" (DSD) both in XML Schemas and the Information Model.
138 -* //**Code list:**// Code lists enumerate a set of values to be used in the representation of dimensions, attributes, and other structural parts of SDMX. They can be supplemented by other structural metadata which indicates how codes are organized into hierarchies.
139 -* //**Organisation Scheme:**// Organisations and organisation structure can be defined in an Organisation Scheme. Specific Organisation Schemes exist for Maintenance Agency, Data Provider, Data Consumer, and Organisation Unit.
140 -* //**Category Scheme and Categorisation:**// Category schemes are made up of a hierarchy of categories, which in SDMX may include any type of useful classification for the organization of data and metadata. A Categorisation links a category to an identifiable object. In this way sets of objects can be categorised. A statistical subject-matter domain scheme is implemented in SDMX as a Category Scheme.
141 -* //**Concept Scheme:**// A concept scheme is a maintained list of concepts that are used in data structure definitions and metadata structure definitions. There can be many such concept schemes. A “core” representation of the concept can be specified (e.g. a core code list, or other representation such as “date”). Note that this core representation can be overridden in the data structure definition or metadata structure definition that uses the concept. Indeed, organisations wishing to remain with version 1.0 key family schema specifications will continue to declare the representation in the key family definition.
142 -* //**Metadata Set:**// A reference metadata set is a set of information pertaining to an object within the formal SDMX view of statistical exchange: they may describe the maintainers of data or structural definitions; they may describe the schedule on which data is released; they may describe the flow of a single type of data over time; they may describe the quality of data, etc. In SDMX, the creators of reference metadata may take whatever concepts they are concerned with, or obliged to report, and provide a reference metadata set containing that information.
143 -* //**Metadata Structure Definition:**// A reference metadata set also has a set of structural metadata which describes how it is organized. This metadata set identifies what reference metadata concepts are being reported, how these concepts relate to each other (typically as hierarchies), what their presentational structure is, how they may be represented (as free text, as coded values, etc.), and with which formal SDMX object types they are associated.
144 -* //**Dataflow Definition:**// In SDMX, data sets are reported or disseminated according to a data flow definition. The data flow definition identifies the data structure definition and may be associated with one or more subject matter domains via a Categorisation (this facilitates the search for data according to organised category schemes). Constraints, in terms of reporting periodicity or sub set of possible keys that are allowed in a data set, may be attached to the data flow definition.
145 -* //**Metadataflow Definition:**// A metadata flow definition is very similar to a data flow definition, but describes, categorises, and constrains metadata sets.
146 -* //**Data Provider: **//An organization which produces data or reference metadata is termed a data provider.
147 -* //**Provision Agreement:**// The set of information which describes the way in which data sets and metadata sets are provided by a data provider. A provision agreement can be constrained in much the same way as a data or metadata flow definition. Thus, a data provider can express the fact that it provides a particular data flow covering a specific set of countries and topics, Importantly, the actual source of registered data or metadata is attached to the provision agreement (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, 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).
148 -* //**Constraint:**// Constraints describe a subset of a data source or metadata source, and may also provide information about scheduled releases of data. They are associated with data providers, provision agreements, data flows, metadataflows, data structure definitions and metadata structure definitions.
149 -* //**Structure Set: **//Structure sets provide a mechanism for grouping structural metadata together to form a complete description of the relationships between specific, related sets of data and metadata. They can be used to map dimensions and attributes to one another, to map concepts, to map code lists, and to map category schemes. They can be used to describe “cubes” of data, even when the data within the cube does not share a single dimensionality.
150 -* //**Reporting Taxonomy: **//A reporting taxonomy allows an organisation to link (possibly in a hierarchical way) a number of cube or data flow 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.
151 -* //**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 sets which describe processes-related concepts.
152 -* //**Hierarchical Code List:**// This supports the specification of code hierarchies. The codes themselves are referenced from the code lists in which they are maintained. The Hierarchical Code List thus specifies the organisation of the codes in one or more hierarchies, but does not define the codes themselves.
136 +* //**[[Data Set>>doc:sdmx:Glossary.Data set.WebHome]]:**// Data is organized into discrete sets, which include particular observations for a specific period of time. A [[data set>>doc:sdmx:Glossary.Data set.WebHome]] can be understood as a collection of similar data, sharing a structure, which covers a fixed period of time.
137 +* //**[[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] ([[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]], also known as Key Family in Version 2.0): **//Each [[data set>>doc:sdmx:Glossary.Data set.WebHome]] has a set of [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. These descriptions are referred to in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] as [[Data Structure Definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]], which include information about how [[concepts>>doc:sdmx:Glossary.Concept.WebHome]] are associated with the [[measures>>doc:sdmx:Glossary.Measure.WebHome]], [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]], and [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] of a data “cube,” along with information about the [[representation>>doc:sdmx:Glossary.Representation.WebHome]] of data and related identifying and descriptive (structural) metadata. In Version 2.1, the term "Key Family" is replaced by [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] ([[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]]) both in XML Schemas and the Information Model.
138 +* //**[[Code list>>doc:sdmx:Glossary.Code list.WebHome]]:**// [[Code lists>>doc:sdmx:Glossary.Code list.WebHome]] enumerate a set of values to be used in the [[representation>>doc:sdmx:Glossary.Representation.WebHome]] of [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]], [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]], and other structural parts of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]. They can be supplemented by other [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] which indicates how [[codes>>doc:sdmx:Glossary.Code.WebHome]] are organized into [[hierarchies>>doc:sdmx:Glossary.Hierarchy.WebHome]].
139 +* //**Organisation Scheme:**// Organisations and organisation structure can be defined in an Organisation Scheme. Specific Organisation Schemes exist for [[Maintenance Agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]], [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]], [[Data Consumer>>doc:sdmx:Glossary.Data consumer.WebHome]], and Organisation Unit.
140 +*
141 +* //**[[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] and Categorisation:**// [[Category schemes>>doc:sdmx:Glossary.Category scheme.WebHome]] are made up of a [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] of [[categories>>doc:sdmx:Glossary.Category.WebHome]], which in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] may include any type of useful classification for the organization of data and metadata. A Categorisation links a [[category>>doc:sdmx:Glossary.Category.WebHome]] to an identifiable object. In this way sets of objects can be categorised. A [[statistical subject-matter domain>>doc:sdmx:Glossary.Statistical subject-matter domain.WebHome]] scheme is implemented in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] as a [[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]].
142 +* //**[[Concept Scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]]:**// A [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] is a maintained list of (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) that are used in [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]] and [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]. There can be many such [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]]. A “core” [[representation>>doc:sdmx:Glossary.Representation.WebHome]] of the (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) can be specified (e.g. a core [[code list>>doc:sdmx:Glossary.Code list.WebHome]], or other [[representation>>doc:sdmx:Glossary.Representation.WebHome]] such as “date”). Note that this core [[representation>>doc:sdmx:Glossary.Representation.WebHome]] can be overridden in the [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] that uses the (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%). Indeed, organisations wishing to remain with version 1.0 key family schema specifications will continue to declare the [[representation>>doc:sdmx:Glossary.Representation.WebHome]] in the key family definition.
143 +* //**[[Metadata Set>>doc:sdmx:Glossary.Metadata set.WebHome]]:**// A [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] set is a set of information pertaining to an object within the formal [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] view of statistical exchange: they may describe the maintainers of data or structural definitions; they may describe the schedule on which data is released; they may describe the flow of a single type of data over time; they may describe the quality of data, etc. In [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], the creators of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] may take whatever (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) they are concerned with, or obliged to report, and provide a [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] set containing that information.
144 +* //**[[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]:**// A [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] set also has a set of [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] which describes how it is organized. This [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]] identifies what [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) are being reported, how these (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) relate to each other (typically as [[hierarchies>>doc:sdmx:Glossary.Hierarchy.WebHome]]), what their presentational structure is, how they may be represented (as free text, as coded values, etc.), and with which formal [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] object types they are associated.
145 +* //**Dataflow Definition:**// In [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] are reported or disseminated according to a [[data flow>>doc:sdmx:Glossary.Dataflow.WebHome]] definition. The [[data flow>>doc:sdmx:Glossary.Dataflow.WebHome]] definition identifies the [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] and may be associated with one or more subject matter domains via a Categorisation (this facilitates the search for data according to organised [[category schemes>>doc:sdmx:Glossary.Category scheme.WebHome]]). [[Constraints>>doc:Glossary.Constraint.WebHome]], in terms of reporting periodicity or sub set of possible keys that are allowed in a [[data set>>doc:sdmx:Glossary.Data set.WebHome]], may be attached to the [[data flow>>doc:sdmx:Glossary.Dataflow.WebHome]] definition.
146 +* //**Metadataflow Definition:**// A [[metadata flow>>doc:sdmx:Glossary.Metadataflow.WebHome]] definition is very similar to a [[data flow>>doc:sdmx:Glossary.Dataflow.WebHome]] definition, but describes, categorises, and constrains [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]].
147 +* //**[[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]]: **//An organization which produces data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] is termed a [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]].
148 +* //**[[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 provider>>doc:sdmx:Glossary.Data provider.WebHome]]. 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-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).
149 +* //**[[Constraint>>doc:Glossary.Constraint.WebHome]]:**// [[Constraints>>doc:Glossary.Constraint.WebHome]] describe a subset of a [[data source>>doc:sdmx:Glossary.Data source.WebHome]] or metadata source, and may also provide information about scheduled releases of data. They are associated with [[data providers>>doc:sdmx:Glossary.Data provider.WebHome]], [[provision agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]], [[data flows>>doc:sdmx:Glossary.Dataflow.WebHome]], [[metadataflows>>doc:sdmx:Glossary.Metadataflow.WebHome]], [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]] and [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]].
150 +* //**Structure Set: **//[[Structure sets>>doc:sdmx:Glossary.Structure set.WebHome]] provide a mechanism for grouping [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] together to form a complete description of the relationships between specific, related sets of data and metadata. They can be used to map [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] and [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] to one another, to map (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%), to map [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], and to map [[category schemes>>doc:sdmx:Glossary.Category scheme.WebHome]]. They can be used to describe “cubes” of data, even when the data within the cube does not share a single dimensionality.
151 +* //**Reporting Taxonomy: **//A reporting taxonomy 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.
152 +* //**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>>doc:sdmx:Glossary.Concept.WebHome]](%%).
153 +* //**[[Hierarchical Code List>>doc:sdmx:Glossary.Hierarchical code list.WebHome]]:**// This supports the specification of [[code>>doc:sdmx:Glossary.Code.WebHome]] [[hierarchies>>doc:sdmx:Glossary.Hierarchy.WebHome]]. 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. The [[Hierarchical Code List>>doc:sdmx:Glossary.Hierarchical code list.WebHome]] thus specifies the organisation of the [[codes>>doc:sdmx:Glossary.Code.WebHome]] in one or more [[hierarchies>>doc:sdmx:Glossary.Hierarchy.WebHome]], but does not define the [[codes>>doc:sdmx:Glossary.Code.WebHome]] themselves.
153 153  
154 -=== Notes on Data Structuring ===
155 +(% class="wikigeneratedid" id="HNotesonDataStructuring" %)
156 +**Notes on Data Structuring**
155 155  
156 -A “cube” is a rich, multi-dimensional construct, which can be viewed along any of its axes (or “dimensions”). Whilst the full structure of cube data can be described in SDMX, the actual “data” specification of SDMX takes a slightly narrower view of these requirements in its version 2.0/2.1 specifications for the purposes of formatting the data for transmission. The view of data in many SDMX formats is primarily as time series – that is, as a set of observations which are organized around the time dimension, so that each observation occurs progressively through time.
158 +A “cube” is a rich, multi-dimensional construct, which can be viewed along any of its axes (or “[[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]]”). Whilst the full structure of cube data can be described in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], the actual “data” specification of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] takes a slightly narrower view of these requirements in its version 2.0/2.1 specifications for the purposes of formatting the data for transmission. The view of data in many [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] formats is primarily as time series – that is, as a set of observations which are organized around the time [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]], so that each observation occurs progressively through time.
157 157  
158 -There are, however, many types of statistical data which are not typically organized for exchange as time series where data are organized around some other, non-time dimension of the cube – what is often called “cross-sectional” data. SDMX supports a unified format that represents in the data set an organisation of the data along any single dimension. In this context, time series is a particular case of the unified format.
160 +There are, however, many types of statistical data which are not typically organized for exchange as time series where data are organized around some other, non-time [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] of the cube – what is often called “cross-sectional” data. [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] supports a unified format that represents in the [[data set>>doc:sdmx:Glossary.Data set.WebHome]] an organisation of the data along any single [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]. In this context, time series is a particular case of the unified format.
159 159  
160 -Another type of structure commonly found in statistical “cubes” of data is the hierarchical classification, used to describe the points along any of its dimensions (or axes). In the 1.0 version, SDMX standards did not provide full support for this functionality. The introduction of these hierarchical classifications is present in the current version of the standard.
162 +Another type of structure commonly found in statistical “cubes” of data is the hierarchical classification, used to describe the points along any of its [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] (or axes). In the 1.0 version, [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards did not provide full support for this functionality. The introduction of these hierarchical classifications is present in the current version of the standard.
161 161  
162 -Further, there is support for the expression of functional dependencies between the various dimensions of a cube, giving support for better processing of “sparse cubes”. This is an aspect of “constraints”, which allow for the framing of a cube region, or for the provision of a set of valid keys within the total set of keys described by the data structure definition.
164 +Further, there is support for the expression of functional dependencies between the various [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] of a cube, giving support for better processing of “sparse cubes”. This is an aspect of “constraints”, which allow for the framing of a cube region, or for the provision of a set of valid keys within the total set of keys described by the [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]].
163 163  
164 -=== Notes on Reference Metadata Structuring ===
166 +(% class="wikigeneratedid" id="HNotesonReferenceMetadataStructuring" %)
167 +**Notes on Reference Metadata Structuring**
165 165  
166 -Metadata structures are based on the idea that concepts can be organised into semantic and presentational hierarchies, and that these hierarchies can form the basis for the structuring of XML reporting formats. There are three message types in SDMX-ML which serve this purpose: the Structure message (providing the metadata structure definition), the Generic Metadata message (providing a single format for any metadata structure definition), and the Structure-specific Metadata message (providing a metadata structure definition-specific format). Typically, this mechanism is suited to supporting reference metadata reporting and dissemination.
169 +Metadata structures are based on the idea that (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) can be organised into semantic and presentational [[hierarchies>>doc:sdmx:Glossary.Hierarchy.WebHome]], and that these [[hierarchies>>doc:sdmx:Glossary.Hierarchy.WebHome]] can form the basis for the structuring of XML reporting formats. There are three message types in [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] which serve this purpose: the Structure message (providing the [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]), the Generic Metadata message (providing a single format for any [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]), and the Structure-specific Metadata message (providing a [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]-specific format). Typically, this mechanism is suited to supporting [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] reporting and dissemination.
167 167  
168 -The Metadata Structure Definition takes //any// concept from concept schemes, and describes how they can be formed into a reporting or dissemination structure as metadata attributes – either as a flat list, or as a hierarchy. The metadata attributes are assigned representations (coded, textual, etc.) and the number of occurrences.
171 +The [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] takes //any// (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) from [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]], and describes how they can be formed into a reporting or dissemination structure as metadata [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] – either as a flat list, or as a [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]. The metadata [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] are assigned [[representations>>doc:sdmx:Glossary.Representation.WebHome]] (coded, textual, etc.) and the number of occurrences.
169 169  
170 -The “target” of the metadata – that is, the class of process, information, organisation, exchange, etc. – which is the subject of the metadata is described. Because the SDMX Information Model gives a formalization of statistical exchange and dissemination, the model can be used as a typology of the different actors and resources within statistical activities. Thus, the “targets” (subjects) of reference metadata sets and metadata flows can be described as corresponding to some standard class by reference to this model.
173 +The “target” of the metadata – that is, the class of process, information, organisation, exchange, etc. – which is the subject of the metadata is described. Because the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] gives a formalization of statistical exchange and dissemination, the model can be used as a typology of the different actors and resources within statistical activities. Thus, the “targets” (subjects) of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] sets and [[metadata flows>>doc:sdmx:Glossary.Metadataflow.WebHome]] can be described as corresponding to some standard class by reference to this model.
171 171  
172 -As with data structures, the generic format for metadata sets provides a known document structure, whilst the structure specific format is derived specifically from a metadata structure definition and can perform a higher degree of schema validation.
175 +As with data structures, the generic format for [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] provides a known document structure, whilst the structure specific format is derived specifically from a [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] and can perform a higher degree of schema validation.
173 173  
174 -== {{id name="_Toc38915"/}}3.5 SDMX Registry Services ==
177 +== SDMX Registry Services ==
175 175  
176 -In order to provide visibility into the large amount of data and metadata which exists within the SDMX model of statistical exchange, it is felt that an architecture based on a set of registry services is potentially useful. A “registry” – as understood in webservices terminology – is an application which maintains and stores metadata for querying, and which can be used by any other application in the network with sufficient access privileges (though note that the mechanism of access control is outside of the scope of the SDMX standard). It can be understood as the index of a distributed database or metadata repository which is made up of all the data provider’s data sets and reference metadata sets within a statistical community, located across the Internet or similar network.
179 +In order to provide visibility into the large amount of data and metadata which exists within the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] model of statistical exchange, it is felt that an architecture based on a set of registry services is potentially useful. A “registry” – as understood in webservices terminology – is an application which maintains and stores metadata for querying, and which can be used by any other application in the network with sufficient access privileges (though note that the mechanism of access control is outside of the scope of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standard). It can be understood as the index of a distributed database or [[metadata repository>>doc:sdmx:Glossary.Metadata repository.WebHome]] which is made up of all the [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]]’s [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] sets within a statistical community, located across the Internet or similar network.
177 177  
178 -Note that the SDMX registry services are not concerned with the storage of data or reference metadata. The assumption is that data and reference metadata lives on the sites of its data providers. The SDMX registry services concern themselves with providing visibility of the data and reference metadata, and information needed to access the data and reference metadata. Thus, a registered data set will have its URL available in the registry, but not the data itself. An application which wishes to access that data would query the registry, perhaps by drilling down via a Category Scheme and Dataflow, for the URL of a registered data source, and then retrieve the data directly from the data provider (using an SDMX-ML query message or other mechanism).
181 +Note that the [[SDMX registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] services are not concerned with the storage of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. The assumption is that data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] lives on the sites of its [[data providers>>doc:sdmx:Glossary.Data provider.WebHome]]. The [[SDMX registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] services concern themselves with providing visibility of the data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]], and information needed to access the data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. Thus, a registered [[data set>>doc:sdmx:Glossary.Data set.WebHome]] will have its URL available in the registry, but not the data itself. An application which wishes to access that data would query the registry, perhaps by drilling down via a [[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] and [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], for the URL of a registered [[data source>>doc:sdmx:Glossary.Data source.WebHome]], and then retrieve the data directly from the [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]] (using an [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] query message or other mechanism).
179 179  
180 -SDMX does not require a particular technology implementation of the registry – instead, it specifies the standard interfaces which may be supported by a registry. Thus, users may implement an SDMX-conformant registry in any fashion they choose, so long as the interfaces are supported as specified here. These interfaces are expressed as XML documents, and form a new part of the SDMX-ML language.
183 +[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] does not require a particular technology implementation of the registry – instead, it specifies the standard interfaces which may be supported by a registry. Thus, users may implement an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-conformant registry in any fashion they choose, so long as the interfaces are supported as specified here. These interfaces are expressed as XML documents, and form a new part of the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] language.
181 181  
182 182  The registry services discussed here can be briefly summarized:
183 183  
184 -* //**Maintenance of Structural Metadata**//**:** This registry service allows users with maintenance agency access privileges to submit and modify structural metadata. In this aspect the registry is acting as a structural metadata repository. However, it is permissible in an SDMX structure to submit just the “stub” of the structural object, such as a code list, and for this stub to reference the actual location from where the metadata can be retrieved, either from a file or a structural metadata resource, such as another registry.
185 -* //**Registration of Data and Metadata Sources: **//This registry service allows users with maintenance agency access privileges to inform the registry of the existence and location (for retrieval) of data sets and reference metadata sets. The registry stores metadata about these objects, and links it to the structural metadata that give sufficient structural information for an application to process it, or for an application to discover its existence. Objects in the registry are organized and categorized according to one or more category schemes.
186 -* //**Querying: **//The registry services have interfaces for querying the metadata contained in a registry, so that applications and users can discover the existence of data sets and reference metadata sets, structural metadata, the providers/agencies associated with those objects, and the provider agreements which describe how the data and metadata are made available, and how they are categorized.
187 -* //**Subscription/Notification:**// It is possible to “subscribe” to specific objects in a registry, so that a notification will be sent to all subscribers whenever the registry objects are updated.
187 +* //**Maintenance of [[Structural Metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]**//**:** This registry service allows users with [[maintenance agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] access privileges to submit and modify [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. In this aspect the registry is acting as a [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] repository. However, it is permissible in an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] structure to submit just the “stub” of the structural object, such as a [[code list>>doc:sdmx:Glossary.Code list.WebHome]], and for this stub to reference the actual location from where the metadata can be retrieved, either from a file or a [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] resource, such as another registry.
188 +* //**Registration of Data and Metadata Sources: **//This registry service allows users with [[maintenance agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] access privileges to inform the registry of the existence and location (for retrieval) of [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] sets. The registry stores metadata about these objects, and links it to the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] that give sufficient structural information for an application to process it, or for an application to discover its existence. Objects in the registry are organized and categorized according to one or more [[category schemes>>doc:sdmx:Glossary.Category scheme.WebHome]].
189 +* //**Querying: **//The registry services have interfaces for querying the metadata contained in a registry, so that applications and users can discover the existence of [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] sets, [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]], the providers/agencies associated with those objects, and the provider agreements which describe how the data and metadata are made available, and how they are categorized.
190 +* //**[[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]]/[[Notification>>doc:sdmx:Glossary.Notification.WebHome]]:**// It is possible to “subscribe” to specific objects in a registry, so that a [[notification>>doc:sdmx:Glossary.Notification.WebHome]] will be sent to all subscribers whenever the registry objects are updated.
188 188  
189 -== {{id name="_Toc38916"/}}3.6 Web services ==
192 +== 3.6 Web services ==
190 190  
191 191  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.
192 192  
193 -SDMX provides guidelines for using these standards in a fashion which will promote interoperability among SDMX web services, and allow for the creation of generic client applications which will be able to communicate meaningfully with any SDMX web service which implements these guidelines.
196 +[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] provides guidelines for using these standards in a fashion which will promote interoperability among [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] web services, and allow for the creation of generic client applications which will be able to communicate meaningfully with any [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] web service which implements these guidelines.
194 194  
195 -More specifically, the SDMX web services guidelines offer:
198 +More specifically, the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] web services guidelines offer:
196 196  
197 -* A normative interface (WSDL) for SOAP-based web services: The 2.0 WebServices Guidelines contained a set of web-services functions, but these have been found through implementation to be insufficient for the types of SDMX-based web services now being developed. Furthermore, the operations and their payload have now become normative (WSDL).
198 -* A normative interface (WADL) for RESTful web services: The RESTful API focuses on simplicity. The aim is not to replicate the full semantic richness of the SDMX-ML Query message but to make it simple to perform a limited set of standard queries. Also, in contrast to other parts of the SDMX specification, the RESTful API focuses solely on data retrieval (via HTTP GET).
200 +* A normative interface (WSDL) for SOAP-based web services: The 2.0 WebServices Guidelines contained a set of web-services functions, but these have been found through implementation to be insufficient for the types of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-based web services now being developed. Furthermore, the operations and their payload have now become normative (WSDL).
201 +* A normative interface (WADL) for RESTful web services: The RESTful API focuses on simplicity. The aim is not to replicate the full semantic richness of the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Query message but to make it simple to perform a limited set of standard queries. Also, in contrast to other parts of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] specification, the RESTful API focuses solely on data retrieval (via HTTP GET).
199 199  
200 -A normative list of common error codes: When web services are used, it is necessary to have error codes which can help to explain the situation when problems are encountered. Prior to version 2.1 of the SDMX standard, there was no set of agreed error codes for use with SDMX web services. Version 2.1 of the SDMX standard fills that gap.
203 +A normative list of common error [[codes>>doc:sdmx:Glossary.Code.WebHome]]: When web services are used, it is necessary to have error [[codes>>doc:sdmx:Glossary.Code.WebHome]] which can help to explain the situation when problems are encountered. Prior to version 2.1 of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standard, there was no set of agreed error [[codes>>doc:sdmx:Glossary.Code.WebHome]] for use with [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] web services. Version 2.1 of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standard fills that gap.
201 201  
202 -= {{id name="_Toc38917"/}}4 The SDMX Information Model =
205 += 4 The SDMX Information Model =
203 203  
204 -SDMX provides a way of modelling statistical data, and defines the set of metadata constructs used for this purpose. Because SDMX specifies formats in two syntaxes for expressing data and structural metadata, the model is used as a mechanism for guaranteeing that transformation between the different formats are lossless. All of the formats are syntax-bound expressions of the common information model. SDMX version 1.0 has based itself on GESMES/TS as an input to the model and formats, both to build on the proven success of this model for time series data exchange, and to ensure backward compatibility with existing GESMES/TS-based systems. Version 2.0/2.1 expands upon the version 1.0 basis to provide a more comprehensive model.
207 +[[SDMX>>doc:sdmx:Glossary.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.Statistical data and metadata exchange.WebHome]] specifies formats in two syntaxes for expressing data and [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]], the model is used as a mechanism for guaranteeing that transformation between the different formats are lossless. All of the formats are syntax-bound expressions of the common information model. [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] version 1.0 has based itself on GESMES/TS as an input to the model and formats, both to build on the proven success of this model for time series data exchange, and to ensure backward compatibility with existing GESMES/TS-based systems. Version 2.0/2.1 expands upon the version 1.0 basis to provide a more comprehensive model.
205 205  
206 -SDMX recognizes that statistical data is structured; in SDMX this structure is termed a Data Structure Definition. “Data sets” 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” of data. Each series or section has a “key” - values for each of a cluster of concepts, also called "dimensions" - 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”. Code lists (enumerations) and other patterns for representation of data and metadata are also modelled.
209 +[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] recognizes that statistical data is structured; in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] this structure is termed a [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]. [[Data sets>>doc:sdmx:Glossary.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” of data. Each series or section has a “key” - values for each of a cluster of concepts, also called [[dimensions>>doc:sdmx:Glossary.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.Attribute.WebHome]]”. [[Code lists>>doc:sdmx:Glossary.Code list.WebHome]] (enumerations) and other patterns for [[representation>>doc:sdmx:Glossary.Representation.WebHome]] of data and metadata are also modelled.
207 207  
208 -There is some similarity between “cube” structures commonly used to process statistical data, and the Data Structure Definition idea in the SDMX Information Model. It is important to note that the data as structured according to the SDMX Information Model is optimized for exchange, potentially with partners who may have no ability to process a “cube” of data coming from complex statistical systems. SDMX time series can be understood as “slices” of the cube. Such a slice is identified by its key. A "series" key consists of the values for all dimensions specified by the key family except time. It is certainly possible to reconstruct and describe data cubes from SDMX-structured data, and to exchange such databases according to the proposed standards. In version 2.0, it becomes possible to more fully describe the structure of cubes, with hierarchical code lists, constraints, and relationships between data structure definitions.
211 +There is some similarity between “cube” structures commonly used to process statistical data, and the [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] idea in the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]. It is important to note that the data as structured according to the [[SDMX Information Model>>doc:sdmx:Glossary.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.Statistical data and metadata exchange.WebHome]] time series can be understood as “slices” of the cube. Such a slice is identified by its key. A "series" key consists of the values for all [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] specified by the key family except time. It is certainly possible to reconstruct and describe data cubes from [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-structured data, and to exchange such databases according to the proposed standards. In version 2.0, it becomes possible to more fully describe the structure of cubes, with [[hierarchical code lists>>doc:sdmx:Glossary.Hierarchical code list.WebHome]], [[сonstraints>>doc:Glossary.Constraint.WebHome]], and relationships between [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]].
209 209  
210 -In version 2.0/2.1, the SDMX standards also provide a view of reference metadata: a mechanism for referencing the meaningful “objects” within the SDMX view of statistical exchange processes (data providers, structures, provisioning agreements, dataflows, metadata flows, 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 which is common to many metadata systems and classification/categorization schemes. SDMX provides a model (and XML formats) for both describing reference metadata structures, and of reporting reference metadata according to those structures.
213 +In version 2.0/2.1, the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards also provide a view of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]: a mechanism for referencing the meaningful “objects” within the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] view of statistical exchange processes ([[data providers>>doc:sdmx:Glossary.Data provider.WebHome]], structures, [[provisioning agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]], [[dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]], [[metadata flows>>doc:sdmx:Glossary.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.Reference metadata.WebHome]] which is common to many metadata systems and classification/categorization schemes. [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] provides a model (and XML formats) for both describing [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] structures, and of reporting [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] according to those structures.
211 211  
212 -Version 2.0/2.1 also introduces 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 and how they are providing it can be expressed; and the technical aspects of service-level agreements (and similar types of provisioning agreements) can be represented.
215 +Version 2.0/2.1 also introduces 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.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.Provision agreement.WebHome]]) can be represented.
213 213  
214 -The SDMX Information Model formally describes all of the objects listed above, so as to present a standard view of the statistical exchange process.
217 +The [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] formally describes all of the objects listed above, so as to present a standard view of the statistical exchange process.
215 215  
216 -The SDMX Information Model is presented using UML, and is also described in prose. While the information model is not normative, it is a valuable tool for understanding and using the normative format specifications.
219 +The [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] is presented using UML, and is also described in prose. While the information model is not normative, it is a valuable tool for understanding and using the normative format specifications.
217 217  
218 -= {{id name="_Toc38918"/}}5 SDMX-EDI =
221 += 5 SDMX-EDI =
219 219  
220 -The SDMX-EDI format is drawn from the GESMES/TS version 3.0 implementation guide, as published as a standard of the SDMX initiative.
223 +The [[SDMX-EDI>>doc:sdmx:Glossary.SDMX-EDI.WebHome]] format is drawn from the GESMES/TS version 3.0 implementation guide, as published as a standard of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] initiative.
221 221  
222 -1. //Statistical Definitions~:// An expression of the structural metadata covered by the SDMX information model in a UN/EDIFACT format.
223 -1. //Statistical Data~:// Optimized for the batch exchange of large amounts of time series data between counterparties, it allows for extremely compact expression of large whole or partial data sets. Non time series data, such as cross-sectional, can be supported if represented as repackaged time series, but there is no direct support for cross-sectional data in this format.
224 -1. //Data Set List~:// a list of data sets and their structural metadata.
225 +1. //Statistical Definitions~:// An expression of the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] covered by the [[SDMX information model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] in a UN/EDIFACT format.
226 +1. //Statistical Data~:// Optimized for the batch exchange of large amounts of time series data between counterparties, it allows for extremely compact expression of large whole or partial [[data sets>>doc:sdmx:Glossary.Data set.WebHome]]. Non time series data, such as cross-sectional, can be supported if represented as repackaged time series, but there is no direct support for cross-sectional data in this format.
227 +1. //[[Data Set>>doc:sdmx:Glossary.Data set.WebHome]] List~:// a list of [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and their [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]].
225 225  
226 -The SDMX Information Model provides the constructs which are found in the
229 +The [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] provides the constructs which are found in the
227 227  
228 -EDIFACT syntax used for SDMX-EDI, and those found in the XML syntax of SDMXML. Since both syntactic implementations reflect the same logical constructs, SDMXEDI data and structural metadata messages can be transformed into corresponding SDMX-ML formats, and vice-versa. Thus, these standards provide for interoperability between the UN/EDIFACT-based and XML-based systems processing and exchanging statistical data and metadata.
231 +EDIFACT syntax used for [[SDMX-EDI>>doc:sdmx:Glossary.SDMX-EDI.WebHome]], and those found in the XML syntax of SDMXML. Since both syntactic implementations reflect the same logical constructs, SDMXEDI data and [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] messages can be transformed into corresponding [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] formats, and vice-versa. Thus, these standards provide for interoperability between the UN/EDIFACT-based and XML-based systems processing and exchanging statistical data and metadata.
229 229  
230 -= {{id name="_Toc38919"/}}6 SDMX-ML =
233 += 6 SDMX-ML =
231 231  
232 -While the SDMX-EDI format is primarily designed to support batch exchange, SDMXML supports a wider range of requirements. XML formats are used for many different types of automated processing, and thus must support more varied processing scenarios. That is why there are several types of messages available as SDMX-ML formats. Each is suited to support a specific set of processing requirements.
235 +While the [[SDMX-EDI>>doc:sdmx:Glossary.SDMX-EDI.WebHome]] format is primarily designed to support batch exchange, SDMXML supports a wider range of requirements. XML formats are used for many different types of automated processing, and thus must support more varied processing scenarios. That is why there are several types of messages available as [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] formats. Each is suited to support a specific set of processing requirements.
233 233  
234 -1. //Structure Definition~:// All SDMX-ML message types share a common XML expression of the metadata needed to understand and process a data set or metadata set, and additional metadata about category schemes and organisations is included. Also, the structural aspects of data and metadata provision – dataflows and metadataflows – are described using this format.
235 -1. //Generic Data~:// All statistical data expressible in SDMX-ML can be marked up according to this data format, in agreement with the contents of a Structure Definition message. It is designed for any scenario where applications receiving the data need to process it according to a single format. Such applications may need independent access to the data set's structure before they process it. Data marked up in this format are not particularly compact, but they make easily available all aspects of the data set. This format does not provide strict validation between the data set and its structural definition using a generic XML parser. It supports the transmission of partial data sets (incremental updates) as well as whole data sets. It supports both the timeseries and the cross-sectional use cases.
236 -1. //Structure-specific Data~:// This format is specific to the Data Structure Definition of the data set (in other terms, it is DSD-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 in XML format (typically the size of the data set is 50% of the same data expressed as Generic Data), provides strict validation of conformance with the DSD using a generic XML parser, and supports the transmission of partial data sets (incremental updates) as well as whole data sets. The Structure-specific Data format specified in SDMX 2.1 supports both the time-series and the cross-sectional use cases which were covered by two distinct formats in SDMX 2.0. 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.
237 -1. //Generic Metadata~:// All reference metadata expressible in SDMX-ML format can be marked up according to this schema. It performs only a minimum of validation, and is somewhat verbose, but it does support the creation of generic software tools and services for processing reference metadata.
238 -1. //Structure-specific Metadata~:// For each metadata structure definition, an XML schema specific to that structure can be created, to perform validation on sets of reported metadata. This structure is less verbose than the Generic Metadata format, and, because the XML mark-up relates directly to the reported concepts, it is appropriate for applications that are designed to process a specific type of metadata report. It is analogous to the Structurespecific Data format for data in its approach to the use of XML.
239 -1. //Query~:// Data and metadata are often published in databases which are available on the web. Thus, it is necessary to have a standard query document which allows the databases to be queried, and return an SDMX-ML data, reference metadata, or structure message. The Query document is an implementation of the SDMX Information Model for use in web services and database-driven applications, allowing for a standard request to be sent to data providers using these technologies.
240 -1. //Registry~:// All of the possible interactions with the SDMX registry services are supported using SDMX-ML interfaces. All but one of these documents are based on a synchronous exchange of documents – a “request” message answered by a “response” message. There are two basic types of request – a “Submit”, which writes metadata to the registry services, and a “Query”, which is used to discover that metadata. Registry interactions provide formats for all types of provisioning metadata, as well as for subscription/notification, structural metadata, and data and metadata registration. The exception is the (Registry) notification message which is asynchronous.
237 +1. //Structure Definition~:// All [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] message types share a common XML expression of the metadata needed to understand and process a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]], and additional metadata about [[category schemes>>doc:sdmx:Glossary.Category scheme.WebHome]] and organisations is included. Also, the structural aspects of data and metadata provision – [[dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] and [[metadataflows>>doc:sdmx:Glossary.Metadataflow.WebHome]] – are described using this format.
238 +1. //Generic Data~:// All statistical data expressible in [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] can be marked up according to this data format, in agreement with the contents of a Structure Definition message. It is designed for any scenario where applications receiving the data need to process it according to a single format. Such applications may need independent access to the [[data set>>doc:sdmx:Glossary.Data set.WebHome]]'s structure before they process it. Data marked up in this format are not particularly compact, but they make easily available all aspects of the [[data set>>doc:sdmx:Glossary.Data set.WebHome]]. This format does not provide strict validation between the [[data set>>doc:sdmx:Glossary.Data set.WebHome]] and its structural definition using a generic XML parser. It 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]]. It supports both the timeseries and the cross-sectional use cases.
239 +1. //Structure-specific Data~:// This format is specific to the [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] of the [[data set>>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 (typically the size of the [[data set>>doc:sdmx:Glossary.Data set.WebHome]] is 50% of the same data expressed as Generic Data), 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]]. The Structure-specific Data format specified in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 supports both the time-series and the cross-sectional use cases which were covered by two distinct formats in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.0. 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.
240 +1. //Generic Metadata~:// All [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] expressible in [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] format can be marked up according to this schema. It performs only a minimum of validation, and is somewhat verbose, but it does support the creation of generic software tools and services for processing [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]].
241 +1. //Structure-specific Metadata~:// For each [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], an XML schema specific to that structure can be created, to perform validation on sets of reported metadata. This structure is less verbose than the Generic Metadata format, and, because the XML mark-up relates directly to the reported (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%), it is appropriate for applications that are designed to process a specific type of metadata report. It is analogous to the Structurespecific Data format for data in its approach to the use of XML.
242 +1. //Query~:// Data and metadata are often published in databases which are available on the web. Thus, it is necessary to have a standard query document which allows the databases to be queried, and return an [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] data, [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]], or structure message. The Query document is an implementation of the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] for use in web services and database-driven applications, allowing for a standard request to be sent to [[data providers>>doc:sdmx:Glossary.Data provider.WebHome]] using these technologies.
243 +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. All but one of these documents are based on a synchronous exchange of documents – a “request” message answered by a “response” message. There are two basic types of request – a “Submit”, which writes metadata to the registry services, and a “Query”, which is used to discover that metadata. Registry interactions provide formats for all types of provisioning metadata, as well as for [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]]/[[notification>>doc:sdmx:Glossary.Notification.WebHome]], [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]], and data and metadata registration. The exception is the (Registry) [[notification>>doc:sdmx:Glossary.Notification.WebHome]] message which is asynchronous.
241 241  
242 -Because all of the SDMX-ML formats are implementations of the same information model, and all the data and metadata messages are derivable from the Structure message which describes a data set or metadata set, it is possible to have standard mappings between each of the similar formats. These mappings can be implemented in generic transformation tools, useful to all SDMX-ML users, and not specific to a particular data set’s key family or metadata set’s structure definition (even though some of the formats they deal with may be). Part of the SDMX-ML package is the set of mappings between the structure-specific data and metadata formats and the Structure Definition format from which all are derivable.
245 +Because all of the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] formats are implementations of the same information model, and all the data and metadata messages are derivable from the Structure message which describes a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]], it is possible to have standard mappings between each of the similar formats. These mappings can be implemented in generic transformation tools, useful to all [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] users, and not specific to a particular [[data set>>doc:sdmx:Glossary.Data set.WebHome]]’s key family or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]]’s structure definition (even though some of the formats they deal with may be). Part of the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] package is the set of mappings between the structure-specific data and metadata formats and the Structure Definition format from which all are derivable.
243 243  
244 -= {{id name="_Toc38920"/}}7 Conformance =
247 += 7 Conformance =
245 245  
246 -This section will contain a normative statement of what applications must do to be considered conformant with the SDMX version 2.1 specifications. This will address both the application functionality that must be supported, and the contents of an Implementer’s Conformance Statement regarding SDMX conformance.
249 +This section will contain a normative statement of what applications must do to be considered conformant with the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] version 2.1 specifications. This will address both the application functionality that must be supported, and the contents of an Implementer’s Conformance Statement regarding [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] conformance.
247 247  
248 -= {{id name="_Toc38921"/}}8 Dependencies on SDMX content-oriented guidelines =
251 += 8 Dependencies on SDMX content-oriented guidelines =
249 249  
250 -The technical standards proposed here are designed so that they can be used in conjunction with other SDMX guidelines which are more closely tied to the content and semantics of statistical data exchange. The SDMX Information Model works equally well with any statistical concept, but to encourage interoperability, it is also necessary to standardize and harmonize the use of specific concepts and terminology. To achieve this goal, SDMX creates and maintains guidelines for crossdomain concepts, terminology, and structural definitions. There are three major parts to this effort.
253 +The technical standards proposed here are designed so that they can be used in conjunction with other [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] guidelines which are more closely tied to the content and semantics of statistical data exchange. The [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] works equally well with any statistical (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%), but to encourage interoperability, it is also necessary to standardize and harmonize the use of specific (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) and terminology. To achieve this goal, [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] creates and maintains guidelines for crossdomain (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%), terminology, and structural definitions. There are three major parts to this effort.
251 251  
252 -== {{id name="_Toc38922"/}}8.1 Cross-Domain Concepts ==
255 +== 8.1 Cross-Domain Concepts ==
253 253  
254 -The SDMX Cross-Domain Concepts is a content guideline concerning concepts which are used across statistical domains. This list is expected to grow and to be subject to revision as SDMX is used in a growing number of domains. The use of the SDMX Cross-Domain Concepts, where appropriate, provides a framework to further promote interoperability among organisations using the technical standards presented here. The harmonization of statistical concepts includes not only the definitions of the concepts, and their names, but also, where appropriate, their representation with standard code lists, and the role they play within data structure definitions and metadata structure definitions.
257 +The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Cross-Domain Concepts>>doc:sdmx:Glossary.Cross-domain concept.WebHome]] is a content guideline concerning (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) which are used across [[statistical domains>>doc:sdmx:Glossary.Statistical subject-matter domain.WebHome]]. This list is expected to grow and to be subject to revision as [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] is used in a growing number of domains. The use of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Cross-Domain Concepts>>doc:sdmx:Glossary.Cross-domain concept.WebHome]], where appropriate, provides a framework to further promote interoperability among organisations using the technical standards presented here. The harmonization of statistical (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) includes not only the definitions of the (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%), and their names, but also, where appropriate, their [[representation>>doc:sdmx:Glossary.Representation.WebHome]] with standard [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], and the role they play within [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]] and metadata structure definitions.
255 255  
256 -The intent of this guideline is two-fold: to provide a core set of concepts which can be used to structure statistical data and metadata, to promote interoperability between systems (“structural metadata”, as described above); and to promote the exchange of metadata more widely, with a set of harmonized concept names and definitions for other types of metadata (“reference metadata”, as defined above.)
259 +The intent of this guideline is two-fold: to provide a core set of (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) which can be used to structure statistical data and metadata, to promote interoperability between systems (“[[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]”, as described above); and to promote the exchange of metadata more widely, with a set of harmonized (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) names and definitions for other types of metadata (“[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]”, as defined above.)
257 257  
258 -== {{id name="_Toc38923"/}}8.2 Metadata Common Vocabulary ==
261 +== 8.2 Metadata Common Vocabulary ==
259 259  
260 -The Metadata Common Vocabulary is an SDMX guideline which provides definition of terms to be used for the comparison and mapping of terminology found in data structure definitions and in other aspects of statistical metadata management. Essentially, it provides ISO-compliant definitions for a wide range of statistical terms, which may be used directly, or against which other terminology systems may be mapped. This set of terms is inclusive of the terminology used within the SDMX Technical Standards.
263 +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 ISO-compliant definitions for a wide range of statistical terms, which may be used directly, or against which other terminology systems may be 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.
261 261  
262 -The MCV provides definitions for terms on which the SDMX Cross-Domain Metadata Concepts work is built.
265 +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>>doc:sdmx:Glossary.Concept.WebHome]](%%) work is built.
263 263  
264 -== {{id name="_Toc38924"/}}8.3 Statistical Subject-Matter Domains ==
267 +== 8.3 Statistical Subject-Matter Domains ==
265 265  
266 -The Statistical Subject-Matter Domains 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 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, concepts, etc. within their domains. Such groups already exist within the international community. SDMX would use the Statistical Subject-Matter Domains list to facilitate the efforts of these groups to develop the kinds of content standards which could support the interoperation of SDMXconformant technical systems within and across statistical domains. The organisation of the content of such schemes is supported in SDMX as a Category Scheme.
269 +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 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>>doc:sdmx:Glossary.Concept.WebHome]](%%), 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 SDMXconformant 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 Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]].
267 267  
268 -SDMX Statistical Subject-Matter Domains will be listed and maintained by the SDMX Initiative and will be subject to adjustment.
271 +[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Statistical Subject-Matter Domains>>doc:sdmx:Glossary.Statistical subject-matter domain.WebHome]] will be listed and maintained by the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Initiative and will be subject to adjustment.
269 269  
270 -= {{id name="_Toc38925"/}}9 Looking Forward =
273 += 9 Looking Forward =
271 271  
272 -The SDMX initiative sees this set of data and metadata formats and registry services interfaces standards as useful in creating more efficient and open systems for statistical exchange. It is anticipated that SDMX will refine these standards further as they are implemented, so as to build on the interoperability enabled by having a set of standard formats and exchanges based on a common information model.
275 +The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] initiative sees this set of data and metadata formats and registry services interfaces standards as useful in creating more efficient and open systems for statistical exchange. It is anticipated that [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] will refine these standards further as they are implemented, so as to build on the interoperability enabled by having a set of standard formats and exchanges based on a common information model.
273 273  
274 -The review process for version 2.0 and 2.1 has suggested that future work should take advantage of a wider participation of the SDMX user community (statistical offices, central banks and other national and international organisations dealing with statistics) in further enhancing the Technical Standards and improving its use.
277 +The review process for version 2.0 and 2.1 has suggested that future work should take advantage of a wider participation of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] user community (statistical offices, central banks and other national and international organisations dealing with statistics) in further enhancing the Technical Standards and improving its use.
275 275  
276 -= {{id name="_Toc38926"/}}10 Validation and Transformation Language =
279 += 10 Validation and Transformation Language =
277 277  
278 -For many years the SDMX initiative has been fostering and supporting the development of a standard calculation language, called Validation and Transformation Language (VTL). A blueprint for defining calculations was already described in the original SDMX 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 able to manipulate SDMX artefacts.
281 +For many years the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] initiative has been fostering and supporting the development of a standard calculation language, called [[Validation and Transformation Language>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] ([[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]). A blueprint for defining calculations was already described in the original [[SDMX>>doc:sdmx:Glossary.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 able to manipulate [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]].
279 279  
280 -These developments started in late 2012 and were put in charge of the Validation and Transformation Language Task Force (VTL TF), which included members of the SDMX Technical Working Group (TWG) and Statistical Working Group (SWG), besides experts coming from the DDI and GSIM communities. The intent was to define a stardard language to be implemented in SDMX and applicable also to GSIM and DDI. This brought to the publication of the VTL 1.0 in 2015. Then new requirements came from a number of proofs of concepts and tests of VTL 1.0 made by several organisations and triggered a large improvement of the language. A new provisional version, the VTL 1.1, was released in public consultation in 2017. The high number of comments received triggered another phase of intensive work, with the main goal of achieving a more robust and forward compatible version. Finally, the VTL 2.0 was published between April and July 2018 (see the SDMX website).
283 +These developments started in late 2012 and were put in charge of the [[Validation and Transformation Language>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Task Force ([[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] TF), which included members of the [[SDMX>>doc:sdmx:Glossary.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 stardard language to be implemented in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] and applicable also to GSIM and DDI. This brought to the publication of the [[VTL>>doc:sdmx:Glossary.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.Validation and transformation language.WebHome]] 1.0 made by several organisations and triggered a large improvement of the language. A new provisional version, the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] 1.1, was released in public consultation in 2017. The high number of [[comments>>doc:sdmx:Glossary.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.Validation and transformation language.WebHome]] 2.0 was published between April and July 2018 (see the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] website).
281 281  
282 -The implementation in the SDMX standards of the VTL 2.0 started in late 2018. It allows to write VTL 2.0 programs for validating and transforming SDMX data, to store these programs in a SDMX metadata registry and to exchange them through SDMX messages, also together the definition of the data structures of the involved data.
285 +The implementation in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards of the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] 2.0 started in late 2018. It allows to write [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] 2.0 programs for validating and transforming [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] data, to store these programs in a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] metadata registry and to exchange them through [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] messages, also together the definition of the data structures of the involved data.
283 283  
284 -The changes of this revision of the SDMX 2.1 standards, released in July 2020, consist essentially in the addition of some new specifications for the management of VTL, leaving all the previous and already existing specifications unchanged. In consequence, no problems of backward compatibility arise and the existing SDMX 2.1 usages are not impacted. SDMX versions lower than 2.1 do not support VTL.
287 +The changes of this revision of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 standards, released in July 2020, consist essentially in the addition of some new specifications for the management of [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]], leaving all the previous and already existing specifications unchanged. In consequence, no problems of backward compatibility arise and the existing [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 usages are not impacted. [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] versions lower than 2.1 do not support [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]].
285 285  
286 -The new SDMX 2.1 parts relevant to VTL are in Section 2 (Information Model), Section 3A (SDMX-ML: XML formats), Section 3B (SDMX-ML: XML Schema, Samples, WADL and WSDL), Section 5 (Registry Specifications), Section 6 (Technical Notes) and in the REST specifications of the SDMX web services. On the contrary, the VTL is not supported in the UN/EDIFACT SDMX formats (Section 4) and in the SDMX SOAP web service interface.
289 +The new [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 parts relevant to [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] are in Section 2 (Information Model), Section 3A ([[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]]: XML formats), Section 3B ([[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]]: XML Schema, Samples, WADL and WSDL), Section 5 (Registry Specifications), Section 6 (Technical Notes) and in the REST specifications of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] web services. On the contrary, the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] is not supported in the UN/EDIFACT [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] formats (Section 4) and in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] SOAP web service interface.
287 287  
288 -As for the Section 2 (Information Model), the change is relevant to the package 13 “Transformations and Expressions”, which previously contained only a blueprint for future elaboration and was not operational. This package is renamed to “Validation and Transformation Language” and is completely reformulated by introducing the actual object classes needed to define and manage VTL 2.0 programs. The other parts of the IM are not impacted.
291 +As for the Section 2 (Information Model), the change is relevant to the package 13 “Transformations and Expressions”, which previously contained only a blueprint for future elaboration and was not operational. This package is renamed to “[[Validation and Transformation Language>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]” and is completely reformulated by introducing the actual object classes needed to define and manage [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] 2.0 programs. The other parts of the IM are not impacted.
289 289  
290 -In the Section 3A and 3B, new schemas, samples and documentation aimed at exchanging VTL programs through SDMX structure messages have been introduced. Other parts are not impacted.
293 +In the Section 3A and 3B, new schemas, samples and documentation aimed at exchanging [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] programs through [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] structure messages have been introduced. Other parts are not impacted.
291 291  
292 -In the section 5 (Registry Specifications), the VTL artefacts have been added. The other artefacts are not impacted.
295 +In the section 5 (Registry Specifications), the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] have been added. The other [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] are not impacted.
293 293  
294 -In the section 6 (Technical Notes), the chapter 10 – “Validation and Transformation Language” – has been introduced. The other parts are not impacted.
297 +In the section 6 (Technical Notes), the chapter 10 – “[[Validation and Transformation Language>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]” – has been introduced. The other parts are not impacted.
295 295  
296 -Finally, new REST interfaces for VTL have been added. These are not maintained any more in the section 7; the link to these specifications can be found on the SDMX website.
299 +Finally, new REST interfaces for [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] have been added. These are not maintained any more in the section 7; the link to these specifications can be found on the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] website.
297 297  
298 298  ----
299 299