Skip to Content

Changes for page 10 Constraints

Last modified by Helena on 2025/09/10 11:19
From version 5.1
edited by Helena
on 2025/05/15 15:48
Change comment: There is no comment for this version
To version 15.2
edited by Helena
on 2025/05/17 00:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,41 +1,43 @@
1 -= 10 Constraints =
1 +{{box title="**Contents**"}}
2 +{{toc/}}
3 +{{/box}}
2 2  
3 3  == 10.1 Introduction ==
4 4  
5 -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:
6 6  
7 7  * Data Structure Definition
8 8  * Metadata Structure Definition
9 -* Dataflow
10 -* Metadataflow
11 -* Provision Agreement
12 -* Metadata Provision Agreement
13 -* 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(%%))
14 14  * Simple or Queryable Data Sources
15 15  * Dataset
16 16  * Metadataset
17 17  
18 -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]].
19 19  
20 20  == 10.2 Types of Constraint ==
21 21  
22 -The Constraint can be of one of two types:
24 +The (% style="color:#2ecc71" %)Constraint(%%) can be of one of two types:
23 23  
24 -* Data constraint
25 -* Metadata constraint
26 +* Data (% style="color:#2ecc71" %)constraint
27 +* Metadata (% style="color:#2ecc71" %)constraint
26 26  
27 -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:
28 28  
29 -* Allowed constraint
30 -* Actual constraint
31 +* Allowed (% style="color:#2ecc71" %)constraint
32 +* Actual (% style="color:#2ecc71" %)constraint
31 31  
32 -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).
33 33  
34 -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:
35 35  
36 36  * They can only be retrieved by the availability requests (as specified in the REST API).
37 -* They depend on the data available in an SDMX Web Service and thus they can only be dynamically generated according to that data.
38 -* 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).
39 39  * Their identifier may also be dynamically generated and thus there is no REST resource based on their identification.
40 40  
41 41  == 10.3 Rules for a Constraint ==
... ... @@ -42,132 +42,136 @@
42 42  
43 43  === 10.3.1 Scope of a Constraint ===
44 44  
45 -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.
46 46  
47 -In terms of data the components are:
49 +In terms of data the [[components>>doc:xwiki:Glossary.Component.WebHome]] are:
48 48  
49 -* Dimension
50 -* Time Dimension
51 -* Data Attribute
52 -* Measure
53 -* Metadata Attribute
54 -* 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]].
55 55  
56 -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:
57 57  
58 -* Metadata Attribute
60 +* Metadata [[Attribute>>doc:xwiki:Glossary.Attribute.WebHome]]
59 59  
60 -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:
61 61  
62 62  * Data Structure Definition
63 -* Dataflow
64 -* Provision Agreement
65 -* 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]]
66 66  
67 -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:
68 68  
69 69  * Metadata Structure Definition
70 -* Metadataflow
71 -* Metadata Provision Agreement
72 +* [[Metadataflow>>doc:xwiki:Glossary.Metadataflow.WebHome]]
73 +* Metadata [[Provision Agreement>>doc:xwiki:Glossary.Provision agreement.WebHome]]
72 72  * Metadata Provider
73 73  * Metadata Set
74 74  
75 -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]].
76 76  
77 -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.
78 78  
79 79  === 10.3.2 Multiple Constraints ===
80 80  
81 -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:
82 82  
83 -**10.3.2.1 Cube Region**
85 +==== 10.3.2.1 Cube Region ====
84 84  
85 -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]]).
86 86  
87 -* 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).
88 -* Component values within a Member Selection may define a validity period. Otherwise, the value is valid for the whole validity of the Cube Region.
89 -* For partial reference resolution purposes (as per the SDMX REST API), the latest non-draft Constraint must be considered.
90 -* 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.
91 -* 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.
92 92  
93 -**10.3.2.2 Key Set**
95 +==== 10.3.2.2 Key Set ====
94 94  
95 -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").
96 96  
97 -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.
98 98  
99 -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.
100 100  
101 101  Finally, a validity period may be specified per Key.
102 102  
103 103  === 10.3.3 Inheritance of a Constraint ===
104 104  
105 -**10.3.3.1 Attachment levels of a Constraint**
107 +==== 10.3.3.1 Attachment levels of a Constraint ====
106 106  
107 -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:
108 108  
109 -• 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
110 110  
111 -▪ Provision Agreement – third level
113 +▪ [[Provision Agreement>>doc:xwiki:Glossary.Provision agreement.WebHome]] – third (% style="color:#2ecc71" %)level
112 112  
113 -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]]).
114 114  
115 -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]].
116 116  
117 -**10.3.3.2 Cascade rules for processing Constraints**
119 +==== 10.3.3.2 Cascade rules for processing Constraints ====
118 118  
119 -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.
120 120  
121 -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(%%).
122 122  
123 -**10.3.3.3 Cube Region**
125 +==== 10.3.3.3 Cube Region ====
124 124  
125 -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:
126 126  
127 -* 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.
128 -* 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).
129 -* 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.
130 -* 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.
131 131  
132 -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(%%).
133 133  
134 -**10.3.3.4 Key Set**
136 +==== 10.3.3.4 Key Set ====
135 135  
136 -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:
137 137  
138 -* The lower-level Constraint cannot be less restrictive than the Constraint specified at the higher level.
139 -* The Constraint at the lower level for any one Member Selection further constrains the keys specified at the higher level(s).
140 -* 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.
141 -* 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(%%).
142 142  
143 -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.
144 144  
145 145  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.
146 146  
147 147  *
148 -*1. Determine all possible keys that are valid at the higher level.
149 -*1. These keys are deemed to be inherited by the lower-level constrained object, subject to the Constraints specified at the lower level.
150 -*1. Determine all possible keys that are possible using the Constraints specified at the lower level.
151 -*1. At the lower level inherit all keys that match with the higher-level Constraint.
152 -*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).
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).
153 153  
154 154  === 10.3.4 Constraints Examples ===
155 155  
156 -**10.3.4.1 Data Constraint and Cascading **The following scenario is used.
158 +==== 10.3.4.1 Data Constraint and Cascading ====
157 157  
158 -A DSD contains the following Dimensions:
160 +The following scenario is used.
159 159  
162 +A [[DSD>>doc:xwiki:Glossary.Data structure definition.WebHome]] contains the following [[Dimensions>>doc:xwiki:Glossary.Dimension.WebHome]]:
163 +
160 160  * GEO – Geography
161 161  * SEX – Sex
162 162  * AGE – Age
163 163  * CAS – Current Activity Status
164 164  
165 -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.
166 166  
167 167  [[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_77bea5e.png||height="344" width="554"]]
168 168  
169 -**Figure 20: Example Scenario for Constraints **Constraints are declared as follows:
173 +**Figure 20: Example Scenario for Constraints **
170 170  
175 +Constraints are declared as follows:
176 +
171 171  [[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_7c36c475.png||height="356" width="541"]]
172 172  
173 173  **Figure 21: Example Constraints**
... ... @@ -209,217 +209,79 @@
209 209  
210 210  DSD Constraint
211 211  
212 -**<str:DataConstraint agencyID="SDMX" id="DATA_CONSTRAINT" version="1.0.0draft" type="Allowed">**
218 +[[image:1747386911707-332.png]]
213 213  
214 -**<com:Name xml:lang="en">SDMX 3.0 Data Constraint sample</com:Name>**
215 -
216 -**<str:ConstraintAttachment>**
217 -
218 -**<str:DataStructure>urn:sdmx:org.sdmx.infomodel.datastructure.**
219 -
220 -**DataStructure=CENSUSHUB:CENSUS(1.0.0)</str:DataStructure>**
221 -
222 -**</str:ConstraintAttachment>**
223 -
224 -**<str:CubeRegion include="true">**
225 -
226 -**<!~-~- the ability to exclude values is illustrated – i.e., all values valid except this one ~-~->**
227 -
228 -**<com:KeyValue id="AGE" include="false">**
229 -
230 -**<com:Value>001</com:Value>**
231 -
232 -**</com:KeyValue>**
233 -
234 -**</str:CubeRegion>**
235 -
236 -**</str:DataConstraint>**
237 -
238 238  Dataflow Constraints
239 239  
240 -**<str:DataConstraint agencyID="SDMX" id="DATA_CONSTRAINT_2" version="1.0.0draft" type="Allowed">**
222 +[[image:1747386933952-158.png]]
241 241  
242 -**<com:Name xml:lang="en">SDMX 3.0 Data Constraint sample</com:Name>**
224 +[[image:1747386970127-658.png]]
243 243  
244 -**<str:ConstraintAttachment>**
245 -
246 -**<str:Dataflow>urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=**
247 -
248 -**CENSUSHUB:CENSUS_CUBE1(1.0.0)</str:Dataflow>**
249 -
250 -**</str:ConstraintAttachment>**
251 -
252 -**<str:CubeRegion include="true">**
253 -
254 -**<com:KeyValue id="AGE" include="true">**
255 -
256 -**<com:Value>002</com:Value>**
257 -
258 -**<com:Value>003</com:Value>**
259 -
260 -**</com:KeyValue>**
261 -
262 -**<com:KeyValue id="CAS">**
263 -
264 -**<com:Value>003</com:Value>**
265 -
266 -**<com:Value>004</com:Value>**
267 -
268 -**</com:KeyValue>**
269 -
270 -**</str:CubeRegion>**
271 -
272 -**</str:DataConstraint>**
273 -
274 -**<str:DataConstraint agencyID="SDMX" id="DATA_CONSTRAINT_3" version="1.0.0draft" type="Allowed">**
275 -
276 -**<com:Name xml:lang="en">SDMX 3.0 Data Constraint sample</com:Name>**
277 -
278 -**<str:ConstraintAttachment>**
279 -
280 -**<str:Dataflow>urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=**
281 -
282 -**CENSUSHUB:CENSUS_CUBE2(1.0.0)</str:Dataflow>**
283 -
284 -**</str:ConstraintAttachment>**
285 -
286 -**<str:CubeRegion include="true">**
287 -
288 -**<com:KeyValue id="CAS" include="true">**
289 -
290 -**<com:Value>TOT</com:Value>**
291 -
292 -**<com:Value>NAP</com:Value>**
293 -
294 -**</com:KeyValue>**
295 -
296 -**</str:CubeRegion>**
297 -
298 -**</str:DataConstraint>**
299 -
300 300  Provision Agreement Constraint
301 301  
302 -**<str:DataConstraint agencyID="SDMX" id="DATA_CONSTRAINT_4" version="1.0.0draft" type="Allowed">**
228 +[[image:1747386991329-805.png]]
303 303  
304 -**<com:Name xml:lang="en">SDMX 3.0 Data Constraint sample</com:Name>**
230 +==== 10.3.4.2 Combination of Constraints ====
305 305  
306 -**<str:ConstraintAttachment>**
307 -
308 -**<str:ProvisionAgreement>urn:sdmx:org.sdmx.infomodel.registry.**
309 -
310 -**ProvisionAgreement=CENSUSHUB:CENSUS_CUBE1_IT(1.0.0)**
311 -
312 -**</str:ProvisionAgreement>**
313 -
314 -**<str:ProvisionAgreement>urn:sdmx:org.sdmx.infomodel.registry.**
315 -
316 -**ProvisionAgreement=CENSUSHUB:CENSUS_CUBE2_IT(1.0.0)**
317 -
318 -**</str:ProvisionAgreement>**
319 -
320 -**</str:ConstraintAttachment>**
321 -
322 -**<str:CubeRegion include="true">**
323 -
324 -**<com:KeyValue id="GEO" include="true">**
325 -
326 -**<com:Value cascadeValues="true">IT</com:Value>**
327 -
328 -**</com:KeyValue>**
329 -
330 -**</str:CubeRegion>**
331 -
332 -**</str:DataConstraint**
333 -
334 -**10.3.4.2 Combination of Constraints**
335 -
336 336  The possible combination of constraining terms are explained in this section, following a few examples.
337 337  
338 338  Let’s assume a DSD with the following Components:
339 339  
340 -|Dimension|FREQ
341 -|Dimension|JD_TYPE
342 -|Dimension|JD_CATEGORY
343 -|Dimension|VIS_CTY
344 -|TimeDimension|TIME_PERIOD
345 -|Attribute|OBS_STATUS
346 -|Attribute|UNIT
347 -|Attribute|COMMENT
348 -|MetadataAttribute|CONTACT
349 -|Measure|MULTISELECT
350 -|Measure|CHOICE
236 +[[image:1747387057775-838.png]]
351 351  
238 +[[image:1747387089210-741.png]]
239 +
352 352  On the above, let’s assume the following use cases with their constraining requirements:
353 353  
354 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_6b13e05d.png||height="12" width="62"]] //**Use Case 1: A Constraint on allowed values for some Dimensions**//
242 +===== 10.3.4.2.1 Use Case 1: A Constraint on allowed values for some Dimensions =====
355 355  
356 356  R1: Allow monthly and quarterly data
357 -
358 358  R2: Allow Mexico for vis-à-vis country
359 359  
360 360  This is expressed with the following CubeRegion:
361 361  
362 -|FREQ|M, Q
363 -|VIS_CTY|MX
249 +[[image:1747387154981-708.png]]
364 364  
365 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_18c3726e.png||height="12" width="64"]] //**Use Case 2: A Constraint on allowed combinations for some Dimensions**//
251 +===== 10.3.4.2.2 Use Case 2: A Constraint on allowed combinations for some Dimensions =====
366 366  
367 367  R1: Allow monthly data for Germany
368 -
369 369  R2: Allow quarterly data for Mexico
370 370  
371 371  This is expressed with the following DataKeySet:
372 372  
373 -|(% rowspan="2" %)Key1|FREQ|M
374 -|VIS_CTY|DE
375 -|(% rowspan="2" %)Key2|FREQ|Q
376 -|VIS_CTY|MX
258 +[[image:1747387188821-467.png]]
377 377  
378 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_8d48dc1a.png||height="12" width="64"]] //**Use Case 3: A Constraint on allowed values for some Dimensions combined with allowed values for some Attributes**//
260 +===== 0.3.4.2.3 Use Case 3: A Constraint on allowed values for some Dimensions combined with allowed values for some Attributes =====
379 379  
380 380  R1: Allow monthly and quarterly data
381 -
382 382  R2: Allow Mexico for vis-à-vis country
383 -
384 384  R3: Allow present for status
385 385  
386 386  This may be expressed with the following CubeRegion:
387 387  
388 -|FREQ|M, Q
389 -|VIS_CTY|MX
390 -|OBS_STATUS|A
268 +[[image:1747387231598-634.png]]
391 391  
392 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_a0d353e8.png||height="12" width="64"]] //**Use Case 4: A Constraint on allowed combinations for some**//
270 +===== 10.3.4.2.4 Use Case 4: A Constraint on allowed combinations for some =====
393 393  
394 394  //**Dimensions combined with specific Attribute values**//
395 395  
396 396  R1: Allow monthly data, for Germany, with unit euro
397 -
398 398  R2: Allow quarterly data, for Mexico, with unit usd
399 399  
400 400  This is may be expressed with the following DataKeySet:
401 401  
402 -|(% rowspan="3" %)Key1|FREQ|M
403 -|VIS_CTY|DE
404 -|UNIT|EUR
405 -|(% rowspan="3" %)Key2|FREQ|Q
406 -|VIS_CTY|MX
407 -|UNIT|USD
279 +[[image:1747387252077-954.png]]
408 408  
409 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_6e97b73c.png||height="12" width="64"]] //**Use Case 5: A Constraint on allowed values for some Dimensions together with some combination of Dimension values**//
281 +[[image:1747387281625-859.png]]
410 410  
411 -R1: For annually and quarterly data, for Mexico and Germany, only A status is allowed
283 +===== 10.3.4.2.5 Use Case 5: A Constraint on allowed values for some Dimensions together with some combination of Dimension values =====
412 412  
285 +R1: For annually and quarterly data, for Mexico and Germany, only A status is allowed
413 413  R2: For monthly data, for Mexico and Germany, only F status is allowed
414 414  
415 415  Considering the above examples, the following CubeRegions would be created:
416 416  
417 -|(% rowspan="3" %)CubeRegion1|FREQ|Q, A
418 -|VIS_CTY|MX, DE
419 -|OBS_STATUS|A
420 -|(% rowspan="3" %)CubeRegion2|FREQ|M
421 -|VIS_CTY|MX, DE
422 -|OBS_STATUS|F
290 +[[image:1747387330751-405.png]]
423 423  
424 424  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).
425 425  
... ... @@ -427,81 +427,56 @@
427 427  
428 428  DSD CubeRegion:
429 429  
430 -|FREQ|M, Q, A
431 -|VIS_CTY|MX, DE
432 -|OBS_STATUS|A, F
298 +[[image:1747387369822-932.png]]
433 433  
434 434  Dataflow1 CubeRegion:
435 435  
436 -|FREQ|Q, A
437 -|VIS_CTY|MX, DE
438 -|OBS_STATUS|F
302 +[[image:1747387387944-676.png]]
439 439  
440 440  Dataflow2 CubeRegion:
441 441  
442 -|FREQ|M
443 -|VIS_CTY|MX, DE
444 -|OBS_STATUS|A
306 +[[image:1747387401689-306.png]]
445 445  
446 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_b4693e0d.png||height="12" width="64"]] //**Use case 6: A Constraint on allowed values for some Dimensions combined with allowed values for Measures**//
308 +===== 10.3.4.2.6 Use case 6: A Constraint on allowed values for some Dimensions combined with allowed values for Measures =====
447 447  
448 448  R1: Allow monthly data, for Germany, with unit euro, and measure choice is 'A'
449 -
450 450  R2: Allow quarterly data, for Mexico, with unit usd, and measure choice is 'B' This is may be expressed with the following DataKeySet:
451 451  
452 -|(% rowspan="4" %)Key1|FREQ|M
453 -|VIS_CTY|DE
454 -|UNIT|EUR
455 -|CHOICE|A
456 -|(% rowspan="4" %)Key2|FREQ|Q
457 -|VIS_CTY|MX
458 -|UNIT|USD
459 -|CHOICE|B
313 +[[image:1747387437317-733.png]]
460 460  
461 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_9818c7f7.png||height="12" width="64"]] //**Use Case 7: A Constraint with wildcards for Codes and removePrefix property**//
315 +===== 10.3.4.2.7 Use Case 7: A Constraint with wildcards for Codes and removePrefix property =====
462 462  
463 463  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.
464 464  
465 465  R1: Allow monthly and quarterly data
466 -
467 467  R2: Allow vis-à-vis countries that start with M
468 -
469 469  R3: Remove the prefix ‘AREA_’
470 470  
323 +[[image:1747387461703-763.png]]
324 +
471 471  This may be expressed with the following CubeRegion:
472 472  
473 -|FREQ|M, Q
474 -|VIS_CTY (removePrefix=’AREA_’)|M%
327 +===== 10.3.4.2.8 Use Case 8: A Constraint with multilingual support on Attributes =====
475 475  
476 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_7df2eea7.png||height="12" width="64"]] //**Use Case 8: A Constraint with multilingual support on Attributes**//
477 -
478 478  R1: Allow monthly and quarterly data
479 -
480 480  R2: Allow Mexico for vis-à-vis country
481 -
482 482  R3: Allow a comment, in English, which includes the term adjusted for status
483 483  
484 484  This may be expressed with the following CubeRegion:
485 485  
486 -|FREQ|M, Q
487 -|VIS_CTY|MX
488 -|COMMENT (lang=’en’)|%adjusted%
335 +[[image:1747387484366-337.png]]
489 489  
490 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_7e57ad28.png||height="12" width="64"]] //**Use Case 9: A Constraint on allowed values for Dimensions combined with allowed values for Metadata Attributes**//
337 +===== 10.3.4.2.9 Use Case 9: A Constraint on allowed values for Dimensions combined with allowed values for Metadata Attributes =====
491 491  
492 492  R1: Allow monthly and quarterly data
493 -
494 494  R2: Allow Mexico for vis-à-vis country
495 -
496 496  R3: Allow John Doe for contact
497 497  
498 498  This may be expressed with the following CubeRegion:
499 499  
500 -|FREQ|M, Q
501 -|VIS_CTY|MX
502 -|CONTACT|John Doe
345 +[[image:1747387514061-293.png]]
503 503  
504 -**10.3.4.3 Other constraining terms**
347 +==== 10.3.4.3 Other constraining terms ====
505 505  
506 506  Beyond the cube regions and keysets, there is one more constraining term, i.e., the ReleaseCalendar.
507 507  
1747386911707-332.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +47.1 KB
Content
1747386933952-158.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +35.3 KB
Content
1747386970127-658.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +59.4 KB
Content
1747386991329-805.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +56.5 KB
Content
1747387057775-838.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +13.1 KB
Content
1747387089210-741.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +8.3 KB
Content
1747387135817-339.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +3.8 KB
Content
1747387154981-708.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +3.8 KB
Content
1747387188821-467.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +8.2 KB
Content
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
1747387369822-932.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +6.9 KB
Content
1747387387944-676.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +6.2 KB
Content
1747387401689-306.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +6.0 KB
Content
1747387437317-733.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +13.9 KB
Content
1747387461703-763.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +6.5 KB
Content
1747387484366-337.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +9.0 KB
Content
1747387514061-293.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +6.3 KB
Content
SDMX 3-0-0 SECTION 6 FINAL-1.0_en_18c3726e.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +1.7 KB
Content
SDMX 3-0-0 SECTION 6 FINAL-1.0_en_6b13e05d.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +1.5 KB
Content
SDMX 3-0-0 SECTION 6 FINAL-1.0_en_6e97b73c.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +1.7 KB
Content
SDMX 3-0-0 SECTION 6 FINAL-1.0_en_7e57ad28.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +1.7 KB
Content
SDMX 3-0-0 SECTION 6 FINAL-1.0_en_8d48dc1a.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +1.7 KB
Content
SDMX 3-0-0 SECTION 6 FINAL-1.0_en_9818c7f7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +1.6 KB
Content
SDMX 3-0-0 SECTION 6 FINAL-1.0_en_a0d353e8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +1.6 KB
Content
SDMX 3-0-0 SECTION 6 FINAL-1.0_en_b4693e0d.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +1.7 KB
Content