Changes for page SDMX 2.1 Standards. Section 6. Technical Notes
Last modified by Artur on 2025/08/19 10:43
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -143,18 +143,21 @@ 143 143 144 144 === 3.4.1 Reporting and Dissemination Guidelines === 145 145 146 - **3.4.1.1 Central Institutions and Their Role in Statistical Data Exchanges**Centralinstitutions 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 ==== 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 + 148 148 Central institutions can play a double role: 149 149 150 150 * collecting and further disseminating statistics; 151 151 * devising structural definitions for use in data exchanges. 152 152 153 - **3.4.1.2 Defining Data Structure Definitions (DSDs)**155 +==== 3.4.1.2 Defining Data Structure Definitions (DSDs) ==== 154 154 155 155 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. 156 156 157 -=== Dimensions, Attributes and Code Lists === 159 +(% class="wikigeneratedid" id="HDimensions2CAttributesandCodeLists" %) 160 +__Dimensions, Attributes and Code Lists__ 158 158 159 159 **//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. 160 160 ... ... @@ -184,7 +184,8 @@ 184 184 185 185 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. 186 186 187 -=== Data Structure Definition Structure === 190 +(% class="wikigeneratedid" id="HDataStructureDefinitionStructure" %) 191 +__Data Structure Definition Structure__ 188 188 189 189 The following items have to be specified by a structural definitions maintenance agency when defining a new data structure definition: 190 190 ... ... @@ -214,7 +214,7 @@ 214 214 * code list name 215 215 * code values and descriptions 216 216 217 -Definition of data flow definitions. 221 +Definition of data flow definitions. Two (or more) partners performing data exchanges in a certain context need to agree on: 218 218 219 219 * the list of data set identifiers they will be using; 220 220 * for each data flow: ... ... @@ -221,10 +221,12 @@ 221 221 * its content and description 222 222 * the relevant DSD that defines the structure of the data reported or disseminated according the the dataflow definition 223 223 224 - **3.4.1.3 Exchanging Attributes**228 +==== 3.4.1.3 Exchanging Attributes ==== 225 225 226 - **//3.4.1.3.1 Attributes on series, sibling and data set level //**//Staticproperties//.230 +===== //3.4.1.3.1 Attributes on series, sibling and data set level // ===== 227 227 232 +//Static properties//. 233 + 228 228 * 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. 229 229 * A centre may agree with its data exchange partners special procedures for authorising the setting of attributes' initial values. 230 230 * Attribute values at a data set level are set and maintained exclusively by the centre administrating the exchanged data set.