Skip to Content

Changes for page 3 SDMX Base Package

Last modified by Helena on 2025/09/10 11:19
From version 3.3
edited by Helena
on 2025/06/08 00:59
Change comment: There is no comment for this version
To version 3.2
edited by Helena
on 2025/06/08 00:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -237,9 +237,13 @@
237 237  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:
238 238  
239 239  DimensionDescriptor: Dimension, TimeDimension
240 +
240 240  GroupDimensionDescriptor: Dimension, TimeDimension
242 +
241 241  MeasureDescriptor: Measure
244 +
242 242  AttributeDescriptor: DataAttribute, MetadataAttributeRef
246 +
243 243  MetadataAttributeDescriptor: MetadataAttribute
244 244  
245 245  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.
... ... @@ -263,36 +263,54 @@
263 263  |**Class**|**Feature**|**Description**
264 264  |StructureUsage|(((
265 265  Inherits from:
270 +
266 266  //MaintainableArtefact//
272 +
267 267  Sub classes are:
274 +
268 268  Dataflow
276 +
269 269  Metadataflow
270 270  )))|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.
271 271  | |structure|An association to a Structure specifying the structure of the artefact.
272 272  |Structure|(((
273 273  Inherits from:
282 +
274 274  //MaintainableArtefact//
284 +
275 275  Sub classes are:
286 +
276 276  DataStructureDefinition MetadataStructureDefinit ion
277 277  )))|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.
278 278  | |grouping|A composite association to one or more component lists.
279 279  |//ComponentList//|(((
280 280  Inherits from:
292 +
281 281  //IdentifiableArtefact//
294 +
282 282  Sub classes are:
296 +
283 283  DimensionDescriptor
298 +
284 284  GroupDimensionDescriptor
300 +
285 285  MeasureDescriptor
302 +
286 286  AttributeDescriptor MetadataAttributeDescrip tor
287 287  )))|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.
288 288  | |components|An aggregate association to one or more components which make up the list.
289 289  |//Component//|(((
290 290  Inherits from:
308 +
291 291  //IdentifiableArtefact//
310 +
292 292  Sub classes are:
312 +
293 293  Measure
294 -//AttributeComponent
295 -DimensionComponent//
314 +
315 +//AttributeComponent//
316 +
317 +//DimensionComponent//
296 296  )))|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.
297 297  | |conceptIdentity|Association to a Concept in a Concept Scheme that identifies and defines the semantic of the Component.
298 298  | |localRepresentation|(((