Skip to Content

Changes for page 1 Introduction

Last modified by Helena on 2025/09/10 11:19
From version 12.2
edited by Helena
on 2025/05/16 13:32
Change comment: There is no comment for this version
To version 11.1
edited by Helena
on 2025/05/15 10:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -23,8 +23,8 @@
23 23  
24 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:
25 25  
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.
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.//  //
28 28  
29 29  [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_bbb8fac9.png||height="54" width="158"]]
30 30  
... ... @@ -43,12 +43,12 @@
43 43  
44 44  The content in the “Feature” column comprises or explains one of the following structural features of the class:
45 45  
46 -* Whether it is an abstract class. Abstract classes are shown in //italic Courier// font.
46 +* Whether it is an abstract class. Abstract classes are shown in //italic Courier// font.//  //
47 47  * The superclass this class inherits from, if any.// //
48 48  * The sub classes of this class, if any.
49 49  * Attribute – the attributeName is shown in Courier font.
50 50  * Association – the associationName is shown in Courier font. If the association is derived from the association between super classes, then the format is /associationName.
51 -* Role – the +roleName is shown in Courier font.
51 +* Role – the +roleName is shown in Courier font.// //
52 52  
53 53  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.
54 54  
... ... @@ -60,11 +60,14 @@
60 60  
61 61  In addition to this, in order to aid understanding each package can be considered to be in one of three conceptual layers:
62 62  
63 -* the SDMX Base layer comprises fundamental building blocks which are used by the Structural Definitions layer and the Reporting and Dissemination layer
64 -* the Structural Definitions layer comprises the definition of the structural artefacts needed to support data and metadata reporting and dissemination
65 -* the Reporting and Dissemination layer comprises the definition of the data and metadata containers used for reporting and dissemination
66 -* In reality the layers have no implicit or explicit structural function as any package can make use of any construct in another package.
63 +the SDMX Base layer comprises fundamental building blocks which are used by the Structural Definitions layer and the Reporting and Dissemination layer
67 67  
65 +the Structural Definitions layer comprises the definition of the structural artefacts needed to support data and metadata reporting and dissemination
66 +
67 +the Reporting and Dissemination layer comprises the definition of the data and metadata containers used for reporting and dissemination
68 +
69 +In reality the layers have no implicit or explicit structural function as any package can make use of any construct in another package.
70 +
68 68  === 1.3.2 Version 1.0 ===
69 69  
70 70  In version 1.0 the metamodel supported the requirements for: