Wiki source code of 10 Constraints

Version 3.3 by Helena on 2025/06/16 12:33

version	line-number	content
1.1	1	{{box title="Contents"}}
	2	{{toc/}}
	3	{{/box}}
	4
1.2	5	== 10.1 Introduction ==
1.1	6
3.2	7	(% style="color:#e74c3c" %)Constraints(%%) are used as a way to restrict what data can be reported, or to report what data exists in a given context. There are three types of (% style="color:#e74c3c" %)Constraint(%%), which serve different purposes
1.1	8
3.2	9	* Availability (% style="color:#e74c3c" %)Constraint
	10	* [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)Constraint
	11	* Reporting (% style="color:#e74c3c" %)Constraints
1.1	12
3.2	13	An Availability (% style="color:#e74c3c" %)Constraint(%%) defines the data that exists in the context of a data query.
1.1	14
3.2	15	They form part of the response message from the Availability REST API. Availability (% style="color:#e74c3c" %)Constraints(%%) are dynamically generated by a system based on the data that exists and the query context. Availability (% style="color:#e74c3c" %)Constraints(%%) are therefore not Identifiable structures (they have no URN).
1.1	16
3.2	17	A [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)Constraint(%%) is a property of a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], they are used to fix the [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] that they use in the [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] which they use. [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)Constraints(%%) enable [[Data Structure Definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]] to evolve over time by having new [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] added, without having to undergo a major (% style="color:#e74c3c" %)version(%%) change.
1.1	18
3.2	19	A Reporting (% style="color:#e74c3c" %)Constraint(%%) is used to define the set of allowed and/or disallowed values that can be reported in a data or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]].
1.1	20
1.2	21	== 10.2 Availability Constraint ==
1.1	22
3.2	23	An Availability (% style="color:#e74c3c" %)Constraint(%%) is not a maintained structure, instead it is generated dynamically as a response to the availability REST API. The purpose of the Availability (% style="color:#e74c3c" %)Constraint(%%) is to define the distinct set of values that have data over 1 or more [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]]. Unlike a Data and Metadata (% style="color:#e74c3c" %)Constraint(%%), which can attach to multiple Constrainable structures (of the same type), an Availability (% style="color:#e74c3c" %)Constraint(%%) can only attach to only one structure. The attachment defines the context of the response (data exists for [[components>>doc:sdmx:Glossary.Component.WebHome]] in the context of). The subset of Constrainable structures the Availability (% style="color:#e74c3c" %)Constraint(%%) can attach to are:
1.1	24
3.2	25	* [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]
	26	* [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]
	27	* [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]
1.1	28
1.2	29	== 10.3 Dimension Constraint ==
	30
3.2	31	A [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)Constraint(%%) is a property of a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]; its purpose is to explicitly list the [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] from the corresponding [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] that are being used by the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]].
1.1	32
3.2	33	[[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)Constraints(%%) were introduced in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 3.1 and are not required for most [[Dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] where the [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] must always contain the full complement of [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] as defined by the corresponding [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]]. However, for some complex data collections, which may span long periods and where the full complement of required [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] are not necessarily known at design time, the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] is subject to increasing its Dimensionality over time. In this scenario it is possible to define the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] as an evolving structure, this property tells the user that the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] can have new [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] added without having to undergo a major (% style="color:#e74c3c" %)version(%%) change; a [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] at (% style="color:#e74c3c" %)version(%%) 1.0.0 for example would be able to add a new [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] and move to (% style="color:#e74c3c" %)version(%%) 1.1.0; a change that would not ordinarily be allowed. A minor (% style="color:#e74c3c" %)version(%%) change on the addition of a new [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is only possible if the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] defines itself as an evolving structure. This is a new property of the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] introduced in (% style="color:#e74c3c" %)version(%%) 3.1 to satisfy this use case. The evolving structure property is either true or false, defaulting to false if not specified. Setting the evolving structure property to true requires a major (% style="color:#e74c3c" %)version(%%) change, and therefore can only be introduced on an x.0.0 release (e.g. 1.0.0). The evolving structure property can be set to false to indicate that there will be no additional [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] added to the Data Structure under the same major (% style="color:#e74c3c" %)version(%%) number; setting the evolving structure property to false does not require require a major (% style="color:#e74c3c" %)version(%%) change on the Data Structure.
1.1	34
3.2	35	When a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] references a [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]], late binding on the minor release, and the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] has the evolving structure property set to true, then the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] must contain a [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)Constraint(%%) to protect its Dimensionality from changing over time without a (% style="color:#e74c3c" %)version(%%) change.
1.1	36
3.2	37	The [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)Constraint(%%) provides the explicit list of [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] that the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] uses from the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] that it references. This enables the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] to evolve over time without breaking the compatibility of [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] against the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]].
1.1	38
3.3	39	__Rules for a Dimension Constraint__
1.1	40
3.2	41	* A [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] must contain a [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)Constraint(%%) if the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] which it uses states that it is an evolving structure and the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] is late binding on the minor release (latest minor release of a given major (% style="color:#e74c3c" %)version(%%), e.g. 1.0+.0)
	42	* The [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)Constraint(%%) can only include [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] from the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] that is referenced by the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]].
	43	* A [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)Constraint(%%) can only be changed if the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] undergoes a major (% style="color:#e74c3c" %)version(%%) change
	44	* [[Datasets>>doc:sdmx:Glossary.Data set.WebHome]] reported against the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] must only contain reported values for the [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] specified in the [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)Constraint(%%).
	45	* When exporting data for the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], the [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] should only include the [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] specified by the [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)Constraint(%%).
	46	* When exporting data for the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] the [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] must contain the full set of [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] as specified by the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]]. The tilde ‘’ character is used to represent a value which is not present due to the [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] not being included in the corresponding [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]].
1.1	47
3.3	48	__Example Datasets with Evolving Structures__
1.1	49
3.2	50	A [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] is built against a [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]. The [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] contains data for two [[Dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]]. [[Dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] ‘DF_POP’ uses a [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)Constraint(%%) which fixes its [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] to FREQ and REF_AREA. [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] ‘DF_POP_SA’ does not reference a [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)Constraint(%%), and as such includes all [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] as specified by the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]].
1.1	51
3.2	52	The resulting [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] contains values ‘’ for both the [[SEX>>doc:sdmx:Glossary.Sex.WebHome]] and [[AGE>>doc:sdmx:Glossary.Age.WebHome]] [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] for the series related to DF_POP.
1.1	53
1.2	54	(% style="width:758.294px" %)
3.2	55	\|(% style="width:119px" %)[[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]\|(% colspan="7" style="width:635px" %)FREQ REF_AREA [[SEX>>doc:sdmx:Glossary.Sex.WebHome]] [[AGE>>doc:sdmx:Glossary.Age.WebHome]] OBS_VALUE TIME_PERIOD UNIT
	56	\|(% style="width:119px" %)DF_POP\|(% style="width:55px" %)A\|(% style="width:103px" %)UK\|(% style="width:79px" %) \|(% style="width:92px" %) \|(% style="width:93px" %)65\|(% style="width:111px" %)2022\|(% style="width:101px" %)6
	57	\|(% style="width:119px" %)DF_POP\|(% style="width:55px" %)A\|(% style="width:103px" %)FR\|(% style="width:79px" %) \|(% style="width:92px" %) \|(% style="width:93px" %)50\|(% style="width:111px" %)2022\|(% style="width:101px" %)6
1.2	58	\|(% style="width:119px" %)DF_POP_SA\|(% style="width:55px" %)A\|(% style="width:103px" %)UK\|(% style="width:79px" %)M\|(% style="width:92px" %)1\|(% style="width:93px" %)1.2\|(% style="width:111px" %)2022\|(% style="width:101px" %)6
1.1	59
1.3	60	== 10.4 Reporting Constraints ==
1.1	61
3.2	62	A Reporting (% style="color:#e74c3c" %)Constraint(%%) is a [[Maintainable Artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]] which restricts the values that can be reported in a [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]] based on one or more inclusion or exclusion rules.
1.1	63
3.2	64	A reporting (% style="color:#e74c3c" %)constraint(%%) is one of the following concrete types:
1.1	65
3.2	66	* Data (% style="color:#e74c3c" %)Constraint
	67	* Metadata (% style="color:#e74c3c" %)Constraint
1.1	68
1.3	69	=== 10.4.1 Data Constraint ===
1.2	70
3.2	71	A Data (% style="color:#e74c3c" %)Constraint(%%) is used to add additional restrictions to the allowable values reported in a [[dataset>>doc:sdmx:Glossary.Data set.WebHome]]. Data (% style="color:#e74c3c" %)Constraints(%%) can be applied to the follow structures which are collectively known as Constrainable structures:
1.1	72
3.2	73	* [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]
	74	* [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]
	75	* [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]
1.1	76	* Data Provider
	77
3.2	78	Note regardless of the Constrainable structure, the restricted values relate to the allowable content for the [[Component>>doc:sdmx:Glossary.Component.WebHome]] of the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] to which the constrained object relates.
1.1	79
1.3	80	=== 10.4.2 Metadata Constraint ===
1.1	81
3.2	82	A Metadata (% style="color:#e74c3c" %)Constraint(%%) is used to add additional restrictions to the allowable values reported in a metadataset. Metadata (% style="color:#e74c3c" %)Constraints(%%) can be applied to the follow structures which are collectively known as Constrainable structures:
1.1	83
	84	* Metadata Structure Definition
3.2	85	* [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]]
	86	* Metadata [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]
1.1	87	* Metadata Provider
	88
3.2	89	Note regardless of the Constrainable structure, the restricted values relate to the allowable content for the [[Component>>doc:sdmx:Glossary.Component.WebHome]] of the [[MSD>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] to which the constrained object relates.
1.1	90
1.3	91	=== 10.4.3 Scope of a Constraint ===
1.1	92
3.2	93	A (% style="color:#e74c3c" %)Constraint(%%) is used specify the content of a data or metadata source in terms of the [[component>>doc:sdmx:Glossary.Component.WebHome]] values or the keys.
1.1	94
3.2	95	In terms of data the [[components>>doc:sdmx:Glossary.Component.WebHome]] are:
1.1	96
3.2	97	* [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]
	98	* Time [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]
	99	* Data [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]
	100	* [[Measure>>doc:sdmx:Glossary.Measure.WebHome]]
	101	* Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]
	102	* DataKeySets: the keys are the content of the KeyDescriptor – i.e., the [[series keys>>doc:sdmx:Glossary.Series key.WebHome]] composed, for each key, by a value for each [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]].
1.1	103
3.2	104	In terms of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] the [[components>>doc:sdmx:Glossary.Component.WebHome]] are:
1.1	105
3.2	106	* Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]
1.1	107
3.2	108	For a (% style="color:#e74c3c" %)Constraint(%%) based on a [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] the (% style="color:#e74c3c" %)Constraint(%%) can reference one or more of:
1.1	109
3.2	110	* [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]
	111	* [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]
	112	* [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]
1.1	113	* Data Provider
	114
3.2	115	For a (% style="color:#e74c3c" %)Constraint(%%) based on an [[MSD>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] the (% style="color:#e74c3c" %)Constraint(%%) can reference one or more of:
1.1	116
	117	* Metadata Structure Definition
3.2	118	* [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]]
	119	* Metadata [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]
1.1	120	* Metadata Provider
3.2	121	* [[Metadata Set>>doc:sdmx:Glossary.Metadata set.WebHome]]
1.1	122
3.2	123	Furthermore, there can be more than one (% style="color:#e74c3c" %)Constraint(%%) specified for a specific object e.g., more than one (% style="color:#e74c3c" %)Constraint(%%) for a specific [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]].
1.1	124
3.2	125	In view of the flexibility of (% style="color:#e74c3c" %)constraints(%%) attachment, clear rules on their usage are required. These are elaborated below.
1.1	126
1.3	127	=== 10.4.4 Multiple Constraints ===
1.1	128
3.2	129	There can be many (% style="color:#e74c3c" %)Constraints(%%) for any Constrainable [[Artefact>>doc:sdmx:Glossary.Artefact.WebHome]] (e.g., [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]]), subject to the following restrictions:
1.1	130
1.3	131	==== 10.4.4.1 Cube Region ====
1.1	132
3.2	133	A (% style="color:#e74c3c" %)Constraint(%%) can contain multiple [[Member Selections>>doc:sdmx:Glossary.Member selection.WebHome]] (e.g., [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]]).
1.1	134
3.2	135	* A specific [[Member Selection>>doc:sdmx:Glossary.Member selection.WebHome]] (e.g., [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] FREQ) can only be contained in one Cube Region for any one attached object (e.g., a specific [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] or specific [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]).
	136	* [[Component>>doc:sdmx:Glossary.Component.WebHome]] values within a [[Member Selection>>doc:sdmx:Glossary.Member selection.WebHome]] may define a validity period. Otherwise, the value is valid for the whole validity of the Cube Region.
	137	* For partial reference resolution purposes (as per the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] REST API), the latest non-draft (% style="color:#e74c3c" %)Constraint(%%) must be considered.
	138	* A [[Member Selection>>doc:sdmx:Glossary.Member selection.WebHome]] may include wildcarding of values (using character ‘%’ to represent zero or more occurrences of any character), as well as cascading through hierarchic structures (e.g., parents in Codelist), or localised values (e.g., text for English only). Lack of locale means any language may match. Cascading values are mutual exclusive to localised values, as the former refer to coded values, while the latter refer to uncoded values.
	139	* Any values included in a [[Member Selection>>doc:sdmx:Glossary.Member selection.WebHome]] for [[Components>>doc:sdmx:Glossary.Component.WebHome]] with an array data type (i.e., [[Measures>>doc:sdmx:Glossary.Measure.WebHome]], [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]] or Metadata [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]]), will be applied as single values and will not be assessed combined with other values to match all possible array values. For example, including the [[Code>>doc:sdmx:Glossary.Code.WebHome]] ‘A’ for an [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] will allow any instance of the [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] that includes ‘A’, like [‘A’, ‘B’] or [‘A’, ‘C’, ‘D’]. Similarly, if [[Code>>doc:sdmx:Glossary.Code.WebHome]] ‘A’ was excluded, all those arrays of values would also be excluded.
1.1	140
1.2	141	==== 10.4.4.2 Key Set ====
1.1	142
3.2	143	Key Sets will be processed in the order they appear in the (% style="color:#e74c3c" %)Constraint(%%) and wildcards can be used (e.g., any key position not reference explicitly is deemed to be "all values").
1.1	144
3.2	145	As the Key Sets can be "included" or "excluded" it is recommended that Key Sets with wildcards are declared before KeySets with specific [[series keys>>doc:sdmx:Glossary.Series key.WebHome]]. This will minimize the risk that keys are inadvertently included or excluded.
1.1	146
3.2	147	In addition, [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]], [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] and Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] (% style="color:#e74c3c" %)constraints(%%) may accompany KeySets, in order to specify the allowed values per Key. Those are expressed following the rules for Cube Regions, as explained above.
1.1	148
	149	Finally, a validity period may be specified per Key.
	150
1.2	151	=== 10.4.4 Versioning ===
1.1	152
3.2	153	When Data and Metadata (% style="color:#e74c3c" %)Constraints(%%) are versioned, the latest (% style="color:#e74c3c" %)version(%%) of the (% style="color:#e74c3c" %)Constraint(%%) is used to generate the reporting restriction rules; all previous (% style="color:#e74c3c" %)versions(%%) are for historical information only.
1.1	154
3.2	155	If restrictions are applicable to certain periods in time, the validFrom and validTo properties can be set on the specific values. This allows (% style="color:#e74c3c" %)Constraints(%%) to evolve over time, increasing their (% style="color:#e74c3c" %)version(%%) number as they do so, whilst being able to maintain a complete set of reporting restrictions for current and past [[datasets>>doc:sdmx:Glossary.Data set.WebHome]].
1.1	156
	157	Example:
	158
3.2	159	Data (% style="color:#e74c3c" %)Constraint(%%) 1.0.0
1.1	160
1.4	161	(% style="width:573.294px" %)
3.2	162	\|(% style="width:108px" %)[[Component>>doc:sdmx:Glossary.Component.WebHome]]\|(% style="width:127px" %)Valid Value\|(% style="width:150px" %)Valid from\|(% style="width:185px" %)Valid to
1.4	163	\|(% rowspan="3" style="width:108px" %)COUNTRY\|(% style="width:127px" %)UK\|(% style="width:150px" %) \|(% style="width:185px" %)
	164	\|(% style="width:127px" %)FR\|(% style="width:150px" %) \|(% style="width:185px" %)
	165	\|(% style="width:127px" %)DE\|(% style="width:150px" %) \|(% style="width:185px" %)
1.1	166
3.2	167	Data (% style="color:#e74c3c" %)Constraint(%%) 1.1.0
1.1	168
1.4	169	(% style="width:576.294px" %)
3.2	170	\|(% style="width:110px" %)[[Component>>doc:sdmx:Glossary.Component.WebHome]]\|(% style="width:129px" %)Valid Value\|(% style="width:145px" %)Valid from\|(% style="width:189px" %)Valid to
1.4	171	\|(% rowspan="3" style="width:110px" %)COUNTRY\|(% style="width:129px" %)UK\|(% style="width:145px" %) \|(% style="width:189px" %)
	172	\|(% style="width:129px" %)FR\|(% style="width:145px" %) \|(% style="width:189px" %)2012
	173	\|(% style="width:129px" %)DE\|(% style="width:145px" %) \|(% style="width:189px" %)
1.1	174
3.2	175	When both (% style="color:#e74c3c" %)versions(%%) of the Data (% style="color:#e74c3c" %)Constraint(%%) are in a system, an [[observation value>>doc:sdmx:Glossary.Observation value.WebHome]] reported against COUNTRY FR for [[time period>>doc:sdmx:Glossary.Time period.WebHome]] 2013 would be deemed invalid as the 1.1.0 rule would be applied.
1.1	176
1.2	177	=== 10.4.6 Inheritance ===
1.1	178
1.2	179	==== 10.4.6.1 Attachment levels of a Constraint ====
1.1	180
3.2	181	There are three (% style="color:#e74c3c" %)levels(%%) of (% style="color:#e74c3c" %)constraint(%%) attachment for which these inheritance rules apply:
1.1	182
3.2	183	* [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]]/[[MSD>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] – top (% style="color:#e74c3c" %)level
	184	** [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]/[[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] – second (% style="color:#e74c3c" %)level
	185	*** [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] – third (% style="color:#e74c3c" %)level
1.1	186
3.2	187	It is not necessary for a (% style="color:#e74c3c" %)Constraint(%%) to be attached to a higher (% style="color:#e74c3c" %)level(%%) [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]]. e.g., it is valid to have a (% style="color:#e74c3c" %)Constraint(%%) for a [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] where there are no (% style="color:#e74c3c" %)constraints(%%) attached the relevant [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] or [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]].
1.1	188
1.2	189	==== 10.4.6.2 Cascade rules for processing Constraints ====
1.1	190
3.2	191	The processing of the (% style="color:#e74c3c" %)constraints(%%) on either [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]/[[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] or [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] must take into account the (% style="color:#e74c3c" %)constraints(%%) declared at higher (% style="color:#e74c3c" %)levels(%%). The rules for the lower-(% style="color:#e74c3c" %)level(%%) (% style="color:#e74c3c" %)constraints(%%) (attached to [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]/ [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] and [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]) are detailed below.
1.1	192
3.2	193	Note that there can be a situation where a (% style="color:#e74c3c" %)constraint(%%) is specified at a lower (% style="color:#e74c3c" %)level(%%) before a (% style="color:#e74c3c" %)constraint(%%) is specified at a higher (% style="color:#e74c3c" %)level(%%). Therefore, it is possible that a higher-(% style="color:#e74c3c" %)level(%%) (% style="color:#e74c3c" %)constraint(%%) makes a lower-(% style="color:#e74c3c" %)level(%%) (% style="color:#e74c3c" %)constraint(%%) invalid. [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] makes no rules on how such a conflict should be handled when processing the (% style="color:#e74c3c" %)constraint(%%) for attachment. However, the cascade rules on evaluating (% style="color:#e74c3c" %)constraints(%%) for usage are clear – the higher-(% style="color:#e74c3c" %)level(%%) (% style="color:#e74c3c" %)constraint(%%) takes precedence in any conflicts that result in a less restrictive specification at the lower (% style="color:#e74c3c" %)level(%%).
1.1	194
1.2	195	==== 10.4.6.3 Cube Region ====
1.1	196
3.2	197	It is not necessary to have a (% style="color:#e74c3c" %)Constraint(%%) on the higher-(% style="color:#e74c3c" %)level(%%) [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] (e.g., [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] referenced by the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]), but if there is such a (% style="color:#e74c3c" %)Constraint(%%) at the higher (% style="color:#e74c3c" %)level(%%)(s) then:
1.1	198
3.2	199	* The lower-(% style="color:#e74c3c" %)level(%%) (% style="color:#e74c3c" %)Constraint(%%) cannot be less restrictive than the (% style="color:#e74c3c" %)Constraint(%%) specified for the same [[Member Selection>>doc:sdmx:Glossary.Member selection.WebHome]] (e.g. [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]) at the next higher (% style="color:#e74c3c" %)level(%%), which constrains that [[Member Selection>>doc:sdmx:Glossary.Member selection.WebHome]]. For example, if the [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] FREQ is constrained to A, Q in a [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]], then the (% style="color:#e74c3c" %)Constraint(%%) at the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] or [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] cannot be A, Q, M or even just M – it can only further constrain A, Q.
	200	* The (% style="color:#e74c3c" %)Constraint(%%) at the lower (% style="color:#e74c3c" %)level(%%) for any one [[Member Selection>>doc:sdmx:Glossary.Member selection.WebHome]] further constrains the content for the same [[Member Selection>>doc:sdmx:Glossary.Member selection.WebHome]] at the higher (% style="color:#e74c3c" %)level(%%)(s).
	201	* Any [[Member Selection>>doc:sdmx:Glossary.Member selection.WebHome]], which is not referenced in a (% style="color:#e74c3c" %)Constraint(%%), is deemed to be constrained according to the (% style="color:#e74c3c" %)Constraint(%%) specified at the next higher (% style="color:#e74c3c" %)level(%%) which (% style="color:#e74c3c" %)constraints(%%) that [[Member Selection>>doc:sdmx:Glossary.Member selection.WebHome]].
	202	* If there is a conflict when resolving the (% style="color:#e74c3c" %)Constraint(%%) in terms of a lower-(% style="color:#e74c3c" %)level(%%) (% style="color:#e74c3c" %)Constraint(%%) being less restrictive than a higher-(% style="color:#e74c3c" %)level(%%) (% style="color:#e74c3c" %)Constraint(%%), then the (% style="color:#e74c3c" %)Constraint(%%) at the higher-(% style="color:#e74c3c" %)level(%%) is used.
1.1	203
3.2	204	Note that it is possible for a (% style="color:#e74c3c" %)Constraint(%%) at a higher (% style="color:#e74c3c" %)level(%%) to constrain, say, four [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] in a single (% style="color:#e74c3c" %)Constraint(%%), and a (% style="color:#e74c3c" %)Constraint(%%) at a lower (% style="color:#e74c3c" %)level(%%) to constrain the same four in two, three, or four (% style="color:#e74c3c" %)Constraints(%%).
1.1	205
1.2	206	==== 10.4.6.4 Key Set ====
1.1	207
3.2	208	It is not necessary to have a (% style="color:#e74c3c" %)Constraint(%%) on the higher-(% style="color:#e74c3c" %)level(%%) [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] (e.g., [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] referenced by the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]), but if there is such a (% style="color:#e74c3c" %)Constraint(%%) at the higher (% style="color:#e74c3c" %)level(%%)(s) then:
1.1	209
3.2	210	* The lower-(% style="color:#e74c3c" %)level(%%) (% style="color:#e74c3c" %)Constraint(%%) cannot be less restrictive than the (% style="color:#e74c3c" %)Constraint(%%) specified at the higher (% style="color:#e74c3c" %)level(%%).
	211	* The (% style="color:#e74c3c" %)Constraint(%%) at the lower (% style="color:#e74c3c" %)level(%%) for any one [[Member Selection>>doc:sdmx:Glossary.Member selection.WebHome]] further constrains the keys specified at the higher (% style="color:#e74c3c" %)level(%%)(s).
	212	* Any [[Member Selection>>doc:sdmx:Glossary.Member selection.WebHome]], which is not referenced in a (% style="color:#e74c3c" %)Constraint(%%), is deemed to be constrained according to the (% style="color:#e74c3c" %)Constraint(%%) specified at the next higher (% style="color:#e74c3c" %)level(%%) which (% style="color:#e74c3c" %)constraints(%%) that [[Member Selection>>doc:sdmx:Glossary.Member selection.WebHome]].
	213	* If there is a conflict when resolving the keys in the (% style="color:#e74c3c" %)Constraint(%%) at two (% style="color:#e74c3c" %)levels(%%), in terms of a lower-(% style="color:#e74c3c" %)level(%%) (% style="color:#e74c3c" %)constraint(%%) being less restrictive than a higher-(% style="color:#e74c3c" %)level(%%) (% style="color:#e74c3c" %)Constraint(%%), then the offending keys specified at the lower (% style="color:#e74c3c" %)level(%%) are not deemed part of the (% style="color:#e74c3c" %)Constraint(%%).
1.1	214
3.2	215	Note that a Key in a Key Set can have wildcarded [[Components>>doc:sdmx:Glossary.Component.WebHome]]. For instance, the (% style="color:#e74c3c" %)Constraint(%%) may simply constrain the [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] FREQ to "A", and all keys where the FREQ="A" are therefore valid.
1.1	216
	217	The following logic explains how the inheritance mechanism works. Note that this is conceptual logic and actual systems may differ in the way this is implemented.
	218
3.2	219	1. Determine all possible keys that are valid at the higher (% style="color:#e74c3c" %)level(%%).
	220	1. These keys are deemed to be inherited by the lower-(% style="color:#e74c3c" %)level(%%) constrained object, subject to the (% style="color:#e74c3c" %)Constraints(%%) specified at the lower (% style="color:#e74c3c" %)level(%%).
	221	1. Determine all possible keys that are possible using the (% style="color:#e74c3c" %)Constraints(%%) specified at the lower (% style="color:#e74c3c" %)level(%%).
	222	1. At the lower (% style="color:#e74c3c" %)level(%%) inherit all keys that match with the higher-(% style="color:#e74c3c" %)level(%%) (% style="color:#e74c3c" %)Constraint(%%).
	223	1. If there are keys in the lower-(% style="color:#e74c3c" %)level(%%) (% style="color:#e74c3c" %)Constraint(%%) that are not inherited then the key is invalid (i.e., it is less restrictive).
1.1	224
1.5	225	=== 10.4.7 Constraints Examples ===
	226
1.2	227	==== 10.4.7.1 Data Constraint and Cascading ====
1.1	228
1.2	229	The following scenario is used.
	230
3.2	231	A [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] contains the following [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]]:
1.1	232
	233	* GEO – Geography
3.2	234	* [[SEX>>doc:sdmx:Glossary.Sex.WebHome]] – [[Sex>>doc:sdmx:Glossary.Sex.WebHome]]
	235	* [[AGE>>doc:sdmx:Glossary.Age.WebHome]] – [[Age>>doc:sdmx:Glossary.Age.WebHome]]
1.1	236	* CAS – Current Activity Status
	237
3.2	238	In the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]], common [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] are used and the requirement is to restrict these at various (% style="color:#e74c3c" %)levels(%%) to specify the actual [[code>>doc:sdmx:Glossary.Code.WebHome]] that are valid for the object to which the (% style="color:#e74c3c" %)Constraint(%%) is attached.
1.1	239
1.6	240	[[image:1750065279010-260.png]]
1.1	241
3.3	242	Figure 20: Example Scenario for Constraints
1.1	243
3.3	244	Constraints are declared as follows:
	245
1.6	246	[[image:1750065319060-899.png]]
1.1	247
3.3	248	Figure 21: Example Constraints
1.1	249
	250	Notes:
	251
3.2	252	[[AGE>>doc:sdmx:Glossary.Age.WebHome]] is constrained for the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] and is further restricted for the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] CENSUS_CUBE1.
1.1	253
3.2	254	* The same (% style="color:#e74c3c" %)Constraint(%%) applies to both Provision Agreements.
1.1	255
	256	The cascade rules elaborated above result as follows:
	257
3.2	258	[[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]]
1.1	259
3.2	260	* Constrained by eliminating [[code>>doc:sdmx:Glossary.Code.WebHome]] 001 from the [[code list>>doc:sdmx:Glossary.Code list.WebHome]] for the [[AGE>>doc:sdmx:Glossary.Age.WebHome]] [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]].
1.1	261
3.2	262	[[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] CENSUS_CUBE1
1.1	263
3.2	264	* Constrained by restricting the [[code list>>doc:sdmx:Glossary.Code list.WebHome]] for the [[AGE>>doc:sdmx:Glossary.Age.WebHome]] [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] to [[codes>>doc:sdmx:Glossary.Code.WebHome]] 002 and 003 (note that this is a more restrictive (% style="color:#e74c3c" %)constraint(%%) than that declared for the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] which specifies all [[codes>>doc:sdmx:Glossary.Code.WebHome]] except [[code>>doc:sdmx:Glossary.Code.WebHome]] 001).
	265	** Restricts the CAS [[codes>>doc:sdmx:Glossary.Code.WebHome]] to 003 and 004.
1.1	266
3.2	267	[[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] CENSUS_CUBE2
1.1	268
3.2	269	* Restricts the [[code list>>doc:sdmx:Glossary.Code list.WebHome]] for the CAS [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] to [[codes>>doc:sdmx:Glossary.Code.WebHome]] TOT and NAP.
	270	** Inherits the [[AGE>>doc:sdmx:Glossary.Age.WebHome]] (% style="color:#e74c3c" %)constraint(%%) applied at the (% style="color:#e74c3c" %)level(%%) of the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]].
1.1	271
3.2	272	[[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] CENSUS_CUBE1_IT
1.1	273
3.2	274	* Restricts the [[codes>>doc:sdmx:Glossary.Code.WebHome]] for the GEO [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] to IT and its children.
	275	** Inherits the (% style="color:#e74c3c" %)constraints(%%) from [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] CENSUS_CUBE1 for the [[AGE>>doc:sdmx:Glossary.Age.WebHome]] and CAS [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]].
1.1	276
3.2	277	[[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] CENSUS_CUBE2_IT
1.1	278
3.2	279	* Restricts the [[codes>>doc:sdmx:Glossary.Code.WebHome]] for the GEO [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] to IT and its children.
	280	** Inherits the (% style="color:#e74c3c" %)constraints(%%) from [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] CENSUS_CUBE2 for the CAS [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]].
	281	** Inherits the [[AGE>>doc:sdmx:Glossary.Age.WebHome]] (% style="color:#e74c3c" %)constraint(%%) applied at the (% style="color:#e74c3c" %)level(%%) of the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]].
1.1	282
3.2	283	The (% style="color:#e74c3c" %)Constraints(%%) are defined as follows:
1.1	284
3.3	285	DSD Constraint
1.1	286
1.8	287	[[image:1750065367824-357.png]]
1.7	288
3.3	289	Dataflow Constraints
1.1	290
1.8	291	[[image:1750065392163-400.png]]
1.7	292
3.3	293	Provision Agreement Constraint
1.1	294
1.8	295	[[image:1750065461589-995.png]]
1.7	296
3.3	297	10.4.7.2 Combination of Constraints
1.1	298
	299	The possible combination of constraining terms are explained in this section, following a few examples.
	300
3.2	301	Let’s assume a [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] with the following [[Components>>doc:sdmx:Glossary.Component.WebHome]]:
1.1	302
1.10	303	(% style="width:459.294px" %)
3.2	304	\|(% style="width:204px" %)(% style="color:#3498db" %)[[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]\|(% style="width:252px" %)(% style="color:#3498db" %)FREQ
	305	\|(% style="width:204px" %)(% style="color:#3498db" %)[[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]\|(% style="width:252px" %)(% style="color:#3498db" %)JD_TYPE
	306	\|(% style="width:204px" %)(% style="color:#3498db" %)[[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]\|(% style="width:252px" %)(% style="color:#3498db" %)JD_CATEGORY
	307	\|(% style="width:204px" %)(% style="color:#3498db" %)[[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]\|(% style="width:252px" %)(% style="color:#3498db" %)VIS_CTY
1.10	308	\|(% style="width:204px" %)(% style="color:#2980b9" %)TimeDimension\|(% style="width:252px" %)(% style="color:#2980b9" %)TIME_PERIOD
3.2	309	\|(% style="width:204px" %)(% style="color:#16a085" %)[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]\|(% style="width:252px" %)(% style="color:#16a085" %)OBS_STATUS
	310	\|(% style="width:204px" %)(% style="color:#16a085" %)[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]\|(% style="width:252px" %)(% style="color:#16a085" %)UNIT
	311	\|(% style="width:204px" %)(% style="color:#16a085" %)[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]\|(% style="width:252px" %)(% style="color:#16a085" %)[[COMMENT>>doc:sdmx:Glossary.Comment.WebHome]]
	312	\|(% style="width:204px" %)(% style="color:#f39c12" %)MetadataAttribute\|(% style="width:252px" %)(% style="color: rgb(243, 156, 18); color: rgb(231, 76, 60)" %)CONTACT
	313	\|(% style="width:204px" %)(% style="color:#e74c3c" %)[[Measure>>doc:sdmx:Glossary.Measure.WebHome]]\|(% style="width:252px" %)(% style="color:#e74c3c" %)MULTISELECT
	314	\|(% style="width:204px" %)(% style="color:#e74c3c" %)[[Measure>>doc:sdmx:Glossary.Measure.WebHome]]\|(% style="width:252px" %)(% style="color:#e74c3c" %)CHOICE
1.1	315
	316	On the above, let’s assume the following use cases with their constraining requirements:
	317
3.3	318	Use Case 1: A Constraint on allowed values for some Dimensions
1.1	319
	320	R1: Allow monthly and quarterly data
	321
	322	R2: Allow Mexico for vis-à-vis country
	323
	324	This is expressed with the following CubeRegion:
	325
1.11	326	(% style="width:287.294px" %)
	327	\|(% style="width:131px" %)(% style="color:#3498db" %)FREQ\|(% style="width:153px" %)(% style="color:#3498db" %)M, Q
	328	\|(% style="width:131px" %)(% style="color:#3498db" %)VIS_CTY\|(% style="width:153px" %)(% style="color:#3498db" %)MX
1.1	329
3.3	330	Use Case 2: A Constraint on allowed combinations for some Dimensions
1.1	331
	332	R1: Allow monthly data for Germany
	333
	334	R2: Allow quarterly data for Mexico
	335
	336	This is expressed with the following DataKeySet:
	337
1.12	338	(% style="width:388.294px" %)
	339	\|(% style="width:105px" %)(% style="color:#2980b9" %)Key1\|(% style="width:137px" %)(% style="color:#2980b9" %)FREQ\|(% style="width:143px" %)(% style="color:#2980b9" %)M
	340	\|(% style="width:105px" %) \|(% style="width:137px" %)(% style="color:#2980b9" %)VIS_CTY\|(% style="width:143px" %)(% style="color:#2980b9" %)DE
	341	\|(% rowspan="2" style="width:105px" %)(% style="color:#2980b9" %)Key2\|(% style="width:137px" %)(% style="color:#2980b9" %)FREQ\|(% style="width:143px" %)(% style="color:#2980b9" %)Q
	342	\|(% style="width:137px" %)(% style="color:#2980b9" %)VIS_CTY\|(% style="width:143px" %)(% style="color:#2980b9" %)MX
1.1	343
3.3	344	Use Case 3: A Constraint on allowed values for some Dimensions combined with allowed values for some Attributes R1: Allow monthly and quarterly data
1.1	345
	346	R2: Allow Mexico for vis-à-vis country
	347
	348	R3: Allow present for status
	349
	350	This may be expressed with the following CubeRegion:
	351
1.13	352	(% style="width:285.294px" %)
	353	\|(% style="width:143px" %)(% style="color:#2980b9" %)FREQ\|(% style="width:139px" %)(% style="color:#2980b9" %)M, Q
	354	\|(% style="width:143px" %)(% style="color:#2980b9" %)VIS_CTY\|(% style="width:139px" %)(% style="color:#2980b9" %)MX
	355	\|(% style="width:143px" %)(% style="color:#27ae60" %)OBS_STATUS\|(% style="width:139px" %)(% style="color:#27ae60" %)A
1.1	356
3.3	357	Use Case 4: A Constraint on allowed combinations for some Dimensions combined with specific Attribute values
1.1	358
	359	R1: Allow monthly data, for Germany, with unit euro
	360
	361	R2: Allow quarterly data, for Mexico, with unit usd
	362
	363	This may be expressed with the following DataKeySet:
	364
1.14	365	(% style="width:389.294px" %)
	366	\|(% rowspan="3" style="width:89px" %)(% style="color:#2980b9" %)Key1\|(% style="width:153px" %)(% style="color:#2980b9" %)FREQ\|(% style="width:142px" %)(% style="color:#2980b9" %)M
	367	\|(% style="width:153px" %)(% style="color:#2980b9" %)VIS_CTY\|(% style="width:142px" %)(% style="color:#2980b9" %)DE
	368	\|(% style="width:153px" %)(% style="color:#27ae60" %)UNIT\|(% style="width:142px" %)(% style="color:#27ae60" %)EUR
	369	\|(% rowspan="3" style="width:89px" %)(% style="color:#2980b9" %)Key2\|(% style="width:153px" %)(% style="color:#2980b9" %)FREQ\|(% style="width:142px" %)(% style="color:#2980b9" %)Q
	370	\|(% style="width:153px" %)(% style="color:#2980b9" %)VIS_CTY\|(% style="width:142px" %)(% style="color:#2980b9" %)MX
	371	\|(% style="width:153px" %)(% style="color:#27ae60" %)UNIT\|(% style="width:142px" %)(% style="color:#27ae60" %)USD
1.1	372
3.3	373	Use Case 5: A Constraint on allowed values for some Dimensions together with some combination of Dimension values
1.1	374
	375	R1: For annually and quarterly data, for Mexico and Germany, only A status is allowed
	376
	377	R2: For monthly data, for Mexico and Germany, only F status is allowed
	378
	379	Considering the above examples, the following CubeRegions would be created:
	380
1.15	381	(% style="width:449.294px" %)
	382	\|(% rowspan="3" style="width:126px" %)(% style="color:#2980b9" %)CubeRegion1\|(% style="width:137px" %)(% style="color:#2980b9" %)FREQ\|(% style="width:183px" %)(% style="color:#2980b9" %)Q, A
	383	\|(% style="width:137px" %)(% style="color:#2980b9" %)VIS_CTY\|(% style="width:183px" %)(% style="color:#2980b9" %)MX, DE
	384	\|(% style="width:137px" %)(% style="color:#27ae60" %)OBS_STATUS\|(% style="width:183px" %)(% style="color:#27ae60" %)A
	385	\|(% rowspan="3" style="width:126px" %)(% style="color:#2980b9" %)CubeRegion2\|(% style="width:137px" %)(% style="color:#2980b9" %)FREQ\|(% style="width:183px" %)(% style="color:#2980b9" %)M
	386	\|(% style="width:137px" %)(% style="color:#2980b9" %)VIS_CTY\|(% style="width:183px" %)(% style="color:#2980b9" %)MX, DE
	387	\|(% style="width:137px" %)(% style="color:#27ae60" %)OBS_STATUS\|(% style="width:183px" %)(% style="color:#27ae60" %)F
1.1	388
3.2	389	The problem with this approach is that according to the business rule for (% style="color:#e74c3c" %)Constraints(%%), only one should be specified per [[Component>>doc:sdmx:Glossary.Component.WebHome]]. Thus, if a software would perform some conflict resolution would end up with empty sets for FREQ and OBS_STATUS (as they do not share any values).
1.1	390
3.2	391	Nevertheless, there is a much easier approach to that; this is the cascading mechanism of (% style="color:#e74c3c" %)Constraints(%%) (as shown in 10.4.7.1). Hence, these rules would be expressed into two (% style="color:#e74c3c" %)levels(%%) of (% style="color:#e74c3c" %)Constraints(%%), e.g., [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] and [[Dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]]:
1.1	392
3.3	393	DSD CubeRegion:
1.1	394
1.15	395	(% style="width:280.294px" %)
1.16	396	\|(% style="width:156px" %)(% style="color:#2980b9" %)FREQ\|(% style="width:121px" %)(% style="color:#2980b9" %)M, Q, A
	397	\|(% style="width:156px" %)(% style="color:#2980b9" %)VIS_CTY\|(% style="width:121px" %)(% style="color:#2980b9" %)MX, DE
	398	\|(% style="width:156px" %)(% style="color:#27ae60" %)OBS_STATUS\|(% style="width:121px" %)(% style="color:#27ae60" %)A, F
1.1	399
	400	Dataflow1 CubeRegion:
	401
1.15	402	(% style="width:285.294px" %)
1.16	403	\|(% style="width:157px" %)(% style="color:#2980b9" %)FREQ\|(% style="width:125px" %)(% style="color:#2980b9" %)Q, A
	404	\|(% style="width:157px" %)(% style="color:#2980b9" %)VIS_CTY\|(% style="width:125px" %)(% style="color:#2980b9" %)MX, DE
	405	\|(% style="width:157px" %)(% style="color:#27ae60" %)OBS_STATUS\|(% style="width:125px" %)(% style="color:#27ae60" %)F
1.1	406
	407	Dataflow2 CubeRegion:
	408
1.15	409	(% style="width:288.294px" %)
1.16	410	\|(% style="width:159px" %)(% style="color:#2980b9" %)FREQ\|(% style="width:126px" %)(% style="color:#2980b9" %)M
	411	\|(% style="width:159px" %)(% style="color:#2980b9" %)VIS_CTY\|(% style="width:126px" %)(% style="color:#2980b9" %)MX, DE
	412	\|(% style="width:159px" %)(% style="color:#27ae60" %)OBS_STATUS\|(% style="width:126px" %)(% style="color:#27ae60" %)A
1.1	413
3.3	414	Use case 6: A Constraint on allowed values for some Dimensions combined with allowed values for Measures
1.1	415
3.2	416	R1: Allow monthly data, for Germany, with unit euro, and [[measure>>doc:sdmx:Glossary.Measure.WebHome]] choice is 'A' R2: Allow quarterly data, for Mexico, with unit usd, and [[measure>>doc:sdmx:Glossary.Measure.WebHome]] choice is 'B'
1.1	417
	418	This may be expressed with the following DataKeySet:
	419
1.17	420	(% style="width:404.294px" %)
	421	\|(% rowspan="4" style="width:99px" %)(% style="color:#2980b9" %)Key1\|(% style="width:153px" %)(% style="color:#2980b9" %)FREQ\|(% style="width:149px" %)(% style="color:#2980b9" %)M
	422	\|(% style="width:153px" %)(% style="color:#2980b9" %)VIS_CTY\|(% style="width:149px" %)(% style="color:#2980b9" %)DE
	423	\|(% style="width:153px" %)(% style="color:#27ae60" %)UNIT\|(% style="width:149px" %)(% style="color:#27ae60" %)EUR
	424	\|(% style="width:153px" %)(% style="color:#e74c3c" %)CHOICE\|(% style="width:149px" %)(% style="color:#e74c3c" %)A
	425	\|(% rowspan="4" style="width:99px" %)(% style="color:#2980b9" %)Key2\|(% style="width:153px" %)(% style="color:#2980b9" %)FREQ\|(% style="width:149px" %)(% style="color:#2980b9" %)Q
	426	\|(% style="width:153px" %)(% style="color:#2980b9" %)VIS_CTY\|(% style="width:149px" %)(% style="color:#2980b9" %)MX
	427	\|(% style="width:153px" %)(% style="color:#27ae60" %)UNIT\|(% style="width:149px" %)(% style="color:#27ae60" %)USD
	428	\|(% style="width:153px" %)(% style="color:#e74c3c" %)CHOICE\|(% style="width:149px" %)(% style="color:#e74c3c" %)B
1.1	429
3.2	430	Use Case 7: A Constraint with wildcards for Codes and removePrefix property
1.1	431
3.2	432	For this example, we assume that the VIS_CTY representation has been prefixed with prefix ‘AREA_’. In this Constraint, we need to remove the prefix.
	433
1.1	434	R1: Allow monthly and quarterly data
	435
	436	R2: Allow vis-à-vis countries that start with M
	437
	438	R3: Remove the prefix ‘AREA_’
	439
	440	This may be expressed with the following CubeRegion:
	441
2.1	442	(% style="width:379.294px" %)
	443	\|(% style="width:264px" %)(% style="color:#2980b9" %)FREQ\|(% style="width:112px" %)(% style="color:#2980b9" %)M, Q
	444	\|(% style="width:264px" %)(% style="color:#2980b9" %)VIS_CTY (removePrefix=’AREA_’)\|(% style="width:112px" %)(% style="color:#2980b9" %)M%
1.1	445
	446	Use Case 8: A Constraint with multilingual support on Attributes
	447
	448	R1: Allow monthly and quarterly data
	449
	450	R2: Allow Mexico for vis-à-vis country
	451
3.2	452	R3: Allow a [[comment>>doc:sdmx:Glossary.Comment.WebHome]], in English, which includes the term adjusted for status
1.1	453
	454	This may be expressed with the following CubeRegion:
	455
2.1	456	(% style="width:382.294px" %)
	457	\|(% style="width:190px" %)(% style="color:#2980b9" %)FREQ\|(% style="width:189px" %)(% style="color:#2980b9" %)M, Q
	458	\|(% style="width:190px" %)(% style="color:#2980b9" %)VIS_CTY\|(% style="width:189px" %)(% style="color:#2980b9" %)MX
3.2	459	\|(% style="width:190px" %)(% style="color:#27ae60" %)[[COMMENT>>doc:sdmx:Glossary.Comment.WebHome]] (lang=’en’)\|(% style="width:189px" %)(% style="color:#27ae60" %)%adjusted%
1.1	460
	461	Use Case 9: A Constraint on allowed values for Dimensions combined with allowed values for Metadata Attributes R1: Allow monthly and quarterly data
	462
	463	R2: Allow Mexico for vis-à-vis country
	464
3.2	465	R3: Allow John Doe for (% style="color:#e74c3c" %)contact(%%)
1.1	466
	467	This may be expressed with the following CubeRegion:
	468
2.1	469	(% style="width:388.294px" %)
	470	\|(% style="width:181px" %)(% style="color:#2980b9" %)FREQ\|(% style="width:204px" %)(% style="color:#2980b9" %)M, Q
	471	\|(% style="width:181px" %)(% style="color:#2980b9" %)VIS_CTY\|(% style="width:204px" %)(% style="color:#2980b9" %)MX
	472	\|(% style="width:181px" %)(% style="color:#f39c12" %)CONTACT\|(% style="width:204px" %)(% style="color:#f39c12" %)John Doe