Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 2.15
edited by Helena
on 2025/05/21 15:08
Change comment: There is no comment for this version
To version 2.10
edited by Helena
on 2025/05/21 15:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1027,31 +1027,49 @@
1027 1027  Report Structure
1028 1028  Metadata Attribute
1029 1029  )))
1030 -|(% style="width:171px" %)Structure Usage|(% style="width:232px" %)Dataflow Definition|(% style="width:206px" %)
1031 -|(% style="width:171px" %) |(% style="width:232px" %)Metadataflow Definition|(% style="width:206px" %)
1032 -|(% style="width:171px" %)None|(% style="width:232px" %)Process|(% style="width:206px" %)Process Step
1033 -|(% style="width:171px" %)None|(% style="width:232px" %)Structure Set|(% style="width:206px" %)(((
1030 +|(% style="width:171px" %) |(% style="width:232px" %) |(% style="width:206px" %)
1031 +|(% style="width:171px" %) |(% style="width:232px" %) |(% style="width:206px" %)
1032 +
1033 +(% style="width:1644.71px" %)
1034 +|(% colspan="2" style="width:213px" %)Structure Usage|(% colspan="2" style="width:1193px" %)Dataflow Definition|(% colspan="2" style="width:234.418px" %)
1035 +|(% colspan="2" style="width:213px" %) |(% colspan="2" style="width:1193px" %)Metadataflow Definition|(% colspan="2" style="width:234.418px" %)
1036 +|(% colspan="2" style="width:213px" %)None|(% colspan="2" style="width:1193px" %)Process|(% colspan="2" style="width:234.418px" %)Process Step
1037 +|(% colspan="2" style="width:213px" %)None|(% colspan="2" style="width:1193px" %)Structure Set|(% colspan="2" style="width:234.418px" %)(((
1034 1034  Component Map
1039 +
1035 1035  Concept Scheme Map
1041 +
1036 1036  Codelist Map
1043 +
1037 1037  Category Scheme Map
1045 +
1038 1038  Reporting Taxonomy Map
1047 +
1039 1039  Organisation Scheme Map
1049 +
1040 1040  Concept Map
1051 +
1041 1041  Code Map
1053 +
1042 1042  Category Map
1055 +
1043 1043  Organisation Map
1057 +
1044 1044  Reporting Category Map
1059 +
1045 1045  Hybrid Codelist Map
1061 +
1046 1046  Hybrid Code Map
1047 1047  )))
1048 -|(% style="width:171px" %)None|(% style="width:232px" %)Provision Agreement|(% style="width:206px" %)
1049 -|(% style="width:171px" %)None|(% style="width:232px" %)Hierarchical Codelist|(% style="width:206px" %)(((
1064 +|(% colspan="2" style="width:213px" %)None|(% colspan="2" style="width:1193px" %)Provision Agreement|(% colspan="2" style="width:234.418px" %)
1065 +|(% colspan="2" style="width:213px" %)None|(% colspan="2" style="width:1193px" %)Hierarchical Codelist|(% colspan="2" style="width:234.418px" %)(((
1050 1050  Hierarchy
1067 +
1051 1051  Hierarchical Code
1052 1052  )))
1070 +|(% style="width:86px" %) |(% style="width:127px" %) |(% style="width:426px" %) |(% style="width:767.58px" %) | |(% style="width:1.41771px" %)
1053 1053  
1054 -**able 4: Table of Maintainable Artefacts for Structural Definition Metadata**
1072 +**Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
1055 1055  
1056 1056  === 7.1.2 Item Scheme, Structure ===
1057 1057  
... ... @@ -1058,7 +1058,10 @@
1058 1058  The artefacts included in the structural definitions are:
1059 1059  
1060 1060  * All types of Item Scheme (Codelist, Concept Scheme, Category Scheme, Organisation Scheme - Agency Scheme, Data Provider Scheme, Data Consumer Scheme, Organisation Unit Scheme)
1061 -* All types of Structure (Data Structure Definition, Metadata Structure Definition)
1079 +* All types of Structure (Data Structure Definition, Metadata Structure
1080 +
1081 +Definition)
1082 +
1062 1062  * All types of Structure Usage (Dataflow Definition, Metadataflow Definition)
1063 1063  
1064 1064  === 7.1.3 Structure Usage ===
... ... @@ -1077,8 +1077,6 @@
1077 1077  
1078 1078  ==== 7.1.3.3 Structure Usage Model ====
1079 1079  
1080 -[[image:1747829078194-749.png]]
1081 -
1082 1082  **Figure 10: SDMX-IM of links from Structure Usage to Category**
1083 1083  
1084 1084  In addition to the maintenance of the Dataflow Definition and the Metadataflow Definition the following links must be maintained in the registry:
... ... @@ -1105,10 +1105,10 @@
1105 1105  
1106 1106  An organisation which publishes statistical data or reference metadata and wishes to make it available to an SDMX enabled community is called a Data Provider. In terms of the SDMX Information Model, the Data Provider is maintained in a Data Provider Scheme.
1107 1107  
1108 -[[image:1747829109466-595.png]]
1109 1109  
1110 1110  **Figure 11: SDMX-IM of the Data Provider**
1111 1111  
1130 +
1112 1112  Note that the Data Provider does not inherit the hierarchy association. The diagram below shows a logical schematic of the data model classes required to maintain provision agreements
1113 1113  
1114 1114  [[image:1747824123019-181.jpeg]]
... ... @@ -1117,10 +1117,8 @@
1117 1117  
1118 1118  The diagram below is a logical representation of the data required in order to maintain Provision Agreements.
1119 1119  
1120 -[[image:1747829139951-378.png]]
1121 1121  
1122 -(% class="wikigeneratedid" id="HFigure13:LogicalclassdiagramoftheinformationcontainedintheProvisionAgreement" %)
1123 -**Figure 13: Logical class diagram of the information contained in the Provision Agreement**
1140 +==== Figure 13: Logical class diagram of the information contained in the Provision Agreement ====
1124 1124  
1125 1125  A Provision Agreement is structural metadata. Each Provision Agreement must reference a Data Provider and a Dataflow or Metadataflow Definition. The Data Provider and the Dataflow/Metadataflow Definition must exist already in order to set up a Provision Agreement.
1126 1126  
... ... @@ -1148,12 +1148,13 @@
1148 1148  
1149 1149  === 7.3.3 Data and Metadata Constraints: Model ===
1150 1150  
1151 -[[image:1747829204737-370.png]]
1152 1152  
1153 -**Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts**
1154 1154  
1155 -The class diagram above shows that DataProvider, DataflowDefinition, MetadataflowDefinition, ProvisionAgreement, DataStructureDefinition, MetadataStructureDefinition, SimpleDatasource and QueryDatasource are all concrete sub-classes of ConstrainableArtefact and can therefore have Constraints specified. Note that the actual Constraint as submitted is associated to the reference classes which inherit from ConstrainableRef: these are used to refer to the classes to which the Constraint applies.
1170 +==== Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts ====
1156 1156  
1172 +The class diagram above shows that DataProvider, DataflowDefinition, MetadataflowDefinition, ProvisionAgreement, DataStructureDefinition, MetadataStructureDefinition, SimpleDatasource and QueryDatasource are all concrete sub-classes of ConstrainableArtefact and can therefore have Constraints specified. Note that the actual Constraint as submitted is associated to the reference classes which inherit from ConstrainableRef: these are used to refer to the classes to which the Constraint applies.
1173 +
1174 +
1157 1157  The content of the Constraint can be found in the SDMX Information Model document.
1158 1158  
1159 1159  == 7.4 Data and Metadata Registration ==
... ... @@ -1188,14 +1188,11 @@
1188 1188  
1189 1189  The Registration has an action attribute which takes one of the following values:
1190 1190  
1191 -(% style="width:970.294px" %)
1192 -|(% style="width:212px" %)**Action Attribute Value**|(% style="width:756px" %)**Behaviour**
1193 -|(% style="width:212px" %)Append|(% style="width:756px" %)Add this Registration to the registry
1194 -|(% style="width:212px" %)Replace|(% style="width:756px" %)Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
1195 -|(% style="width:212px" %)Delete|(% style="width:756px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
1209 +|**Action Attribute Value**|**Behaviour**
1210 +|Append|Add this Registration to the registry
1211 +|Replace|Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
1212 +|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
1196 1196  
1197 -[[image:1747829290890-122.png]]
1198 -
1199 1199  **Figure 17: Logical Class Diagram of Registration of Data and Metadata**
1200 1200  
1201 1201  The Query Datasource is an abstract class that represents a data source which can understand an SDMX-ML query (SOAPDatasource) or RESTful query
1747829078194-749.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -40.4 KB
Content
1747829109466-595.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -30.4 KB
Content
1747829139951-378.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -21.1 KB
Content
1747829204737-370.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -55.8 KB
Content
1747829290890-122.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -41.4 KB
Content