Last modified by Helena on 2025/09/10 11:19

From version 10.2
edited by Helena
on 2025/05/14 14:41
Change comment: There is no comment for this version
To version 11.1
edited by Helena
on 2025/05/14 14:45
Change comment: There is no comment for this version

Summary

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,31 +338,18 @@
338 338  MeasureDimension behaviour as illustrated in the SDMX-ML example below:
339 339  
340 340  <str:MeasureList id=”MeasureDescriptor”>
341 -
342 342  <str:Measure id=”OBS_VALUE” minOccurs=”1” maxOccurs=”1” usage=”mandatory” > <str:ConceptIdentity>
343 -
344 344  <Ref id=”OBS_VALUE” maintainableParentID=”CONCEPTS” agencyID=”SDMX” maintainableParentVersion=”1.0.0” />
345 -
346 346  </str:ConceptIdentity>
347 -
348 348  <str:LocalRepresentation>
349 -
350 350  <str:TextFormat textType=”String” isMultiLingual=”true” />
351 -
352 352  </str:LocalRepresentation>
353 -
354 354  <str:ConceptRole>
355 -
356 356  <Ref id=”MEASURE” maintainableParentID=”SDMX_CONCEPT_ROLES” agencyID=”SDMX” maintainableParentVersion=”1.0.0” />
357 -
358 358  </str:ConceptRole>
359 -
360 360  </str:Measure>
361 -
362 362  ...
363 -
364 364  <str:Measure>
365 -
366 366  </str:MeasureList>
367 367  
368 368  === Multi-value measures and attributes ===
... ... @@ -503,7 +503,7 @@
503 503  
504 504  = 5 REST Web Services API =
505 505  
506 -== //5.1 Simplified list of resources// ==
493 +== 5.1 Simplified list of resources ==
507 507  
508 508  The version 3.0 REST API has just five main resources:
509 509  
... ... @@ -517,7 +517,7 @@
517 517  
518 518  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.
519 519  
520 -== //5.2 Improved data queries// ==
507 +== 5.2 Improved data queries ==
521 521  
522 522  Data queries have been changed to provide more granular selections from contexts wider than just a Dataflow.
523 523  
... ... @@ -556,7 +556,7 @@
556 556  
557 557  /data/dataflow/ESTAT/ICP/1.0.0/M…A.ANR,M…A.INX,M…B.CTG
558 558  
559 -== //5.3 Improved reference metadata queries// ==
546 +== 5.3 Improved reference metadata queries ==
560 560  
561 561  Reference metadata queries have been improved with a number of new options to retrieve metadata reports.
562 562  
... ... @@ -572,7 +572,7 @@
572 572  
573 573  /metadata/structure/datastructure/BIS/BIS_CBS/1.0
574 574  
575 -== //5.4 Structural metadata maintenance// ==
562 +== 5.4 Structural metadata maintenance ==
576 576  
577 577  Support has been added for maintenance of structural metadata.
578 578  
... ... @@ -580,7 +580,7 @@
580 580  
581 581  = 6 XML, JSON, CSV and EDI Transmission formats =
582 582  
583 -== //6.1 SDMX-ML// ==
570 +== 6.1 SDMX-ML ==
584 584  
585 585  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.
586 586  
... ... @@ -666,7 +666,7 @@
666 666  
667 667  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.
668 668  
669 -== //6.2 SDMX-JSON// ==
656 +== 6.2 SDMX-JSON ==
670 670  
671 671  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.
672 672  
... ... @@ -686,7 +686,7 @@
686 686  
687 687  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.
688 688  
689 -== //6.3 SDMX-CSV// ==
676 +== 6.3 SDMX-CSV ==
690 690  
691 691  CSV in SDMX is used transmission of data and reference metadata only.
692 692  
... ... @@ -704,7 +704,7 @@
704 704  
705 705  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.
706 706  
707 -=== //6.4 EDI deprecation// ===
694 +=== 6.4 EDI deprecation ===
708 708  
709 709  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.
710 710