Skip to Content
Last modified by Helena K. on 2026/06/08 17:06
From version 5.1
edited by Helena K.
on 2025/06/08 11:42
Change comment: There is no comment for this version
To version 21.2
edited by Helena K.
on 2026/06/08 17:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Tags
... ... @@ -1,0 +1,1 @@
1 +Attribute|Codelist|Constraint|Data Provider|Data Structure Definition|Hierarchy|Identifiable Artefact|Language|Maintenance agency|Metadata Set|Metadata Structure Definition|Metadata repository|Provision Agreement|Reference metadata|Reference period|SDMX Information Model|Statistical Data and Metadata eXchange|Structural metadata|Time period
Content
... ... @@ -4,30 +4,32 @@
4 4  
5 5  == 7.1 Context ==
6 6  
7 -Besides the possibility to extend the components of Data Structure Definitions by metadata attributes defined in Metadata Structure Definitions, the SDMX metamodel allows metadata to describe any identifiable artefact. These metadata can be:
7 +Besides the possibility to extend the [[components>>doc:IMElements.components.WebHome]] of Data Structure Definitions by [[metadata>>doc:IMElements.metadata.WebHome]] attributes defined in Metadata Structure Definitions, the SDMX metamodel allows [[metadata>>doc:IMElements.metadata.WebHome]] to describe any identifiable artefact. These [[metadata>>doc:IMElements.metadata.WebHome]] can be:
8 8  
9 9  1. Exchanged without the need to embed it within the object that it is describing.
10 -1. Stored separately from the object that it describes, yet be linked to it (for example, an organisation has a metadata repository which supports the dissemination of metadata resulting from metadata requests generated by systems or services that have access to the object for which the metadata pertains. This is common in web dissemination where additional metadata is available for viewing (and eventually downloading) by clicking on an “information” icon next to the object to which the metadata is attached).
10 +1. Stored separately from the object that it describes, yet be linked to it (for example, an organisation has a metadata repository which supports the dissemination of [[metadata>>doc:IMElements.metadata.WebHome]] resulting from [[metadata>>doc:IMElements.metadata.WebHome]] requests generated by systems or services that have access to the object for which the [[metadata>>doc:IMElements.metadata.WebHome]] pertains. This is common in web dissemination where additional [[metadata>>doc:IMElements.metadata.WebHome]] is available for viewing (and eventually downloading) by clicking on an “information” icon next to the object to which the [[metadata>>doc:IMElements.metadata.WebHome]] is attached).
11 11  1. Versioned and maintained like structural metadata, but from Metadata Providers than Agencies.
12 -1. Reported according to a defined structure.
12 +1. Reported according to a defined [[structure>>doc:IMElements.structure.WebHome]].
13 13  
14 14  In order to achieve this, the following structures are modelled:
15 15  
16 -* The Metadata Structure Definition which comprises the metadata attributes that can be attached to the various object types (these attributes can be structured in a hierarchy), together with any constraints that may apply (e.g., association to a code list that contains valid values for the attribute when reported in a metadata set),
17 -* The Metadataflow and/or Metadata Provision Agreement, which contains the objects to which the metadata are to be associated (attached),
18 -* The Metadata Set, which contains reported metadata.
16 +* The Metadata Structure Definition which comprises the [[metadata>>doc:IMElements.metadata.WebHome]] attributes that can be attached to the various object types (these attributes can be structured in a hierarchy), together with any constraints that may apply (e.g., association to a code list that contains valid values for the attribute when reported in a metadata set),
17 +* The [[Metadataflow>>doc:IMElements.AnnotableArtefact.IdentifiableArtefact.NameableArtefact.VersionableArtefact.MaintainableArtefact.StructureUsage.Metadataflow.WebHome]] and/or Metadata Provision Agreement, which contains the objects to which the [[metadata>>doc:IMElements.metadata.WebHome]] are to be associated (attached),
18 +* The Metadata Set, which contains reported [[metadata>>doc:IMElements.metadata.WebHome]].
19 19  
20 20  == 7.2 Inheritance ==
21 21  
22 22  === 7.2.1 Introduction ===
23 23  
24 -As with the Data Structure Definition Structure, many of the constructs in this layer of the model inherit from the SDMX Base layer. Therefore, it is necessary to study both the inheritance and the relationship diagrams to understand the functionality of individual packages. The diagram below shows the full inheritance tree for the classes concerned with the MetadataStructureDefinition, the MetadataProvisionAgreement, the Metadataflow and the MetadataSet.
24 +As with the Data Structure Definition [[Structure>>doc:IMElements.AnnotableArtefact.IdentifiableArtefact.NameableArtefact.VersionableArtefact.MaintainableArtefact.Structure.WebHome]], many of the constructs in this layer of the model inherit from the SDMX Base layer. Therefore, it is necessary to study both the inheritance and the relationship diagrams to understand the functionality of individual
25 25  
26 +packages. The diagram below shows the full inheritance tree for the classes concerned with the MetadataStructureDefinition, the MetadataProvisionAgreement, the Metadataflow and the MetadataSet.
27 +
26 26  There are very few additional classes in the MetadataStructureDefinition package that do not themselves inherit from classes in the SDMX Base. In other words, the SDMX Base gives most of the structure of this sub model both in terms of associations and in terms of attributes. The relationship diagrams shown in this section show clearly when these associations are inherited from the SDMX Base (see the Appendix “A Short Guide to UML in the SDMX Information Model” to see the diagrammatic notation used to depict this).
27 27  
28 28  === 7.2.2 Class Diagram - Inheritance ===
29 29  
30 -[[image:1749246462779-763.jpeg]]** **
32 +[[image:image58.png]]
31 31  
32 32  **Figure 32: Inheritance class diagram of the Metadata Structure Definition**
33 33  
... ... @@ -59,7 +59,7 @@
59 59  
60 60  === 7.3.3 Class Diagram – Relationship ===
61 61  
62 -[[image:1749246462786-944.jpeg]]
64 +[[image:image59.png]]
63 63  
64 64  **Figure 33: Relationship class diagram of the Metadata Structure Definition**
65 65  
... ... @@ -81,10 +81,8 @@
81 81  
82 82  The definition of the various types of Representation can be found in the specification of the Base constructs. Note that if the Representation is non-enumerated then the association is to the ExtendedFacet (which allows for XHTML as a FacetValueType). If the Representation is enumerated, then is must use a Codelist.
83 83  
84 -The Metadataflow is linked to a MetadataStructureDefinition. The Metadataflow, in addition to the attributes inherited from the Base classes, it also has a list of
86 +The Metadataflow is linked to a MetadataStructureDefinition. The Metadataflow, in addition to the attributes inherited from the Base classes, it also has a list of IdentifiableObjectSelection constructs, which resolve into the IdentifiableArtefacts that the Metadatasets will refer to. The IdentifiableObjectSelection acts like a reference, but it may also include wildcarding part of the reference terms.
85 85  
86 -IdentifiableObjectSelection constructs, which resolve into the IdentifiableArtefacts that the Metadatasets will refer to. The IdentifiableObjectSelection acts like a reference, but it may also include wildcarding part of the reference terms.
87 -
88 88  The MetadataProvisionAgreement is linked to a Metadataflow. The former, like the Metadataflow, may have IdentifiableObjectSelection constructs to be used for specifying the proper targets for reference metadata.
89 89  
90 90  ==== 7.3.4.2 Definitions ====
... ... @@ -124,7 +124,7 @@
124 124  
125 125  === 7.4.1 Class Diagram ===
126 126  
127 -[[image:1749246462791-735.jpeg]]
127 +[[image:image60.png]]
128 128  
129 129  **Figure 34: Relationship Class Diagram of the Metadata Set**
130 130  
... ... @@ -174,8 +174,8 @@
174 174  |//MetadataAttributeValue//|(((
175 175  Abstract class
176 176  Sub classes are:
177 -//UncodedMetadataAttrib uteValue//
178 -CodedMetadataAttribut eValue
177 +//UncodedMetadataAttributeValue//
178 +CodedMetadataAttributeValue
179 179  )))|(% style="width:515px" %)The value for a Metadata Attribute.
180 180  | |(((
181 181  +valueFor
... ... @@ -192,8 +192,7 @@
192 192  Sub class:
193 193  XHTMLAttributeValue
194 194  TextAttributeValue
195 -OtherUncodedAttribute
196 -Value
195 +OtherUncodedAttributeValue
197 197  )))|(% style="width:515px" %)The content of a Metadata Attribute value where this is textual.
198 198  |XHTMLAttributeValue| |(% style="width:515px" %)This contains XHTML
199 199  | |value|(% style="width:515px" %)The string value of the XHTML
1749246462779-763.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -42.2 KB
Content
1749246462786-944.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -35.1 KB
Content
1749246462791-735.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -60.0 KB
Content
image58.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +123.2 KB
Content
image59.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +65.8 KB
Content
image60.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +97.4 KB
Content
SUZ.Methodology.Code.MethodologyClass[0]
index
... ... @@ -1,1 +1,0 @@
1 -8
SKMS.Methodology.Code.MethodologyClass[0]
Index
... ... @@ -1,0 +1,1 @@
1 +8
© Semantic R&D Group, 2026