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

Summary

Details

Page properties
Content
... ... @@ -91,12 +91,13 @@
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 -{{box}}
95 -**SDMX representation**
94 +|(((
95 +(% class="wikigeneratedid" id="HSDMXrepresentation-2" %)
96 +SDMX representation
96 96  
97 97  * **CONF_STATUS**: E;
98 98  * **EMBARGO**_**TIME** (Observation, Conditional): [timestamp]
99 -{{/box}}
100 +)))
100 100  
101 101  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.
102 102  
... ... @@ -105,7 +105,7 @@
105 105  * (Recommended) With UTC indicator: 2017-12-15T14:02:29Z
106 106  * With timezone indicator: 2017-12-15T15:02:29+01:00
107 107  
108 -=== **//Enabling the frontloading of data into systems//** ===
109 +**//Enabling the frontloading of data into systems//**
109 109  
110 110  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.
111 111  
... ... @@ -113,11 +113,12 @@
113 113  
114 114  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.
115 115  
116 -{{box}}
117 +|(((
118 +(% class="wikigeneratedid" id="HSDMXRepresentation" %)
117 117  SDMX Representation
118 118  
119 119  * **CONF_STATUS**: <Set to the required confidentiality status after the embargo time elapses>; <Header>\<EmbargoDate>: [timestamp]
120 -{{/box}}
122 +)))
121 121  
122 122  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.
123 123  
... ... @@ -125,7 +125,7 @@
125 125  
126 126  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).
127 127  
128 -== Use of the CONF_REDIST attribute ==
130 +=== Use of the CONF_REDIST attribute ===
129 129  
130 130  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:
131 131  
© Semantic R&D Group, 2026