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 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
... ... @@ -132,9 +132,8 @@
132 132  
133 133  **6. Uncoded statistical concept** text values are:
134 134  
135 -*
136 -** Maximum 1050 characters;
137 -** From ISO 8859-1 character set.
135 +* Maximum 1050 characters;
136 +* From ISO 8859-1 character set.
138 138  
139 139  **7. Time series keys**:
140 140  
... ... @@ -142,20 +142,23 @@
142 142  
143 143  == 3.4 SDMX-ML and SDMX-EDI Best Practices ==
144 144  
145 -=== 3.4.1 Reporting and Dissemination Guidelines ===
144 +=== 3.4.1 Reporting and Dissemination Guidelines ===
146 146  
147 -**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 ====
148 148  
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 +
149 149  Central institutions can play a double role:
150 150  
151 151  * collecting and further disseminating statistics;
152 152  * devising structural definitions for use in data exchanges.
153 153  
154 -**3.4.1.2 Defining Data Structure Definitions (DSDs)**
155 +==== 3.4.1.2 Defining Data Structure Definitions (DSDs) ====
155 155  
156 156  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.
157 157  
158 -=== Dimensions, Attributes and Code Lists ===
159 +(% class="wikigeneratedid" id="HDimensions2CAttributesandCodeLists" %)
160 +__Dimensions, Attributes and Code Lists__
159 159  
160 160  **//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.
161 161  
... ... @@ -185,7 +185,8 @@
185 185  
186 186  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.
187 187  
188 -=== Data Structure Definition Structure ===
190 +(% class="wikigeneratedid" id="HDataStructureDefinitionStructure" %)
191 +__Data Structure Definition Structure__
189 189  
190 190  The following items have to be specified by a structural definitions maintenance agency when defining a new data structure definition:
191 191  
... ... @@ -215,7 +215,7 @@
215 215  * code list name
216 216  * code values and descriptions
217 217  
218 -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:
219 219  
220 220  * the list of data set identifiers they will be using;
221 221  * for each data flow:
... ... @@ -222,10 +222,12 @@
222 222  * its content and description
223 223  * the relevant DSD that defines the structure of the data reported or disseminated according the the dataflow definition
224 224  
225 -**3.4.1.3 Exchanging Attributes**
228 +==== 3.4.1.3 Exchanging Attributes ====
226 226  
227 -**//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 // =====
228 228  
232 +//Static properties//.
233 +
229 229  * 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.
230 230  * A centre may agree with its data exchange partners special procedures for authorising the setting of attributes' initial values.
231 231  * Attribute values at a data set level are set and maintained exclusively by the centre administrating the exchanged data set.