Difference between revisions of "Dataflow V10"
Jump to navigation
Jump to search
(→Usage) |
(→Usage) |
||
| Line 31: | Line 31: | ||
==Usage== | ==Usage== | ||
| − | In conjunction with a [[Provision_Agreement|Provision Agreement]], data can be loaded and validated against the concepts and rules and restrictions of as defined in it's Data Structure. | + | In conjunction with a [[Provision_Agreement|Provision Agreement]], data can be loaded and validated against the concepts and rules and restrictions of as defined in it's [[Data_Structure|Data Structure]]. |
==Conventions== | ==Conventions== | ||
Revision as of 09:45, 9 February 2021
Contents
Overview
A Dataflow defines a data 'topic' for collection or dissemination. A Dataflow must be linked to a Data Structure.
Structure Properties
| Structure Type | Standard SDMX Structural Metadata Artefact |
|---|---|
| Maintainable | Yes |
| Identifiable | Yes |
| Item Scheme | No |
| SDMX Information Model Versions | 2.0, 2.1 |
| URN - datastructure.Dataflow namespace | urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow. |
Context within the SDMX 2.1 Information Model
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 for more information on Data Structures.
Usage
In conjunction with a Provision Agreement, data can be loaded and validated against the concepts and rules and restrictions of as defined in it's Data Structure.
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 |
You can seem more examples and information on Identities in this article.
