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.2
edited by Helena
on 2025/05/16 13:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -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:
281 +
281 281  //MaintainableArtefact//
282 282  
283 283  Sub classes are:
285 +
284 284  Dataflow
287 +
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:
293 +
290 290  //MaintainableArtefact//
291 291  
292 292  Sub classes are:
297 +
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:
303 +
298 298  //IdentifiableArtefact//
299 299  
300 300  Sub classes are:
307 +
301 301  DimensionDescriptor
309 +
302 302  GroupDimensionDescriptor
311 +
303 303  MeasureDescriptor
313 +
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:
319 +
309 309  //IdentifiableArtefact//
310 310  
311 311  Sub classes are:
323 +
312 312  Measure
313 -//AttributeComponent
314 -DimensionComponent//
325 +
326 +//AttributeComponent//
327 +
328 +//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 -----
396 +[[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_59eee18f.gif||alt="Shape29" height="1" width="192"]]
383 383  
398 +^^2^^ In the JSON schemas, more complex data types are complemented with regular expressions, whenever no direct mapping to a standard type exists.
399 +
384 384  {{putFootnotes/}}