Skip to Content

Changes for page 3 SDMX Base Package

Last modified by Helena on 2025/09/10 11:19
From version 12.1
edited by Helena
on 2025/05/16 13:38
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.
... ... @@ -278,40 +278,54 @@
278 278  |**Class**|(% style="width:284px" %)**Feature**|(% style="width:353px" %)**Description**
279 279  |StructureUsage|(% style="width:284px" %)(((
280 280  Inherits from:
309 +
281 281  //MaintainableArtefact//
282 282  
283 283  Sub classes are:
313 +
284 284  Dataflow
315 +
285 285  Metadataflow
286 286  )))|(% style="width:353px" %)An artefact whose components are described by a Structure. In concrete terms (sub-classes) an example would be a Dataflow which is linked to a given structure – in this case the Data Structure Definition.
287 287  | |(% style="width:284px" %)structure|(% style="width:353px" %)An association to a Structure specifying the structure of the artefact.
288 288  |Structure|(% style="width:284px" %)(((
289 289  Inherits from:
321 +
290 290  //MaintainableArtefact//
291 291  
292 292  Sub classes are:
325 +
293 293  DataStructureDefinition MetadataStructureDefinit ion
294 294  )))|(% style="width:353px" %)Abstract specification of a list of lists to define a complex tabular structure. A concrete example of this would be statistical concepts, code lists, and their organisation in a data or metadata structure definition, defined by a centre institution, usually for the exchange of statistical information with its partners.
295 295  | |(% style="width:284px" %)grouping|(% style="width:353px" %)A composite association to one or more component lists.
296 296  |//ComponentList//|(% style="width:284px" %)(((
297 297  Inherits from:
331 +
298 298  //IdentifiableArtefact//
299 299  
300 300  Sub classes are:
335 +
301 301  DimensionDescriptor
337 +
302 302  GroupDimensionDescriptor
339 +
303 303  MeasureDescriptor
341 +
304 304  AttributeDescriptor MetadataAttributeDescriptor
305 305  )))|(% style="width:353px" %)An abstract definition of a list of components. A concrete example is a Dimension Descriptor, which defines the list of Dimensions in a Data Structure Definition.
306 306  | |(% style="width:284px" %)components|(% style="width:353px" %)An aggregate association to one or more components which make up the list.
307 307  |//Component//|(% style="width:284px" %)(((
308 308  Inherits from:
347 +
309 309  //IdentifiableArtefact//
310 310  
311 311  Sub classes are:
351 +
312 312  Measure
313 -//AttributeComponent
314 -DimensionComponent//
353 +
354 +//AttributeComponent//
355 +
356 +//DimensionComponent//
315 315  )))|(% style="width:353px" %)A Component is an abstract super class used to define qualitative and quantitative data and metadata items that belong to a Component List and hence a Structure. Component is refined through its sub-classes.
316 316  | |(% style="width:284px" %)conceptIdentity|(% style="width:353px" %)(((
317 317  Association to a Concept in a Concept Scheme that identifies and defines the
... ... @@ -379,6 +379,8 @@
379 379  |decimals|(% style="width:827px" %)The decimals facet indicates the number of characters allowed after the decimal separator.
380 380  |pattern|(% style="width:827px" %)The pattern attribute holds any regular expression permitted in the implementation syntax (e.g., W3C XML Schema).
381 381  
382 -----
424 +[[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_59eee18f.gif||alt="Shape29" height="1" width="192"]]
383 383  
426 +^^2^^ In the JSON schemas, more complex data types are complemented with regular expressions, whenever no direct mapping to a standard type exists.
427 +
384 384  {{putFootnotes/}}