Changes for page SDMX 3.0 Standards. Summary of Major Changes and New Functionality
Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -312,16 +312,16 @@ 312 312 > </Metadata> 313 313 > </Obs> 314 314 315 - (% class="wikigeneratedid" id="HNew-MetadataProvisionAgreement"%)316 - **New - Metadata Provision Agreement**315 +=== New - Metadata Provision Agreement === 316 + 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 - (% class="wikigeneratedid" id="HMovetargettoMetadataflowandMetadataProvisionAgreement"%)320 - **Move target to Metadataflow and Metadata Provision Agreement**319 +=== Move target to Metadataflow and Metadata Provision Agreement === 320 + 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 - (% class="wikigeneratedid" id="HAddmaintainablepropertiestoreferencemetadata"%)324 - **Add maintainable properties to reference metadata**323 +=== Add maintainable properties to reference metadata === 324 + 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 == ... ... @@ -328,10 +328,14 @@ 328 328 329 329 Several changes have been made the Data Structure Definition to support microdata use cases in addition to aggregated time series. 330 330 331 -(% class="wikigeneratedid" id="HMultiplemeasures" %) 332 -**Multiple measures** 333 -Multiple measures are a common characteristic of microdatasets. To support this use case, the MeasureDimension has been deprecated and replaced with the option to define zero or more measures. Measures now act like any other component in that they use concepts, can have their own local coded or uncoded representation defined within the Data Structure Definition, and can be either mandatory or conditional. Creating a measure with the “MEASURE” concept role applied emulates the version 2.1 MeasureDimension behaviour as illustrated in the SDMX-ML example below: 331 +=== Multiple measures === 334 334 333 +Multiple measures are a common characteristic of microdatasets. To support this use case, the MeasureDimension has been deprecated and replaced with the option to define zero or more measures. Measures now act like any other component in that they use concepts, can have their own local coded or uncoded representation defined within the 334 + 335 +Data Structure Definition, and can be either mandatory or conditional. Creating a measure with the “MEASURE” concept role applied emulates the version 2.1 336 + 337 +MeasureDimension behaviour as illustrated in the SDMX-ML example below: 338 + 335 335 > <str:MeasureList id=”MeasureDescriptor”> 336 336 > <str:Measure id=”OBS_VALUE” minOccurs=”1” maxOccurs=”1” usage=”mandatory” > <str:ConceptIdentity> 337 337 > <Ref id=”OBS_VALUE” maintainableParentID=”CONCEPTS” agencyID=”SDMX” maintainableParentVersion=”1.0.0” /> ... ... @@ -347,18 +347,20 @@ 347 347 > <str:Measure> 348 348 > </str:MeasureList> 349 349 350 - (% class="wikigeneratedid" id="HMulti-valuemeasuresandattributes"%)351 - **Multi-value measures and attributes**354 +=== Multi-value measures and attributes === 355 + 352 352 Both measures and attributes have been extended with the option to take ‘arrays’ of 193 multiple coded or uncoded values. This supports use cases like multiple observation 194 status flags. New //minOccurs// and //maxOccurs// properties define the valid number of 195 values. The //usage// property separately defines whether the measure or attribute is //mandatory// or optional. In the SDMX-ML measure example above, the properties //minOccurs=”1” maxOccurs=”1” usage=”mandatory”// specify that OBS_VALUE must be 198 reported, and can only consist of a single value. 353 353 354 - (% class="wikigeneratedid" id="HAttributesrelationshiptomeasures"%)355 - **Attributes relationship to measures**358 +=== Attributes relationship to measures === 359 + 356 356 In addition to attaching attributes to a specific level within the dataset, their relationship 202 to measures can also be defined. 357 357 358 -(% class="wikigeneratedid" id="HValuelists" %) 359 -**Value lists** 360 -Value lists help in modelling microdata by providing an enumeration similar to code lists 206 but allowing any string values without being restricted to the rules of SDMX identifiers. That allows ValueItems (the equivalent to Code) to contain symbols like ‘¥’ and ‘€’, but also means they are not identifiable. 362 +=== Value lists === 361 361 364 +Value lists help in modelling microdata by providing an enumeration similar to code lists 206 but allowing any string values without being restricted to the rules of SDMX identifiers. 365 + 366 +That allows ValueItems (the equivalent to Code) to contain symbols like ‘¥’ and ‘€’, but 208 also means they are not identifiable. 367 + 362 362 == 3.6 Geospatial Data Exchange == 363 363 364 364 The version 3.0 model has been extended to provide explicit support for geospatial data.