Skip to Content
Last modified by Artur K. on 2026/05/29 14:28
From version 3.2
edited by Helena K.
on 2026/01/27 13:15
Change comment: There is no comment for this version
To version 3.8
edited by Helena K.
on 2026/01/27 13:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -70,13 +70,12 @@
70 70  
71 71  The forwarding of confidential data is represented as follows in SDMX:
72 72  
73 -|(((
74 -(% class="wikigeneratedid" id="HSDMXrepresentation-1" %)
75 -SDMX representation
73 +{{box}}
74 +**SDMX representation**
76 76  
77 77  * **CONF_STATUS**: N;
78 78  * **CONF_REDIST **(Observation, Conditional): [Organisation(s)];
79 -)))
78 +{{/box}}
80 80  
81 81  === Adding embargo information to a data message ===
82 82  
... ... @@ -91,13 +91,12 @@
91 91  
92 92  If the goal is to allow the data recipient to have privileged access to embargoed observations in a data message (message), the embargoed observation’s CONF_STATUS attribute should be coded as “E: Not for publication until the embargo time expires; free for publication after the embargo time expires.” with an observation level attribute EMBARGO_TIME (date/time/time zone).
93 93  
94 -|(((
95 -(% class="wikigeneratedid" id="HSDMXrepresentation-2" %)
96 -SDMX representation
93 +{{box}}
94 +**SDMX representation**
97 97  
98 98  * **CONF_STATUS**: E;
99 99  * **EMBARGO**_**TIME** (Observation, Conditional): [timestamp]
100 -)))
98 +{{/box}}
101 101  
102 102  Including a time zone is strongly recommended and the best case is to use the UTC (Coordinated Universal Time) time standard. However, if no time zone is provided then the time zone of the recipient is assumed.
103 103  
... ... @@ -106,7 +106,7 @@
106 106  * (Recommended) With UTC indicator: 2017-12-15T14:02:29Z
107 107  * With timezone indicator: 2017-12-15T15:02:29+01:00
108 108  
109 -**//Enabling the frontloading of data into systems//**
107 +=== //Enabling the frontloading of data into systems// ===
110 110  
111 111  If the goal is to allow frontloading of a whole data message into systems so that the data can be made visible to users at the expiry of the embargo date/time, the header section of the message should contain an embargo date/time attribute. This implies that all information in the data message is under the embargo date/time set in the header. The header attribute EmbargoDate with format date/time/time zone indicates until when the whole data message received cannot be shared with any recipient users.
112 112  
... ... @@ -114,12 +114,11 @@
114 114  
115 115  Note that this scenario presumes that all data in the message cannot be viewed before the header EmbargoDate, and that there is no privileged access before this time. However, observations may be marked with any other confidentiality status that is valid after the frontloading EmbargoDate elapses.
116 116  
117 -|(((
118 -(% class="wikigeneratedid" id="HSDMXRepresentation" %)
115 +{{box}}
119 119  SDMX Representation
120 120  
121 121  * **CONF_STATUS**: <Set to the required confidentiality status after the embargo time elapses>; <Header>\<EmbargoDate>: [timestamp]
122 -)))
119 +{{/box}}
123 123  
124 124  The two ways of representing embargoed data exist to provide efficiency in the exchange, allow for differentiating data intended to be frontloaded and data aimed to be provided in advance to a restricted audience, and provide flexibility when few observations need to be embargoed in a large data message. The trade-off is the complication of system implementation to support the two representations of embargo, which has to be done locally on a case-by-case basis.
125 125  
... ... @@ -127,38 +127,34 @@
127 127  
128 128  In data flows that feature confidential data, CONF_STATUS is highly recommended to be a mandatory attribute. However, if CONF_STATUS is optional in the DSD and missing from an observation, it is always implied to be “F” (free).
129 129  
130 -=== Use of the CONF_REDIST attribute ===
127 +== Use of the CONF_REDIST attribute ==
131 131  
132 132  The CONF_REDIST attribute defines the secondary recipient(s) to whom the sender allows the primary recipient to forward confidential data. It is recommended to be an optional attribute at observation level. Ideally it should reference a shared code list containing standard organisation codes. To allow several secondary recipients there are these possibilities:
133 133  
134 -Use a code that represents multiple organisations, or;
131 +1. Use a code that represents multiple organisations, or;
132 +1. Use several CONF_REDIST attributes to portray the multiple recipients. Each attribute represents one recipient and references the same codelist. This implementation is cleaner than the above point 1, though this will require adding as many attributes to your DSD as there are potential recipients of the redistributed confidential data.
135 135  
136 -Use several CONF_REDIST attributes to portray the multiple recipients. Each attribute represents one recipient and references the same codelist. This implementation is cleaner than the above point 1, though this will require adding as many attributes to your DSD as there are potential recipients of the redistributed confidential data.
137 -
138 138  If the EMBARGO_TIME and CONF_REDIST attributes are both used:
139 139  
140 140  1. Data is available only to the organisations in CONF_REDIST until EMBARGO_TIME
141 141  1. Data is available to the public after EMBARGO_TIME
142 142  
143 -|(% colspan="3" %)(((
139 +(% style="width:768.957px" %)
140 +|(% colspan="3" style="width:766px" %)(((
144 144  (% class="wikigeneratedid" id="HPrivilegedAccess" %)
145 -Privileged Access
142 +**Privileged Access**
146 146  )))
147 -|**Use case**|**No forwarding**|**Forwarding**
148 -|**Embargo**|(((
144 +|(% style="width:202px" %)**Use case**|(% style="width:207px" %)**No forwarding**|(% style="width:357px" %)**Forwarding**
145 +|(% style="width:202px" %)**Embargo**|(% style="width:207px" %)(((
149 149  CONF_STATUS: E
150 -
151 151  EMBARGO_TIME
152 -)))|(((
148 +)))|(% style="width:357px" %)(((
153 153  CONF_STATUS: E
154 -
155 155  EMBARGO_TIME
156 -
157 157  CONF_REDIST
158 158  )))
159 -|**No embargo**|CONF_STATUS: N|(((
153 +|(% style="width:202px" %)**No embargo**|(% style="width:207px" %)CONF_STATUS: N|(% style="width:357px" %)(((
160 160  CONF_STATUS:N
161 -
162 162  CONF_REDIST
163 163  )))
164 164  
... ... @@ -171,17 +171,15 @@
171 171  * The national statistical institutes send data to Eurostat, and allow the data to be shared with the ECB for statistical coproduction
172 172  * The data may only be shared with the public on the next day
173 173  
174 -**CONF_STATUS:**E**;**
167 +* **CONF_STATUS:**E**;**
168 +* **CONF_REDIST: **ECB**;**
169 +* **EMBARGO_TIME=<**T+1 day**, **e.g.** **2017-12-15T10:00:00Z>
175 175  
176 -**CONF_REDIST: **ECB**;**
177 -
178 -**EMBARGO_TIME=<**T+1 day**, **e.g.** **2017-12-15T10:00:00Z>
179 -
180 180  The solutions suggested above aim at covering the most common confidentiality and embargo use cases within a single transmission from the primary reporter to the primary recipient. However, for some more complex scenarios it might still be required to make multiple transmissions.
181 181  
182 182  It is strongly recommended that use cases are specified in an agreement between organisations involved in regular transmissions up-front in order to avoid unnecessary delay in data publication or – much worse – confidentiality breaches.
183 183  
184 -**Annex 1: SDMX Representation of the confidentiality use cases**
175 += Annex 1: SDMX Representation of the confidentiality use cases =
185 185  
186 186  |(((
187 187  (% class="wikigeneratedid" id="HUsecase" %)
© Semantic R&D Group, 2026