Last modified by Artur on 2025/08/19 10:43

From version 4.2
edited by Helena
on 2025/05/21 21:28
Change comment: There is no comment for this version
To version 4.3
edited by Helena
on 2025/05/21 21:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -63,18 +63,12 @@
63 63  
64 64  The following section provides a brief overview of the differences between the various SDMX formats.
65 65  
66 -Version 2.0 was characterised by 4 data messages, each with a distinct format: Generic, Compact, Cross-Sectional and Utility. Because of the design, data in some formats could not always be related to another format. In version 2.1, this issue has been addressed by merging some formats and eliminating others. As a result, in
66 +Version 2.0 was characterised by 4 data messages, each with a distinct format: Generic, Compact, Cross-Sectional and Utility. Because of the design, data in some formats could not always be related to another format. In version 2.1, this issue has been addressed by merging some formats and eliminating others. As a result, in SDMX 2.1 there are just two types of data formats: //GenericData// and //StructureSpecificData// (i.e. specific to one Data Structure Definition).
67 67  
68 -SDMX 2.1 there are just two types of data formats: //GenericData// and
69 -
70 -//StructureSpecificData// (i.e. specific to one Data Structure Definition).
71 -
72 72  Both of these formats are now flexible enough to allow for data to be oriented in series with any dimension used to disambiguate the observations (as opposed to only time or a cross sectional measure in version 2.0). The formats have also been expanded to allow for ungrouped observations.
73 73  
74 -To allow for applications which only understand time series data, variations of these formats have been introduced in the form of two data messages;
70 +To allow for applications which only understand time series data, variations of these formats have been introduced in the form of two data messages; //GenericTimeSeriesData// and //StructureSpecificTimeSeriesData//. It is important to note that these variations are built on the same root structure and can be processed in the same manner as the base format so that they do NOT introduce additional processing requirements.
75 75  
76 -//GenericTimeSeriesData// and //StructureSpecificTimeSeriesData//. It is important to note that these variations are built on the same root structure and can be processed in the same manner as the base format so that they do NOT introduce additional processing requirements.
77 -
78 78  === //Structure Definition// ===
79 79  
80 80  The SDMX-ML Structure Message supports the use of annotations to the structure, which is not supported by the SDMX-EDI syntax.