Skip to Content

Changes for page 3 SDMX Base Package

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

Summary

Details

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