Changes for page Guidelines for Confidentiality and Embargo in SDMX

Summary

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

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