Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 15.5
edited by Helena
on 2025/05/16 13:16
Change comment: There is no comment for this version
To version 16.2
edited by Helena
on 2025/05/16 13:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -247,8 +247,8 @@
247 247  
248 248  Reference metadata has been substantially re-designed for version 3.0 to simplify the model and better support practical use cases.
249 249  
250 -=== Simplify Metadata Structure Definition ===
251 -
250 +(% class="wikigeneratedid" id="HSimplifyMetadataStructureDefinition" %)
251 +**Simplify Metadata Structure Definition**
252 252  The Metadata Structure Definition (MSD) has been simplified to remove target information, and the support of multiple report structures. The MSD now only contains Metadata Attributes which are used to define the structure of a report.
253 253  
254 254  [[image:SDMX 3-0-0 Major Changes FINAL-1.0_en_ad5f5c97.png||height="346" width="494"]]
... ... @@ -259,8 +259,8 @@
259 259  
260 260  //Figure 3 the simplified version 3.0 MSD//
261 261  
262 -=== Change to reference metadata reported against data ===
263 -
262 +(% class="wikigeneratedid" id="HChangetoreferencemetadatareportedagainstdata" %)
263 +**Change to reference metadata reported against data**
264 264  Reference metadata associated with datasets, data series or observations are now reported with the data. The dataset’s DSD must reference an MSD to define the structure of its reference metadata. In practice reference metadata for data are transmitted as part of the data message. The metadata attributes are treated in a similar way to the data attributes appearing in the message at the dataset, data series or individual observation level as appropriate. In contrast to simple data attributes, metadata attributes defined by an MSD can be organised into a hierarchical structure as illustrated in Figure 3 above. For this reason, metadata attributes appear in data messages structured in the same way as metadata messages.
265 265  
266 266  The SDMX-ML example below is an excerpt from a structure specific data message illustrating reporting of reference metadata with a hierarchical structure at the observation level.
... ... @@ -312,16 +312,16 @@
312 312  > </Metadata>
313 313  > </Obs>
314 314  
315 -=== New - Metadata Provision Agreement ===
316 -
315 +(% class="wikigeneratedid" id="HNew-MetadataProvisionAgreement" %)
316 +**New - Metadata Provision Agreement**
317 317  In version 2.1 a Provision Agreement could be used to report information against a Dataflow or Metadataflow. From version 3.0 this is managed by two separate structures, the Data Provision Agreement and the Metadata Provision Agreement.
318 318  
319 -=== Move target to Metadataflow and Metadata Provision Agreement ===
320 -
319 +(% class="wikigeneratedid" id="HMovetargettoMetadataflowandMetadataProvisionAgreement" %)
320 +**Move target to Metadataflow and Metadata Provision Agreement**
321 321  For reference metadata that is reported against structures, the allowable targets information which is used to specify what structures the reference metadata can be reported against, has moved to the Metadataflow and can be further refined in the Metadata Provision Agreement.
322 322  
323 -=== Add maintainable properties to reference metadata ===
324 -
323 +(% class="wikigeneratedid" id="HAddmaintainablepropertiestoreferencemetadata" %)
324 +**Add maintainable properties to reference metadata**
325 325  A Metadataset now has mandatory identification information, (owner id, id, version) enabling metadata providers to uniquely identify their reports for create, update or delete maintenance operations.
326 326  
327 327  == 3.5 Microdata Exchange ==