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

Summary

Details

Page properties
Content
... ... @@ -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  
1111 +
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**
1121 +==== 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.
1151 +==== Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts ====
1156 1156  
1153 +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.
1154 +
1155 +
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 ==
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