Skip to Content

Changes for page 10 Constraints

Last modified by Helena on 2025/09/10 11:19
From version 14.6
edited by Helena
on 2025/05/16 12:24
Change comment: There is no comment for this version
To version 16.4
edited by Helena
on 2025/05/19 14:18
Change comment: Update document after refactoring.

Summary

Details

Page properties
Parent
... ... @@ -1,0 +1,1 @@
1 +Methodology.SDMX 3\.0 Standards\. Technical notes.WebHome
Content
... ... @@ -4,40 +4,40 @@
4 4  
5 5  == 10.1 Introduction ==
6 6  
7 -A Constraint is a Maintainable Artefact that can be associated to one or more of:
7 +A (% style="color:#2ecc71" %)Constraint(%%) is a [[Maintainable Artefact>>doc:xwiki:Glossary.Maintainable artefact.WebHome]] that can be associated to one or more of:
8 8  
9 9  * Data Structure Definition
10 10  * Metadata Structure Definition
11 -* Dataflow
12 -* Metadataflow
13 -* Provision Agreement
14 -* Metadata Provision Agreement
15 -* Data Provider or Metadata Provider (this is restricted to a Release Calendar Constraint)
11 +* [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]]
12 +* [[Metadataflow>>doc:xwiki:Glossary.Metadataflow.WebHome]]
13 +* [[Provision Agreement>>doc:xwiki:Glossary.Provision agreement.WebHome]]
14 +* Metadata [[Provision Agreement>>doc:xwiki:Glossary.Provision agreement.WebHome]]
15 +* [[Data Provider>>doc:xwiki:Glossary.Data provider.WebHome]] or Metadata Provider (this is restricted to a [[Release Calendar>>doc:xwiki:Glossary.Release policy - release calendar.WebHome]] (% style="color:#2ecc71" %)Constraint(%%))
16 16  * Simple or Queryable Data Sources
17 17  * Dataset
18 18  * Metadataset
19 19  
20 -Note that regardless of the Artefact to which the Constraint is associated, it is constraining the contents of code lists in the DSD to which the constrained object is related. This does not apply, of course, to a Metadata/Data Provider as the latter can be associated, via the (Metadata) Provision Agreement, to many MSDs/DSDs. Hence the reason for the restriction on the type of Constraint that can be attached to a Metadata/Data Provider.
20 +Note that regardless of the [[Artefact>>doc:xwiki:Glossary.Artefact.WebHome]] to which the (% style="color:#2ecc71" %)Constraint(%%) is associated, it is constraining the contents of [[code lists>>doc:xwiki:Glossary.Code list.WebHome]] in the [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]] to which the constrained object is related. This does not apply, of course, to a Metadata/[[Data Provider>>doc:xwiki:Glossary.Data provider.WebHome]] as the latter can be associated, via the (Metadata) [[Provision Agreement>>doc:xwiki:Glossary.Provision agreement.WebHome]], to many MSDs/DSDs. Hence the reason for the restriction on the type of (% style="color:#2ecc71" %)Constraint(%%) that can be attached to a Metadata/[[Data Provider>>doc:xwiki:Glossary.Data provider.WebHome]].
21 21  
22 22  == 10.2 Types of Constraint ==
23 23  
24 -The Constraint can be of one of two types:
24 +The (% style="color:#2ecc71" %)Constraint(%%) can be of one of two types:
25 25  
26 -* Data constraint
27 -* Metadata constraint
26 +* Data (% style="color:#2ecc71" %)constraint
27 +* Metadata (% style="color:#2ecc71" %)constraint
28 28  
29 -The Data Constraint may serve two different perspectives, depending on the way the latter is retrieved. These are:
29 +The Data (% style="color:#2ecc71" %)Constraint(%%) may serve two different perspectives, depending on the way the latter is retrieved. These are:
30 30  
31 -* Allowed constraint
32 -* Actual constraint
31 +* Allowed (% style="color:#2ecc71" %)constraint
32 +* Actual (% style="color:#2ecc71" %)constraint
33 33  
34 -The former (allowed – also valid for Metadata Constraint) is specified by a data or metadata provider or consumer for sharing the allowed data and metadata in the context of their DSD or MSD exchanges, e.g., only Monthly data for a specific Dataflow. The latter (actual) is a dynamic Constraint in response to an availability request (only possible for data).
34 +The former (allowed – also valid for Metadata (% style="color:#2ecc71" %)Constraint(%%)) is specified by a data or metadata provider or consumer for sharing the allowed data and metadata in the context of their [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]] or [[MSD>>doc:xwiki:Glossary.Metadata structure definition.WebHome]] exchanges, e.g., only Monthly data for a specific [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]]. The latter (actual) is a dynamic (% style="color:#2ecc71" %)Constraint(%%) in response to an availability request (only possible for data).
35 35  
36 -For Actual Data Constraints, there a few characteristics that are worth noting:
36 +For Actual Data (% style="color:#2ecc71" %)Constraints(%%), there a few characteristics that are worth noting:
37 37  
38 38  * They can only be retrieved by the availability requests (as specified in the REST API).
39 -* They depend on the data available in an SDMX Web Service and thus they can only be dynamically generated according to that data.
40 -* Although they are Maintainable Artefacts, they cannot change independently of data; thus, they cannot be versioned (they are non-versioned, as explained in section 14).
39 +* They depend on the data available in an [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] Web Service and thus they can only be dynamically generated according to that data.
40 +* Although they are [[Maintainable Artefacts>>doc:xwiki:Glossary.Maintainable artefact.WebHome]], they cannot change independently of data; thus, they cannot be versioned (they are non-versioned, as explained in section 14).
41 41  * Their identifier may also be dynamically generated and thus there is no REST resource based on their identification.
42 42  
43 43  == 10.3 Rules for a Constraint ==
... ... @@ -44,61 +44,61 @@
44 44  
45 45  === 10.3.1 Scope of a Constraint ===
46 46  
47 -A Constraint is used specify the content of a data or metadata source in terms of the component values or the keys.
47 +A (% style="color:#2ecc71" %)Constraint(%%) is used specify the content of a data or metadata source in terms of the [[component>>doc:xwiki:Glossary.Component.WebHome]] values or the keys.
48 48  
49 -In terms of data the components are:
49 +In terms of data the [[components>>doc:xwiki:Glossary.Component.WebHome]] are:
50 50  
51 -* Dimension
52 -* Time Dimension
53 -* Data Attribute
54 -* Measure
55 -* Metadata Attribute
56 -* DataKeySets: the keys are the content of the KeyDescriptor – i.e., the series keys composed, for each key, by a value for each Dimension.
51 +* [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]]
52 +* Time [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]]
53 +* Data [[Attribute>>doc:xwiki:Glossary.Attribute.WebHome]]
54 +* [[Measure>>doc:xwiki:Glossary.Measure.WebHome]]
55 +* Metadata [[Attribute>>doc:xwiki:Glossary.Attribute.WebHome]]
56 +* DataKeySets: the keys are the content of the KeyDescriptor – i.e., the [[series keys>>doc:xwiki:Glossary.Series key.WebHome]] composed, for each key, by a value for each [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]].
57 57  
58 -In terms of reference metadata the components are:
58 +In terms of [[reference metadata>>doc:xwiki:Glossary.Reference metadata.WebHome]] the [[components>>doc:xwiki:Glossary.Component.WebHome]] are:
59 59  
60 -* Metadata Attribute
60 +* Metadata [[Attribute>>doc:xwiki:Glossary.Attribute.WebHome]]
61 61  
62 -For a Constraint based on a DSD the Constraint can reference one or more of:
62 +For a (% style="color:#2ecc71" %)Constraint(%%) based on a [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]] the (% style="color:#2ecc71" %)Constraint(%%) can reference one or more of:
63 63  
64 64  * Data Structure Definition
65 -* Dataflow
66 -* Provision Agreement
67 -* Data Provider
65 +* [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]]
66 +* [[Provision Agreement>>doc:xwiki:Glossary.Provision agreement.WebHome]]
67 +* [[Data Provider>>doc:xwiki:Glossary.Data provider.WebHome]]
68 68  
69 -For a Constraint based on an MSD the Constraint can reference one or more of:
69 +For a (% style="color:#2ecc71" %)Constraint(%%) based on an [[MSD>>doc:xwiki:Glossary.Metadata structure definition.WebHome]] the (% style="color:#2ecc71" %)Constraint(%%) can reference one or more of:
70 70  
71 71  * Metadata Structure Definition
72 -* Metadataflow
73 -* Metadata Provision Agreement
72 +* [[Metadataflow>>doc:xwiki:Glossary.Metadataflow.WebHome]]
73 +* Metadata [[Provision Agreement>>doc:xwiki:Glossary.Provision agreement.WebHome]]
74 74  * Metadata Provider
75 75  * Metadata Set
76 76  
77 -Furthermore, there can be more than one Constraint specified for a specific object e.g., more than one Constraint for a specific DSD.
77 +Furthermore, there can be more than one (% style="color:#2ecc71" %)Constraint(%%) specified for a specific object e.g., more than one (% style="color:#2ecc71" %)Constraint(%%) for a specific [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]].
78 78  
79 -In view of the flexibility of constraints attachment, clear rules on their usage are required. These are elaborated below.
79 +In view of the flexibility of (% style="color:#2ecc71" %)constraints(%%) attachment, clear rules on their usage are required. These are elaborated below.
80 80  
81 81  === 10.3.2 Multiple Constraints ===
82 82  
83 -There can be many Constraints for any Constrainable Artefact (e.g., DSD), subject to the following restrictions:
83 +There can be many (% style="color:#2ecc71" %)Constraints(%%) for any Constrainable [[Artefact>>doc:xwiki:Glossary.Artefact.WebHome]] (e.g., [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]]), subject to the following restrictions:
84 84  
85 85  ==== 10.3.2.1 Cube Region ====
86 86  
87 -A Constraint can contain multiple Member Selections (e.g., Dimensions).
87 +A (% style="color:#2ecc71" %)Constraint(%%) can contain multiple [[Member Selections>>doc:xwiki:Glossary.Member selection.WebHome]] (e.g., [[Dimensions>>doc:xwiki:Glossary.Dimension.WebHome]]).
88 88  
89 -* A specific Member Selection (e.g., Dimension FREQ) can only be contained in one Cube Region for any one attached object (e.g., a specific DSD or specific Dataflow).
90 -* Component values within a Member Selection may define a validity period. Otherwise, the value is valid for the whole validity of the Cube Region.
91 -* For partial reference resolution purposes (as per the SDMX REST API), the latest non-draft Constraint must be considered.
92 -* A Member Selection may include wildcarding of values (using character ‘%’ to represent zero or more occurrences of any character), as well as cascading through hierarchic structures (e.g., parents in Codelist), or localised values (e.g., text for English only). Lack of locale means any language may match. Cascading values are mutual exclusive to localised values, as the former refer to coded values, while the latter refer to uncoded values.
93 -* Any values included in a Member Selection for Components with an array data type (i.e., Measures, Attributes or Metadata Attributes), will be applied as single values and will not be assessed combined with other values to match all possible array values. For example, including the Code ‘A’ for an Attribute will allow any instance of the Attribute that includes ‘A’, like [‘A’, ‘B’] or [‘A’, ‘C’, ‘D’]. Similarly, if Code ‘A’ was excluded, all those arrays of values would also be excluded.
89 +* A specific [[Member Selection>>doc:xwiki:Glossary.Member selection.WebHome]] (e.g., [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] FREQ) can only be contained in one Cube Region for any one attached object (e.g., a specific [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]] or specific [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]]).
90 +* [[Component>>doc:xwiki:Glossary.Component.WebHome]] values within a [[Member Selection>>doc:xwiki:Glossary.Member selection.WebHome]] may define a validity period. Otherwise, the value is valid for the whole validity of the Cube Region.
91 +* For partial reference resolution purposes (as per the [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] REST API), the latest non-draft (% style="color:#2ecc71" %)Constraint(%%) must be considered.
92 +* A [[Member Selection>>doc:xwiki:Glossary.Member selection.WebHome]] may include wildcarding of values (using character ‘%’ to represent zero or more occurrences of any character), as well as cascading through hierarchic structures (e.g., parents in Codelist), or localised values (e.g., text for English only). Lack of locale means any language may match. Cascading values are mutual exclusive to localised values, as the former refer to coded values, while the latter refer to uncoded values.
93 +* Any values included in a [[Member Selection>>doc:xwiki:Glossary.Member selection.WebHome]] for [[Components>>doc:xwiki:Glossary.Component.WebHome]] with an array data type (i.e., [[Measures>>doc:xwiki:Glossary.Measure.WebHome]], [[Attributes>>doc:xwiki:Glossary.Attribute.WebHome]] or Metadata [[Attributes>>doc:xwiki:Glossary.Attribute.WebHome]]), will be applied as single values and will not be assessed combined with other values to match all possible array values. For example, including the [[Code>>doc:xwiki:Glossary.Code.WebHome]] ‘A’ for an [[Attribute>>doc:xwiki:Glossary.Attribute.WebHome]] will allow any instance of the [[Attribute>>doc:xwiki:Glossary.Attribute.WebHome]] that includes ‘A’, like [‘A’, ‘B’] or [‘A’, ‘C’, ‘D’]. Similarly, if [[Code>>doc:xwiki:Glossary.Code.WebHome]] ‘A’ was excluded, all those arrays of values would also be excluded.
94 94  
95 95  ==== 10.3.2.2 Key Set ====
96 96  
97 -Key Sets will be processed in the order they appear in the Constraint and wildcards can be used (e.g., any key position not reference explicitly is deemed to be "all values").
97 +Key Sets will be processed in the order they appear in the (% style="color:#2ecc71" %)Constraint(%%) and wildcards can be used (e.g., any key position not reference explicitly is deemed to be "all values").
98 98  
99 -As the Key Sets can be "included" or "excluded" it is recommended that Key Sets with wildcards are declared before KeySets with specific series keys. This will minimize the risk that keys are inadvertently included or excluded.
99 +As the Key Sets can be "included" or "excluded" it is recommended that Key Sets with wildcards are declared before KeySets with specific [[series keys>>doc:xwiki:Glossary.Series key.WebHome]]. This will minimize the risk that keys are inadvertently included or excluded.
100 100  
101 -In addition, Attribute, Measure and Metadata Attribute constraints may accompany KeySets, in order to specify the allowed values per Key. Those are expressed following the rules for Cube Regions, as explained above.
101 +In addition, [[Attribute>>doc:xwiki:Glossary.Attribute.WebHome]], [[Measure>>doc:xwiki:Glossary.Measure.WebHome]] and Metadata [[Attribute>>doc:xwiki:Glossary.Attribute.WebHome]] (% style="color:#2ecc71" %)constraints(%%) may accompany KeySets, in order to specify the allowed values per Key. Those are expressed following the rules for Cube Regions, as explained above.
102 102  
103 103  Finally, a validity period may be specified per Key.
104 104  
... ... @@ -106,52 +106,52 @@
106 106  
107 107  ==== 10.3.3.1 Attachment levels of a Constraint ====
108 108  
109 -There are three levels of constraint attachment for which these inheritance rules apply:
109 +There are three (% style="color:#2ecc71" %)levels(%%) of (% style="color:#2ecc71" %)constraint(%%) attachment for which these inheritance rules apply:
110 110  
111 -• DSD/MSD – top level o Dataflow/Metadataflow – second level
111 +• [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]]/[[MSD>>doc:xwiki:Glossary.Metadata structure definition.WebHome]] – top (% style="color:#2ecc71" %)level(%%) o [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]]/[[Metadataflow>>doc:xwiki:Glossary.Metadataflow.WebHome]] – second (% style="color:#2ecc71" %)level
112 112  
113 -▪ Provision Agreement – third level
113 +▪ [[Provision Agreement>>doc:xwiki:Glossary.Provision agreement.WebHome]] – third (% style="color:#2ecc71" %)level
114 114  
115 -Note that these rules do not apply to the Simple Datasource or Queryable Datasource; the Constraint(s) attached to these artefacts are resolved for this artefact only and do not take into account Constraints attached to other artefacts (e.g., Provision Agreement, Dataflow, DSD).
115 +Note that these rules do not apply to the Simple Datasource or Queryable Datasource; the (% style="color:#2ecc71" %)Constraint(%%)(s) attached to these [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] are resolved for this [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] only and do not take into account (% style="color:#2ecc71" %)Constraints(%%) attached to other [[artefacts>>doc:xwiki:Glossary.Artefact.WebHome]] (e.g., [[Provision Agreement>>doc:xwiki:Glossary.Provision agreement.WebHome]], [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]], [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]]).
116 116  
117 -It is not necessary for a Constraint to be attached to a higher level artefact. e.g., it is valid to have a Constraint for a Provision Agreement where there are no constraints attached the relevant dataflow or DSD.
117 +It is not necessary for a (% style="color:#2ecc71" %)Constraint(%%) to be attached to a higher (% style="color:#2ecc71" %)level(%%) [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]]. e.g., it is valid to have a (% style="color:#2ecc71" %)Constraint(%%) for a [[Provision Agreement>>doc:xwiki:Glossary.Provision agreement.WebHome]] where there are no (% style="color:#2ecc71" %)constraints(%%) attached the relevant [[dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] or [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]].
118 118  
119 119  ==== 10.3.3.2 Cascade rules for processing Constraints ====
120 120  
121 -The processing of the constraints on either Dataflow/Metadataflow or Provision Agreement must take into account the constraints declared at higher levels. The rules for the lower-level constraints (attached to Dataflow/ Metadataflow and Provision Agreement) are detailed below.
121 +The processing of the (% style="color:#2ecc71" %)constraints(%%) on either [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]]/[[Metadataflow>>doc:xwiki:Glossary.Metadataflow.WebHome]] or [[Provision Agreement>>doc:xwiki:Glossary.Provision agreement.WebHome]] must take into account the (% style="color:#2ecc71" %)constraints(%%) declared at higher (% style="color:#2ecc71" %)levels(%%). The rules for the lower-(% style="color:#2ecc71" %)level(%%) (% style="color:#2ecc71" %)constraints(%%) (attached to [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]]/ [[Metadataflow>>doc:xwiki:Glossary.Metadataflow.WebHome]] and [[Provision Agreement>>doc:xwiki:Glossary.Provision agreement.WebHome]]) are detailed below.
122 122  
123 -Note that there can be a situation where a constraint is specified at a lower level before a constraint is specified at a higher level. Therefore, it is possible that a higher-level constraint makes a lower-level constraint invalid. SDMX makes no rules on how such a conflict should be handled when processing the constraint for attachment. However, the cascade rules on evaluating constraints for usage are clear – the higher-level constraint takes precedence in any conflicts that result in a less restrictive specification at the lower level.
123 +Note that there can be a situation where a (% style="color:#2ecc71" %)constraint(%%) is specified at a lower (% style="color:#2ecc71" %)level(%%) before a (% style="color:#2ecc71" %)constraint(%%) is specified at a higher (% style="color:#2ecc71" %)level(%%). Therefore, it is possible that a higher-(% style="color:#2ecc71" %)level(%%) (% style="color:#2ecc71" %)constraint(%%) makes a lower-(% style="color:#2ecc71" %)level(%%) (% style="color:#2ecc71" %)constraint(%%) invalid. [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] makes no rules on how such a conflict should be handled when processing the (% style="color:#2ecc71" %)constraint(%%) for attachment. However, the cascade rules on evaluating (% style="color:#2ecc71" %)constraints(%%) for usage are clear – the higher-(% style="color:#2ecc71" %)level(%%) (% style="color:#2ecc71" %)constraint(%%) takes precedence in any conflicts that result in a less restrictive specification at the lower (% style="color:#2ecc71" %)level(%%).
124 124  
125 125  ==== 10.3.3.3 Cube Region ====
126 126  
127 -It is not necessary to have a Constraint on the higher-level artefact (e.g., DSD referenced by the Dataflow), but if there is such a Constraint at the higher level(s) then:
127 +It is not necessary to have a (% style="color:#2ecc71" %)Constraint(%%) on the higher-(% style="color:#2ecc71" %)level(%%) [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] (e.g., [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]] referenced by the [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]]), but if there is such a (% style="color:#2ecc71" %)Constraint(%%) at the higher (% style="color:#2ecc71" %)level(%%)(s) then:
128 128  
129 -* The lower-level Constraint cannot be less restrictive than the Constraint specified for the same Member Selection (e.g. Dimension) at the next higher level, which constrains that Member Selection. For example, if the Dimension FREQ is constrained to A, Q in a DSD, then the Constraint at the Dataflow or Provision Agreement cannot be A, Q, M or even just M – it can only further constrain A, Q.
130 -* The Constraint at the lower level for any one Member Selection further constrains the content for the same Member Selection at the higher level(s).
131 -* Any Member Selection, which is not referenced in a Constraint, is deemed to be constrained according to the Constraint specified at the next higher level which constraints that Member Selection.
132 -* If there is a conflict when resolving the Constraint in terms of a lower-level Constraint being less restrictive than a higher-level Constraint, then the Constraint at the higher-level is used.
129 +* The lower-(% style="color:#2ecc71" %)level(%%) (% style="color:#2ecc71" %)Constraint(%%) cannot be less restrictive than the (% style="color:#2ecc71" %)Constraint(%%) specified for the same [[Member Selection>>doc:xwiki:Glossary.Member selection.WebHome]] (e.g. [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]]) at the next higher (% style="color:#2ecc71" %)level(%%), which constrains that [[Member Selection>>doc:xwiki:Glossary.Member selection.WebHome]]. For example, if the [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] FREQ is constrained to A, Q in a [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]], then the (% style="color:#2ecc71" %)Constraint(%%) at the [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]] or [[Provision Agreement>>doc:xwiki:Glossary.Provision agreement.WebHome]] cannot be A, Q, M or even just M – it can only further constrain A, Q.
130 +* The (% style="color:#2ecc71" %)Constraint(%%) at the lower (% style="color:#2ecc71" %)level(%%) for any one [[Member Selection>>doc:xwiki:Glossary.Member selection.WebHome]] further constrains the content for the same [[Member Selection>>doc:xwiki:Glossary.Member selection.WebHome]] at the higher (% style="color:#2ecc71" %)level(%%)(s).
131 +* Any [[Member Selection>>doc:xwiki:Glossary.Member selection.WebHome]], which is not referenced in a (% style="color:#2ecc71" %)Constraint(%%), is deemed to be constrained according to the (% style="color:#2ecc71" %)Constraint(%%) specified at the next higher (% style="color:#2ecc71" %)level(%%) which (% style="color:#2ecc71" %)constraints(%%) that [[Member Selection>>doc:xwiki:Glossary.Member selection.WebHome]].
132 +* If there is a conflict when resolving the (% style="color:#2ecc71" %)Constraint(%%) in terms of a lower-(% style="color:#2ecc71" %)level(%%) (% style="color:#2ecc71" %)Constraint(%%) being less restrictive than a higher-(% style="color:#2ecc71" %)level(%%) (% style="color:#2ecc71" %)Constraint(%%), then the (% style="color:#2ecc71" %)Constraint(%%) at the higher-(% style="color:#2ecc71" %)level(%%) is used.
133 133  
134 -Note that it is possible for a Constraint at a higher level to constrain, say, four Dimensions in a single Constraint, and a Constraint at a lower level to constrain the same four in two, three, or four Constraints.
134 +Note that it is possible for a (% style="color:#2ecc71" %)Constraint(%%) at a higher (% style="color:#2ecc71" %)level(%%) to constrain, say, four [[Dimensions>>doc:xwiki:Glossary.Dimension.WebHome]] in a single (% style="color:#2ecc71" %)Constraint(%%), and a (% style="color:#2ecc71" %)Constraint(%%) at a lower (% style="color:#2ecc71" %)level(%%) to constrain the same four in two, three, or four (% style="color:#2ecc71" %)Constraints(%%).
135 135  
136 136  ==== 10.3.3.4 Key Set ====
137 137  
138 -It is not necessary to have a Constraint on the higher-level artefact (e.g., DSD referenced by the Dataflow), but if there is such a Constraint at the higher level(s) then:
138 +It is not necessary to have a (% style="color:#2ecc71" %)Constraint(%%) on the higher-(% style="color:#2ecc71" %)level(%%) [[artefact>>doc:xwiki:Glossary.Artefact.WebHome]] (e.g., [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]] referenced by the [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]]), but if there is such a (% style="color:#2ecc71" %)Constraint(%%) at the higher (% style="color:#2ecc71" %)level(%%)(s) then:
139 139  
140 -* The lower-level Constraint cannot be less restrictive than the Constraint specified at the higher level.
141 -* The Constraint at the lower level for any one Member Selection further constrains the keys specified at the higher level(s).
142 -* Any Member Selection, which is not referenced in a Constraint, is deemed to be constrained according to the Constraint specified at the next higher level which constraints that Member Selection.
143 -* If there is a conflict when resolving the keys in the Constraint at two levels, in terms of a lower-level constraint being less restrictive than a higher-level Constraint, then the offending keys specified at the lower level are not deemed part of the Constraint.
140 +* The lower-(% style="color:#2ecc71" %)level(%%) (% style="color:#2ecc71" %)Constraint(%%) cannot be less restrictive than the (% style="color:#2ecc71" %)Constraint(%%) specified at the higher (% style="color:#2ecc71" %)level(%%).
141 +* The (% style="color:#2ecc71" %)Constraint(%%) at the lower (% style="color:#2ecc71" %)level(%%) for any one [[Member Selection>>doc:xwiki:Glossary.Member selection.WebHome]] further constrains the keys specified at the higher (% style="color:#2ecc71" %)level(%%)(s).
142 +* Any [[Member Selection>>doc:xwiki:Glossary.Member selection.WebHome]], which is not referenced in a (% style="color:#2ecc71" %)Constraint(%%), is deemed to be constrained according to the (% style="color:#2ecc71" %)Constraint(%%) specified at the next higher (% style="color:#2ecc71" %)level(%%) which (% style="color:#2ecc71" %)constraints(%%) that [[Member Selection>>doc:xwiki:Glossary.Member selection.WebHome]].
143 +* If there is a conflict when resolving the keys in the (% style="color:#2ecc71" %)Constraint(%%) at two (% style="color:#2ecc71" %)levels(%%), in terms of a lower-(% style="color:#2ecc71" %)level(%%) (% style="color:#2ecc71" %)constraint(%%) being less restrictive than a higher-(% style="color:#2ecc71" %)level(%%) (% style="color:#2ecc71" %)Constraint(%%), then the offending keys specified at the lower (% style="color:#2ecc71" %)level(%%) are not deemed part of the (% style="color:#2ecc71" %)Constraint(%%).
144 144  
145 -Note that a Key in a Key Set can have wildcarded Components. For instance, the Constraint may simply constrain the Dimension FREQ to "A", and all keys where the FREQ="A" are therefore valid.
145 +Note that a Key in a Key Set can have wildcarded [[Components>>doc:xwiki:Glossary.Component.WebHome]]. For instance, the (% style="color:#2ecc71" %)Constraint(%%) may simply constrain the [[Dimension>>doc:xwiki:Glossary.Dimension.WebHome]] FREQ to "A", and all keys where the FREQ="A" are therefore valid.
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 -*
150 -*1. Determine all possible keys that are valid at the higher level.
151 -*1. These keys are deemed to be inherited by the lower-level constrained object, subject to the Constraints specified at the lower level.
152 -*1. Determine all possible keys that are possible using the Constraints specified at the lower level.
153 -*1. At the lower level inherit all keys that match with the higher-level Constraint.
154 -*1. If there are keys in the lower-level Constraint that are not inherited then the key is invalid (i.e., it is less restrictive).
149 +*
150 +*1. Determine all possible keys that are valid at the higher (% style="color:#2ecc71" %)level(%%).
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 +*1. Determine all possible keys that are possible using the (% style="color:#2ecc71" %)Constraints(%%) specified at the lower (% style="color:#2ecc71" %)level(%%).
153 +*1. At the lower (% style="color:#2ecc71" %)level(%%) inherit all keys that match with the higher-(% style="color:#2ecc71" %)level(%%) (% style="color:#2ecc71" %)Constraint(%%).
154 +*1. If there are keys in the lower-(% style="color:#2ecc71" %)level(%%) (% style="color:#2ecc71" %)Constraint(%%) that are not inherited then the key is invalid (i.e., it is less restrictive).
155 155  
156 156  === 10.3.4 Constraints Examples ===
157 157  
... ... @@ -159,7 +159,7 @@
159 159  
160 160  The following scenario is used.
161 161  
162 -A DSD contains the following Dimensions:
162 +A [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]] contains the following [[Dimensions>>doc:xwiki:Glossary.Dimension.WebHome]]:
163 163  
164 164  * GEO – Geography
165 165  * SEX – Sex
... ... @@ -166,7 +166,7 @@
166 166  * AGE – Age
167 167  * CAS – Current Activity Status
168 168  
169 -In the DSD, common code lists are used and the requirement is to restrict these at various levels to specify the actual code that are valid for the object to which the Constraint is attached.
169 +In the [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]], common [[code lists>>doc:xwiki:Glossary.Code list.WebHome]] are used and the requirement is to restrict these at various (% style="color:#2ecc71" %)levels(%%) to specify the actual [[code>>doc:xwiki:Glossary.Code.WebHome]] that are valid for the object to which the (% style="color:#2ecc71" %)Constraint(%%) is attached.
170 170  
171 171  [[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_77bea5e.png||height="344" width="554"]]
172 172  
... ... @@ -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  
... ... @@ -337,22 +337,18 @@
337 337  ===== 10.3.4.2.9 Use Case 9: A Constraint on allowed values for Dimensions combined with allowed values for Metadata Attributes =====
338 338  
339 339  R1: Allow monthly and quarterly data
340 -
341 341  R2: Allow Mexico for vis-à-vis country
342 -
343 343  R3: Allow John Doe for contact
344 344  
345 345  This may be expressed with the following CubeRegion:
346 346  
347 -|FREQ|M, Q
348 -|VIS_CTY|MX
349 -|CONTACT|John Doe
345 +[[image:1747387514061-293.png]]
350 350  
351 351  ==== 10.3.4.3 Other constraining terms ====
352 352  
353 353  Beyond the cube regions and keysets, there is one more constraining term, i.e., the ReleaseCalendar.
354 354  
355 -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.
356 356  
357 357  For example, the ReleaseCalendar for Provider BIS, is specified in the three following terms:
358 358  
... ... @@ -362,4 +362,4 @@
362 362  
363 363  With the above terms, BIS would need to report data between the 10^^th^^ and 15^^th^^ of every month.
364 364  
365 -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.
1747387514061-293.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +6.3 KB
Content