Changes for page Guidelines for Confidentiality and Embargo in SDMX

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -70,12 +70,13 @@
70	70
71	71	The forwarding of confidential data is represented as follows in SDMX:
72	72
73		-{{box}}
74		-**SDMX representation**
	73	+|(((
	74	+(% class="wikigeneratedid" id="HSDMXrepresentation-1" %)
	75	+SDMX representation
75	75
76	76	* **CONF_STATUS**: N;
77	77	* **CONF_REDIST **(Observation, Conditional): [Organisation(s)];
78		-{{/box}}
	79	+)))
79	79
80	80	=== Adding embargo information to a data message ===
81	81
...	...	@@ -90,12 +90,13 @@
90	90
91	91	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).
92	92
93		-{{box}}
94		-**SDMX representation**
	94	+|(((
	95	+(% class="wikigeneratedid" id="HSDMXrepresentation-2" %)
	96	+SDMX representation
95	95
96	96	* **CONF_STATUS**: E;
97	97	* **EMBARGO**_**TIME** (Observation, Conditional): [timestamp]
98		-{{/box}}
	100	+)))
99	99
100	100	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.
101	101
...	...	@@ -104,7 +104,7 @@
104	104	* (Recommended) With UTC indicator: 2017-12-15T14:02:29Z
105	105	* With timezone indicator: 2017-12-15T15:02:29+01:00
106	106
107		-=== //Enabling the frontloading of data into systems// ===
	109	+**//Enabling the frontloading of data into systems//**
108	108
109	109	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.
110	110
...	...	@@ -112,11 +112,12 @@
112	112
113	113	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.
114	114
115		-{{box}}
	117	+|(((
	118	+(% class="wikigeneratedid" id="HSDMXRepresentation" %)
116	116	SDMX Representation
117	117
118	118	* **CONF_STATUS**: <Set to the required confidentiality status after the embargo time elapses>; <Header>\<EmbargoDate>: [timestamp]
119		-{{/box}}
	122	+)))
120	120
121	121	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.
122	122
...	...	@@ -124,7 +124,7 @@
124	124
125	125	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).
126	126
127		-== Use of the CONF_REDIST attribute ==
	130	+=== Use of the CONF_REDIST attribute ===
128	128
129	129	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:
130	130
...	...	@@ -273,5 +273,4 @@
273	273
274	274	----
275	275
276		-
277		-{{putFootnotes/}}
	279	+ {{putFootnotes/}}