Skip to Content

Changes for page 3 SDMX Base Package

Last modified by Helena on 2025/09/10 11:19
From version 11.2
edited by Helena
on 2025/05/16 13:37
Change comment: There is no comment for this version
To version 11.1
edited by Helena
on 2025/05/15 10:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -9,7 +9,9 @@
9 9  The motivation for establishing the SDMX Base package is as follows:
10 10  
11 11  it is accepted “Best Practise” to identify fundamental archetypes occurring in a model
12 +
12 12  identification of commonly found structures or “patterns” leads to easier understanding
14 +
13 13  identification of patterns encourages re-use
14 14  
15 15  Each of the class diagrams in this section views classes from the SDMX Base package from a different perspective. There are detailed views of specific patterns, plus overviews showing inheritance between classes, and relationships amongst classes.
... ... @@ -192,17 +192,27 @@
192 192  |**Class**|(% style="width:272px" %)**Feature**|(% style="width:422px" %)**Description**
193 193  |//ItemScheme//|(% style="width:272px" %)(((
194 194  Inherits from:
197 +
195 195  //MaintainableArtefact//
199 +
196 196  Direct sub classes are:
201 +
197 197  CategoryScheme
203 +
198 198  ConceptScheme
205 +
199 199  Codelist
207 +
200 200  ReportingTaxonomy
209 +
201 201  //OrganisationScheme//
211 +
202 202  TransformationScheme
203 -CustomTypeScheme
204 -NamePersonalisationSc heme
213 +
214 +CustomTypeScheme NamePersonalisationSc heme
215 +
205 205  RulesetScheme
217 +
206 206  VtlMappingScheme UserDefinedOperatorSc heme
207 207  )))|(% style="width:422px" %)The descriptive information for an arrangement or division of objects into groups based on characteristics, which the objects have in common.
208 208  | |(% style="width:272px" %)isPartial|(% style="width:422px" %)Denotes whether the Item Scheme contains a subset of the full set of Items in the maintained scheme.
... ... @@ -211,17 +211,29 @@
211 211  Inherits from:
212 212  
213 213  //NameableArtefact//
226 +
214 214  Direct sub classes are
228 +
215 215  Category
230 +
216 216  Concept
232 +
217 217  Code
234 +
218 218  ReportingCategory
236 +
219 219  //Organisation//
238 +
220 220  Transformation
240 +
221 221  CustomType
242 +
222 222  NamePersonalisation
244 +
223 223  Ruleset
246 +
224 224  VtlMapping
248 +
225 225  UserDefinedOperator
226 226  )))|(% style="width:422px" %)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.
227 227  | |(% style="width:272px" %)hierarchy|(% style="width:422px" %)This allows an Item optionally to have one or more child Items.
... ... @@ -253,9 +253,13 @@
253 253  The //Component// is contained in a //ComponentList//. The type of //Component// in a //ComponentList// is dependent on the concrete class of the ComponentList as follows:
254 254  
255 255  DimensionDescriptor: Dimension, TimeDimension
280 +
256 256  GroupDimensionDescriptor: Dimension, TimeDimension
282 +
257 257  MeasureDescriptor: Measure
284 +
258 258  AttributeDescriptor: DataAttribute, MetadataAttributeRef
286 +
259 259  MetadataAttributeDescriptor: MetadataAttribute
260 260  
261 261  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.