Changes for page 13 Data Provisioning
Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,8 +1,14 @@ 1 +{{box title="**Contents**"}} 2 +{{toc/}} 3 +{{/box}} 4 + 5 +== 13.1 Class Diagram == 6 + 1 1 **Figure 44: Relationship and inheritance class diagram of data/metadata provisioning** 2 2 3 -== =13.2 Explanation of the Diagram ===9 +== 13.2 Explanation of the Diagram == 4 4 5 -=== =13.2.1 Narrative ====11 +=== 13.2.1 Narrative === 6 6 7 7 This sub model links many artefacts in the SDMX-IM and is pivotal to an SDMX metadata registry, as all of the artefacts in this sub model must be accessible to an application that is responsible for data and metadata registration or for an application that requires access to the data or metadata. 8 8 ... ... @@ -18,61 +18,52 @@ 18 18 19 19 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. 20 20 21 -The diagram below shows in schematic way the essential navigation through the SDMX structural artefacts that eventually link to a data or metadata registration [[^^~[1~]^^>>path:#_ftn1]].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}}. 22 22 23 23 [[image:1749246752523-973.jpeg]] 24 24 25 25 **Figure 45: Schematic of the linking of structural metadata to data and metadata registration** 26 26 27 -=== =13.2.2 Definitions ====33 +=== 13.2.2 Definitions === 28 28 29 -|**Class**|**Feature**|**Description** 30 -|//StructureUsage//|((( 35 +(% style="width:971.835px" %) 36 +|**Class**|(% style="width:185px" %)**Feature**|(% style="width:569px" %)**Description** 37 +|//StructureUsage//|(% style="width:185px" %)((( 31 31 Abstract class: 32 - 33 33 Sub classes are: 34 - 35 - Dataflow 36 - 40 +Dataflow 37 37 Metadataflow 38 -)))|This is described in the Base. 39 -| |controlledBy|Association to the Provision Agreements that comprise the metadata related to the provision of data. 40 -|DataProvider| |See Organisation Scheme. 41 -| |hasAgreement|Association to the Provision Agreements for which the provider supplies data or metadata. 42 -| |+source|Association to a data source, which can process a data query. 43 -|MetadataProvider| |See Organisation Scheme. 44 -| |hasAgreement|Association to the Metadata Provision Agreements for which the provider supplies data or metadata. 45 -| |+source|Association to a metadata source, which can process a metadata query. 46 -|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. 47 -| |+source|Association to a data source, which can process a data query. 48 -|MetadataProvisionAgr 49 -| |+source|Association to reference metadata source, which can process a metadata query. 50 -|//Datasource//|((( 42 +)))|(% style="width:569px" %)This is described in the Base. 43 +| |(% style="width:185px" %)controlledBy|(% style="width:569px" %)Association to the Provision Agreements that comprise the metadata related to the provision of data. 44 +|DataProvider|(% style="width:185px" %) |(% style="width:569px" %)See Organisation Scheme. 45 +| |(% style="width:185px" %)hasAgreement|(% style="width:569px" %)Association to the Provision Agreements for which the provider supplies data or metadata. 46 +| |(% style="width:185px" %)+source|(% style="width:569px" %)Association to a data source, which can process a data query. 47 +|MetadataProvider|(% style="width:185px" %) |(% style="width:569px" %)See Organisation Scheme. 48 +| |(% style="width:185px" %)hasAgreement|(% style="width:569px" %)Association to the Metadata Provision Agreements for which the provider supplies data or metadata. 49 +| |(% style="width:185px" %)+source|(% style="width:569px" %)Association to a metadata source, which can process a metadata query. 50 +|ProvisionAgreement|(% style="width:185px" %) |(% style="width:569px" %)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 +| |(% style="width:185px" %)+source|(% style="width:569px" %)Association to a data source, which can process a data query. 52 +|MetadataProvisionAgreement|(% style="width:185px" %) |(% style="width:569px" %)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 +| |(% style="width:185px" %)+source|(% style="width:569px" %)Association to reference metadata source, which can process a metadata query. 54 +|//Datasource//|(% style="width:185px" %)((( 51 51 Abstract class 52 - 53 - Sub classes are: 54 - 56 +Sub classes are: 55 55 SimpleDatasource 56 - 57 57 //QueryDatasource// 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 accessible as a file at a URL. 61 -|//QueryDatasource//|((( 59 +)))|(% style="width:569px" %)Identification of the location or service from where data or reference metadata can be obtained. 60 +| |(% style="width:185px" %)+sourceURL|(% style="width:569px" %)The URL of the data or reference metadata source (a file or a web service). 61 +|SimpleDatasource|(% style="width:185px" %) |(% style="width:569px" %)An SDMX dataset accessible as a file at a URL. 62 +|//QueryDatasource//|(% style="width:185px" %)((( 62 62 Abstract class Inherits from: 63 - 64 - //Datasource// 65 - 64 +//Datasource// 66 66 Sub classes are: 66 +RESTDatasource 67 +)))|(% style="width:569px" %)A data source, which can process a data query. 68 +|RESTDatasource|(% style="width:185px" %) |(% style="width:569px" %)A data source that is accessible via a RESTful web services interface. 69 +| |(% style="width:185px" %)+specificationURL|(% style="width:569px" %)Association to the URL for the specification of the web service. 70 +|Registration|(% style="width:185px" %) |(% style="width:569px" %)This is not detailed here but is shown as the link between the SDMX-IM and the Registry Service API. It denotes a data registration document. 67 67 68 - RESTDatasource 69 -)))|A data source, which can process a data query. 70 -|RESTDatasource| |A data 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 registration document. 73 - 74 - 75 - 76 76 ---- 77 77 78 -[[~[1~]>>path:#_ftnref1]] Provider Scheme, Provider, Provision Agreement and Registered source refer both to data and reference metadata. 74 + 75 +{{putFootnotes/}}
- SUZ.Methodology.Code.MethodologyClass[0]
-
- index
-
... ... @@ -1,0 +1,1 @@ 1 +14