Skip to Content

Changes for page 13 Data Provisioning

Last modified by Artur on 2025/09/10 11:19
From version 4.1
edited by Helena
on 2025/05/15 09:59
Change comment: There is no comment for this version
To version 4.2
edited by Helena
on 2025/05/15 11:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,6 @@
1 -= 13 Data Provisioning =
1 +{{box title="**Contents**"}}
2 +{{toc/}}
3 +{{/box}}
2 2  
3 3  == 13.1 Class Diagram ==
4 4  
... ... @@ -22,7 +22,7 @@
22 22  
23 23  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.
24 24  
25 -The diagram below shows in schematic way the essential navigation through the SDMX structural artefacts that eventually link to a data or metadata registration^^[[^^4^^>>path:#sdfootnote4sym||name="sdfootnote4anc"]]^^.
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^^[[(% class="wikiinternallink wikiinternallink" %)^^4^^>>path:#sdfootnote4sym||name="sdfootnote4anc"]](%%)^^.
26 26  
27 27  [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_39d2fe45.jpg||height="360" width="592"]]
28 28  
... ... @@ -40,24 +40,24 @@
40 40  
41 41  Metadataflow
42 42  )))|This is described in the Base.
43 -||controlledBy//    //|Association to the Provision Agreements that comprise the metadata related to the provision of data.
44 -|DataProvider||See Organisation Scheme.
45 -||hasAgreement|Association to the Provision Agreements for which the provider supplies data or metadata.
46 -||+source|Association to a data source, which can process a data query.
47 -|MetadataProvider||See Organisation Scheme.
48 -||hasAgreement|Association to the Metadata Provision Agreements for which the provider supplies data or metadata.
49 -||+source|Association to a metadata source, which can process a metadata query.
50 -|ProvisionAgreement||Links the Data Provider to the relevant Structure Usage (i.e., the Dataflow) for which the provider supplies data. The agreement may constrain the scope of the data that can be provided, by means of a DataConstraint.
51 -||+source|Association to a data source, which can process a data query.
52 -|MetadataProvisionAgr eement||Links the Metadata Provider to the relevant Structure Usage (i.e., the Metadataflow) for which the provider supplies metadata. The agreement may constrain the scope of the metadata that can be provided, by means of a MetadataConstraint.
53 -||+source|Association to reference metadata source, which can process a metadata query.
45 +| |controlledBy//    //|Association to the Provision Agreements that comprise the metadata related to the provision of data.
46 +|DataProvider| |See Organisation Scheme.
47 +| |hasAgreement|Association to the Provision Agreements for which the provider supplies data or metadata.
48 +| |+source|Association to a data source, which can process a data query.
49 +|MetadataProvider| |See Organisation Scheme.
50 +| |hasAgreement|Association to the Metadata Provision Agreements for which the provider supplies data or metadata.
51 +| |+source|Association to a metadata source, which can process a metadata query.
52 +|ProvisionAgreement| |Links the Data Provider to the relevant Structure Usage (i.e., the Dataflow) for which the provider supplies data. The agreement may constrain the scope of the data that can be provided, by means of a DataConstraint.
53 +| |+source|Association to a data source, which can process a data query.
54 +|MetadataProvisionAgr eement| |Links the Metadata Provider to the relevant Structure Usage (i.e., the Metadataflow) for which the provider supplies metadata. The agreement may constrain the scope of the metadata that can be provided, by means of a MetadataConstraint.
55 +| |+source|Association to reference metadata source, which can process a metadata query.
54 54  |//Datasource//|(((
55 55  Abstract class
56 56  
57 57  Sub classes are: SimpleDatasource //QueryDatasource//
58 58  )))|Identification of the location or service from where data or reference metadata can be obtained.
59 -||+sourceURL//    //|The URL of the data or reference metadata source (a file or a web service).
60 -|SimpleDatasource||An SDMX dataset / metadataset accessible as a file at a URL.
61 +| |+sourceURL//    //|The URL of the data or reference metadata source (a file or a web service).
62 +|SimpleDatasource| |An SDMX dataset / metadataset accessible as a file at a URL.
61 61  |//QueryDatasource//|(((
62 62  Abstract class Inherits from:
63 63  
... ... @@ -67,8 +67,6 @@
67 67  
68 68  RESTDatasource
69 69  )))|A data or reference metadata source, which can process a data or metadata query.
70 -|RESTDatasource||A data or reference metadata source that is accessible via a RESTful web services interface.
71 -||+specificationURL|Association to the URL for the specification of the web service.
72 -|Registration||This is not detailed here but is shown as the link between the SDMX-IM and the Registry Service API. It denotes a data or metadata registration document.
73 -
74 -
72 +|RESTDatasource| |A data or reference metadata source that is accessible via a RESTful web services interface.
73 +| |+specificationURL|Association to the URL for the specification of the web service.
74 +|Registration| |This is not detailed here but is shown as the link between the SDMX-IM and the Registry Service API. It denotes a data or metadata registration document.