Skip to Content

Changes for page 1 Introduction

Last modified by Helena on 2025/09/10 11:19
From version 1.1
edited by Helena
on 2025/06/07 00:39
Change comment: There is no comment for this version
To version 3.3
edited by Helena
on 2025/06/08 14:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Tags
... ... @@ -1,0 +1,1 @@
1 +Artefact|Attribute|Category scheme|Code|Concept scheme|Data structure definition|Dataflow|Notification|Reference metadata|SDMX Information Model|Statistical data and metadata exchange|Subscription
Content
... ... @@ -1,110 +1,107 @@
1 -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.
1 +{{box title="**Contents**"}}
2 +{{toc/}}
3 +{{/box}}
2 2  
3 -=== 1.1 Related Documents ===
5 +This document is not normative but provides a detailed view of the information model on which the normative [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] specifications are based. Those new to the UML notation or to the (% style="color:#e74c3c" %)concept(%%) of [[Data Structure Definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]] may wish to read the appendixes in this document as an introductory exercise.
4 4  
5 -This document is one of two documents concerned with the SDMX Information Model. The complete set of documents is:
7 +== 1.1 Related Documents ==
6 6  
7 -* 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.
8 -* 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.
9 +This document is one of two documents concerned with the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]. The complete set of documents is:
9 9  
10 -=== 1.2 Modelling Technique and Diagrammatic Notes ===
11 +* [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 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>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] technical standards in a syntax neutral form.
12 +* [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] SECTION 05 REGISTRY SPECIFICATION: LOGICAL INTERFACES: This document provides the logical specification for the registry interfaces, including [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]]/[[notification>>doc:sdmx:Glossary.Notification.WebHome]], registration/submission of data and metadata, and querying.
11 11  
12 -The modelling technique used for the SDMX Information Model (SDMX-IM) is the Unified
14 +== 1.2 Modelling Technique and Diagrammatic Notes ==
13 13  
14 -Modelling Language (UML). An overview of the constructs of UML that are used in the SDMXIM can be found in the Appendix “A Short Guide to UML in the SDMX Information Model”
16 +The modelling technique used for the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] ([[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]) is the Unified
15 15  
16 -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.
18 +Modelling Language (UML). An overview of the constructs of UML that are used in the SDMXIM can be found in the Appendix “A Short Guide to UML in the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]”
17 17  
20 +UML diagramming allows a class to be shown with or without the compartments for one or both of [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] and operations (sometimes called methods). In this document the operations compartment is not shown as there are no operations.
21 +
18 18  **Figure 1 Class with operations suppressed**
19 19  
20 -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:
24 +In some diagrams for some classes the [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] compartment is suppressed even though there may be some [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]. This is deliberate and is done to aid clarity of the diagram. The method used is:
21 21  
22 -* The attributes will always be present on the class diagram where the class is defined and its attributes and associations are defined.
23 -* On other diagrams, such as inheritance diagrams, the attributes may be suppressed from the class for clarity.
26 +* The [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] will always be present on the class diagram where the class is defined and its [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] and associations are defined.
27 +* On other diagrams, such as inheritance diagrams, the [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] may be suppressed from the class for clarity.
24 24  
25 -**Figure 2 Class with attributes also suppressed**
29 +**Figure 2 Class with [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] also suppressed**
26 26  
27 -Note that, in any case, attributes inherited from a super class are not shown in the sub class.
31 +Note that, in any case, [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] inherited from a super class are not shown in the sub class.
28 28  
29 -The following table structure is used in the definition of the classes, attributes, and associations.
33 +The following table structure is used in the definition of the classes, [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]], and associations.
30 30  
35 +(% style="width:680.835px" %)
36 +|(% style="width:129px" %)**Class**|(% style="width:226px" %)**Feature**|(% style="width:322px" %)**Description**
37 +|(% style="width:129px" %)ClassName|(% style="width:226px" %) |(% style="width:322px" %)
38 +|(% style="width:129px" %) |(% style="width:226px" %)attributeName|(% style="width:322px" %)
39 +|(% style="width:129px" %) |(% style="width:226px" %)associationName|(% style="width:322px" %)
40 +|(% style="width:129px" %) |(% style="width:226px" %)+roleName|(% style="width:322px" %)
31 31  
32 -|**Class**|**Feature**|**Description**
33 -|ClassName| |
34 -| |attributeName|
35 -| |associationName|
36 -| |+roleName|
37 -
38 38  The content in the “Feature” column comprises or explains one of the following structural features of the class:
39 39  
40 40  * Whether it is an abstract class. Abstract classes are shown in //italic Courier// font.
41 41  * The superclass this class inherits from, if any.
42 42  * The sub classes of this class, if any.
43 -* Attribute – the attributeName is shown in Courier font.
47 +* [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] – the attributeName is shown in Courier font.
44 44  * Association – the associationName is shown in Courier font. If the association is derived from the association between super classes, then the format is /associationName.
45 45  * Role – the +roleName is shown in Courier font.
46 46  
47 -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.
51 +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>>doc:sdmx:Glossary.Concept scheme.WebHome]].
48 48  
49 -=== 1.3 Overall Functionality ===
53 +== 1.3 Overall Functionality ==
50 50  
51 -==== 1.3.1 Information Model Packages ====
55 +=== 1.3.1 Information Model Packages ===
52 52  
53 -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.
57 +The [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] ([[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]) 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.
54 54  
55 55  In addition to this, to aid understanding each package can be considered to be in one of three conceptual layers:
56 56  
57 -the SDMX Base layer comprises fundamental building blocks which are used by the Structural Definitions layer and the Reporting and Dissemination layer
61 +the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Base layer comprises fundamental building blocks which are used by the Structural Definitions layer and the Reporting and Dissemination layer
58 58  
59 -the Structural Definitions layer comprises the definition of the structural artefacts needed to support data and metadata reporting and dissemination
63 +the Structural Definitions layer comprises the definition of the structural [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] needed to support data and metadata reporting and dissemination
60 60  
61 61  the Reporting and Dissemination layer comprises the definition of the data and metadata containers used for reporting and dissemination
62 62  
63 63  In reality the layers have no implicit or explicit structural function as any package can make use of any construct in another package.
64 64  
65 -==== 1.3.2 Version 1.0 ====
69 +=== 1.3.2 Version 1.0 ===
66 66  
67 -In version 1.0 the metamodel supported the requirements for:
71 +In (% style="color:#e74c3c" %)version(%%) 1.0 the metamodel supported the requirements for:
68 68  
69 -Data Structure Definition including (domain) category scheme, (metadata) concept scheme, and code list
73 +[[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] including (domain) [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]], (metadata) [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]], and [[code>>doc:sdmx:Glossary.Code.WebHome]] list
70 70  
71 71  Data and related metadata reporting and dissemination
72 72  
73 -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.
77 +The [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] comprises a number of packages. These packages act as convenient compartments for the various sub models in the [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]. The diagram below shows the sub models of the [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] that were included in the (% style="color:#e74c3c" %)version(%%) 1.0 specification.
74 74  
75 75  [[image:1749245986724-174.png]]
76 76  
77 -**Figure 3: SDMX Information Model Version 1.0 package structure**
81 +**Figure 3: [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] (% style="color:#e74c3c" %)Version(%%) 1.0 package structure**
78 78  
79 -==== 1.3.3 Version 2.0/2.1 ====
83 +=== 1.3.3 Version 2.0/2.1 ===
80 80  
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
85 +The (% style="color:#e74c3c" %)version(%%) 2.0/2.1 model extends the functionality of (% style="color:#e74c3c" %)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 (% style="color:#e74c3c" %)version(%%) 2.0/2.1
82 82  
83 83  Metadata structure definition
84 -
85 85  Metadata set
86 -
87 87  Hierarchical Codelist
88 -
89 89  Data and Metadata Provisioning
90 -
91 91  Process
92 -
93 93  Mapping
94 -
95 95  Constraints
96 -
97 97  Constructs supporting the Registry
98 98  
99 -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.
96 +Furthermore, the term [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] replaces the term Key Family: as both of these terms are used in various communities, they are synonymous. The term [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] is used in the model and this document.
100 100  
101 101  [[image:1749245986730-349.jpeg]]
102 102  
103 -**Figure 4 SDMX Information Model Version 2.0/2.1 package structure**
100 +**Figure 4 [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] (% style="color:#e74c3c" %)Version(%%) 2.0/2.1 package structure**
104 104  
105 105  Additional constructs that are specific to a registry-based scenario can be found in the Specification of Registry Interfaces. For information these are shown on the diagram below and comprise:
106 106  
107 -* Subscription and Notification
104 +* [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] and [[Notification>>doc:sdmx:Glossary.Notification.WebHome]]
108 108  * Registration
109 109  * Discovery
110 110  
... ... @@ -114,9 +114,9 @@
114 114  
115 115  **Figure 5: SDMX Information Model Version 2.0/2.1 package structure including the registry**
116 116  
117 -==== 1.3.4 Version 3.0 ====
114 +=== 1.3.4 Version 3.0 ===
118 118  
119 -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”.
116 +The (% style="color:#e74c3c" %)version(%%) 3.0 model introduces changes in the way [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] are handled. In addition, it includes a few more [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]]. Finally, a few abstractions have been added, as shown in section “Basic Inheritance” in “Figure 11: Basic Inheritance from the Base Structures”.
120 120  
121 121  The IM packages are largely the same.
122 122  
... ... @@ -124,11 +124,10 @@
124 124  
125 125  **Figure 6: SDMX Information Model version 3.0 package structure**
126 126  
127 -==== 1.3.5 Version 3.1 ====
124 +=== 1.3.5 Version 3.1 ===
128 128  
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.
126 +Whilst some additional properties have been added to [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]], Data (% style="color:#e74c3c" %)Constraint(%%), [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] v3.1 does not change the high (% style="color:#e74c3c" %)level(%%) information model, it remains as it is in Figure 6.
130 130  
131 -
132 132  ----
133 133  
134 -[[~[1~]>>path:#_ftnref1]] OLAP: On line analytical processing
130 +{{putFootnotes/}}
SUZ.Methodology.Code.MethodologyClass[0]
index
... ... @@ -1,0 +1,1 @@
1 +2