Difference between revisions of "Constraint"
Jump to navigation
Jump to search
(→Usage) |
(→Usage) |
||
Line 30: | Line 30: | ||
==Usage== | ==Usage== | ||
− | <p>Constraints | + | <p> Constraints can be used to specify a subset of the theoretical content of data set or metadata set which can be derived from the specification of the DSD or MSD. |
− | |||
− | |||
<p>Each [[Constraint|Constraint]] references a type of Structure and within that type many structures can be constrained.</p> | <p>Each [[Constraint|Constraint]] references a type of Structure and within that type many structures can be constrained.</p> | ||
[[File:Data and Metadata Constraints.PNG|600px]] | [[File:Data and Metadata Constraints.PNG|600px]] |
Revision as of 07:00, 31 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 can be used to specify a subset of the theoretical content of data set or metadata set which can be derived from the specification of the DSD or MSD.
Each Constraint references a type of Structure and within that type many structures can be constrained.