Changes for page Standardising Reference Metadata Reporting in SDMX
Last modified by Artur K. on 2026/05/29 14:29
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -179,13 +179,12 @@ 179 179 1. (in an MSD) the associated SDMX artefact type, e.g. Dataset; Dataflow; Provision agreement; 180 180 1. the associated “level” within the artefact, e.g. for a Dataset: Dataset; Series; Observation. 181 181 182 - 183 - 184 184 These are some example attachments, others are possible: 185 185 186 - the “Contact” concept may be attached to a Dataset artefact at the Dataset level; the “Adjustment” concept may be attached to a Dataset artefact at the Series level; the “Statistical population” concept may be attached to a Codelist artefact. 184 +* the “Contact” concept may be attached to a Dataset artefact at the Dataset level; 185 +* the “Adjustment” concept may be attached to a Dataset artefact at the Series level; 186 +* the “Statistical population” concept may be attached to a Codelist artefact. 187 187 188 - 189 189 This version of the proposal does not include an attachment recommendation for each concept. Recommended attachments may be provided in a future version of this guideline based on the feedback and forthcoming implementations. If you have any questions on how to attach reference metadata, please contact the SDMX Statistical Working Group (swg@sdmx.org). 190 190 191 191 == List of Reference Metadata Concepts == ... ... @@ -226,7 +226,7 @@ 226 226 227 227 //Example usage: if an organisation receives data from a member agency and publishes it, the “Contact organisation” concept would usually be the publishing organisation.// 228 228 )))|CONTACT_ORGANISATION 229 -|**Contact organisation unit**|Addressable 228 +|**Contact organisation unit**|Addressable subdivision of an organisation.|ORGANISATION_UNIT 230 230 |**Contact person function**|((( 231 231 Area of technical responsibility of the contact, such as “methodology”, “database management” or 232 232 ... ... @@ -234,8 +234,6 @@ 234 234 )))|CONTACT_FUNCT 235 235 |**Contact phone number**|Telephone number of the contact points for the data or metadata.|CONTACT_PHONE 236 236 237 - 238 - 239 239 === LEGAL AND INSTITUTIONAL ENVIRONMENT === 240 240 241 241 |**Name**|**Definition**|**Concept ID** ... ... @@ -248,16 +248,13 @@ 248 248 * //or the granular “Institutional mandate xxx” concepts but not the “Institutional mandate” concept.// 249 249 )))|INST_MANDATE 250 250 |**Institutional mandate – data sharing**|Arrangements or procedures for data sharing and coordination between data producing agencies.|INST_MAN_SHAR 251 -|**Institutional mandate -legal acts and other agreements**|Legal acts or other formal or informal agreements that assign responsibility as well as the authority to an Agency for the collection, processing, and dissemination of statistics.|INST_MAN_LA_OA248 +|**Institutional mandate – legal acts and other agreements**|Legal acts or other formal or informal agreements that assign responsibility as well as the authority to an Agency for the collection, processing, and dissemination of statistics.|INST_MAN_LA_OA 252 252 |**Confidentiality**|((( 253 253 Property of data indicating whether they are subject to dissemination restrictions. 254 254 255 255 //Recommended usage. Use~:// 256 256 257 -* //either the summary “Confidentiality” concept but not the granular// 258 - 259 -//“Confidentiality xxx” concepts,// 260 - 254 +* //either the summary “Confidentiality” concept but not the granular “Confidentiality xxx” concepts,// 261 261 * //or the granular “Confidentiality xxx” concepts but not the “Confidentiality” concept.// 262 262 )))|CONF 263 263 |**Confidentiality - data treatment**|Rules applied for treating the Data Set to ensure that private information from individual units cannot be accessed and to prevent unauthorised disclosure.|CONF_DATA_TR