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
-
... ... @@ -271,48 +271,47 @@ 271 271 * TITLE – a multi-lingual data attribute 272 272 * SOURCE_AGENCY – a multi-value data attribute 273 273 274 -<Obs xsi:type="dsd:ObsType" OBS_VALUE="112" OBS_STAUS=”A” TIME_PERIOD="2010-09"> 275 -<!—- complex multi-value and multi-lingual data attributes ~-~-> 276 -<Comp id="TITLE" xsi:type="ns1:TITLE_ATTRIBUTE"> 277 -<Value> 278 -<common:Text xml:lang="en">Some English Text</common:Text> 279 -<common:Text xml:lang="fr">Quelques textes en anglais</common:Text> 280 -</Value> 281 -</Comp> 274 +> <Obs xsi:type="dsd:ObsType" OBS_VALUE="112" OBS_STAUS=”A” TIME_PERIOD="2010-09"> 275 +> <!—- complex multi-value and multi-lingual data attributes ~-~-> 276 +> <Comp id="TITLE" xsi:type="ns1:TITLE_ATTRIBUTE"> 277 +> <Value> 278 +> <common:Text xml:lang="en">Some English Text</common:Text> 279 +> <common:Text xml:lang="fr">Quelques textes en anglais</common:Text> 280 +> </Value> 281 +> </Comp> 282 +> <Comp id="SOURCE_AGENCY" xsi:type="ns1:SOURCE_AGENCY_ATTRIBUTE"> 283 +> <Value>4F0</Value> 284 +> <Value>4D0</Value> 285 +> <Value>CZ2</Value> 286 +> </Comp> 287 +> <!—- metadata attributes are reported like in metadata messages ~-~-> 288 +> <Metadata> 289 +> <Attribute id="COLLECTION"> 290 +> <Attribute id="METHOD"> 291 +> <Text lang="en">AAA</Text> 292 +> </Attribute> 293 +> </Attribute> 294 +> <Attribute id="CONTACT"> 295 +> <Value>CONTACT 1</Value> 296 +> <Attribute id="NAME"> 297 +> <Value>Contact 1 Name 1</Value> 298 +> </Attribute> 299 +> <Attribute id="NAME"> 300 +> <Value>Contact 1 Name 2</Value> 301 +> </Attribute> 302 +> </Attribute> 303 +> <Attribute id="CONTACT"> 304 +> <Value>CONTACT 2</Value> 305 +> <Attribute id="NAME"> 306 +> <Value>Contact 2 Name 1</Value> 307 +> </Attribute> 308 +> <Attribute id="NAME"> 309 +> <Value>Contact 2 Name 2</Value> 310 +> </Attribute> 311 +> </Attribute> 312 +> </Metadata> 313 +> </Obs> 282 282 283 -<Comp id="SOURCE_AGENCY" xsi:type="ns1:SOURCE_AGENCY_ATTRIBUTE"> 284 -<Value>4F0</Value> 285 -<Value>4D0</Value> 286 -<Value>CZ2</Value> 287 -</Comp> 288 -<!—- metadata attributes are reported like in metadata messages ~-~-> 289 -<Metadata> 290 -<Attribute id="COLLECTION"> 291 -<Attribute id="METHOD"> 292 -<Text lang="en">AAA</Text> 293 -</Attribute> 294 -</Attribute> 295 -<Attribute id="CONTACT"> 296 -<Value>CONTACT 1</Value> 297 -<Attribute id="NAME"> 298 -<Value>Contact 1 Name 1</Value> 299 -</Attribute> 300 -<Attribute id="NAME"> 301 -<Value>Contact 1 Name 2</Value> 302 -</Attribute> 303 -</Attribute> 304 -<Attribute id="CONTACT"> 305 -<Value>CONTACT 2</Value> 306 -<Attribute id="NAME"> 307 -<Value>Contact 2 Name 1</Value> 308 -</Attribute> 309 -<Attribute id="NAME"> 310 -<Value>Contact 2 Name 2</Value> 311 -</Attribute> 312 -</Attribute> 313 -</Metadata> 314 -</Obs> 315 - 316 316 === New - Metadata Provision Agreement === 317 317 318 318 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. ... ... @@ -337,29 +337,25 @@ 337 337 338 338 MeasureDimension behaviour as illustrated in the SDMX-ML example below: 339 339 340 -<str:MeasureList id=”MeasureDescriptor”> 341 -<str:Measure id=”OBS_VALUE” minOccurs=”1” maxOccurs=”1” usage=”mandatory” > <str:ConceptIdentity> 342 -<Ref id=”OBS_VALUE” maintainableParentID=”CONCEPTS” agencyID=”SDMX” maintainableParentVersion=”1.0.0” /> 343 -</str:ConceptIdentity> 344 -<str:LocalRepresentation> 345 -<str:TextFormat textType=”String” isMultiLingual=”true” /> 346 -</str:LocalRepresentation> 347 -<str:ConceptRole> 348 -<Ref id=”MEASURE” maintainableParentID=”SDMX_CONCEPT_ROLES” agencyID=”SDMX” maintainableParentVersion=”1.0.0” /> 349 -</str:ConceptRole> 350 -</str:Measure> 351 -... 352 -<str:Measure> 353 -</str:MeasureList> 339 +> <str:MeasureList id=”MeasureDescriptor”> 340 +> <str:Measure id=”OBS_VALUE” minOccurs=”1” maxOccurs=”1” usage=”mandatory” > <str:ConceptIdentity> 341 +> <Ref id=”OBS_VALUE” maintainableParentID=”CONCEPTS” agencyID=”SDMX” maintainableParentVersion=”1.0.0” /> 342 +> </str:ConceptIdentity> 343 +> <str:LocalRepresentation> 344 +> <str:TextFormat textType=”String” isMultiLingual=”true” /> 345 +> </str:LocalRepresentation> 346 +> <str:ConceptRole> 347 +> <Ref id=”MEASURE” maintainableParentID=”SDMX_CONCEPT_ROLES” agencyID=”SDMX” maintainableParentVersion=”1.0.0” /> 348 +> </str:ConceptRole> 349 +> </str:Measure> 350 +> ... 351 +> <str:Measure> 352 +> </str:MeasureList> 354 354 355 355 === Multi-value measures and attributes === 356 356 357 -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 356 +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. 358 358 359 -//mandatory// or optional. In the SDMX-ML measure example above, the properties 360 - 361 -//minOccurs=”1” maxOccurs=”1” usage=”mandatory”// specify that OBS_VALUE must be 198 reported, and can only consist of a single value. 362 - 363 363 === Attributes relationship to measures === 364 364 365 365 In addition to attaching attributes to a specific level within the dataset, their relationship 202 to measures can also be defined.