Changes for page 13 Data Provisioning
Last modified by Helena K. on 2026/06/09 11:08
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 2 added, 1 removed)
-
Objects (0 modified, 1 added, 1 removed)
Details
- Page properties
-
- Tags
-
... ... @@ -1,0 +1,1 @@ 1 +Artefact|Categorisation|Constraint|Data Provider|Data Set|Data Source|Metadata Set|Metadata repository|Provision Agreement|Reference metadata|SDMX Information Model|SDMX Registry|Statistical Data and Metadata eXchange - Content
-
... ... @@ -4,6 +4,8 @@ 4 4 5 5 == 13.1 Class Diagram == 6 6 7 +[[image:image70.png]] 8 + 7 7 **Figure 44: Relationship and inheritance class diagram of data/metadata provisioning** 8 8 9 9 == 13.2 Explanation of the Diagram == ... ... @@ -16,10 +16,8 @@ 16 16 17 17 A ProvisionAgreement / MetadataProvisionAgreement links the artefact that defines how data / metadata are structured and classified (//StructureUsage//) to the DataProvider / MetadataProvider. By means of a data registration, it references the //Datasource// (data only), whether this be an SDMX conformant file on a website (SimpleDatasource) or a database service capable of supporting an SDMX query and responding with an SDMX conformant document (//QueryDatasource//). 18 18 19 -The //StructureUsage//, which has concrete classes of Dataflow and Metadataflow identifies the corresponding DataStructureDefinition or 21 +The //StructureUsage//, which has concrete classes of Dataflow and Metadataflow identifies the corresponding DataStructureDefinition or MetadataStructureDefinition, and, via Categorisation, can link to one or more Category(s) in a CategoryScheme such as a subject matter domain scheme, by which the //StructureUsage// can be classified. This can assist in drilling down from subject matter domains to find the data or metadata that may be relevant. 20 20 21 -MetadataStructureDefinition, and, via Categorisation, can link to one or more Category(s) in a CategoryScheme such as a subject matter domain scheme, by which the //StructureUsage// can be classified. This can assist in drilling down from subject matter domains to find the data or metadata that may be relevant. 22 - 23 23 The SimpleDatasource links to the actual DataSet on a website (this is shown on the diagram as a dependency called “references”). The sourceURL is obtained during the registration process of the DataSet. Additional information about the content of the SimpleDatasource is stored in the registry in terms of a //Constraint// (see 12.3) for the Registration. 24 24 25 25 The //QueryDatasource// is an abstract class that represents a data source, which can understand an SDMX RESTful query (RESTDatasource) and respond appropriately. Each of these different //Datasource//s inherit the dataURL from //Datasource//, and the //QueryDatasource// has an additional URL, the specURL, to locate the specification of the service (i.e., the open API specification for RESTDatasource), which describes how to access it. All other supported protocols are assumed to use the SimpleDatasource URL. ... ... @@ -26,7 +26,7 @@ 26 26 27 27 The diagram below shows in schematic way the essential navigation through the SDMX structural artefacts that eventually link to a data or metadata registration{{footnote}}Provider Scheme, Provider, Provision Agreement and Registered source refer both to data and reference metadata.{{/footnote}}. 28 28 29 -[[image: 1749246752523-973.jpeg]]29 +[[image:image71.png]] 30 30 31 31 **Figure 45: Schematic of the linking of structural metadata to data and metadata registration** 32 32 ... ... @@ -71,5 +71,4 @@ 71 71 72 72 ---- 73 73 74 - 75 75 {{putFootnotes/}}
- 1749246752523-973.jpeg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -xwiki:XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -24.6 KB - Content
- image70.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +132.4 KB - Content
- image71.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +62.5 KB - Content
- SUZ.Methodology.Code.MethodologyClass[0]
-
- index
-
... ... @@ -1,1 +1,0 @@ 1 -14
- SKMS.Methodology.Code.MethodologyClass[0]
-
- Index
-
... ... @@ -1,0 +1,1 @@ 1 +14