Difference between revisions of "Dataflow V10"

From FMR Knowledge Base
Jump to navigation Jump to search
(Usage)
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Category:SDMX Structures]]
+
[[Category:SDMX 2.1 Structures]]
 
=Overview=
 
=Overview=
 
A Dataflow represents a Data Set.
 
A Dataflow represents a Data Set.
  
While a Data Structure Definition defines Dimensions, Attributes, Measures and associated representation that comprise the valid structure of data and related metadata of Data Sets of a particular class, a Dataflow is a specific Data Set instance.
+
While a [[Data Structure Definition V10|Data Structure Definition]] defines Dimensions, Attributes, Measures and associated representation that comprise the valid structure of data and related metadata of Data Sets of a particular class, a Dataflow is a specific Data Set instance.
  
This decoupling of Data Structure Definitions from Dataflows makes them reusable. A Data Structure Definition for health data may be used by many different organisations and countries, each using it to create their own Dataflows. The European Central Bank (ECB) have a Balance Sheet Items DSD which is referenced by three Dataflows: Balance Sheet Items; Balance Sheet Items Statistics (tables 2 to 5 of the Blue Book), Key euro area indicators (BSI).
+
This decoupling of Data Structure Definitions from Dataflows makes them reusable. A Data Structure Definition for health data may be used by many different organisations and countries to create Dataflows for their own local health Data Sets. The European Central Bank (ECB) have a Balance Sheet Items DSD which is referenced by three Dataflows: Balance Sheet Items; Balance Sheet Items Statistics (tables 2 to 5 of the Blue Book), Key euro area indicators (BSI).
  
 
Data is disseminated against a Dataflow and must conform to the template defined by the DSD that the Dataflow references.
 
Data is disseminated against a Dataflow and must conform to the template defined by the DSD that the Dataflow references.
Line 17: Line 17:
 
|-
 
|-
 
! scope=row style="text-align: left;"  | Maintainable
 
! scope=row style="text-align: left;"  | Maintainable
| [[Maintainable|Yes]]
+
| [[Maintainable_V10|Yes]]
 
|-
 
|-
 
! scope=row style="text-align: left;"  | Identifiable
 
! scope=row style="text-align: left;"  | Identifiable
| [[Identifiable|Yes]]
+
| [[Identifiable V10|Yes]]
 
|-
 
|-
 
! scope=row style="text-align: left;"  | Item Scheme
 
! scope=row style="text-align: left;"  | Item Scheme
| [[Item_Scheme|No]]
+
| [[Item_Scheme_V10|No]]
 
|-
 
|-
 
! scope=row style="text-align: left;"  | SDMX Information Model Versions  
 
! scope=row style="text-align: left;"  | SDMX Information Model Versions  
| 2.0, 2.1
+
| 1.0, 2.0, 2.1
 
|-
 
|-
 
! scope=row style="text-align: left;"  | URN - datastructure.Dataflow namespace
 
! scope=row style="text-align: left;"  | URN - datastructure.Dataflow namespace
Line 34: Line 34:
 
==Context within the SDMX 2.1 Information Model==
 
==Context within the SDMX 2.1 Information Model==
  
[[File:L_Dataflow1.png|900px]]<br>
+
[[File:L_Dataflow1.png|Dataflow|600px]]<br>
 
 
The schematic illustrates the core artifacts of the SDMX 2.1 Information Model, and how Dataflows fit in. A Dataflow requires a Data Structure, please refer to this article [https://fmrwiki.sdmxcloud.org/Data_Structure_Definition for more information on Data Structures.]
 
  
 
==Usage==
 
==Usage==
In conjunction with a [[Provision_Agreement|Provision Agreement]], data can be loaded and validated against the concepts and rules and restrictions  as defined in its [[Data_Structure_Definitions|Data Structure]]. A Dataflow may also have additional restrictions applied by virtue of any [[Content_Constraint|Content Constraints]].
+
In conjunction with a [[Data_Provision_Agreement|Provision Agreement]], data can be loaded and validated against the concepts and rules and restrictions  as defined in its [[Data_Structure_Definitions|Data Structure]]. A Dataflow may also have additional restrictions applied by virtue of any [[Content_Constraint|Content Constraints]].
  
 
==Conventions==
 
==Conventions==
Line 53: Line 51:
 
| IAEG-SDGs || DF_SDG_GLC || SDG Country Global Dataflow || [https://registry.sdmx.org/ws/public/sdmxapi/rest/dataflow/IAEG-SDGs/DF_SDG_GLC/1.3 SDMX-ML]
 
| IAEG-SDGs || DF_SDG_GLC || SDG Country Global Dataflow || [https://registry.sdmx.org/ws/public/sdmxapi/rest/dataflow/IAEG-SDGs/DF_SDG_GLC/1.3 SDMX-ML]
 
|}
 
|}
 
[[URN|You can seem more examples and information on Identities in this article]].
 

Latest revision as of 06:40, 28 March 2024

Overview

A Dataflow represents a Data Set.

While a Data Structure Definition defines Dimensions, Attributes, Measures and associated representation that comprise the valid structure of data and related metadata of Data Sets of a particular class, a Dataflow is a specific Data Set instance.

This decoupling of Data Structure Definitions from Dataflows makes them reusable. A Data Structure Definition for health data may be used by many different organisations and countries to create Dataflows for their own local health Data Sets. The European Central Bank (ECB) have a Balance Sheet Items DSD which is referenced by three Dataflows: Balance Sheet Items; Balance Sheet Items Statistics (tables 2 to 5 of the Blue Book), Key euro area indicators (BSI).

Data is disseminated against a Dataflow and must conform to the template defined by the DSD that the Dataflow references.

Data is also reported (indirectly) against a Dataflow, so it is possible to impose different restrictions on difference Dataflows using Constraints.

Structure Properties

Structure Type Standard SDMX Structural Metadata Artefact
Maintainable Yes
Identifiable Yes
Item Scheme No
SDMX Information Model Versions 1.0, 2.0, 2.1
URN - datastructure.Dataflow namespace urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow.

Context within the SDMX 2.1 Information Model

Dataflow

Usage

In conjunction with a Provision Agreement, data can be loaded and validated against the concepts and rules and restrictions as defined in its Data Structure. A Dataflow may also have additional restrictions applied by virtue of any Content Constraints.

Conventions

Dataflow IDs IDs are conventionally uppercase using underscores '_' as separators if required. Examples:

Agency Concept Scheme ID Description SDMX-ML
ESTAT NAREG_T1200_A NA Regional Statistics SDMX-ML
IAEG-SDGs DF_SDG_GLC SDG Country Global Dataflow SDMX-ML