Skip to Content

Changes for page 3 SDMX Base Package

Last modified by Helena on 2025/09/10 11:19
From version 2.3
edited by Helena
on 2025/06/08 00:51
Change comment: There is no comment for this version
To version 2.4
edited by Helena
on 2025/06/08 00:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -116,9 +116,9 @@
116 116  
117 117  **Figure 12: Class Diagram of Basic Data Types**
118 118  
119 -===== 3.4.2 Explanation of the Diagram =====
119 +=== 3.4.2 Explanation of the Diagram ===
120 120  
121 -====== 3.4.2.1 Narrative ======
121 +==== 3.4.2.1 Narrative ====
122 122  
123 123  The FacetType and FacetValueType enumerations are used to specify the valid format of the content of a non-enumerated Concept or the usage of a Concept when specified for use on a //Component// on a //Structure// (such as a Dimension in a DataStructureDefinition). The description of the various types can be found in the chapter on ConceptScheme (section 4.5).
124 124  
... ... @@ -139,23 +139,23 @@
139 139  
140 140  The VersionType data types provides the details for versioning according to SDMX versioning rules, as explained in SDMX Standards Section 6, paragraph “4.3 Versioning”.
141 141  
142 -==== //3.5 The Item Scheme Pattern// ====
142 +== 3.5 The Item Scheme Pattern ==
143 143  
144 -===== 3.5.1 Context =====
144 +=== 3.5.1 Context ===
145 145  
146 146  The Item Scheme is a basic architectural pattern that allows the creation of list schemes for use in simple taxonomies, for example.
147 147  
148 148  The //ItemScheme// is the basis for CategoryScheme, Codelist, ConceptScheme, ReportingTaxonomy, //OrganisationScheme//, TransformationScheme, CustomTypeScheme, NamePersonalisationScheme, RulesetScheme, VtlMappingScheme and UserDefinedOperatorScheme.
149 149  
150 -===== 3.5.2 Class Diagram =====
150 +=== 3.5.2 Class Diagram ===
151 151  
152 152  [[image:1749246130543-644.jpeg]]
153 153  
154 154  **Figure 13 The Item Scheme pattern**
155 155  
156 -===== 3.5.3 Explanation of the Diagram =====
156 +=== 3.5.3 Explanation of the Diagram ===
157 157  
158 -====== 3.5.3.1 Narrative ======
158 +==== 3.5.3.1 Narrative ====
159 159  
160 160  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 is derived 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 ConceptScheme. The associated Concepts are //Item//s.
161 161  
... ... @@ -169,37 +169,28 @@
169 169  
170 170  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//.
171 171  
172 -====== 3.5.3.2 Definitions ======
172 +==== 3.5.3.2 Definitions ====
173 173  
174 -|**Class**|**Feature**|**Description**
175 -|//ItemScheme//|(((
174 +(% style="width:989.835px" %)
175 +|**Class**|(% style="width:297px" %)**Feature**|(% style="width:583px" %)**Description**
176 +|//ItemScheme//|(% style="width:297px" %)(((
176 176  Inherits from:
177 -
178 178  //MaintainableArtefact//
179 -
180 180  Direct sub classes are:
181 -
182 182  CategoryScheme
183 -
184 184  ConceptScheme
185 -
186 186  Codelist
187 -
188 188  ReportingTaxonomy
189 -
190 190  //OrganisationScheme//
191 -
192 192  TransformationScheme
193 -
194 194  CustomTypeScheme NamePersonalisationSc heme
195 -
196 196  RulesetScheme
197 -
198 -VtlMappingScheme UserDefinedOperatorSc heme
199 -)))|The descriptive information for an arrangement or division of objects into groups based on characteristics, which the objects have in common.
200 -| |isPartial|Denotes whether the Item Scheme contains a subset of the full set of Items in the maintained scheme.
201 -| |/items|Association to the Items in the scheme.
202 -|//Item//|(((
188 +VtlMappingScheme
189 +UserDefinedOperatorSc heme
190 +)))|(% style="width:583px" %)The descriptive information for an arrangement or division of objects into groups based on characteristics, which the objects have in common.
191 +| |(% style="width:297px" %)isPartial|(% style="width:583px" %)Denotes whether the Item Scheme contains a subset of the full set of Items in the maintained scheme.
192 +| |(% style="width:297px" %)/items|(% style="width:583px" %)Association to the Items in the scheme.
193 +|//Item//|(% style="width:297px" %)(((
203 203  Inherits from:
204 204  
205 205  //NameableArtefact//
... ... @@ -225,9 +225,8 @@
225 225  VtlMapping
226 226  
227 227  UserDefinedOperator// //hierarchy
228 -)))|(((
219 +)))|(% style="width:583px" %)(((
229 229  The Item is an item of content in an Item Scheme. This may be a node in a taxonomy or ontology, a code in a code list etc. Node that at the conceptual level the Organisation is not hierarchic.
230 -
231 231  This allows an Item optionally to have one or more child Items
232 232  )))
233 233