Changes for page Guidelines for Confidentiality and Embargo in SDMX

Summary

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

Details

Page properties

Content

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