Skip to Content
Last modified by Artur on 2025/08/19 10:43
From version 4.6
edited by Helena
on 2025/05/21 21:32
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
... ... @@ -77,8 +77,10 @@
77 77  
78 78  === //Validation// ===
79 79  
80 -SDMX-EDI – as is typical of EDIFACT syntax messages – leaves validation to dedicated applications (“validation” being the checking of syntax, data typing, and adherence of the data message to the structure as described in the structural definition.)
80 +SDMX-EDI – as is typical of EDIFACT syntax messages – leaves validation to dedicated applications (“validation” being the checking of syntax, data typing, and adherence of the data message to the structure as described in the structural
81 81  
82 +definition.)
83 +
82 82  The SDMX-ML Generic Data Message also leaves validation above the XML syntax level to the application.
83 83  
84 84  The SDMX-ML DSD-specific messages will allow validation of XML syntax and datatyping to be performed with a generic XML parser, and enforce agreement between the structural definition and the data to a moderate degree with the same tool.
... ... @@ -89,13 +89,17 @@
89 89  
90 90  === //Character Encodings// ===
91 91  
92 -All SDMX-ML messages use the UTF-8 encoding, while SDMX-EDI uses the ISO 8879-1 character encoding. There is a greater capacity with UTF-8 to express some character sets (see the “APPENDIX: MAP OF ISO 8859-1 (UNOC) CHARACTER SET (LATIN 1 OR “WESTERN”) in the document “SYNTAX AND DOCUMENTATION VERSION 2.0”.) Many transformation tools are available which allow XML instances with UTF-8 encodings to be expressed as ISO 8879-1-encoded characters, and to transform UTF-8 into ISO 8879-1. Such tools should be used when transforming SDMX-ML messages into SDMX-EDI messages and vice-versa.
94 +All SDMX-ML messages use the UTF-8 encoding, while SDMX-EDI uses the ISO 8879-1 character encoding. There is a greater capacity with UTF-8 to express some character sets (see the “APPENDIX: MAP OF ISO 8859-1 (UNOC) CHARACTER
93 93  
96 +SET (LATIN 1 OR “WESTERN”) in the document “SYNTAX AND
97 +
98 +DOCUMENTATION VERSION 2.0”.) Many transformation tools are available which allow XML instances with UTF-8 encodings to be expressed as ISO 8879-1-encoded characters, and to transform UTF-8 into ISO 8879-1. Such tools should be used when transforming SDMX-ML messages into SDMX-EDI messages and vice-versa.
99 +
94 94  === //Data Typing// ===
95 95  
96 96  The XML syntax and EDIFACT syntax have different data-typing mechanisms. The section below provides a set of conventions to be observed when support for messages in both syntaxes is required. For more information on the SDMX-ML representations of data, see below.
97 97  
98 -==== 3.3.2 Data Types ====
104 +==== 3.3.2 Data Types ====
99 99  
100 100  The XML syntax has a very different mechanism for data-typing than the EDIFACT syntax, and this difference may create some difficulties for applications which support both EDIFACT-based and XML-based SDMX data formats. This section provides a set of conventions for the expression in data in all formats, to allow for clean interoperability between them.
101 101  
... ... @@ -111,8 +111,7 @@
111 111  1*. Maximum 70 characters.
112 112  1*. From ISO 8859-1 character set (including accented characters)
113 113  1. **Descriptions **are:
114 -1*. Maximum 350 characters;
115 -1*. From ISO 8859-1 character set.
120 +1*. Maximum 350 characters;  From ISO 8859-1 character set.
116 116  1. **Code values** are:
117 117  1*. Maximum 18 characters;
118 118  1*. Any of A..Z (upper case alphabetic), 0..9 (numeric), _ (underscore), / (solidus, slash), = (equal sign), - (hyphen);
... ... @@ -121,25 +121,21 @@
121 121  
122 122  A..Z (upper case alphabetic), 0..9 (numeric), _ (underscore)
123 123  
124 -**5. Observation values** are:
129 +1. **Observation values** are:
130 +1*. Decimal numerics (signed only if they are negative);
131 +1*. The maximum number of significant figures is:
132 +1*. 15 for a positive number
133 +1*. 14 for a positive decimal or a negative integer
134 +1*. 13 for a negative decimal
135 +1*. Scientific notation may be used.
136 +1. **Uncoded statistical concept** text values are:
137 +1*.
138 +1**. Maximum 1050 characters;
139 +1**. From ISO 8859-1 character set.
140 +1. **Time series keys**:
125 125  
126 -* Decimal numerics (signed only if they are negative);
127 -* The maximum number of significant figures is:
128 -* 15 for a positive number
129 -* 14 for a positive decimal or a negative integer
130 -* 13 for a negative decimal
131 -* Scientific notation may be used.
142 +In principle, the maximum permissible length of time series keys used in a data exchange does not need to be restricted. However, for working purposes, an effort is made to limit the maximum length to 35 characters; in this length, also (for SDMXEDI) one (separator) position is included between all successive dimension values; this means that the maximum length allowed for a pure series key (concatenation of dimension values) can be less than 35 characters.  The separator character is a colon (“:”) by conventional usage.
132 132  
133 -**6. Uncoded statistical concept** text values are:
134 -
135 -*
136 -** Maximum 1050 characters;
137 -** From ISO 8859-1 character set.
138 -
139 -**7. Time series keys**:
140 -
141 -In principle, the maximum permissible length of time series keys used in a data exchange does not need to be restricted. However, for working purposes, an effort is made to limit the maximum length to 35 characters; in this length, also (for SDMXEDI) one (separator) position is included between all successive dimension values; this means that the maximum length allowed for a pure series key (concatenation of dimension values) can be less than 35 characters. The separator character is a colon (“:”) by conventional usage.
142 -
143 143  == 3.4 SDMX-ML and SDMX-EDI Best Practices ==
144 144  
145 145  === 3.4.1 Reporting and Dissemination Guidelines ===