Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 11.2
edited by Helena
on 2025/05/14 14:51
Change comment: There is no comment for this version
To version 11.1
edited by Helena
on 2025/05/14 14:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -385,7 +385,7 @@
385 385  * 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.
386 386  * 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.
387 387  
388 -== 3.7 Structure Mapping ==
388 +=== 3.7 Structure Mapping ===
389 389  
390 390  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.
391 391  
... ... @@ -417,7 +417,7 @@
417 417  
418 418  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.
419 419  
420 -== 3.8 Constraints ==
420 +=== 3.8 Constraints ===
421 421  
422 422  Constraints in version 3.0 are modelled using two separate artefacts which replace the version 2.1 content constraint:
423 423  
... ... @@ -432,17 +432,17 @@
432 432  
433 433  Attachment constraints have been deprecated due to a lack of use cases.
434 434  
435 -== 3.9 Code List Extension ==
435 +=== 3.9 Code List Extension ===
436 436  
437 437  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.
438 438  
439 439  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.
440 440  
441 -== 3.10 Discriminated Union of Code Lists ==
441 +=== 3.10 Discriminated Union of Code Lists ===
442 442  
443 443  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.
444 444  
445 -== 3.11 Code Hierarchies ==
445 +=== 3.11 Code Hierarchies ===
446 446  
447 447  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).
448 448