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

Summary

Details

Page properties
Content
... ... @@ -121,37 +121,43 @@
121 121  
122 122  A..Z (upper case alphabetic), 0..9 (numeric), _ (underscore)
123 123  
124 -1. **Observation values** are:
125 -1*. Decimal numerics (signed only if they are negative);
126 -1*. The maximum number of significant figures is:
127 -1*. 15 for a positive number
128 -1*. 14 for a positive decimal or a negative integer
129 -1*. 13 for a negative decimal
130 -1*. Scientific notation may be used.
131 -1. **Uncoded statistical concept** text values are:
132 -1*.
133 -1**. Maximum 1050 characters;
134 -1**. From ISO 8859-1 character set.
135 -1. **Time series keys**:
124 +**5. Observation values** are:
136 136  
137 -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.
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.
138 138  
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 +
139 139  == 3.4 SDMX-ML and SDMX-EDI Best Practices ==
140 140  
141 -=== 3.4.1 Reporting and Dissemination Guidelines ===
144 +=== 3.4.1 Reporting and Dissemination Guidelines ===
142 142  
143 -**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.
146 +==== 3.4.1.1 Central Institutions and Their Role in Statistical Data Exchanges ====
144 144  
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 +
145 145  Central institutions can play a double role:
146 146  
147 147  * collecting and further disseminating statistics;
148 148  * devising structural definitions for use in data exchanges.
149 149  
150 -**3.4.1.2 Defining Data Structure Definitions (DSDs)**
155 +==== 3.4.1.2 Defining Data Structure Definitions (DSDs) ====
151 151  
152 152  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.
153 153  
154 -=== Dimensions, Attributes and Code Lists ===
159 +(% class="wikigeneratedid" id="HDimensions2CAttributesandCodeLists" %)
160 +__Dimensions, Attributes and Code Lists__
155 155  
156 156  **//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.
157 157  
... ... @@ -181,7 +181,8 @@
181 181  
182 182  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.
183 183  
184 -=== Data Structure Definition Structure ===
190 +(% class="wikigeneratedid" id="HDataStructureDefinitionStructure" %)
191 +__Data Structure Definition Structure__
185 185  
186 186  The following items have to be specified by a structural definitions maintenance agency when defining a new data structure definition:
187 187  
... ... @@ -211,7 +211,7 @@
211 211  * code list name
212 212  * code values and descriptions
213 213  
214 -Definition of data flow definitions.  Two (or more) partners performing data exchanges in a certain context need to agree on:
221 +Definition of data flow definitions. Two (or more) partners performing data exchanges in a certain context need to agree on:
215 215  
216 216  * the list of data set identifiers they will be using;
217 217  * for each data flow:
... ... @@ -218,10 +218,12 @@
218 218  * its content and description
219 219  * the relevant DSD that defines the structure of the data reported or disseminated according the the dataflow definition
220 220  
221 -**3.4.1.3 Exchanging Attributes**
228 +==== 3.4.1.3 Exchanging Attributes ====
222 222  
223 -**//3.4.1.3.1 Attributes on series, sibling and data set level //**//Static properties//.
230 +===== //3.4.1.3.1 Attributes on series, sibling and data set level // =====
224 224  
232 +//Static properties//.
233 +
225 225  * 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.
226 226  * A centre may agree with its data exchange partners special procedures for authorising the setting of attributes' initial values.
227 227  * Attribute values at a data set level are set and maintained exclusively by the centre administrating the exchanged data set.