Difference between revisions of "Constraint"

From FMR Knowledge Base
Jump to navigation Jump to search
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
__NOTOC__
 
[[Category:SDMX 3.0 Structures]]
 
[[Category:SDMX 3.0 Structures]]
 
=Data Constraint or Metadata Constraint Overview=
 
=Data Constraint or Metadata Constraint Overview=
<p>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.</p>
+
<p>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|Data or Metadata Structure Definition]] a [[Data_or_Metadataflow|Data or Metadataflow]], a [[Data_or_Metadata_Provision_Agreement|Provision or Metadata Provision Agreement]], or [[ Data_or_Metadata_Provider|Data or Matadata Provider]]. Collectively these are termed as Constrainable Structures.</p>
 +
 
 +
[[File:Data and Metadata Constraints.PNG|600px]]
  
 
==Structure Properties==
 
==Structure Properties==
Line 15: Line 18:
 
|-
 
|-
 
! scope=row style="text-align: left;"  | Item Scheme
 
! scope=row style="text-align: left;"  | Item Scheme
| [[Item_Scheme|No]]
+
| [[Item_Scheme V11|No]]
 
|-
 
|-
 
! scope=row style="text-align: left;"  | SDMX Information Model Versions  
 
! scope=row style="text-align: left;"  | SDMX Information Model Versions  
Line 30: Line 33:
  
 
==Usage==
 
==Usage==
<p>Constraints (DSDs) are used to ???????:
+
<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>
  
 +
==Conventions==
 +
'''Constraint IDs'''
 +
IDs are conventionally uppercase using underscores '_' as separators if required. Examples:
  
<p>Each [[Dataflow|Dataflow]] references a single DSD which describes the structure of the dataset that the Dataflow represents.</p>
+
{| class="wikitable"
 +
|-
 +
! Agency !! Concept Scheme ID !! Description !! SDMX-ML
 +
|-
 +
| ECB || EXR || Periodicity || [https://demo11.metadatatechnology.com/FusionRegistry/sdmx/v2/structure/dataconstraint/ECB/EXR/1.0 SDMX-ML]
 +
|}

Latest revision as of 03:24, 28 March 2024

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 Metadataflow, a Provision or Metadata Provision Agreement, or Data or Matadata Provider. Collectively these are termed as Constrainable Structures.

Data and Metadata Constraints.PNG

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

Constraint

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.

Conventions

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

Agency Concept Scheme ID Description SDMX-ML
ECB EXR Periodicity SDMX-ML