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

Summary

Details

Page properties
Content
... ... @@ -43,11 +43,11 @@
43 43  
44 44  The data’s CONF_STATUS attribute should be set to “Free (free for publication)”.
45 45  
46 -|(((
47 -=== SDMX representation ===
46 +{{box}}
47 +**SDMX representation**
48 48  
49 49  * **CONF_STATUS**: F
50 -)))
50 +{{/box}}
51 51  
52 52  == Use case 2: Confidential data ==
53 53  
... ... @@ -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
94 +{{box}}
95 +**SDMX representation**
97 97  
98 98  * **CONF_STATUS**: E;
99 99  * **EMBARGO**_**TIME** (Observation, Conditional): [timestamp]
100 -)))
99 +{{/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//**
108 +=== **//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" %)
116 +{{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 -)))
120 +{{/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  
... ... @@ -276,4 +276,5 @@
276 276  
277 277  ----
278 278  
279 - {{putFootnotes/}}
277 +
278 +{{putFootnotes/}}
© Semantic R&D Group, 2026