Skip to Content

Changes for page 1 Introduction

Last modified by Helena K. on 2026/06/08 15:37
From version 20.2
edited by Helena K.
on 2026/06/08 15:33
Change comment: There is no comment for this version
To version 2.1
edited by Helena K.
on 2025/06/07 00:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,10 +5,6 @@
1 -{{box title="**Contents**"}}
2 -{{toc/}}
3 -{{/box}}
4 -
5 5  This document is not normative but provides a detailed view of the information model on which the normative SDMX specifications are based. Those new to the UML notation or to the concept of Data Structure Definitions may wish to read the appendixes in this document as an introductory exercise.
6 6  
7 -== 1.1 Related Documents ==
3 +=== 1.1 Related Documents ===
8 8  
9 9  This document is one of two documents concerned with the SDMX Information Model. The complete set of documents is:
10 10  
... ... @@ -11,7 +11,7 @@
11 11  * SDMX SECTION 02 INFORMATION MODEL: UML CONCEPTUAL DESIGN (this document): This document comprises the complete definition of the information model, with the exception of the registry interfaces. It is intended for technicians wishing to understand the complete scope of the SDMX technical standards in a syntax neutral form.
12 12  * SDMX SECTION 05 REGISTRY SPECIFICATION: LOGICAL INTERFACES: This document provides the logical specification for the registry interfaces, including subscription/notification, registration/submission of data and metadata, and querying.
13 13  
14 -== 1.2 Modelling Technique and Diagrammatic Notes ==
10 +=== 1.2 Modelling Technique and Diagrammatic Notes ===
15 15  
16 16  The modelling technique used for the SDMX Information Model (SDMX-IM) is the Unified
17 17  
... ... @@ -19,8 +19,6 @@
19 19  
20 20  UML diagramming allows a class to be shown with or without the compartments for one or both of attributes and operations (sometimes called methods). In this document the operations compartment is not shown as there are no operations.
21 21  
22 -[[image:1749563229253-391.png]]
23 -
24 24  **Figure 1 Class with operations suppressed**
25 25  
26 26  In some diagrams for some classes the attribute compartment is suppressed even though there may be some attributes. This is deliberate and is done to aid clarity of the diagram. The method used is:
... ... @@ -28,8 +28,6 @@
28 28  * The attributes will always be present on the class diagram where the class is defined and its attributes and associations are defined.
29 29  * On other diagrams, such as inheritance diagrams, the attributes may be suppressed from the class for clarity.
30 30  
31 -[[image:1749563243362-354.png]]
32 -
33 33  **Figure 2 Class with attributes also suppressed**
34 34  
35 35  Note that, in any case, attributes inherited from a super class are not shown in the sub class.
... ... @@ -36,13 +36,13 @@
36 36  
37 37  The following table structure is used in the definition of the classes, attributes, and associations.
38 38  
39 -(% style="width:680.835px" %)
40 -|(% style="width:129px" %)**Class**|(% style="width:226px" %)**Feature**|(% style="width:322px" %)**Description**
41 -|(% style="width:129px" %)ClassName|(% style="width:226px" %) |(% style="width:322px" %)
42 -|(% style="width:129px" %) |(% style="width:226px" %)attributeName|(% style="width:322px" %)
43 -|(% style="width:129px" %) |(% style="width:226px" %)associationName|(% style="width:322px" %)
44 -|(% style="width:129px" %) |(% style="width:226px" %)+roleName
45 45  
32 +|**Class**|**Feature**|**Description**
33 +|ClassName| |
34 +| |attributeName|
35 +| |associationName|
36 +| |+roleName|
37 +
46 46  The content in the “Feature” column comprises or explains one of the following structural features of the class:
47 47  
48 48  * Whether it is an abstract class. Abstract classes are shown in //italic Courier// font.
... ... @@ -54,9 +54,9 @@
54 54  
55 55  The Description column provides a short definition or explanation of the Class or Feature. UML class names may be used in the description and if so, they are presented in normal font with spaces between words. For example, the class ConceptScheme will be written as Concept Scheme.
56 56  
57 -== 1.3 Overall Functionality ==
49 +=== 1.3 Overall Functionality ===
58 58  
59 -=== 1.3.1 Information Model Packages ===
51 +==== 1.3.1 Information Model Packages ====
60 60  
61 61  The SDMX Information Model (SDMX-IM) is a conceptual metamodel from which syntax specific implementations are developed. The model is constructed as a set of functional packages which assist in the understanding, re-use and maintenance of the model.
62 62  
... ... @@ -70,7 +70,7 @@
70 70  
71 71  In reality the layers have no implicit or explicit structural function as any package can make use of any construct in another package.
72 72  
73 -=== 1.3.2 Version 1.0 ===
65 +==== 1.3.2 Version 1.0 ====
74 74  
75 75  In version 1.0 the metamodel supported the requirements for:
76 76  
... ... @@ -80,26 +80,33 @@
80 80  
81 81  The SDMX-IM comprises a number of packages. These packages act as convenient compartments for the various sub models in the SDMX-IM. The diagram below shows the sub models of the SDMX-IM that were included in the version 1.0 specification.
82 82  
83 -[[image:image4.png]]
75 +[[image:1749245986724-174.png]]
84 84  
85 85  **Figure 3: SDMX Information Model Version 1.0 package structure**
86 86  
87 -=== 1.3.3 Version 2.0/2.1 ===
79 +==== 1.3.3 Version 2.0/2.1 ====
88 88  
89 -The version 2.0/2.1 model extends the functionality of version 1.0. principally in the area of metadata, but also in various ways to define structures to support data analysis by systems with knowledge of cube type structures such as OLAP{{footnote}}OLAP: On line analytical processing{{/footnote}} systems. The following major constructs have been added at version 2.0/2.1
81 +The version 2.0/2.1 model extends the functionality of version 1.0. principally in the area of metadata, but also in various ways to define structures to support data analysis by systems with knowledge of cube type structures such as OLAP[[^^~[1~]^^>>path:#_ftn1]] systems. The following major constructs have been added at version 2.0/2.1
90 90  
91 91  Metadata structure definition
84 +
92 92  Metadata set
86 +
93 93  Hierarchical Codelist
88 +
94 94  Data and Metadata Provisioning
90 +
95 95  Process
92 +
96 96  Mapping
94 +
97 97  Constraints
96 +
98 98  Constructs supporting the Registry
99 99  
100 100  Furthermore, the term Data Structure Definition replaces the term Key Family: as both of these terms are used in various communities, they are synonymous. The term Data Structure Definition is used in the model and this document.
101 101  
102 -[[image:image5.png]]
101 +[[image:1749245986730-349.jpeg]]
103 103  
104 104  **Figure 4 SDMX Information Model Version 2.0/2.1 package structure**
105 105  
... ... @@ -111,26 +111,25 @@
111 111  
112 112  Note that the data and metadata required for registry functions are not confined to the registry, and the registry also makes use of the other packages in the Information Model.
113 113  
114 -[[image:image6.png]]
113 +[[image:1749245986733-116.jpeg]]
115 115  
116 116  **Figure 5: SDMX Information Model Version 2.0/2.1 package structure including the registry**
117 117  
118 -=== 1.3.4 Version 3.0 ===
117 +==== 1.3.4 Version 3.0 ====
119 119  
120 120  The version 3.0 model introduces changes in the way reference metadata are handled. In addition, it includes a few more artefacts. Finally, a few abstractions have been added, as shown in section “Basic Inheritance” in “Figure 11: Basic Inheritance from the Base Structures”.
121 121  
122 122  The IM packages are largely the same.
123 123  
124 -[[image:image7.png]]
123 +[[image:1749245986737-968.jpeg]]
125 125  
126 126  **Figure 6: SDMX Information Model version 3.0 package structure**
127 127  
128 -=== 1.3.5 Version 3.1 ===
127 +==== 1.3.5 Version 3.1 ====
129 129  
130 -Whilst some additional properties have been added to Dataflow, DSD, Data Constraint, SDMX v3.1 doe
129 +Whilst some additional properties have been added to Dataflow, DSD, Data Constraint, SDMX v3.1 does not change the high level information model, it remains as it is in Figure 6.
131 131  
132 -s not change the high level information model, it remains as it is in Figure 6.
133 133  
134 134  ----
135 135  
136 -{{putFootnotes/}}
134 +[[~[1~]>>path:#_ftnref1]] OLAP: On line analytical processing
1749563229253-391.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.arturkryazhev
Size
... ... @@ -1,1 +1,0 @@
1 -9.8 KB
Content
1749563243362-354.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.arturkryazhev
Size
... ... @@ -1,1 +1,0 @@
1 -2.2 KB
Content
image4.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -35.7 KB
Content
image5.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -78.0 KB
Content
image6.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -82.9 KB
Content
image7.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -90.8 KB
Content
1749245986724-174.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +9.9 KB
Content
1749245986730-349.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +20.4 KB
Content
1749245986733-116.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +24.4 KB
Content
1749245986737-968.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +26.8 KB
Content
SKMS.Methodology.Code.MethodologyClass[0]
Index
... ... @@ -1,1 +1,0 @@
1 -2
SUZ.Methodology.Code.MethodologyClass[0]
index
... ... @@ -1,0 +1,1 @@
1 +2
© Semantic R&D Group, 2026