Skip to Content

Changes for page 10 Constraints

Last modified by Helena on 2025/09/10 11:19
From version 14.4
edited by Helena
on 2025/05/16 12:22
Change comment: There is no comment for this version
To version 14.2
edited by Helena
on 2025/05/16 12:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -265,29 +265,42 @@
265 265  
266 266  This may be expressed with the following CubeRegion:
267 267  
268 -[[image:1747387231598-634.png]]
269 269  
269 +|FREQ|M, Q
270 +|VIS_CTY|MX
271 +|OBS_STATUS|A
272 +
270 270  ===== 10.3.4.2.4 Use Case 4: A Constraint on allowed combinations for some =====
271 271  
272 272  //**Dimensions combined with specific Attribute values**//
273 273  
274 274  R1: Allow monthly data, for Germany, with unit euro
278 +
275 275  R2: Allow quarterly data, for Mexico, with unit usd
276 276  
277 277  This is may be expressed with the following DataKeySet:
278 278  
279 -[[image:1747387252077-954.png]]
283 +|(% rowspan="3" style="width:87px" %)Key1|(% style="width:1327px" %)FREQ|M
284 +|(% style="width:1327px" %)VIS_CTY|DE
285 +|(% style="width:1327px" %)UNIT|EUR
286 +|(% rowspan="3" style="width:87px" %)Key2|(% style="width:1327px" %)FREQ|Q
287 +|(% style="width:1327px" %)VIS_CTY|MX
288 +|(% style="width:1327px" %)UNIT|USD
280 280  
281 -[[image:1747387281625-859.png]]
282 -
283 283  ===== 10.3.4.2.5 Use Case 5: A Constraint on allowed values for some Dimensions together with some combination of Dimension values =====
284 284  
285 285  R1: For annually and quarterly data, for Mexico and Germany, only A status is allowed
293 +
286 286  R2: For monthly data, for Mexico and Germany, only F status is allowed
287 287  
288 288  Considering the above examples, the following CubeRegions would be created:
289 289  
290 -[[image:1747387330751-405.png]]
298 +|(% rowspan="3" %)CubeRegion1|FREQ|Q, A
299 +|VIS_CTY|MX, DE
300 +|OBS_STATUS|A
301 +|(% rowspan="3" %)CubeRegion2|FREQ|M
302 +|VIS_CTY|MX, DE
303 +|OBS_STATUS|F
291 291  
292 292  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).
293 293  
... ... @@ -295,15 +295,37 @@
295 295  
296 296  DSD CubeRegion:
297 297  
311 +|FREQ|M, Q, A
312 +|VIS_CTY|MX, DE
313 +|OBS_STATUS|A, F
314 +
298 298  Dataflow1 CubeRegion:
299 299  
317 +|FREQ|Q, A
318 +|VIS_CTY|MX, DE
319 +|OBS_STATUS|F
320 +
300 300  Dataflow2 CubeRegion:
301 301  
323 +|FREQ|M
324 +|VIS_CTY|MX, DE
325 +|OBS_STATUS|A
326 +
302 302  ===== 10.3.4.2.6 Use case 6: A Constraint on allowed values for some Dimensions combined with allowed values for Measures =====
303 303  
304 304  R1: Allow monthly data, for Germany, with unit euro, and measure choice is 'A'
330 +
305 305  R2: Allow quarterly data, for Mexico, with unit usd, and measure choice is 'B' This is may be expressed with the following DataKeySet:
306 306  
333 +|(% rowspan="4" %)Key1|FREQ|M
334 +|VIS_CTY|DE
335 +|UNIT|EUR
336 +|CHOICE|A
337 +|(% rowspan="4" %)Key2|FREQ|Q
338 +|VIS_CTY|MX
339 +|UNIT|USD
340 +|CHOICE|B
341 +
307 307  ===== 10.3.4.2.7 Use Case 7: A Constraint with wildcards for Codes and removePrefix property =====
308 308  
309 309  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.
1747387231598-634.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -6.2 KB
Content
1747387252077-954.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -5.1 KB
Content
1747387281625-859.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -6.0 KB
Content
1747387330751-405.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -15.8 KB
Content