Skip to Content
Last modified by Artur K. on 2026/05/29 14:28
From version 2.1
edited by Helena K.
on 2026/01/27 12:56
Change comment: There is no comment for this version
To version 2.6
edited by Helena K.
on 2026/01/27 13:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,12 +4,12 @@
4 4  
5 5  = Document History =
6 6  
7 -|Version|Date|Comment
8 -|1.0|21/8/2015|Initial version.
9 -|2.0|7/3/2018|(((
7 +(% style="width:1039.96px" %)
8 +|Version|(% style="width:110px" %)Date|(% style="width:856px" %)Comment
9 +|1.0|(% style="width:110px" %)21/8/2015|(% style="width:856px" %)Initial version.
10 +|2.0|(% style="width:110px" %)7/3/2018|(% style="width:856px" %)(((
10 10  Replaced the “Embargo: Privileged access” use case confidentiality status to use CONF_STATUS:E instead of CONF_STATUS:N. When this guideline is implemented, the CONF_STATUS:N can no longer be used for this use case (the embargo time is ignored if the CONF_STATUS is N).
11 11  
12 -
13 13  Clarified the document text, removed superfluous text.
14 14  
15 15  Added use of time zone is recommended.
... ... @@ -17,7 +17,7 @@
17 17  
18 18  = Introduction =
19 19  
20 -This paper presents use case scenarios related to confidentiality and embargo in SDMX data exchanges, and provides recommendations on how to represent these elements in the SDMX model. The aim is to provide a consistent and practical way to represent these aspects in SDMX artefacts in order to promote cross-domain consistency, and harmonise methodology and processes.
20 +This paper presents use case scenarios related to confidentiality and embargo in SDMX data exchanges, and provides recommendations on how to represent these elements in the SDMX model. The aim is to provide a consistent and practical way to represent these aspects in SDMX artefacts in order to promote cross-domain consistency, and harmonise methodology and processes.
21 21  
22 22  Confidentiality aims at protecting data from unauthorised disclosure that could be prejudicial or harmful to the interest of the source or other relevant parties.
23 23  
... ... @@ -35,7 +35,7 @@
35 35  
36 36  = Use Cases =
37 37  
38 -This section describes the confidentiality and embargo use cases that are addressed by these guidelines.  The use cases and embargo SDMX representations are summarised in annex 1:
38 +This section describes the confidentiality and embargo use cases that are addressed by these guidelines. The use cases and embargo SDMX representations are summarised in annex 1:
39 39  
40 40  == Use case 1: Non-confidential data ==
41 41  
... ... @@ -43,30 +43,30 @@
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  
54 54  === Exchange of confidential data without embargo nor forwarding to secondary recipients ===
55 55  
56 -One or more observations in the data message are confidential. Embargo does not play a role in this scenario. Depending on arrangements between data exchange partners, this data can be made available to privileged data users.
56 +One or more observations in the data message are confidential. Embargo does not play a role in this scenario. Depending on arrangements between data exchange partners, this data can be made available to privileged data users.
57 57  
58 -The observation’s CONF_STATUS attribute should use a specific code denoting the confidential character of the information.  Below are some examples of such confidentiality statuses{{footnote}}For a full list of confidentiality statuses, see https://sdmx.org/wp-content/uploads/CL_CONF_STATUS_1_2_2018.docx{{/footnote}}:
58 +The observation’s CONF_STATUS attribute should use a specific code denoting the confidential character of the information. Below are some examples of such confidentiality statuses{{footnote}}For a full list of confidentiality statuses, see https://sdmx.org/wp-content/uploads/CL_CONF_STATUS_1_2_2018.docx{{/footnote}}:
59 59  
60 -* **N**:   Not for publication, restricted for internal use only.  Used to denote observations that are restricted for internal use only within organisations
61 -* **C**:   Confidential statistical information (primary confidentiality) due to identifiable respondents
62 -* **D**:   Secondary confidentiality set by the sender, not for publication
63 -* **A**:   Primary confidentiality due to small counts
60 +* **N**: Not for publication, restricted for internal use only. Used to denote observations that are restricted for internal use only within organisations
61 +* **C**: Confidential statistical information (primary confidentiality) due to identifiable respondents
62 +* **D**: Secondary confidentiality set by the sender, not for publication
63 +* **A**: Primary confidentiality due to small counts
64 64  
65 65  === Forwarding confidential data to secondary recipients ===
66 66  
67 67  A sender sends confidential data to certain primary recipients, and allows those to forward the confidential data to a restricted and pre-defined set of secondary recipients.
68 68  
69 -The observation’s CONF_STATUS attribute should be marked as “Not for publication, restricted for internal use only”.  An additional observation-level attribute: CONF_REDIST, defines the secondary recipient(s) to whom the sender allows the primary recipient to forward confidential data{{footnote}}Example: National statistical institute XX reporting data to Eurostat indicates that Eurostat can forward those data to the ECB, IMF and OECD.  More complex use case: The reporting organization specifies that Eurostat can forward those data only to the ECB Statistics Department, thus excluding all other organisations as well as all other ECB departments.{{/footnote}}.  See section **Use of the CONF_REDIST attribute** for the appropriate coding of this attribute.
69 +The observation’s CONF_STATUS attribute should be marked as “Not for publication, restricted for internal use only”. An additional observation-level attribute: CONF_REDIST, defines the secondary recipient(s) to whom the sender allows the primary recipient to forward confidential data{{footnote}}Example: National statistical institute XX reporting data to Eurostat indicates that Eurostat can forward those data to the ECB, IMF and OECD.  More complex use case: The reporting organization specifies that Eurostat can forward those data only to the ECB Statistics Department, thus excluding all other organisations as well as all other ECB departments.{{/footnote}}. See section **Use of the CONF_REDIST attribute** for the appropriate coding of this attribute.
70 70  
71 71  The forwarding of confidential data is represented as follows in SDMX:
72 72  
... ... @@ -99,7 +99,7 @@
99 99  * **EMBARGO**_**TIME** (Observation, Conditional): [timestamp]
100 100  )))
101 101  
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.
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  
104 104  These two examples represent the same time for a recipient established in the Central European time zone (e.g. Germany, Norway, Gibraltar):
105 105  
... ... @@ -108,11 +108,11 @@
108 108  
109 109  **//Enabling the frontloading of data into systems//**
110 110  
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. 
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  
113 113  Once the EmbargoDate in the header elapses, each observation’s confidentiality status becomes that which is marked in the CONF_STATUS attributes.
114 114  
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.
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 117  |(((
118 118  (% class="wikigeneratedid" id="HSDMXRepresentation" %)
... ... @@ -121,19 +121,19 @@
121 121  * **CONF_STATUS**: <Set to the required confidentiality status after the embargo time elapses>; <Header>\<EmbargoDate>: [timestamp]
122 122  )))
123 123  
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.
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  
126 126  = Additional recommendations and examples =
127 127  
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).
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 130  === Use of the CONF_REDIST attribute ===
131 131  
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:
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 134  Use a code that represents multiple organisations, or;
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.
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 137  
138 138  If the EMBARGO_TIME and CONF_REDIST attributes are both used:
139 139  
... ... @@ -177,7 +177,7 @@
177 177  
178 178  **EMBARGO_TIME=<**T+1 day**, **e.g.** **2017-12-15T10:00:00Z>
179 179  
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.
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  
... ... @@ -218,7 +218,7 @@
218 218  
219 219  )))|(((
220 220  (% class="wikigeneratedid" id="HCONF_STATUSwillusuallybeCbutmayalsobeD3BS3BA3BO3BT3BG3BM3BNdependingontherequiredstatusandconfidentialityreason.A0SeetheCL_CONF_STATUScodelistfordetails5B35D" %)
221 -CONF_STATUS will usually be C but may also be D;S;A;O;T;G;M;N depending on the required status and confidentiality reason.  See the CL_CONF_STATUS code list for details{{footnote}}https://sdmx.org/wp-content/uploads/CL_CONF_STATUS_1_2_2018.docx{{/footnote}}
221 +CONF_STATUS will usually be C but may also be D;S;A;O;T;G;M;N depending on the required status and confidentiality reason. See the CL_CONF_STATUS code list for details{{footnote}}https://sdmx.org/wp-content/uploads/CL_CONF_STATUS_1_2_2018.docx{{/footnote}}
222 222  )))
223 223  |(((
224 224  **Forwarding of confidential data**
... ... @@ -254,7 +254,7 @@
254 254  CONF_REDIST: (Observation, Conditional)
255 255  )))|(((
256 256  (% class="wikigeneratedid" id="HOnlytheobservationswithanEMBARGO_TIMEattributeareembargoed.Aftertheembargotimeelapses2Cthedataarefreeforpublication28equivalenttoFstatus29." %)
257 -Only the observations with an EMBARGO_TIME attribute are embargoed. After the embargo time elapses, the data are free for publication (equivalent to F status).
257 +Only the observations with an EMBARGO_TIME attribute are embargoed. After the embargo time elapses, the data are free for publication (equivalent to F status).
258 258  
259 259  (% class="wikigeneratedid" id="HCONF_REDISTmayrepresentmultipleorganisations" %)
260 260  CONF_REDIST may represent multiple organisations
© Semantic R&D Group, 2026