Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 2.11
edited by Helena
on 2025/05/21 15:04
Change comment: There is no comment for this version
To version 2.14
edited by Helena
on 2025/05/21 15:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1077,6 +1077,8 @@
1077 1077  
1078 1078  ==== 7.1.3.3 Structure Usage Model ====
1079 1079  
1080 +[[image:1747829078194-749.png]]
1081 +
1080 1080  **Figure 10: SDMX-IM of links from Structure Usage to Category**
1081 1081  
1082 1082  In addition to the maintenance of the Dataflow Definition and the Metadataflow Definition the following links must be maintained in the registry:
... ... @@ -1103,10 +1103,10 @@
1103 1103  
1104 1104  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.
1105 1105  
1108 +[[image:1747829109466-595.png]]
1106 1106  
1107 1107  **Figure 11: SDMX-IM of the Data Provider**
1108 1108  
1109 -
1110 1110  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
1111 1111  
1112 1112  [[image:1747824123019-181.jpeg]]
... ... @@ -1115,8 +1115,10 @@
1115 1115  
1116 1116  The diagram below is a logical representation of the data required in order to maintain Provision Agreements.
1117 1117  
1120 +[[image:1747829139951-378.png]]
1118 1118  
1119 -==== Figure 13: Logical class diagram of the information contained in the Provision Agreement ====
1122 +(% class="wikigeneratedid" id="HFigure13:LogicalclassdiagramoftheinformationcontainedintheProvisionAgreement" %)
1123 +**Figure 13: Logical class diagram of the information contained in the Provision Agreement**
1120 1120  
1121 1121  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.
1122 1122  
... ... @@ -1144,13 +1144,12 @@
1144 1144  
1145 1145  === 7.3.3 Data and Metadata Constraints: Model ===
1146 1146  
1151 +[[image:1747829204737-370.png]]
1147 1147  
1153 +**Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts**
1148 1148  
1149 -==== Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts ====
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.
1150 1150  
1151 -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.
1152 -
1153 -
1154 1154  The content of the Constraint can be found in the SDMX Information Model document.
1155 1155  
1156 1156  == 7.4 Data and Metadata Registration ==
... ... @@ -1185,10 +1185,11 @@
1185 1185  
1186 1186  The Registration has an action attribute which takes one of the following values:
1187 1187  
1188 -|**Action Attribute Value**|**Behaviour**
1189 -|Append|Add this Registration to the registry
1190 -|Replace|Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
1191 -|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
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
1192 1192  
1193 1193  **Figure 17: Logical Class Diagram of Registration of Data and Metadata**
1194 1194  
1747829078194-749.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +40.4 KB
Content
1747829109466-595.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +30.4 KB
Content
1747829139951-378.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +21.1 KB
Content
1747829204737-370.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +55.8 KB
Content