Changes for page 3 SDMX Base Package
Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -9,9 +9,7 @@ 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 - 13 13 identification of commonly found structures or “patterns” leads to easier understanding 14 - 15 15 identification of patterns encourages re-use 16 16 17 17 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. ... ... @@ -194,27 +194,17 @@ 194 194 |**Class**|(% style="width:272px" %)**Feature**|(% style="width:422px" %)**Description** 195 195 |//ItemScheme//|(% style="width:272px" %)((( 196 196 Inherits from: 197 - 198 198 //MaintainableArtefact// 199 - 200 200 Direct sub classes are: 201 - 202 202 CategoryScheme 203 - 204 204 ConceptScheme 205 - 206 206 Codelist 207 - 208 208 ReportingTaxonomy 209 - 210 210 //OrganisationScheme// 211 - 212 212 TransformationScheme 213 - 214 -CustomTypeScheme NamePersonalisationSc heme 215 - 203 +CustomTypeScheme 204 +NamePersonalisationSc heme 216 216 RulesetScheme 217 - 218 218 VtlMappingScheme UserDefinedOperatorSc heme 219 219 )))|(% style="width:422px" %)The descriptive information for an arrangement or division of objects into groups based on characteristics, which the objects have in common. 220 220 | |(% 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. ... ... @@ -223,29 +223,17 @@ 223 223 Inherits from: 224 224 225 225 //NameableArtefact// 226 - 227 227 Direct sub classes are 228 - 229 229 Category 230 - 231 231 Concept 232 - 233 233 Code 234 - 235 235 ReportingCategory 236 - 237 237 //Organisation// 238 - 239 239 Transformation 240 - 241 241 CustomType 242 - 243 243 NamePersonalisation 244 - 245 245 Ruleset 246 - 247 247 VtlMapping 248 - 249 249 UserDefinedOperator 250 250 )))|(% 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. 251 251 | |(% style="width:272px" %)hierarchy|(% style="width:422px" %)This allows an Item optionally to have one or more child Items. ... ... @@ -277,13 +277,9 @@ 277 277 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: 278 278 279 279 DimensionDescriptor: Dimension, TimeDimension 280 - 281 281 GroupDimensionDescriptor: Dimension, TimeDimension 282 - 283 283 MeasureDescriptor: Measure 284 - 285 285 AttributeDescriptor: DataAttribute, MetadataAttributeRef 286 - 287 287 MetadataAttributeDescriptor: MetadataAttribute 288 288 289 289 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. ... ... @@ -306,54 +306,40 @@ 306 306 |**Class**|(% style="width:284px" %)**Feature**|(% style="width:353px" %)**Description** 307 307 |StructureUsage|(% style="width:284px" %)((( 308 308 Inherits from: 309 - 310 310 //MaintainableArtefact// 311 311 312 312 Sub classes are: 313 - 314 314 Dataflow 315 - 316 316 Metadataflow 317 317 )))|(% 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. 318 318 | |(% style="width:284px" %)structure|(% style="width:353px" %)An association to a Structure specifying the structure of the artefact. 319 319 |Structure|(% style="width:284px" %)((( 320 320 Inherits from: 321 - 322 322 //MaintainableArtefact// 323 323 324 324 Sub classes are: 325 - 326 326 DataStructureDefinition MetadataStructureDefinit ion 327 327 )))|(% 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. 328 328 | |(% style="width:284px" %)grouping|(% style="width:353px" %)A composite association to one or more component lists. 329 329 |//ComponentList//|(% style="width:284px" %)((( 330 330 Inherits from: 331 - 332 332 //IdentifiableArtefact// 333 333 334 334 Sub classes are: 335 - 336 336 DimensionDescriptor 337 - 338 338 GroupDimensionDescriptor 339 - 340 340 MeasureDescriptor 341 - 342 342 AttributeDescriptor MetadataAttributeDescriptor 343 343 )))|(% 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. 344 344 | |(% style="width:284px" %)components|(% style="width:353px" %)An aggregate association to one or more components which make up the list. 345 345 |//Component//|(% style="width:284px" %)((( 346 346 Inherits from: 347 - 348 348 //IdentifiableArtefact// 349 349 350 350 Sub classes are: 351 - 352 352 Measure 353 - 354 -//AttributeComponent// 355 - 356 -//DimensionComponent// 313 +//AttributeComponent 314 +DimensionComponent// 357 357 )))|(% 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. 358 358 | |(% style="width:284px" %)conceptIdentity|(% style="width:353px" %)((( 359 359 Association to a Concept in a Concept Scheme that identifies and defines the