Changes for page 10 Constraints

Last modified by Helena on 2025/09/10 11:19

From 14.1 to 14.2 From 14.4 to 14.5

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

edited by Helena
on 2025/05/16 12:22

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 4 added, 0 removed)

Details

Page properties

Content

@@ -265,42 +265,29 @@
  This may be expressed with the following CubeRegion:
++[[image:1747387231598-634.png]]
--|FREQ|M, Q
--|VIS_CTY|MX
--|OBS_STATUS|A
--
  ===== 10.3.4.2.4 Use Case 4: A Constraint on allowed combinations for some =====
  //**Dimensions combined with specific Attribute values**//
  R1: Allow monthly data, for Germany, with unit euro
--
  R2: Allow quarterly data, for Mexico, with unit usd
  This is may be expressed with the following DataKeySet:
--|(% rowspan="3" style="width:87px" %)Key1|(% style="width:1327px" %)FREQ|M
--|(% style="width:1327px" %)VIS_CTY|DE
--|(% style="width:1327px" %)UNIT|EUR
--|(% rowspan="3" style="width:87px" %)Key2|(% style="width:1327px" %)FREQ|Q
--|(% style="width:1327px" %)VIS_CTY|MX
--|(% style="width:1327px" %)UNIT|USD
++[[image:1747387252077-954.png]]
++[[image:1747387281625-859.png]]
++
  ===== 10.3.4.2.5 Use Case 5: A Constraint on allowed values for some Dimensions together with some combination of Dimension values =====
  R1: For annually and quarterly data, for Mexico and Germany, only A status is allowed
--
  R2: For monthly data, for Mexico and Germany, only F status is allowed
  Considering the above examples, the following CubeRegions would be created:
--|(% rowspan="3" %)CubeRegion1|FREQ|Q, A
--|VIS_CTY|MX, DE
--|OBS_STATUS|A
--|(% rowspan="3" %)CubeRegion2|FREQ|M
--|VIS_CTY|MX, DE
--|OBS_STATUS|F
++[[image:1747387330751-405.png]]
  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).
@@ -308,37 +308,15 @@
  DSD CubeRegion:
--|FREQ|M, Q, A
--|VIS_CTY|MX, DE
--|OBS_STATUS|A, F
--
  Dataflow1 CubeRegion:
--|FREQ|Q, A
--|VIS_CTY|MX, DE
--|OBS_STATUS|F
--
  Dataflow2 CubeRegion:
--|FREQ|M
--|VIS_CTY|MX, DE
--|OBS_STATUS|A
--
  ===== 10.3.4.2.6 Use case 6: A Constraint on allowed values for some Dimensions combined with allowed values for Measures =====
  R1: Allow monthly data, for Germany, with unit euro, and measure choice is 'A'
--
  R2: Allow quarterly data, for Mexico, with unit usd, and measure choice is 'B' This is may be expressed with the following DataKeySet:
--|(% rowspan="4" %)Key1|FREQ|M
--|VIS_CTY|DE
--|UNIT|EUR
--|CHOICE|A
--|(% rowspan="4" %)Key2|FREQ|Q
--|VIS_CTY|MX
--|UNIT|USD
--|CHOICE|B
--
  ===== 10.3.4.2.7 Use Case 7: A Constraint with wildcards for Codes and removePrefix property =====
  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,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

1747387330751-405.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+15.8 KB

Content