Skip to Content

Changes for page 10 Constraints

Last modified by Helena on 2025/09/10 11:19
From version 9.1
edited by Helena
on 2025/05/15 15:48
Change comment: There is no comment for this version
To version 14.1
edited by Helena
on 2025/05/16 00:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,6 @@
1 -= 10 Constraints =
1 +{{box title="**Contents**"}}
2 +{{toc/}}
3 +{{/box}}
2 2  
3 3  == 10.1 Introduction ==
4 4  
... ... @@ -80,7 +80,7 @@
80 80  
81 81  There can be many Constraints for any Constrainable Artefact (e.g., DSD), subject to the following restrictions:
82 82  
83 -**10.3.2.1 Cube Region**
85 +==== 10.3.2.1 Cube Region ====
84 84  
85 85  A Constraint can contain multiple Member Selections (e.g., Dimensions).
86 86  
... ... @@ -90,7 +90,7 @@
90 90  * A Member Selection 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.
91 91  * Any values included in a Member Selection for Components with an array data type (i.e., Measures, Attributes or Metadata Attributes), 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 ‘A’ for an Attribute will allow any instance of the Attribute that includes ‘A’, like [‘A’, ‘B’] or [‘A’, ‘C’, ‘D’]. Similarly, if Code ‘A’ was excluded, all those arrays of values would also be excluded.
92 92  
93 -**10.3.2.2 Key Set**
95 +==== 10.3.2.2 Key Set ====
94 94  
95 95  Key Sets will be processed in the order they appear in the Constraint and wildcards can be used (e.g., any key position not reference explicitly is deemed to be "all values").
96 96  
... ... @@ -102,7 +102,7 @@
102 102  
103 103  === 10.3.3 Inheritance of a Constraint ===
104 104  
105 -**10.3.3.1 Attachment levels of a Constraint**
107 +==== 10.3.3.1 Attachment levels of a Constraint ====
106 106  
107 107  There are three levels of constraint attachment for which these inheritance rules apply:
108 108  
... ... @@ -114,13 +114,13 @@
114 114  
115 115  It is not necessary for a Constraint to be attached to a higher level artefact. e.g., it is valid to have a Constraint for a Provision Agreement where there are no constraints attached the relevant dataflow or DSD.
116 116  
117 -**10.3.3.2 Cascade rules for processing Constraints**
119 +==== 10.3.3.2 Cascade rules for processing Constraints ====
118 118  
119 119  The processing of the constraints on either Dataflow/Metadataflow or Provision Agreement must take into account the constraints declared at higher levels. The rules for the lower-level constraints (attached to Dataflow/ Metadataflow and Provision Agreement) are detailed below.
120 120  
121 121  Note that there can be a situation where a constraint is specified at a lower level before a constraint is specified at a higher level. Therefore, it is possible that a higher-level constraint makes a lower-level constraint invalid. SDMX makes no rules on how such a conflict should be handled when processing the constraint for attachment. However, the cascade rules on evaluating constraints for usage are clear – the higher-level constraint takes precedence in any conflicts that result in a less restrictive specification at the lower level.
122 122  
123 -**10.3.3.3 Cube Region**
125 +==== 10.3.3.3 Cube Region ====
124 124  
125 125  It is not necessary to have a Constraint on the higher-level artefact (e.g., DSD referenced by the Dataflow), but if there is such a Constraint at the higher level(s) then:
126 126  
... ... @@ -131,7 +131,7 @@
131 131  
132 132  Note that it is possible for a Constraint at a higher level to constrain, say, four Dimensions in a single Constraint, and a Constraint at a lower level to constrain the same four in two, three, or four Constraints.
133 133  
134 -**10.3.3.4 Key Set**
136 +==== 10.3.3.4 Key Set ====
135 135  
136 136  It is not necessary to have a Constraint on the higher-level artefact (e.g., DSD referenced by the Dataflow), but if there is such a Constraint at the higher level(s) then:
137 137  
... ... @@ -153,8 +153,10 @@
153 153  
154 154  === 10.3.4 Constraints Examples ===
155 155  
156 -**10.3.4.1 Data Constraint and Cascading **The following scenario is used.
158 +==== 10.3.4.1 Data Constraint and Cascading ====
157 157  
160 +The following scenario is used.
161 +
158 158  A DSD contains the following Dimensions:
159 159  
160 160  * GEO – Geography
... ... @@ -166,8 +166,10 @@
166 166  
167 167  [[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_77bea5e.png||height="344" width="554"]]
168 168  
169 -**Figure 20: Example Scenario for Constraints **Constraints are declared as follows:
173 +**Figure 20: Example Scenario for Constraints **
170 170  
175 +Constraints are declared as follows:
176 +
171 171  [[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_7c36c475.png||height="356" width="541"]]
172 172  
173 173  **Figure 21: Example Constraints**
... ... @@ -331,7 +331,7 @@
331 331  
332 332  **</str:DataConstraint**
333 333  
334 -**10.3.4.2 Combination of Constraints**
340 +==== 10.3.4.2 Combination of Constraints ====
335 335  
336 336  The possible combination of constraining terms are explained in this section, following a few examples.
337 337  
... ... @@ -351,7 +351,7 @@
351 351  
352 352  On the above, let’s assume the following use cases with their constraining requirements:
353 353  
354 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_6b13e05d.png||height="12" width="62"]] //**Use Case 1: A Constraint on allowed values for some Dimensions**//
360 +===== 10.3.4.2.1 Use Case 1: A Constraint on allowed values for some Dimensions =====
355 355  
356 356  R1: Allow monthly and quarterly data
357 357  
... ... @@ -362,7 +362,7 @@
362 362  |FREQ|M, Q
363 363  |VIS_CTY|MX
364 364  
365 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_18c3726e.png||height="12" width="64"]] //**Use Case 2: A Constraint on allowed combinations for some Dimensions**//
371 +===== 10.3.4.2.2 Use Case 2: A Constraint on allowed combinations for some Dimensions =====
366 366  
367 367  R1: Allow monthly data for Germany
368 368  
... ... @@ -375,7 +375,7 @@
375 375  |(% rowspan="2" %)Key2|FREQ|Q
376 376  |VIS_CTY|MX
377 377  
378 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_8d48dc1a.png||height="12" width="64"]] //**Use Case 3: A Constraint on allowed values for some Dimensions combined with allowed values for some Attributes**//
384 +===== 10.3.4.2.3 Use Case 3: A Constraint on allowed values for some Dimensions combined with allowed values for some Attributes =====
379 379  
380 380  R1: Allow monthly and quarterly data
381 381  
... ... @@ -389,7 +389,7 @@
389 389  |VIS_CTY|MX
390 390  |OBS_STATUS|A
391 391  
392 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_a0d353e8.png||height="12" width="64"]] //**Use Case 4: A Constraint on allowed combinations for some**//
398 +===== 10.3.4.2.4 Use Case 4: A Constraint on allowed combinations for some =====
393 393  
394 394  //**Dimensions combined with specific Attribute values**//
395 395  
... ... @@ -399,14 +399,14 @@
399 399  
400 400  This is may be expressed with the following DataKeySet:
401 401  
402 -|(% rowspan="3" %)Key1|FREQ|M
403 -|VIS_CTY|DE
404 -|UNIT|EUR
405 -|(% rowspan="3" %)Key2|FREQ|Q
406 -|VIS_CTY|MX
407 -|UNIT|USD
408 +|(% rowspan="3" style="width:87px" %)Key1|(% style="width:1327px" %)FREQ|M
409 +|(% style="width:1327px" %)VIS_CTY|DE
410 +|(% style="width:1327px" %)UNIT|EUR
411 +|(% rowspan="3" style="width:87px" %)Key2|(% style="width:1327px" %)FREQ|Q
412 +|(% style="width:1327px" %)VIS_CTY|MX
413 +|(% style="width:1327px" %)UNIT|USD
408 408  
409 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_6e97b73c.png||height="12" width="64"]] //**Use Case 5: A Constraint on allowed values for some Dimensions together with some combination of Dimension values**//
415 +===== 10.3.4.2.5 Use Case 5: A Constraint on allowed values for some Dimensions together with some combination of Dimension values =====
410 410  
411 411  R1: For annually and quarterly data, for Mexico and Germany, only A status is allowed
412 412  
... ... @@ -443,7 +443,7 @@
443 443  |VIS_CTY|MX, DE
444 444  |OBS_STATUS|A
445 445  
446 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_b4693e0d.png||height="12" width="64"]] //**Use case 6: A Constraint on allowed values for some Dimensions combined with allowed values for Measures**//
452 +===== 10.3.4.2.6 Use case 6: A Constraint on allowed values for some Dimensions combined with allowed values for Measures =====
447 447  
448 448  R1: Allow monthly data, for Germany, with unit euro, and measure choice is 'A'
449 449  
... ... @@ -458,7 +458,7 @@
458 458  |UNIT|USD
459 459  |CHOICE|B
460 460  
461 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_9818c7f7.png||height="12" width="64"]] //**Use Case 7: A Constraint with wildcards for Codes and removePrefix property**//
467 +===== 10.3.4.2.7 Use Case 7: A Constraint with wildcards for Codes and removePrefix property =====
462 462  
463 463  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.
464 464  
... ... @@ -473,7 +473,7 @@
473 473  |FREQ|M, Q
474 474  |VIS_CTY (removePrefix=’AREA_’)|M%
475 475  
476 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_7df2eea7.png||height="12" width="64"]] //**Use Case 8: A Constraint with multilingual support on Attributes**//
482 +===== 10.3.4.2.8 Use Case 8: A Constraint with multilingual support on Attributes =====
477 477  
478 478  R1: Allow monthly and quarterly data
479 479  
... ... @@ -487,7 +487,7 @@
487 487  |VIS_CTY|MX
488 488  |COMMENT (lang=’en’)|%adjusted%
489 489  
490 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_7e57ad28.png||height="12" width="64"]] //**Use Case 9: A Constraint on allowed values for Dimensions combined with allowed values for Metadata Attributes**//
496 +===== 10.3.4.2.9 Use Case 9: A Constraint on allowed values for Dimensions combined with allowed values for Metadata Attributes =====
491 491  
492 492  R1: Allow monthly and quarterly data
493 493  
... ... @@ -501,7 +501,7 @@
501 501  |VIS_CTY|MX
502 502  |CONTACT|John Doe
503 503  
504 -**10.3.4.3 Other constraining terms**
510 +==== 10.3.4.3 Other constraining terms ====
505 505  
506 506  Beyond the cube regions and keysets, there is one more constraining term, i.e., the ReleaseCalendar.
507 507  
SDMX 3-0-0 SECTION 6 FINAL-1.0_en_18c3726e.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +1.7 KB
Content
SDMX 3-0-0 SECTION 6 FINAL-1.0_en_6b13e05d.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +1.5 KB
Content
SDMX 3-0-0 SECTION 6 FINAL-1.0_en_7e57ad28.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +1.7 KB
Content
SDMX 3-0-0 SECTION 6 FINAL-1.0_en_a0d353e8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +1.6 KB
Content