Changes for page SDMX 3.0 Standards. Summary of Major Changes and New Functionality

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

From 13.1 to 12.1 From 15.4 to 15.3

From version 15.3

edited by Helena
on 2025/05/16 13:14

Change comment: There is no comment for this version

To version 13.1

edited by Helena
on 2025/05/14 14:53

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -271,47 +271,48 @@
  * TITLE – a multi-lingual data attribute
  * SOURCE_AGENCY – a multi-value data attribute
--> <Obs xsi:type="dsd:ObsType" OBS_VALUE="112" OBS_STAUS=”A” TIME_PERIOD="2010-09">
-->     <!—- complex multi-value and multi-lingual data attributes ~-~->
-->     <Comp id="TITLE" xsi:type="ns1:TITLE_ATTRIBUTE">
-->         <Value>
-->         <common:Text xml:lang="en">Some English Text</common:Text>
-->         <common:Text xml:lang="fr">Quelques textes en anglais</common:Text>
-->         </Value>
-->     </Comp>
-->     <Comp id="SOURCE_AGENCY" xsi:type="ns1:SOURCE_AGENCY_ATTRIBUTE">
-->         <Value>4F0</Value>
-->         <Value>4D0</Value>
-->         <Value>CZ2</Value>
-->     </Comp>
--> <!—- metadata attributes are reported like in metadata messages ~-~->
--> <Metadata>
-->     <Attribute id="COLLECTION">
-->         <Attribute id="METHOD">
-->             <Text lang="en">AAA</Text>
-->         </Attribute>
-->     </Attribute>
-->     <Attribute id="CONTACT">
-->          <Value>CONTACT 1</Value>
-->          <Attribute id="NAME">
-->             <Value>Contact 1 Name 1</Value>
-->      </Attribute>
-->      <Attribute id="NAME">
-->             <Value>Contact 1 Name 2</Value>
-->         </Attribute>
-->     </Attribute>
-->     <Attribute id="CONTACT">
-->           <Value>CONTACT 2</Value>
-->         <Attribute id="NAME">
-->             <Value>Contact 2 Name 1</Value>
-->       </Attribute>
-->       <Attribute id="NAME">
-->                 <Value>Contact 2 Name 2</Value>
-->                </Attribute>
-->           </Attribute>
-->       </Metadata>
--> </Obs>
++<Obs xsi:type="dsd:ObsType" OBS_VALUE="112" OBS_STAUS=”A” TIME_PERIOD="2010-09">
++<!—- complex multi-value and multi-lingual data attributes ~-~->
++<Comp id="TITLE" xsi:type="ns1:TITLE_ATTRIBUTE">
++<Value>
++<common:Text xml:lang="en">Some English Text</common:Text>
++<common:Text xml:lang="fr">Quelques textes en anglais</common:Text>
++</Value>
++</Comp>
++<Comp id="SOURCE_AGENCY" xsi:type="ns1:SOURCE_AGENCY_ATTRIBUTE">
++<Value>4F0</Value>
++<Value>4D0</Value>
++<Value>CZ2</Value>
++</Comp>
++<!—- metadata attributes are reported like in metadata messages ~-~->
++<Metadata>
++<Attribute id="COLLECTION">
++<Attribute id="METHOD">
++<Text lang="en">AAA</Text>
++</Attribute>
++</Attribute>
++<Attribute id="CONTACT">
++<Value>CONTACT 1</Value>
++<Attribute id="NAME">
++<Value>Contact 1 Name 1</Value>
++</Attribute>
++<Attribute id="NAME">
++<Value>Contact 1 Name 2</Value>
++</Attribute>
++</Attribute>
++<Attribute id="CONTACT">
++<Value>CONTACT 2</Value>
++<Attribute id="NAME">
++<Value>Contact 2 Name 1</Value>
++</Attribute>
++<Attribute id="NAME">
++<Value>Contact 2 Name 2</Value>
++</Attribute>
++</Attribute>
++</Metadata>
++</Obs>
++
  === New - Metadata Provision Agreement ===
  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.
@@ -336,25 +336,29 @@
  MeasureDimension behaviour as illustrated in the SDMX-ML example below:
--> <str:MeasureList id=”MeasureDescriptor”>
-->     <str:Measure id=”OBS_VALUE” minOccurs=”1” maxOccurs=”1” usage=”mandatory” > <str:ConceptIdentity>
-->         <Ref id=”OBS_VALUE” maintainableParentID=”CONCEPTS” agencyID=”SDMX” maintainableParentVersion=”1.0.0” />
-->     </str:ConceptIdentity>
-->     <str:LocalRepresentation>
-->         <str:TextFormat textType=”String” isMultiLingual=”true” />
-->     </str:LocalRepresentation>
-->     <str:ConceptRole>
-->         <Ref id=”MEASURE” maintainableParentID=”SDMX_CONCEPT_ROLES” agencyID=”SDMX” maintainableParentVersion=”1.0.0” />
-->     </str:ConceptRole>
-->  </str:Measure>
-->         ...
-->     <str:Measure>
--> </str:MeasureList>
++<str:MeasureList id=”MeasureDescriptor”>
++<str:Measure id=”OBS_VALUE” minOccurs=”1” maxOccurs=”1” usage=”mandatory” > <str:ConceptIdentity>
++<Ref id=”OBS_VALUE” maintainableParentID=”CONCEPTS” agencyID=”SDMX” maintainableParentVersion=”1.0.0” />
++</str:ConceptIdentity>
++<str:LocalRepresentation>
++<str:TextFormat textType=”String” isMultiLingual=”true” />
++</str:LocalRepresentation>
++<str:ConceptRole>
++<Ref id=”MEASURE” maintainableParentID=”SDMX_CONCEPT_ROLES” agencyID=”SDMX” maintainableParentVersion=”1.0.0” />
++</str:ConceptRole>
++</str:Measure>
++...
++<str:Measure>
++</str:MeasureList>
  === Multi-value measures and attributes ===
--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.
++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.
++
  === Attributes relationship to measures ===
  In addition to attaching attributes to a specific level within the dataset, their relationship 202 to measures can also be defined.
@@ -386,8 +386,8 @@
  The version 2.1 Codelist Map been replaced with Representation Map which allows mappings to be defined between any combination of Code Lists, Value Lists and noncoded representations such as text strings and numbers.
--(% class="wikigeneratedid" id="HMany-to-manysourceandtargetcomponents" %)
--**Many-to-many source and target components**
++=== Many-to-many source and target components ===
++
  Structure mapping rules may be defined with both multiple source components and multiple target components in contrast to version 2.1 where only one source and target was allowed. That supports many-to-many (n-n) mapping use cases where the output of a mapping rule may be dependent on the combination of a number of input components. For instance:
  Set the output component INDICATOR=”DE_A” if the input components are FREQ=”A” and REF_AREA=”DE”.
@@ -397,18 +397,19 @@
  Set the output components FREQ=”A”, REF_AREA=”DE” if the input component INDICATOR=”DE_A”.
  **Fixed source and target**
++
  The Structure Map may now define input or output components which have a fixed value.
--(% class="wikigeneratedid" id="HTimerepresentationsmapping" %)
--**Time representations mapping**
++=== Time representations mapping ===
++
  Non SDMX time representations may now be described in a Structure Map, allowing them to be mapped into SDMX time formats.
--(% class="wikigeneratedid" id="HRegularexpressionandsubstringmappings" %)
--**Regular expression and substring mappings**
++=== Regular expression and substring mappings ===
++
  All item maps allow the use of regular expressions and substrings to match source values, specifically: Concept Scheme Map, Reporting Taxonomy Map, Category Scheme Map and Organisation Scheme Map.
--(% class="wikigeneratedid" id="HItemmapsvalidityperiod" %)
--**Item maps validity period**
++=== Item maps validity period ===
++
  Item maps may further define the period for which the mapping is valid, meaning the mapping rule will only be applied if the row of information being mapped is within the period.
  == 3.8 Constraints ==