Skip to Content

Changes for page 10 Constraints

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

Summary

Details

Page properties
Content
... ... @@ -265,42 +265,27 @@
265 265  
266 266  This may be expressed with the following CubeRegion:
267 267  
268 +[[image:1747387231598-634.png]]
268 268  
269 -|FREQ|M, Q
270 -|VIS_CTY|MX
271 -|OBS_STATUS|A
272 -
273 273  ===== 10.3.4.2.4 Use Case 4: A Constraint on allowed combinations for some =====
274 274  
275 275  //**Dimensions combined with specific Attribute values**//
276 276  
277 277  R1: Allow monthly data, for Germany, with unit euro
278 -
279 279  R2: Allow quarterly data, for Mexico, with unit usd
280 280  
281 281  This is may be expressed with the following DataKeySet:
282 282  
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
279 +[[image:1747387252077-954.png]]
289 289  
290 290  ===== 10.3.4.2.5 Use Case 5: A Constraint on allowed values for some Dimensions together with some combination of Dimension values =====
291 291  
292 292  R1: For annually and quarterly data, for Mexico and Germany, only A status is allowed
293 -
294 294  R2: For monthly data, for Mexico and Germany, only F status is allowed
295 295  
296 296  Considering the above examples, the following CubeRegions would be created:
297 297  
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
288 +[[image:1747387281625-859.png]]
304 304  
305 305  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).
306 306  
... ... @@ -308,22 +308,10 @@
308 308  
309 309  DSD CubeRegion:
310 310  
311 -|FREQ|M, Q, A
312 -|VIS_CTY|MX, DE
313 -|OBS_STATUS|A, F
314 -
315 315  Dataflow1 CubeRegion:
316 316  
317 -|FREQ|Q, A
318 -|VIS_CTY|MX, DE
319 -|OBS_STATUS|F
320 -
321 321  Dataflow2 CubeRegion:
322 322  
323 -|FREQ|M
324 -|VIS_CTY|MX, DE
325 -|OBS_STATUS|A
326 -
327 327  ===== 10.3.4.2.6 Use case 6: A Constraint on allowed values for some Dimensions combined with allowed values for Measures =====
328 328  
329 329  R1: Allow monthly data, for Germany, with unit euro, and measure choice is 'A'
1747387231598-634.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +6.2 KB
Content
1747387252077-954.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +5.1 KB
Content
1747387281625-859.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +6.0 KB
Content