Changes for page 4 Specific Item Schemes

Last modified by Artur on 2025/09/10 11:19

From 15.2 to 15.1 From 15.10 to 15.9

From version 15.9

edited by Helena
on 2025/05/16 13:47

Change comment: There is no comment for this version

To version 15.2

edited by Helena
on 2025/05/16 13:39

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -36,24 +36,11 @@
  ==== 4.3.2.1 Narrative ====
--The Codelist inherits from the //ItemScheme// and therefore has the following attributes:
++The Codelist inherits from the //ItemScheme// and therefore has the following attributes: id uri urn version validFrom validTo isExternalReference serviceURL structureURL isPartial
--id
--uri
--urn
--version
--validFrom
--validTo
--isExternalReference
--serviceURL
--structureURL
--isPartial
--
  The Code inherits from //Item// and has the following attributes:
--id
--uri
--urn
++id uri urn
  Both Codelist and Code have the association to InternationalString to support a multilingual name, an optional multi-lingual description, and an association to Annotation to support notes (not shown).
@@ -88,12 +88,14 @@
  ==== 4.3.3.1 Narrative ====
--A Codelist may extend other Codelists via the CodelistExtension class. The latter, via the sequence, indicates the order of precedence of the extended Codelists for conflict resolution of Codes. Besides that, the prefix property is used to ensure uniqueness of inherited Codes in the extending{{footnote}}The Codelist that extends 0..* Codelists is the 'extending' Codelist, while the Codelist(s) that are inherited is/are the 'extended' Codelist(s).{{/footnote}} Codelist in case conflicting Codes must be included in the latter. Each CodelistExtension association may include one InclusiveCodeSelection or one ExclusiveCodeSelection; those allow including or excluding a specific selection of Codes from the extended Codelists.
++A Codelist may extend other Codelists via the CodelistExtension class. The latter, via the sequence, indicates the order of precedence of the extended Codelists for conflict resolution of Codes. Besides that, the prefix property is used to ensure uniqueness of inherited Codes in the extending^^[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^ Codelist in case conflicting Codes must be included in the latter. Each CodelistExtension association may include one InclusiveCodeSelection or one ExclusiveCodeSelection; those allow including or excluding a specific selection of Codes from the extended Codelists.
  The code selection classes may have MemberValues in order to specify the subset of the Codes that should be included or excluded from the extended Codelist. A MemberValue may have a value that corresponds to a ,,Code,,, including its children ,,Code,,s (via the ,,cascadeValues,, property), or even include instances of the wildcard character ‘%’ in order to point to a set of ,,Code,,s with common parts in their identifiers.
  ==== 4.3.3.2 Definitions ====
++:
++
  (((
  (% style="width:753.039px" %)
  |(% style="width:184px" %)**Class**|(% style="width:145px" %)**Feature**|(% style="width:421px" %)**Description**
@@ -113,7 +113,7 @@
  === 4.3.4 Class Diagram – Geospatial Codelist ===
--The geospatial support is implemented via an extension of the normal //Codelist//. This is illustrated in the following diagrams.
++The geospatial support is implemented via an extension of the normal ,,Codelist,,. This is illustrated in the following diagrams.
  [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_472b895.jpg||height="863" width="466"]]
@@ -128,6 +128,7 @@
  A //GeoCodelist// is a specialisation of Codelist that includes geospatial information, by comprising a set of special Codes, i.e., //GeoRefCode//s. A //GeoCodelist// may be implemented by any of the two following classes, via the geoType property:
  GeographicCodelist
++
  GeoGridCodelist
  The former, i.e., GeographicCodelist, comprises a set of GeoFeatureSetCodes, by adding a value in the Code that follows a pattern to represent a geo feature set.
@@ -149,7 +149,9 @@
  )))
  |(% colspan="2" %)//GeoRefCode//|(% colspan="4" %)(((
  Abstract Class Sub Classes:
++
  GeoFeatureSet
++
  GeoGridCode
  )))|The abstract class that represents a special type of Code, which includes geospatial information.
  |(% colspan="2" %)GeographicCodelist|(% colspan="4" %) |A special Codelist that has been extended to add a geographical feature set to each of its items, typically, this would include all types of administrative geographies.
@@ -174,16 +174,7 @@
  A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following attributes:
--id
--uri
--urn
--version
--validFrom
--validTo
--isExternalReference
--registryURL
--structureURL
--repositoryURL
++id// //uri// //urn// //version// //validFrom// //validTo// //isExternalReference registryURL structureURL repositoryURL
  ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed constraints, to the former.
@@ -216,26 +216,10 @@
  === 4.5.2 Explanation of the Diagram ===
--The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes:
++The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes: id uri urn version validFrom validTo isExternalReference registryURL structureURL repositoryURL isPartial Concept inherits from Item and has the following attributes:
--id
--uri
--urn
--version
--validFrom
--validTo
--isExternalReference
--registryURL
--structureURL
--repositoryURL
--isPartial
++id uri urn
--Concept inherits from Item and has the following attributes:
--
--id
--uri
--urn
--
  Through the inheritance from //NameableArtefact// both ConceptScheme and Concept have the association to InternationalString to support a multi-lingual name, an optional multilingual description, and an association to Annotation to support notes (not shown).
  Through the inheritance from //ItemScheme// the ConceptScheme comprise one or more Concepts, and the Concept itself can have one or more child Concepts in the (inherited) hierarchy association. Note that a child Concept can have only one parent Concept in this association.
@@ -266,10 +266,12 @@
  |(% style="width:204px" %)**Class**|(% style="width:222px" %)**Feature**|(% style="width:337px" %)**Description**
  |(% style="width:204px" %)ConceptScheme|(% style="width:222px" %)(((
  Inherits from
++
  //ItemScheme//
  )))|(% style="width:337px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
  |(% style="width:204px" %)Concept|(% style="width:222px" %)(((
  Inherits from
++
  //Item//
  )))|(% style="width:337px" %)A concept is a unit of knowledge created by a unique combination of characteristics.
  |(% style="width:204px" %) |(% style="width:222px" %)/hierarchy|(% style="width:337px" %)Associates the parent and the child concept.
@@ -298,22 +298,11 @@
  The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes:
--id
--uri
--urn
--version
--validFrom
--validTo
--isExternalReference
--structureURL
--serviceURL
--isPartial
++id uri urn version validFrom validTo isExternalReference structureURL serviceURL isPartial
  Category inherits from //Item// and has the following attributes:
--id
--uri
--urn
++id uri urn
  Both CategoryScheme and Category have the association to InternationalString to support a multi-lingual name, an optional multi-lingual description, and an association to Annotation to support notes (not shown on the model).
@@ -518,5 +518,3 @@
  |(% style="width:177px" %) |(% style="width:152px" %)+structure|(% style="width:428px" %)(((
  Association to the Data Structure Definition and Metadata Structure Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report.
  )))
--
--{{putFootnotes/}}