Difference between revisions of "Constraint"
Jump to navigation
Jump to search
(→Structure Properties) |
|||
| Line 28: | Line 28: | ||
[[File:SDMX3 Constraint.png|Constraint|600px]] | [[File:SDMX3 Constraint.png|Constraint|600px]] | ||
| + | |||
| + | ==Usage== | ||
| + | <p>Constraints (DSDs) are used to ???????: | ||
| + | |||
| + | |||
| + | |||
| + | <p>Each [[Dataflow|Dataflow]] references a single DSD which describes the structure of the dataset that the Dataflow represents.</p> | ||
Revision as of 02:20, 30 August 2022
Contents
Data Constraint or Metadata Constraint Overview
A SDMX Data or Metadata Constraint provides the ability to further restrict the allowable content of a Codelist in the context of a Data or Metadata Structure Definition, a Data or Metadata flow, a Provision or Metadata Agreement, or Data or Matadata Provider. Collectively these are termed as Constrainable Structures.
Structure Properties
| Structure Type | Standard SDMX Structural Metadata Artefact |
|---|---|
| Maintainable | Yes |
| Identifiable | Yes |
| Item Scheme | No |
| SDMX Information Model Versions | 3.0 |
| URN - DataConstraint namespace | urn:sdmx:org.sdmx.infomodel.datastructure.DataConstraint |
Context within the SDMX 3.0 Information Model
Usage
Constraints (DSDs) are used to ???????:
Each Dataflow references a single DSD which describes the structure of the dataset that the Dataflow represents.
