Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 7.9
edited by Helena
on 2025/05/14 13:38
Change comment: There is no comment for this version
To version 10.2
edited by Helena
on 2025/05/14 14:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -1 Overview
1 +SDMX STANDARDS
Parent
... ... @@ -1,0 +1,1 @@
1 +Methodology.WebHome
Content
... ... @@ -215,7 +215,8 @@
215 215  Removed Maintainable Artefacts
216 216  
217 217  * Structure Set – replaced by Structure Map and the four item scheme maps
218 -* Hierarchical Codelist – replaced by Hierarchy and Hierarchy Association • Constraint – replaced by Data Constraint and Metadata Constraint
218 +* Hierarchical Codelist – replaced by Hierarchy and Hierarchy Association
219 +* Constraint – replaced by Data Constraint and Metadata Constraint
219 219  
220 220  Changed Maintainable Artefacts
221 221  
... ... @@ -229,7 +229,7 @@
229 229  
230 230  * GeospatialInformation – a string type where the value is an expression defining a set of geographical features using a purpose-designed syntax
231 231  
232 -== //3.3 Areas Unchanged from Version 2.1// ==
233 +== 3.3 Areas Unchanged from Version 2.1 ==
233 233  
234 234  The following areas of the information model are unchanged from version 2.1:
235 235  
... ... @@ -242,7 +242,7 @@
242 242  * Reporting taxonomy
243 243  * Process
244 244  
245 -== //3.4 Reference Metadata// ==
246 +== 3.4 Reference Metadata ==
246 246  
247 247  Reference metadata has been substantially re-designed for version 3.0 to simplify the model and better support practical use cases.
248 248  
... ... @@ -271,83 +271,45 @@
271 271  * SOURCE_AGENCY – a multi-value data attribute
272 272  
273 273  <Obs xsi:type="dsd:ObsType" OBS_VALUE="112" OBS_STAUS=”A” TIME_PERIOD="2010-09">
274 -
275 275  <!—- complex multi-value and multi-lingual data attributes ~-~->
276 -
277 277  <Comp id="TITLE" xsi:type="ns1:TITLE_ATTRIBUTE">
278 -
279 279  <Value>
280 -
281 281  <common:Text xml:lang="en">Some English Text</common:Text>
282 -
283 283  <common:Text xml:lang="fr">Quelques textes en anglais</common:Text>
284 -
285 285  </Value>
286 -
287 287  </Comp>
288 288  
289 289  <Comp id="SOURCE_AGENCY" xsi:type="ns1:SOURCE_AGENCY_ATTRIBUTE">
290 -
291 291  <Value>4F0</Value>
292 -
293 293  <Value>4D0</Value>
294 -
295 295  <Value>CZ2</Value>
296 -
297 297  </Comp>
298 -
299 299  <!—- metadata attributes are reported like in metadata messages ~-~->
300 -
301 301  <Metadata>
302 -
303 303  <Attribute id="COLLECTION">
304 -
305 305  <Attribute id="METHOD">
306 -
307 307  <Text lang="en">AAA</Text>
308 -
309 309  </Attribute>
310 -
311 311  </Attribute>
312 -
313 313  <Attribute id="CONTACT">
314 -
315 315  <Value>CONTACT 1</Value>
316 -
317 317  <Attribute id="NAME">
318 -
319 319  <Value>Contact 1 Name 1</Value>
320 -
321 321  </Attribute>
322 -
323 323  <Attribute id="NAME">
324 -
325 325  <Value>Contact 1 Name 2</Value>
326 -
327 327  </Attribute>
328 -
329 329  </Attribute>
330 -
331 331  <Attribute id="CONTACT">
332 -
333 333  <Value>CONTACT 2</Value>
334 -
335 335  <Attribute id="NAME">
336 -
337 337  <Value>Contact 2 Name 1</Value>
338 -
339 339  </Attribute>
340 -
341 341  <Attribute id="NAME">
342 -
343 343  <Value>Contact 2 Name 2</Value>
344 -
345 345  </Attribute>
346 -
347 347  </Attribute>
348 -
349 349  </Metadata>
350 -
351 351  </Obs>
352 352  
353 353  === New - Metadata Provision Agreement ===
... ... @@ -362,7 +362,7 @@
362 362  
363 363  A Metadataset now has mandatory identification information, (owner id, id, version) enabling metadata providers to uniquely identify their reports for create, update or delete maintenance operations.
364 364  
365 -== //3.5 Microdata Exchange// ==
328 +== 3.5 Microdata Exchange ==
366 366  
367 367  Several changes have been made the Data Structure Definition to support microdata use cases in addition to aggregated time series.
368 368  
... ... @@ -420,7 +420,7 @@
420 420  
421 421  That allows ValueItems (the equivalent to Code) to contain symbols like ‘¥’ and ‘€’, but 208 also means they are not identifiable.
422 422  
423 -== //3.6 Geospatial Data Exchange// ==
386 +== 3.6 Geospatial Data Exchange ==
424 424  
425 425  The version 3.0 model has been extended to provide explicit support for geospatial data.
426 426  
... ... @@ -435,7 +435,7 @@
435 435  * GeographicCodelist – each item includes an element to represent a specific Geo Feature Set which is described using the same expression syntax as for GeospatialInformation type.
436 436  * GeoGridCodelist – A code list defining a geographical grid composed of cells representing regular squared portions of the Earth. Each item references a cell within the grid.
437 437  
438 -=== //3.7 Structure Mapping// ===
401 +=== 3.7 Structure Mapping ===
439 439  
440 440  The Structure Set in version 2.1 is a container for many mapping structures including Data Structure Map, Codelist Map and Concept Map. For version 3.0 the Structure Set artefact has been deprecated and replaced with a number of new maintainables giving better flexibility and reusability, specifically: Structure Map, Concept Scheme Map, Representation Map, Reporting Taxonomy Map, Category Scheme Map and Organisation Scheme Map.
441 441  
... ... @@ -467,7 +467,7 @@
467 467  
468 468  Item maps may further define the period for which the mapping is valid, meaning the mapping rule will only be applied if the row of information being mapped is within the period.
469 469  
470 -=== //3.8 Constraints// ===
433 +=== 3.8 Constraints ===
471 471  
472 472  Constraints in version 3.0 are modelled using two separate artefacts which replace the version 2.1 content constraint:
473 473  
... ... @@ -482,17 +482,17 @@
482 482  
483 483  Attachment constraints have been deprecated due to a lack of use cases.
484 484  
485 -=== //3.9 Code List Extension// ===
448 +=== 3.9 Code List Extension ===
486 486  
487 487  In addition to the two new specialised geospatial forms, the option has been added to define a code list as an extension of, or by inheriting codes from, other lists. An optional prefix can be added to inherited codes to disambiguate duplicates.
488 488  
489 489  This feature allows new code lists to be easily derived from existing lists without the need to make and manually maintain copies. When querying for extended code list structures using the REST API, the option has been added to retrieve either the definition or the materialised list. Traditional literal lists of codes continue to be supported.
490 490  
491 -=== //3.10 Discriminated Union of Code Lists// ===
454 +=== 3.10 Discriminated Union of Code Lists ===
492 492  
493 493  Combining code list extension with wildcarded constraints solves the discriminated union of code lists problem where a classification or breakdown has multiple “variants” which are all valid but mutually exclusive. A common example is economic activity where several alternative classification schemes are in use including ISIC revisions 1 to 4 and NACE as used in the European Community.
494 494  
495 -=== //3.11 Code Hierarchies// ===
458 +=== 3.11 Code Hierarchies ===
496 496  
497 497  Code hierarchies allow the definition of complex hierarchies of codes from potentially multiple lists for data discovery purposes. Hierarchical Codelist has been deprecated and replaced by two new artefacts: Hierarchy – the actual hierarchy of codes, and Hierarchy Association links hierarchies directly to any other identifiable object, a capability missing 312 from the version 2.1 model. Further, the linkage can be within a particular context, for instance linking a hierarchy to a dimension within the context of a specific Dataflow (dimension REF_AREA in the context of the ECB:EXR Dataflow).
498 498  
SUZ.Methodology.Code.MethodologyClass[0]