Changes for page 1 Introduction
Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -xwiki:XWiki.elena semanticproorg1 +xwiki:XWiki.helena - Tags
-
... ... @@ -1,1 +1,0 @@ 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
-
... ... @@ -2,40 +2,36 @@ 2 2 {{toc/}} 3 3 {{/box}} 4 4 5 -This document is not normative but provides a detailed view of the information model on which the normative [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]]specifications are based. Those new to the UML notation or to the concept of[[Data Structure Definitions>>doc:sdmx:Glossary.Datastructure definition.WebHome]] may wish to read the appendixes in this document as an introductory exercise.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 7 == 1.1 Related Documents == 8 8 9 -This document is one of two documents concerned with the [[SDMX Information Model>>doc:sdmx:Glossary.SDMXInformation Model.WebHome]].The complete set of documents is:9 +This document is one of two documents concerned with the SDMX Information Model. The complete set of documents is: 10 10 11 -* [[SDMX>>doc:sdmx:Glossary.Statisticaldata 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.Statisticaldata and metadata exchange.WebHome]] technical standards in a syntax neutral form.12 -* [[SDMX>>doc:sdmx:Glossary.Statisticaldata 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 +* 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 +* 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 14 == 1.2 Modelling Technique and Diagrammatic Notes == 15 15 16 -The modelling technique used for the [[SDMX Information Model>>doc:sdmx:Glossary.SDMXInformation Model.WebHome]]([[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]) is the Unified16 +The modelling technique used for the SDMX Information Model (SDMX-IM) is the Unified 17 17 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]]”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” 19 19 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.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 -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:24 +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: 27 27 28 -* 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.29 -* On other diagrams, such as inheritance diagrams, the [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]may be suppressed from the class for clarity.26 +* The attributes will always be present on the class diagram where the class is defined and its attributes and associations are defined. 27 +* On other diagrams, such as inheritance diagrams, the attributes may be suppressed from the class for clarity. 30 30 31 - [[image:1749563243362-354.png]]29 +**Figure 2 Class with attributes also suppressed** 32 32 33 - **Figure2 Classwith[[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]also suppressed**31 +Note that, in any case, attributes inherited from a super class are not shown in the sub class. 34 34 35 - Notethat,in any case,[[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]inheritedfroma superclass are notshowninthesub class.33 +The following table structure is used in the definition of the classes, attributes, and associations. 36 36 37 -The following table structure is used in the definition of the classes, [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]], and associations. 38 - 39 39 (% style="width:680.835px" %) 40 40 |(% style="width:129px" %)**Class**|(% style="width:226px" %)**Feature**|(% style="width:322px" %)**Description** 41 41 |(% style="width:129px" %)ClassName|(% style="width:226px" %) |(% style="width:322px" %) ... ... @@ -48,23 +48,23 @@ 48 48 * Whether it is an abstract class. Abstract classes are shown in //italic Courier// font. 49 49 * The superclass this class inherits from, if any. 50 50 * The sub classes of this class, if any. 51 -* [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]– the attributeName is shown in Courier font.47 +* Attribute – the attributeName is shown in Courier font. 52 52 * Association – the associationName is shown in Courier font. If the association is derived from the association between super classes, then the format is /associationName. 53 53 * Role – the +roleName is shown in Courier font. 54 54 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>>doc:sdmx:Glossary.Concept scheme.WebHome]].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. 56 56 57 57 == 1.3 Overall Functionality == 58 58 59 59 === 1.3.1 Information Model Packages === 60 60 61 -The [[SDMX Information Model>>doc:sdmx:Glossary.SDMXInformation 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.57 +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 63 63 In addition to this, to aid understanding each package can be considered to be in one of three conceptual layers: 64 64 65 -the [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]]Base layer comprises fundamental building blocks which are used by the Structural Definitions layer and the Reporting and Dissemination layer61 +the SDMX Base layer comprises fundamental building blocks which are used by the Structural Definitions layer and the Reporting and Dissemination layer 66 66 67 -the Structural Definitions layer comprises the definition of the structural [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]]needed to support data and metadata reporting and dissemination63 +the Structural Definitions layer comprises the definition of the structural artefacts needed to support data and metadata reporting and dissemination 68 68 69 69 the Reporting and Dissemination layer comprises the definition of the data and metadata containers used for reporting and dissemination 70 70 ... ... @@ -74,11 +74,11 @@ 74 74 75 75 In version 1.0 the metamodel supported the requirements for: 76 76 77 - [[Data Structure Definition>>doc:sdmx:Glossary.Datastructure 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]]list73 +Data Structure Definition including (domain) category scheme, (metadata) concept scheme, and code list 78 78 79 79 Data and related metadata reporting and dissemination 80 80 81 -The [[SDMX-IM>>doc:sdmx:Glossary.SDMXInformation 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.SDMXInformation Model.WebHome]].The diagram below shows the sub models of the[[SDMX-IM>>doc:sdmx:Glossary.SDMXInformation Model.WebHome]] that were included in the version 1.0 specification.77 +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 83 [[image:1749245986724-174.png]] 84 84 ... ... @@ -89,15 +89,22 @@ 89 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 90 90 91 91 Metadata structure definition 88 + 92 92 Metadata set 90 + 93 93 Hierarchical Codelist 92 + 94 94 Data and Metadata Provisioning 94 + 95 95 Process 96 + 96 96 Mapping 98 + 97 97 Constraints 100 + 98 98 Constructs supporting the Registry 99 99 100 -Furthermore, the term [[Data Structure Definition>>doc:sdmx:Glossary.Datastructuredefinition.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.Datastructure definition.WebHome]] is used in the model and this document.103 +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 102 [[image:1749245986730-349.jpeg]] 103 103 ... ... @@ -105,7 +105,7 @@ 105 105 106 106 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: 107 107 108 -* [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]]and[[Notification>>doc:sdmx:Glossary.Notification.WebHome]]111 +* Subscription and Notification 109 109 * Registration 110 110 * Discovery 111 111 ... ... @@ -117,7 +117,7 @@ 117 117 118 118 === 1.3.4 Version 3.0 === 119 119 120 -The version 3.0 model introduces changes in the way [[reference metadata>>doc:sdmx:Glossary.Referencemetadata.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”.123 +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 ... ... @@ -127,8 +127,9 @@ 127 127 128 128 === 1.3.5 Version 3.1 === 129 129 130 -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>>doc:sdmx:Glossary.Constraint.WebHome]](%%),[[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]]v3.1 does not change the high level information model, it remains as it is in Figure 6.133 +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 132 ---- 133 133 137 + 134 134 {{putFootnotes/}}
- 1749563229253-391.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -xwiki:XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -9.8 KB - Content
- 1749563243362-354.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -xwiki:XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -2.2 KB - Content