Changes for page Guidelines for Confidentiality and Embargo in SDMX

Summary

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

Details

Page properties

Content

...	...	@@ -91,12 +91,13 @@
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		-{{box}}
95		-**SDMX representation**
	94	+|(((
	95	+(% class="wikigeneratedid" id="HSDMXrepresentation-2" %)
	96	+SDMX representation
96	96
97	97	* **CONF_STATUS**: E;
98	98	* **EMBARGO**_**TIME** (Observation, Conditional): [timestamp]
99		-{{/box}}
	100	+)))
100	100
101	101	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	102
...	...	@@ -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//** ===
	109	+**//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
...	...	@@ -113,11 +113,12 @@
113	113
114	114	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	115
116		-{{box}}
	117	+|(((
	118	+(% class="wikigeneratedid" id="HSDMXRepresentation" %)
117	117	SDMX Representation
118	118
119	119	* **CONF_STATUS**: <Set to the required confidentiality status after the embargo time elapses>; <Header>\<EmbargoDate>: [timestamp]
120		-{{/box}}
	122	+)))
121	121
122	122	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.
123	123