Skip to Content

Changes for page 4 Specific Item Schemes

Last modified by Artur on 2025/09/10 11:19
From version 3.7
edited by Helena
on 2025/05/20 12:13
Change comment: There is no comment for this version
To version 4.2
edited by Artur
on 2025/05/20 14:28
Change comment: Update document after refactoring.

Summary

Details

Page properties
Parent
... ... @@ -1,0 +1,1 @@
1 +Methodology.SDMX 2\.1 Standards\. Section 2\. Information model\: UML conceptual design.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.helena
1 +xwiki:XWiki.arturkryazhev
Content
... ... @@ -121,10 +121,8 @@
121 121  
122 122  The ConceptScheme can have one or more Concepts. A Concept can have zero or more child Concepts, thus supporting a hierarchy of Concepts. Note that a child Concept can have only one parent Concept in this association. The purpose of the hierarchy is to relate concepts that have a semantic relationship: for example a Reporting_Country and Vis_a_Vis_Country may both have Country as a parent concept, or a CONTACT may have a PRIMARY_CONTACT as a child concept. It is not the purpose of such schemes to define reporting structures: these reporting structures are defined in the MetadataStructureDefinition.
123 123  
124 -The Concept can be associated with a coreRepresentation. The coreRepresentation isthe specification of the format and value domain of the Concept when used on a structure like a DataStructureDefinition or a
124 +The Concept can be associated with a coreRepresentation. The coreRepresentation isthe specification of the format and value domain of the Concept when used on a structure like a DataStructureDefinition or a MetadataStructureDefinition, unless the specification of the Representation is overridden in the relevant structure definition. In a hierarchical ConceptScheme the Representation is inherited from the parent Concept unless overridden at the level of the child Concept.
125 125  
126 -MetadataStructureDefinition, unless the specification of the Representation is overridden in the relevant structure definition. In a hierarchical ConceptScheme the Representation is inherited from the parent Concept unless overridden at the level of the child Concept.
127 -
128 128  Note that the ConceptScheme is used as the Representation of the MeasureDimension in a DataStructureDefinition (see 5.3.2). Each Concept in this ConceptScheme is a specific measure, each of which can be given a coreRepresentation. Thus the valid format of the observation for each measure when reported in a data set for the MeasureDimension is specified in the Concept. This allows a different format for each measure. This is covered in more detail in 5.3.
129 129  
130 130  The Representation is documented in more detail in the section on the SDMX Base.
... ... @@ -163,8 +163,11 @@
163 163  
164 164  === {{id name="_Toc370999"/}}4.5.2 Class diagram - Inheritance ===
165 165  
166 -====== Figure 18 Inheritance Class diagram of the Category Scheme ======
164 +====== [[image:1747732448450-721.png]] ======
167 167  
166 +(% class="wikigeneratedid" id="HFigure18InheritanceClassdiagramoftheCategoryScheme" %)
167 +**Figure 18 Inheritance Class diagram of the Category Scheme**
168 +
168 168  === {{id name="_Toc371000"/}}4.5.3 Explanation of the Diagram ===
169 169  
170 170  ==== 4.5.3.1 Narrative ====
... ... @@ -197,12 +197,12 @@
197 197  
198 198  === {{id name="_Toc371001"/}}4.5.4 Class diagram - Relationship ===
199 199  
201 +[[image:1747732486733-495.png]]
202 +
200 200  **Figure 19: Relationship Class diagram of the Category Scheme**
201 201  
202 -The CategoryScheme can have one or more Categorys. The Category is Identifiable and has identity information. A Category can have zero or more child Categorys, thus supporting a hierarchy of Categorys. Any IdentifiableArtefact can be +categorisedBy a Category. This is achieved by means of a Categorisation. Each
205 +The CategoryScheme can have one or more Categorys. The Category is Identifiable and has identity information. A Category can have zero or more child Categorys, thus supporting a hierarchy of Categorys. Any IdentifiableArtefact can be +categorisedBy a Category. This is achieved by means of a Categorisation. Each Categorisation can associate one IdentifiableArtefact with one Category. Multiple Categorisations can be used to build a set of IdentifiableArtefacts that are +categorisedBy the same Category. Note that there is no navigation (i.e. no embedded reference) to the Categorisation from the Category. From an implementation perspective this is necessary as Categorisation has no affect on the versioning of either the Category or the IdentifiableArtefact.
203 203  
204 -Categorisation can associate one IdentifiableArtefact with one Category. Multiple Categorisations can be used to build a set of IdentifiableArtefacts that are +categorisedBy the same Category. Note that there is no navigation (i.e. no embedded reference) to the Categorisation from the Category. From an implementation perspective this is necessary as Categorisation has no affect on the versioning of either the Category or the IdentifiableArtefact.
205 -
206 206  ==== 4.5.4.1 Definitions ====
207 207  
208 208  (((
... ... @@ -316,6 +316,7 @@
316 316  
317 317  === {{id name="_Toc371006"/}}4.7.1 Class Diagram ===
318 318  
320 +[[image:1747732548003-370.png]]
319 319  
320 320  **Figure 21: Class diagram of the Reporting Taxonomy**
321 321  
1747732448450-721.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +34.0 KB
Content
1747732486733-495.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +18.6 KB
Content
1747732548003-370.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +48.9 KB
Content