Changes for page 10 Constraints

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

From version 15.2
edited by Helena
on 2025/05/17 00:19
Change comment: There is no comment for this version
To version 17.1
edited by Artur
on 2025/05/21 10:38
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,0 +1,1 @@
1 +Methodology.SDMX 3\.0 Standards\. Section 6\. Technical notes.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.helena
1 +xwiki:XWiki.arturkryazhev
Tags
... ... @@ -1,0 +1,1 @@
1 +Age|Artefact|Attribute|Code|Code list|Comment|Component|Data provider|Data set|Data structure definition|Dataflow|Dimension|Maintainable artefact|Measure|Member selection|Metadata structure definition|Metadataflow|Provision agreement|Reference metadata|Release policy - release calendar|Representation|Series key|Statistical data and metadata exchange
Content
... ... @@ -146,7 +146,7 @@
146 146  
147 147  The following logic explains how the inheritance mechanism works. Note that this is conceptual logic and actual systems may differ in the way this is implemented.
148 148  
149 -*
149 +*
150 150  *1. Determine all possible keys that are valid at the higher (% style="color:#2ecc71" %)level(%%).
151 151  *1. These keys are deemed to be inherited by the lower-(% style="color:#2ecc71" %)level(%%) constrained object, subject to the (% style="color:#2ecc71" %)Constraints(%%) specified at the lower (% style="color:#2ecc71" %)level(%%).
152 152  *1. Determine all possible keys that are possible using the (% style="color:#2ecc71" %)Constraints(%%) specified at the lower (% style="color:#2ecc71" %)level(%%).
... ... @@ -180,50 +180,50 @@
180 180  
181 181  Notes:
182 182  
183 -AGE is constrained for the DSD and is further restricted for the Dataflow CENSUS_CUBE1.
183 +[[AGE>>doc:xwiki:Glossary.Age.WebHome]] is constrained for the [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]] and is further restricted for the [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] CENSUS_CUBE1.
184 184  
185 -* The same Constraint applies to both Provision Agreements.
185 +* The same (% style="color:#2ecc71" %)Constraint(%%) applies to both Provision Agreements.
186 186  
187 187  The cascade rules elaborated above result as follows:
188 188  
189 -DSD
189 +[[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]]
190 190  
191 -* Constrained by eliminating code 001 from the code list for the AGE Dimension.
191 +* Constrained by eliminating [[code>>doc:xwiki:Glossary.Code.WebHome]] 001 from the [[code list>>doc:xwiki:Glossary.Code list.WebHome]] for the [[AGE>>doc:xwiki:Glossary.Age.WebHome]] [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]].
192 192  
193 -Dataflow CENSUS_CUBE1
193 +[[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] CENSUS_CUBE1
194 194  
195 -* Constrained by restricting the code list for the AGE Dimension to codes 002 and 003 (note that this is a more restrictive constraint than that declared for the DSD which specifies all codes except code 001).
196 -** Restricts the CAS codes to 003 and 004.
195 +* Constrained by restricting the [[code list>>doc:xwiki:Glossary.Code list.WebHome]] for the [[AGE>>doc:xwiki:Glossary.Age.WebHome]] [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] to [[codes>>doc:xwiki:Glossary.Code.WebHome]] 002 and 003 (note that this is a more restrictive (% style="color:#2ecc71" %)constraint(%%) than that declared for the [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]] which specifies all [[codes>>doc:xwiki:Glossary.Code.WebHome]] except [[code>>doc:xwiki:Glossary.Code.WebHome]] 001).
196 +** Restricts the CAS [[codes>>doc:xwiki:Glossary.Code.WebHome]] to 003 and 004.
197 197  
198 -Dataflow CENSUS_CUBE2
198 +[[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] CENSUS_CUBE2
199 199  
200 -* Restricts the code list for the CAS Dimension to codes TOT and NAP.
201 -** Inherits the AGE constraint applied at the level of the DSD.
200 +* Restricts the [[code list>>doc:xwiki:Glossary.Code list.WebHome]] for the CAS [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] to [[codes>>doc:xwiki:Glossary.Code.WebHome]] TOT and NAP.
201 +** Inherits the [[AGE>>doc:xwiki:Glossary.Age.WebHome]] (% style="color:#2ecc71" %)constraint(%%) applied at the (% style="color:#2ecc71" %)level(%%) of the [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]].
202 202  
203 203  Provision Agreement CENSUS_CUBE1_IT
204 204  
205 -* Restricts the codes for the GEO Dimension to IT and its children.
206 -** Inherits the constraints from Dataflow CENSUS_CUBE1 for the AGE and CAS Dimensions.
205 +* Restricts the [[codes>>doc:xwiki:Glossary.Code.WebHome]] for the GEO [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] to IT and its children.
206 +** Inherits the (% style="color:#2ecc71" %)constraints(%%) from [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] CENSUS_CUBE1 for the [[AGE>>doc:xwiki:Glossary.Age.WebHome]] and CAS Dimensions.
207 207  
208 208  Provision Agreement CENSUS_CUBE2_IT
209 209  
210 -* Restricts the codes for the GEO Dimension to IT and its children.
211 -** Inherits the constraints from Dataflow CENSUS_CUBE2 for the CAS Dimension.
212 -** Inherits the AGE constraint applied at the level of the DSD.
210 +* Restricts the [[codes>>doc:xwiki:Glossary.Code.WebHome]] for the GEO [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] to IT and its children.
211 +** Inherits the (% style="color:#2ecc71" %)constraints(%%) from [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] CENSUS_CUBE2 for the CAS [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]].
212 +** Inherits the [[AGE>>doc:xwiki:Glossary.Age.WebHome]] (% style="color:#2ecc71" %)constraint(%%) applied at the (% style="color:#2ecc71" %)level(%%) of the [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]].
213 213  
214 -The Constraints are defined as follows:
214 +The (% style="color:#2ecc71" %)Constraints(%%) are defined as follows:
215 215  
216 -DSD Constraint
216 +[[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]] (% style="color:#2ecc71" %)Constraint
217 217  
218 218  [[image:1747386911707-332.png]]
219 219  
220 -Dataflow Constraints
220 +[[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] (% style="color:#2ecc71" %)Constraints
221 221  
222 222  [[image:1747386933952-158.png]]
223 223  
224 224  [[image:1747386970127-658.png]]
225 225  
226 -Provision Agreement Constraint
226 +[[Provision Agreement>>doc:xwiki:Glossary.Provision agreement.WebHome]] (% style="color:#2ecc71" %)Constraint
227 227  
228 228  [[image:1747386991329-805.png]]
229 229  
... ... @@ -231,7 +231,7 @@
231 231  
232 232  The possible combination of constraining terms are explained in this section, following a few examples.
233 233  
234 -Let’s assume a DSD with the following Components:
234 +Let’s assume a [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]] with the following [[Components>>doc:xwiki:Glossary.Component.WebHome]]:
235 235  
236 236  [[image:1747387057775-838.png]]
237 237  
... ... @@ -257,7 +257,7 @@
257 257  
258 258  [[image:1747387188821-467.png]]
259 259  
260 -===== 0.3.4.2.3 Use Case 3: A Constraint on allowed values for some Dimensions combined with allowed values for some Attributes =====
260 +===== 10.3.4.2.3 Use Case 3: A Constraint on allowed values for some Dimensions combined with allowed values for some Attributes =====
261 261  
262 262  R1: Allow monthly and quarterly data
263 263  R2: Allow Mexico for vis-à-vis country
... ... @@ -269,7 +269,7 @@
269 269  
270 270  ===== 10.3.4.2.4 Use Case 4: A Constraint on allowed combinations for some =====
271 271  
272 -//**Dimensions combined with specific Attribute values**//
272 +//**[[Dimensions>>doc:xwiki:Glossary.Dimension.WebHome]] combined with specific [[Attribute>>doc:xwiki:Glossary.Attribute.WebHome]] values**//
273 273  
274 274  R1: Allow monthly data, for Germany, with unit euro
275 275  R2: Allow quarterly data, for Mexico, with unit usd
... ... @@ -289,11 +289,11 @@
289 289  
290 290  [[image:1747387330751-405.png]]
291 291  
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).
292 +The problem with this approach is that according to the business rule for (% style="color:#2ecc71" %)Constraints(%%), only one should be specified per [[Component>>doc:xwiki:Glossary.Component.WebHome]]. 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  
294 -Nevertheless, there is a much easier approach to that; this is the cascading mechanism of Constraints (as shown in 10.3.4.1). Hence, these rules would be expressed into two levels of Constraints, e.g., DSD and Dataflows:
294 +Nevertheless, there is a much easier approach to that; this is the cascading mechanism of (% style="color:#2ecc71" %)Constraints(%%) (as shown in 10.3.4.1). Hence, these rules would be expressed into two (% style="color:#2ecc71" %)levels(%%) of (% style="color:#2ecc71" %)Constraints(%%), e.g., [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]] and [[Dataflows>>doc:xwiki:Glossary.Dataflow.WebHome]]:
295 295  
296 -DSD CubeRegion:
296 +[[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]] CubeRegion:
297 297  
298 298  [[image:1747387369822-932.png]]
299 299  
... ... @@ -307,28 +307,28 @@
307 307  
308 308  ===== 10.3.4.2.6 Use case 6: A Constraint on allowed values for some Dimensions combined with allowed values for Measures =====
309 309  
310 -R1: Allow monthly data, for Germany, with unit euro, and measure choice is 'A'
311 -R2: Allow quarterly data, for Mexico, with unit usd, and measure choice is 'B' This is may be expressed with the following DataKeySet:
310 +R1: Allow monthly data, for Germany, with unit euro, and [[measure>>doc:xwiki:Glossary.Measure.WebHome]] choice is 'A'
311 +R2: Allow quarterly data, for Mexico, with unit usd, and [[measure>>doc:xwiki:Glossary.Measure.WebHome]] choice is 'B' This is may be expressed with the following DataKeySet:
312 312  
313 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 -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.
317 +For this example, we assume that the VIS_CTY [[representation>>doc:xwiki:Glossary.Representation.WebHome]] has been prefixed with prefix ‘AREA_’. In this (% style="color:#2ecc71" %)Constraint(%%), we need to remove the prefix.
318 318  
319 319  R1: Allow monthly and quarterly data
320 320  R2: Allow vis-à-vis countries that start with M
321 321  R3: Remove the prefix ‘AREA_’
322 322  
323 -[[image:1747387461703-763.png]]
324 -
325 325  This may be expressed with the following CubeRegion:
326 326  
327 -===== 10.3.4.2.8 Use Case 8: A Constraint with multilingual support on Attributes =====
325 +[[image:1747387461703-763.png]]
328 328  
327 +10.3.4.2.8 Use Case 8: A Constraint with multilingual support on Attributes
328 +
329 329  R1: Allow monthly and quarterly data
330 330  R2: Allow Mexico for vis-à-vis country
331 -R3: Allow a comment, in English, which includes the term adjusted for status
331 +R3: Allow a [[comment>>doc:xwiki:Glossary.Comment.WebHome]], in English, which includes the term adjusted for status
332 332  
333 333  This may be expressed with the following CubeRegion:
334 334  
... ... @@ -348,7 +348,7 @@
348 348  
349 349  Beyond the cube regions and keysets, there is one more constraining term, i.e., the ReleaseCalendar.
350 350  
351 -The ReleaseCalendar is the only term that does not apply on Components; it specifies the schedule of publication or reporting of the dataset or metadataset.
351 +The ReleaseCalendar is the only term that does not apply on [[Components>>doc:xwiki:Glossary.Component.WebHome]]; it specifies the schedule of publication or reporting of the [[dataset>>doc:xwiki:Glossary.Data set.WebHome]] or metadataset.
352 352  
353 353  For example, the ReleaseCalendar for Provider BIS, is specified in the three following terms:
354 354  
... ... @@ -358,4 +358,4 @@
358 358  
359 359  With the above terms, BIS would need to report data between the 10^^th^^ and 15^^th^^ of every month.
360 360  
361 -NOTE: The SDMX 2.1 constraining term ReferencePeriod has been deprecated in SDMX 3.0; thus, the TimeDimension and any Dimension with a time Representation can be constrained within a CubeRegion or MetadataTargetRegion, using the TimeRangeValue.
361 +NOTE: The [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 constraining term ReferencePeriod has been deprecated in [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] 3.0; thus, the TimeDimension and any [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] with a time [[Representation>>doc:xwiki:Glossary.Representation.WebHome]] can be constrained within a CubeRegion or MetadataTargetRegion, using the TimeRangeValue.
SUZ.Methodology.Code.MethodologyClass[0]