Skip to Content
Last modified by Artur on 2025/08/19 10:43
From version 5.1
edited by Helena
on 2025/05/21 21:35
Change comment: There is no comment for this version
To version 4.4
edited by Helena
on 2025/05/21 21:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -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.
114 +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,43 +121,37 @@
121 121  
122 122  A..Z (upper case alphabetic), 0..9 (numeric), _ (underscore)
123 123  
124 -**5. Observation values** are:
123 +1. **Observation values** are:
124 +1*. Decimal numerics (signed only if they are negative);
125 +1*. The maximum number of significant figures is:
126 +1*. 15 for a positive number
127 +1*. 14 for a positive decimal or a negative integer
128 +1*. 13 for a negative decimal
129 +1*. Scientific notation may be used.
130 +1. **Uncoded statistical concept** text values are:
131 +1*.
132 +1**. Maximum 1050 characters;
133 +1**. From ISO 8859-1 character set.
134 +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.
136 +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 -* Maximum 1050 characters;
136 -* From ISO 8859-1 character set.
137 -
138 -**7. Time series keys**:
139 -
140 -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.
141 -
142 142  == 3.4 SDMX-ML and SDMX-EDI Best Practices ==
143 143  
144 -=== 3.4.1 Reporting and Dissemination Guidelines ===
140 +=== 3.4.1 Reporting and Dissemination Guidelines ===
145 145  
146 -==== 3.4.1.1 Central Institutions and Their Role in Statistical Data Exchanges ====
142 +**3.4.1.1 Central Institutions and Their Role in Statistical Data Exchanges **Central institutions are the organisations to which other partner institutions "report" statistics. These statistics are used by central institutions either to compile aggregates and/or they are put together and made available in a uniform manner (e.g. on-line or on a CD-ROM or through file transfers). Therefore, central institutions receive data from other institutions and, usually, they also "disseminate" data to individual and/or institutions for end-use.  Within a country, a NSI or a national central bank (NCB) plays, of course, a central institution role as it collects data from other entities and it disseminates statistical information to end users. In SDMX the role of central institution is very important: every statistical message is based on underlying structural definitions (statistical concepts, code lists, DSDs) which have been devised by a particular agency, usually a central institution. Such an institution plays the role of the reference "structural definitions maintenance agency" for the corresponding messages which are exchanged. Of course, two institutions could exchange data using/referring to structural information devised by a third institution.
147 147  
148 -Central institutions are the organisations to which other partner institutions "report" statistics. These statistics are used by central institutions either to compile aggregates and/or they are put together and made available in a uniform manner (e.g. on-line or on a CD-ROM or through file transfers). Therefore, central institutions receive data from other institutions and, usually, they also "disseminate" data to individual and/or institutions for end-use.  Within a country, a NSI or a national central bank (NCB) plays, of course, a central institution role as it collects data from other entities and it disseminates statistical information to end users. In SDMX the role of central institution is very important: every statistical message is based on underlying structural definitions (statistical concepts, code lists, DSDs) which have been devised by a particular agency, usually a central institution. Such an institution plays the role of the reference "structural definitions maintenance agency" for the corresponding messages which are exchanged. Of course, two institutions could exchange data using/referring to structural information devised by a third institution.
149 -
150 150  Central institutions can play a double role:
151 151  
152 152  * collecting and further disseminating statistics;
153 153  * devising structural definitions for use in data exchanges.
154 154  
155 -==== 3.4.1.2 Defining Data Structure Definitions (DSDs) ====
149 +**3.4.1.2 Defining Data Structure Definitions (DSDs)**
156 156  
157 157  The following guidelines are suggested for building a DSD. However, it is expected that these guidelines will be considered by central institutions when devising new DSDs.
158 158  
159 -(% class="wikigeneratedid" id="HDimensions2CAttributesandCodeLists" %)
160 -__Dimensions, Attributes and Code Lists__
153 +=== Dimensions, Attributes and Code Lists ===
161 161  
162 162  **//Avoid dimensions that are not appropriate for all the series in the data structure definition.//**  If some dimensions are not applicable (this is evident from the need to have a code in a code list which is marked as “not applicable”, “not relevant” or “total”) for some series then consider moving these series to a new data structure definition in which these dimensions are dropped from the key structure. This is a judgement call as it is sometimes difficult to achieve this without increasing considerably the number of DSDs.
163 163  
... ... @@ -187,8 +187,7 @@
187 187  
188 188  The same code list can be used for several statistical concepts, within a data structure definition or across DSDs. Note that SDMX has recognised that these classifications are often quite large and the usage of codes in any one DSD is only a small extract of the full code list. In this version of the standard it is possible to exchange and disseminate a **partial code list** which is extracted from the full code list and which supports the dimension values valid for a particular DSD.
189 189  
190 -(% class="wikigeneratedid" id="HDataStructureDefinitionStructure" %)
191 -__Data Structure Definition Structure__
183 +=== Data Structure Definition Structure ===
192 192  
193 193  The following items have to be specified by a structural definitions maintenance agency when defining a new data structure definition:
194 194  
... ... @@ -218,7 +218,7 @@
218 218  * code list name
219 219  * code values and descriptions
220 220  
221 -Definition of data flow definitions. Two (or more) partners performing data exchanges in a certain context need to agree on:
213 +Definition of data flow definitions.  Two (or more) partners performing data exchanges in a certain context need to agree on:
222 222  
223 223  * the list of data set identifiers they will be using;
224 224  * for each data flow:
... ... @@ -225,12 +225,10 @@
225 225  * its content and description
226 226  * the relevant DSD that defines the structure of the data reported or disseminated according the the dataflow definition
227 227  
228 -==== 3.4.1.3 Exchanging Attributes ====
220 +**3.4.1.3 Exchanging Attributes**
229 229  
230 -===== //3.4.1.3.1 Attributes on series, sibling and data set level // =====
222 +**//3.4.1.3.1 Attributes on series, sibling and data set level //**//Static properties//.
231 231  
232 -//Static properties//.
233 -
234 234  * Upon creation of a series the sender has to provide to the receiver values for all mandatory attributes. In case they are available, values for conditional attributes  should also be provided. Whereas initially this information may be provided by means other than SDMX-ML or SDMX-EDI messages (e.g. paper, telephone) it is expected that partner institutions will be in a position to provide this information in SDMX-ML or SDMX-EDI format over time.
235 235  * A centre may agree with its data exchange partners special procedures for authorising the setting of attributes' initial values.
236 236  * Attribute values at a data set level are set and maintained exclusively by the centre administrating the exchanged data set.