Last modified by Artur K. on 2026/05/29 14:28

From version 3.3
edited by Helena K.
on 2026/01/27 13:16
Change comment: There is no comment for this version
To version 3.6
edited by Helena K.
on 2026/01/27 13:18
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  
... ... @@ -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//**
107 +=== //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  
... ... @@ -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 ===
127 +== 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