Changes for page Guidelines for Confidentiality and Embargo in SDMX

Last modified by Artur K. on 2026/05/29 14:28

From version 3.4

edited by Helena K.
on 2026/01/27 13:17

Change comment: There is no comment for this version

To version 3.5

edited by Helena K.
on 2026/01/27 13:17

Change comment: There is no comment for this version

Summary

Page properties

Content

@@ -125,7 +125,7 @@
  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).
--=== Use of the CONF_REDIST attribute ===
++== Use of the CONF_REDIST attribute ==
  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: