Skip to Content

Changes for page 3 SDMX Base Package

Last modified by Helena on 2025/09/10 11:19
From version 6.6
edited by Helena
on 2025/05/20 00:25
Change comment: There is no comment for this version
To version 6.3
edited by Helena
on 2025/05/20 00:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -159,8 +159,7 @@
159 159  
160 160  [[image:SDMX_2-1_SECTION_2_InformationModel_2020-07_a2879920.jpg||height="602" width="614"]]
161 161  
162 -(% class="wikigeneratedid" id="HFigure12TheItemSchemePattern" %)
163 -**Figure 12 The Item Scheme Pattern**
162 +====== Figure 12 The Item Scheme Pattern ======
164 164  
165 165  ===== {{id name="_Toc370981"/}}3.5.3 Explanation of the Diagram =====
166 166  
... ... @@ -186,47 +186,73 @@
186 186  
187 187  ==== 3.5.3.2 Definitions ====
188 188  
189 -(% style="width:911.294px" %)
190 -|**Class**|(% style="width:246px" %)**Feature**|(% style="width:478px" %)**Description**
191 -|//ItemScheme//|(% style="width:246px" %)(((
188 +|**Class**|**Feature**|**Description**
189 +|//ItemScheme//|(((
192 192  Inherits from:
191 +
193 193  //MaintainableArtefact//
193 +
194 194  Direct sub classes are:
195 +
195 195  CategoryScheme
197 +
196 196  ConceptScheme
199 +
197 197  Codelist
198 -)))|(% style="width:478px" %)The descriptive information for an arrangement or division of objects into groups based on characteristics, which the objects have in common.
199 -| |(% style="width:246px" %)(((
201 +)))|The descriptive information for an arrangement or division of objects into groups based on characteristics, which the objects have in common.
202 +| |(((
200 200  ReportingTaxonomy
204 +
201 201  //OrganisationScheme//
206 +
202 202  Transformation Scheme
208 +
203 203  CustomTypeScheme
210 +
204 204  NamePersonasationScheme
212 +
205 205  RuletScheme
214 +
206 206  VtlMappingScheme
216 +
207 207  UserDefinedOperatorScheme
208 -)))|(% style="width:478px" %)
209 -| |(% style="width:246px" %)isPartial|(% style="width:478px" %)Denotes whether the Item Scheme contains a sub set of the full set of Items in the maintained scheme.
210 -| |(% style="width:246px" %)items|(% style="width:478px" %)Association to the Items in the scheme.
211 -|//Item//|(% style="width:246px" %)(((
218 +)))|
219 +| |isPartial|Denotes whether the Item Scheme contains a sub set of the full set of Items in the maintained scheme.
220 +| |items|Association to the Items in the scheme.
221 +|//Item//|(((
212 212  Inherits from:
223 +
213 213  //NameableArtefact//
214 -Direct sub classes are Category
225 +
226 +Direct sub classes are
227 +
228 +Category
229 +
215 215  Concept
231 +
216 216  Code
233 +
217 217  ReportingCategory
235 +
218 218  //Organisation//
237 +
219 219  Transformation
239 +
220 220  CustomType
241 +
221 221  NamePersonlisation
243 +
222 222  Ruleset
245 +
223 223  VtlMapping
224 -UserDefinedOperator
225 -)))|(% style="width:478px" %)(((
247 +
248 +UserDefinedOperator//    //
249 +)))|(((
226 226  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.
251 +
227 227  Note that at the conceptual level the Organisation is not hierarchic
228 228  )))
229 -| |(% style="width:246px" %)hierarchy|(% style="width:478px" %)This allows an Item optionally to have one or more child Items.
254 +| |hierarchy|This allows an Item optionally to have one or more child Items.
230 230  
231 231  == {{id name="_Toc370982"/}}3.6 The Structure Pattern ==
232 232  
... ... @@ -242,8 +242,7 @@
242 242  
243 243  [[image:SDMX_2-1_SECTION_2_InformationModel_2020-07_b6478a73.png||height="774" width="556"]]
244 244  
245 -(% class="wikigeneratedid" id="HFigure14:RepresentationwithintheStructurePattern" %)
246 -**Figure 14: Representation within the Structure Pattern**
270 +====== Figure 14: Representation within the Structure Pattern ======
247 247  
248 248  === {{id name="_Toc370985"/}}3.6.3 Explanation of the Diagrams ===
249 249  
... ... @@ -267,7 +267,7 @@
267 267  
268 268  __ReportStructure__: MetadataAttribute
269 269  
270 -Each Component takes its semantic (and possibly also its representation) from a Concept in a ConceptScheme. This is represented by the conceptIdentity association to Concept.
294 +Each Component takes its semantic (and possibly also its representation) from a Concept in 773 a ConceptScheme. This is represented by the conceptIdentity association to Concept.
271 271  
272 272  The //Component// may also have a localRepresentation, This allows a concrete class, such as Dimension, to specify its representation which is local to the //Structure// in which it is contained (for Dimension this will be DataStructureDefinition), and thus overrides any coreRepresentation specified for the Concept.
273 273