Interoperability Basis Platform

== 10.1 Introduction ==

(% 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

8

9

* Availability (% style="color:#e74c3c" %)Constraint

10

* [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)Constraint

11

* Reporting (% style="color:#e74c3c" %)Constraints

12

13

An Availability (% style="color:#e74c3c" %)Constraint(%%) defines the data that exists in the context of a data query.

14

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).

16

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.

18

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]].

20

21

== 10.2 Availability Constraint ==

22

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:

24

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]]

28

29

== 10.3 Dimension Constraint ==

30

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]].

32

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.

34

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.

36

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]].

38

39

__**Rules for a Dimension Constraint**__

40

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]].

47

48

__**Example Datasets with Evolving Structures**__

49

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]].

51

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.

53

54

(% style="width:758.294px" %)

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**

== 10.4 Reporting Constraints ==

61

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.

63

64

A reporting (% style="color:#e74c3c" %)constraint(%%) is one of the following concrete types:

65

66

* Data (% style="color:#e74c3c" %)Constraint

67

* Metadata (% style="color:#e74c3c" %)Constraint

68

69

=== 10.4.1 Data Constraint ===

70

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:

72

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]]

76

* Data Provider

77

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.

79

80

=== 10.4.2 Metadata Constraint ===

81

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:

83

84

* Metadata Structure Definition

85

* [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]]

86

* Metadata [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]

87

* Metadata Provider

88

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.

90

91

=== 10.4.3 Scope of a Constraint ===

92

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.

94

95

In terms of data the [[components>>doc:sdmx:Glossary.Component.WebHome]] are:

96

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]].

103

104

In terms of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] the [[components>>doc:sdmx:Glossary.Component.WebHome]] are:

105

106

* Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]

107

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:

109

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]]

113

* Data Provider

114

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:

116

117

* Metadata Structure Definition

118

* [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]]

119

* Metadata [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]

120

* Metadata Provider

121

* [[Metadata Set>>doc:sdmx:Glossary.Metadata set.WebHome]]

122

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]].

124

125

In view of the flexibility of (% style="color:#e74c3c" %)constraints(%%) attachment, clear rules on their usage are required. These are elaborated below.

126

127

=== 10.4.4 Multiple Constraints ===

128

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:

130

131

==== 10.4.4.1 Cube Region ====

132

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]]).

134

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.

140

141

==== 10.4.4.2 Key Set ====

142

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").

144

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.

146

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.

148

149

Finally, a validity period may be specified per Key.

150

151

=== 10.4.4 Versioning ===

152

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.

154

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]].

Example:

Data (% style="color:#e74c3c" %)Constraint(%%) 1.0.0

160

161

(% style="width:573.294px" %)

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

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" %)

166

167

Data (% style="color:#e74c3c" %)Constraint(%%) 1.1.0

168

169

(% style="width:576.294px" %)

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

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" %)

174

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.

176

177

=== 10.4.6 Inheritance ===

178

179

==== 10.4.6.1 Attachment levels of a Constraint ====

180

181

There are three (% style="color:#e74c3c" %)levels(%%) of (% style="color:#e74c3c" %)constraint(%%) attachment for which these inheritance rules apply:

182

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

186

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]].

188

189

==== 10.4.6.2 Cascade rules for processing Constraints ====

190

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.

192

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(%%).

194

195

==== 10.4.6.3 Cube Region ====

196

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:

198

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.

203

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(%%).

205

206

==== 10.4.6.4 Key Set ====

207

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:

209

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(%%).

214

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.

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

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).

224

225

=== 10.4.7 Constraints Examples ===

226

227

==== 10.4.7.1 Data Constraint and Cascading ====

228

229

The following scenario is used.

230

231

A [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] contains the following [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]]:

232

233

* GEO – Geography

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]]

236

* CAS – Current Activity Status

237

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.

239

240

[[image:1750065279010-260.png]]

241

242

**Figure 20: Example Scenario for Constraints **

243

244

Constraints are declared as follows:

245

246

[[image:1750065319060-899.png]]

247

248

**Figure 21: Example Constraints**

Notes:

[[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.

253

254

* The same (% style="color:#e74c3c" %)Constraint(%%) applies to both Provision Agreements.

255

256

The cascade rules elaborated above result as follows:

257

258

[[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]]

259

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]].

261

262

[[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] CENSUS_CUBE1

263

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.

266

267

[[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] CENSUS_CUBE2

268

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]].

271

272

[[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] CENSUS_CUBE1_IT

273

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]].

276

277

[[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] CENSUS_CUBE2_IT

278

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]].

282

283

The (% style="color:#e74c3c" %)Constraints(%%) are defined as follows:

DSD Constraint

[[image:1750065367824-357.png]]

Dataflow Constraints

[[image:1750065392163-400.png]]

292

293

Provision Agreement Constraint

294

295

[[image:1750065461589-995.png]]

296

297

**10.4.7.2 Combination of Constraints**

298

299

The possible combination of constraining terms are explained in this section, following a few examples.

300

301

Let’s assume a [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] with the following [[Components>>doc:sdmx:Glossary.Component.WebHome]]:

302

303

(% style="width:459.294px" %)

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

308

|(% style="width:204px" %)(% style="color:#2980b9" %)TimeDimension|(% style="width:252px" %)(% style="color:#2980b9" %)TIME_PERIOD

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

315

316

On the above, let’s assume the following use cases with their constraining requirements:

317

318

**Use Case 1: A Constraint on allowed values for some Dimensions**

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

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

329

330

**Use Case 2: A Constraint on allowed combinations for some Dimensions**

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

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

343

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

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

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

356

357

**Use Case 4: A Constraint on allowed combinations for some Dimensions combined with specific Attribute values**

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

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

372

373

**Use Case 5: A Constraint on allowed values for some Dimensions together with some combination of Dimension values**

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

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

388

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).

390

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]]:

DSD CubeRegion:

(% style="width:280.294px" %)

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

399

400

Dataflow1 CubeRegion:

401

402

(% style="width:285.294px" %)

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

406

407

Dataflow2 CubeRegion:

408

409

(% style="width:288.294px" %)

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

413

414

**Use case 6: A Constraint on allowed values for some Dimensions combined with allowed values for Measures**

415

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'

417

418

This may be expressed with the following DataKeySet:

419

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

429

430

**Use Case 7: A Constraint with wildcards for Codes and removePrefix property**

431

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

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

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%

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

452

R3: Allow a [[comment>>doc:sdmx:Glossary.Comment.WebHome]], in English, which includes the term adjusted for status

453

454

This may be expressed with the following CubeRegion:

455

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

459

|(% style="width:190px" %)(% style="color:#27ae60" %)[[COMMENT>>doc:sdmx:Glossary.Comment.WebHome]] (lang=’en’)|(% style="width:189px" %)(% style="color:#27ae60" %)%adjusted%

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

465

R3: Allow John Doe for (% style="color:#e74c3c" %)contact(%%)

466

467

This may be expressed with the following CubeRegion:

468

469

(% style="width:388.294px" %)