Content Constraint - Revision history

Vmurrell: /* Conventions */

2024-03-28T10:28:30Z

‎Conventions

Vmurrell: /* Structure Properties */

2024-03-28T10:26:36Z

‎Structure Properties

Vmurrell at 10:25, 28 March 2024

2024-03-28T10:25:52Z

Vmurrell at 09:38, 19 July 2023

2023-07-19T09:38:14Z

Vmurrell: /* Context within the SDMX 2.1 Information Model */

2021-05-05T10:32:06Z

‎Context within the SDMX 2.1 Information Model

Glenn: /* Defining Content Constraints */

2021-03-17T17:22:09Z

‎Defining Content Constraints

Vmurrell at 09:59, 9 March 2021

2021-03-09T09:59:59Z

Vmurrell: /* Structure Properties */

2021-02-20T16:50:46Z

‎Structure Properties

Vmurrell: /* Structure Properties */

2021-02-20T16:48:52Z

‎Structure Properties

Vmurrell: /* Context within the SDMX 2.1 Information Model */

2021-02-12T12:43:21Z

‎Context within the SDMX 2.1 Information Model

@@ Line 76: / Line 76: @@
 | WB || GHA || GHA || [	https://demo.metadatatechnology.com/FusionRegistry/ws/public/sdmxapi/rest/contentconstraint/WB/GHA/1.0 SDMX-ML]
 |}
-[[URN|You can seem more examples and information on Identities in this article]].
+[[URN_V10|You can seem more examples and information on Identities in this article]].

@@ Line 9: / Line 9: @@
 |-
 ! scope=row style="text-align: left;"  | Maintainable
-| [[Maintainable|Yes]]
+| [[Maintainable_V10|Yes]]
 |-
 ! scope=row style="text-align: left;"  | Identifiable
-| [[Identifiable|Yes]]
+| [[Identifiable_V10|Yes]]
 |-
 ! 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

← Older revision		Revision as of 10:25, 28 March 2024
Line 1:		Line 1:
		+	__NOTOC__
	[[Category:SDMX 2.1 Structures]]		[[Category:SDMX 2.1 Structures]]
	=Overview=		=Overview=

@@ Line 1: / Line 1: @@
-[[Category:SDMX Structures]]
+[[Category:SDMX 2.1 Structures]]
 =Overview=
 Content Constraints define restrictions on Codelists or Series for Data Reporting.

@@ Line 26: / Line 26: @@
 ==Context within the SDMX 2.1 Information Model==
-[[File:L_ContentConstraint1.png|900px]]<br>
+[[File:L_ContentConstraint1.png|Content Constraints|900px]]<br>
 The schematic illustrates the core artefacts of the SDMX 2.1 Information Model, and how Content Constraints fit in.

@@ Line 57: / Line 57: @@
 '''Series''' allows a list of series keys to be included with a wildcard facility available on dimensions.
-'''Cube''' allows the definition of data 'cubes' to either include or exclude and the resulting constraint is the intersection of the various cubes. A cube is defined by specifying a value or list of values for each dimension.
+'''Cube Region''' allows the definition of data 'cubes' to either include or exclude and the resulting constraint is the intersection of the various cubes. A cube is defined by specifying a value or list of values for each dimension.
 You can read more about creating constraints using the GUI [[Content_Constraints|in this article]].

@@ Line 34: / Line 34: @@
 Constraints can be applied to DSD, Dataflow, Provision Agreement or Data Provider in order to restrict the data being validated or converted. This is to allow organisations flexibility whether to apply constraints and at what level.
-Note that regardless of the artiefact to which the Constraint is associated, it is constraining the contents of code lists in the DSD to which the constrained object is related.
+Note that regardless of the artefact to which the Constraint is associated, it is constraining the contents of code lists in the DSD to which the constrained object is related.
 The Constraint can be of one of two types:<br>
@@ Line 45: / Line 45: @@
 Allowable content constraints can also be used to control how Reference Metadata is reported.
-These type of constraints are created and maintained as physical artefacts in the Registry under the Reporting Constraints menu.
+These types of constraints are created and maintained as physical artefacts in the Registry under the Reporting Constraints menu.
 ===Actual===
-Actual defines what data actually exists in a data source. This helps with data discovery in that it gives a data consumer information on the scope of data available before querying.  The [https://fmrwiki.sdmxcloud.org/Data_Availability_Web_ServiceData Availability API] returns ‘actual’ constraints explaining what codes are available for each dimension. <br>
+Actual defines what data exists in a data source. This helps with data discovery in that it gives a data consumer information on the scope of data available before querying.  The [https://fmrwiki.sdmxcloud.org/Data_Availability_Web_ServiceData Availability API] returns ‘actual’ constraints explaining what codes are available for each dimension. <br>
-These type of constraints are created when the Availability query is performed and as such are not stored as physical artefacts in the Registry and are not visibly in the GUI.
+These types of constraints are created when the Availability query is performed and as such are not stored as physical artefacts in the Registry and are not visibly in the GUI.
 ==Defining Content Constraints==

@@ Line 17: / Line 17: @@
 |-
 ! scope=row style="text-align: left;"  | SDMX Information Model Versions
-| 1.0, 2.0, 2.1
+| 2.0, 2.1
 |-
 ! scope=row style="text-align: left;"  | URN - ContentConstraint namespace

@@ Line 19: / Line 19: @@
 | 1.0, 2.0, 2.1
 |-
-! scope=row style="text-align: left;"  | URN - ConceptScheme namespace
+! scope=row style="text-align: left;"  | URN - ContentConstraint namespace
-| <nowiki>urn:sdmx:org.sdmx.infomodel.conceptscheme.ConceptScheme</nowiki>
+| <nowiki>urn:sdmx:org.sdmx.infomodel.contentconstraint</nowiki>
 |-
 |}

@@ Line 30: / Line 30: @@
 [[File:L_ContentConstraint1.png|900px]]<br>
-The schematic illustrates the core artifacts of the SDMX 2.1 Information Model, and how Content Constraints fit in.
+The schematic illustrates the core artefacts of the SDMX 2.1 Information Model, and how Content Constraints fit in.
 ==Usage==