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
-
... ... @@ -65,7 +65,7 @@ 65 65 66 66 Version 3.0 introduces breaking changes into the web services API, transmission formats and information model. A summary is given in the table below. 67 67 68 -== 2.1 Web Services API == 68 +== //2.1 Web Services API// == 69 69 70 70 (% style="width:948.039px" %) 71 71 |**REST API**|(% style="width:818px" %)((( ... ... @@ -86,7 +86,7 @@ 86 86 ))) 87 87 |**SOAP API**|(% style="width:818px" %)The SOAP API has been deprecated. 88 88 89 -== 2.2 Transmission Formats == 89 +== //2.2 Transmission Formats// == 90 90 91 91 ((( 92 92 (% style="width:952.039px" %) ... ... @@ -122,7 +122,7 @@ 122 122 |(% style="width:130px" %)**SDMX-CSV**|(% style="width:820px" %)The CSV data and reference metadata messages are not backwardly compatible with those under version 2.1 due to changes to the structure of the messages needed to support new features such as the improved REST API data queries. 123 123 ))) 124 124 125 -== 2.3 Information Model == 125 +== //2.3 Information Model// == 126 126 127 127 ((( 128 128 (% style="width:955.039px" %) ... ... @@ -177,7 +177,7 @@ 177 177 178 178 = 3 Information Model = 179 179 180 -== 3.1 Version 3.0 Information Model == 180 +== //3.1 Version 3.0 Information Model// == 181 181 182 182 [[image:SDMX 3-0-0 Major Changes FINAL-1.0_en_6fc573fe.png||height="404" width="718"]] 183 183 ... ... @@ -187,7 +187,7 @@ 187 187 188 188 A number of ancillary structures including organisation schemes, process and reporting taxonomy are unchanged and have not been shown. Similarly, Organisation Scheme Map and Reporting Taxonomy Map have been omitted for simplicity. A schematic of the 2.1 model is given in Appendix A for comparison purposes. 189 189 190 -== 3.2 Key Changes from Version 2.1 == 190 +== //3.2 Key Changes from Version 2.1// == 191 191 192 192 New Maintainable Artefacts 193 193 ... ... @@ -338,18 +338,31 @@ 338 338 MeasureDimension behaviour as illustrated in the SDMX-ML example below: 339 339 340 340 <str:MeasureList id=”MeasureDescriptor”> 341 + 341 341 <str:Measure id=”OBS_VALUE” minOccurs=”1” maxOccurs=”1” usage=”mandatory” > <str:ConceptIdentity> 343 + 342 342 <Ref id=”OBS_VALUE” maintainableParentID=”CONCEPTS” agencyID=”SDMX” maintainableParentVersion=”1.0.0” /> 345 + 343 343 </str:ConceptIdentity> 347 + 344 344 <str:LocalRepresentation> 349 + 345 345 <str:TextFormat textType=”String” isMultiLingual=”true” /> 351 + 346 346 </str:LocalRepresentation> 353 + 347 347 <str:ConceptRole> 355 + 348 348 <Ref id=”MEASURE” maintainableParentID=”SDMX_CONCEPT_ROLES” agencyID=”SDMX” maintainableParentVersion=”1.0.0” /> 357 + 349 349 </str:ConceptRole> 359 + 350 350 </str:Measure> 361 + 351 351 ... 363 + 352 352 <str:Measure> 365 + 353 353 </str:MeasureList> 354 354 355 355 === Multi-value measures and attributes === ... ... @@ -490,7 +490,7 @@ 490 490 491 491 = 5 REST Web Services API = 492 492 493 -== 5.1 Simplified list of resources == 506 +== //5.1 Simplified list of resources// == 494 494 495 495 The version 3.0 REST API has just five main resources: 496 496 ... ... @@ -504,7 +504,7 @@ 504 504 505 505 This and changes in the URLs and query parameters on the data, availability and metadata resources means that, with the exception of schema queries, the version 3.0 API is not backwardly compatible. 506 506 507 -== 5.2 Improved data queries == 520 +== //5.2 Improved data queries// == 508 508 509 509 Data queries have been changed to provide more granular selections from contexts wider than just a Dataflow. 510 510 ... ... @@ -543,7 +543,7 @@ 543 543 544 544 /data/dataflow/ESTAT/ICP/1.0.0/M…A.ANR,M…A.INX,M…B.CTG 545 545 546 -== 5.3 Improved reference metadata queries == 559 +== //5.3 Improved reference metadata queries// == 547 547 548 548 Reference metadata queries have been improved with a number of new options to retrieve metadata reports. 549 549 ... ... @@ -559,7 +559,7 @@ 559 559 560 560 /metadata/structure/datastructure/BIS/BIS_CBS/1.0 561 561 562 -== 5.4 Structural metadata maintenance == 575 +== //5.4 Structural metadata maintenance// == 563 563 564 564 Support has been added for maintenance of structural metadata. 565 565 ... ... @@ -567,7 +567,7 @@ 567 567 568 568 = 6 XML, JSON, CSV and EDI Transmission formats = 569 569 570 -== 6.1 SDMX-ML == 583 +== //6.1 SDMX-ML// == 571 571 572 572 The SDMX-ML XML messages have been modified and updated for version 3.0. While they broadly follow the same principles, there have been significant changes which break backward compatibility. 573 573 ... ... @@ -653,7 +653,7 @@ 653 653 654 654 The option to reference structures using Agency, ID and Version has been removed. From SDMX version 3.0 URN is used for all referencing purposes with the exception of local references such as where groups reference dimensions within a DSD. 655 655 656 -== 6.2 SDMX-JSON == 669 +== //6.2 SDMX-JSON// == 657 657 658 658 Like SDMX-ML, the SDMX-JSON messages have been significantly modified and updated for version 3.0. They are not backwardly compatible with version 2.1. 659 659 ... ... @@ -673,7 +673,7 @@ 673 673 674 674 As for SDMX-ML, the option to reference structures using Agency, ID and Version has been removed with URN used for all non-local referencing purposes. 675 675 676 -== 6.3 SDMX-CSV == 689 +== //6.3 SDMX-CSV// == 677 677 678 678 CSV in SDMX is used transmission of data and reference metadata only. 679 679 ... ... @@ -691,7 +691,7 @@ 691 691 692 692 The SDMX-CSV metadata message is new for version 3.0 and, like the SDMX-ML and SDMX-JSON equivalents, is used for the transmission reference metadata sets. 693 693 694 -=== 6.4 EDI deprecation === 707 +=== //6.4 EDI deprecation// === 695 695 696 696 The EDI format for transmission of both structures and data has been deprecated. Version 3.0 is therefore not backwardly compatible with legacy EDI messages. 697 697