Skip to Content

Changes for page 3 SDMX Base Package

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

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,0 @@
1 -Methodology.SDMX 2\.1 Standards\. Section 2\. Information model\: UML conceptual design.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.arturkryazhev
1 +xwiki:XWiki.helena
Content
... ... @@ -113,8 +113,6 @@
113 113  
114 114  === {{id name="_Toc370976"/}}3.4.1 Class Diagram ===
115 115  
116 -[[image:1747690333052-506.png]]
117 -
118 118  **Figure 11: Class Diagram of Basic Data Types**
119 119  
120 120  === {{id name="_Toc370977"/}}3.4.2 Explanation of the Diagram ===
... ... @@ -164,14 +164,16 @@
164 164  (% class="wikigeneratedid" id="HFigure12TheItemSchemePattern" %)
165 165  **Figure 12 The Item Scheme Pattern**
166 166  
167 -=== {{id name="_Toc370981"/}}3.5.3 Explanation of the Diagram ===
165 +===== {{id name="_Toc370981"/}}3.5.3 Explanation of the Diagram =====
168 168  
169 -==== 3.5.3.1 Narrative ====
167 +**3.5.3.1 Narrative**
170 170  
171 171  The //ItemScheme// is an abstract class which defines a set of //Item// (this class is also abstract). Its main purpose is to define a mechanism which can be used to create taxonomies which can classify other parts of the SDMX Information Model. It inherits from //MaintainableArtefact// which gives it the ability to be annotated, have identity, naming, versioning and be associated with an Agency. An example of a concrete class is a CategoryScheme. The associated Category are //Items//.
172 172  
173 -In an exchange environment an ItemScheme is allowed to contain a sub-set of the Items in the maintained //ItemScheme//. If such an //ItemScheme// is disseminated with a sub-set of the Items then the fact that this is a sub-set is denoted by setting the isPartial attribute to “true”.
171 +In an exchange environment an ItemScheme is allowed to contain a sub-set of the Items in the maintained //ItemScheme//. If such an //ItemScheme// is disseminated with a sub-set of the Items then the fact that this is a sub-set is denoted by setting the isPartial attribute to
174 174  
173 +“true”.
174 +
175 175  A “partial” //ItemScheme// cannot be maintained independently in its partial form i.e. it cannot contain //Item//s that are not present in the full //ItemScheme// and the content of any one //Item //(e.g. names and descriptions) cannot deviate from the content in the full //ItemScheme//.
176 176  
177 177  Furthermore, the Id of the //ItemScheme// where isPartial is set to “true” is the same as the Id of the full //ItemScheme// (maintenance agency, id, version). This is important as this is the Id that that is referenced in other structures (e.g. a Codelist referenced in a DSD) and this Id is always the same, regardless of whether the disseminated //ItemScheme// is the full //ItemScheme// or a partial //ItemScheme//.
... ... @@ -178,8 +178,10 @@
178 178  
179 179  The purpose of a partial //ItemScheme// is to support the exchange and dissemination of a subset ItemScheme without the need to maintain multiple //ItemScheme//s which contain the same //Item//s. For instance, when a Codelist is used in a DataStructureDefinition it is sometimes the case that only a sub-set of the Codes in a Codelist are relevant. In this case a partial Codelist can be constructed using the Constraint mechanism explained later in this document.
180 180  
181 -//Item// inherits from //NameableArtefact// which gives it the ability to be annotated and have identity, and therefore has id, uri and urn attributes, a name and a description in the form of an InternationalString. Unlike the parent //ItemScheme//, the //Item// itself is not a //MaintainableArtefact// and therefore cannot have an independent Agency (i.e. it implicitly has the same agency as the //ItemScheme//).
181 +//Item// inherits from //NameableArtefact// which gives it the ability to be annotated and have identity, and therefore has id, uri and urn attributes, a name and a description in the form of an
182 182  
183 +InternationalString. Unlike the parent //ItemScheme//, the //Item// itself is not a //MaintainableArtefact// and therefore cannot have an independent Agency (i.e. it implicitly has the same agency as the //ItemScheme//).
184 +
183 183  The //Item// can be hierarchic and so one //Item// can have child //Item//s. The restriction of the hierarchic association is that a child //Item// can have only parent //Item//.
184 184  
185 185  ==== 3.5.3.2 Definitions ====
... ... @@ -257,7 +257,7 @@
257 257  
258 258  __GroupDimensionDescriptor__: Dimension, Measure Dimension, Time Dimension
259 259  
260 -__MeasureDescriptor__: PrimaryMeasure
262 +MeasureDescriptor: PrimaryMeasure
261 261  
262 262  __AttributeDescriptor:__ Data Attribute
263 263  
1747690333052-506.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -67.4 KB
Content