Changes for page 10 Constraints
Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 5 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -278,6 +278,8 @@ 278 278 279 279 [[image:1747387252077-954.png]] 280 280 281 +[[image:1747387281625-859.png]] 282 + 281 281 ===== 10.3.4.2.5 Use Case 5: A Constraint on allowed values for some Dimensions together with some combination of Dimension values ===== 282 282 283 283 R1: For annually and quarterly data, for Mexico and Germany, only A status is allowed ... ... @@ -285,7 +285,7 @@ 285 285 286 286 Considering the above examples, the following CubeRegions would be created: 287 287 288 -[[image:1747387 281625-859.png]]290 +[[image:1747387330751-405.png]] 289 289 290 290 The problem with this approach is that according to the business rule for Constraints, only one should be specified per Component. 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). 291 291 ... ... @@ -293,24 +293,22 @@ 293 293 294 294 DSD CubeRegion: 295 295 298 +[[image:1747387369822-932.png]] 299 + 296 296 Dataflow1 CubeRegion: 297 297 302 +[[image:1747387387944-676.png]] 303 + 298 298 Dataflow2 CubeRegion: 299 299 306 +[[image:1747387401689-306.png]] 307 + 300 300 ===== 10.3.4.2.6 Use case 6: A Constraint on allowed values for some Dimensions combined with allowed values for Measures ===== 301 301 302 302 R1: Allow monthly data, for Germany, with unit euro, and measure choice is 'A' 303 - 304 304 R2: Allow quarterly data, for Mexico, with unit usd, and measure choice is 'B' This is may be expressed with the following DataKeySet: 305 305 306 -|(% rowspan="4" %)Key1|FREQ|M 307 -|VIS_CTY|DE 308 -|UNIT|EUR 309 -|CHOICE|A 310 -|(% rowspan="4" %)Key2|FREQ|Q 311 -|VIS_CTY|MX 312 -|UNIT|USD 313 -|CHOICE|B 313 +[[image:1747387437317-733.png]] 314 314 315 315 ===== 10.3.4.2.7 Use Case 7: A Constraint with wildcards for Codes and removePrefix property ===== 316 316 ... ... @@ -317,16 +317,12 @@ 317 317 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. 318 318 319 319 R1: Allow monthly and quarterly data 320 - 321 321 R2: Allow vis-à-vis countries that start with M 322 - 323 323 R3: Remove the prefix ‘AREA_’ 324 324 323 + 325 325 This may be expressed with the following CubeRegion: 326 326 327 -|FREQ|M, Q 328 -|VIS_CTY (removePrefix=’AREA_’)|M% 329 - 330 330 ===== 10.3.4.2.8 Use Case 8: A Constraint with multilingual support on Attributes ===== 331 331 332 332 R1: Allow monthly and quarterly data
- 1747387330751-405.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +15.8 KB - Content
- 1747387369822-932.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +6.9 KB - Content
- 1747387387944-676.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +6.2 KB - Content
- 1747387401689-306.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +6.0 KB - Content
- 1747387437317-733.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +13.9 KB - Content