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
-
... ... @@ -272,45 +272,45 @@ 272 272 * SOURCE_AGENCY – a multi-value data attribute 273 273 274 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> 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> 314 314 315 315 === New - Metadata Provision Agreement === 316 316 ... ... @@ -336,29 +336,25 @@ 336 336 337 337 MeasureDimension behaviour as illustrated in the SDMX-ML example below: 338 338 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> 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> 353 353 354 354 === Multi-value measures and attributes === 355 355 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 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. 357 357 358 -//mandatory// or optional. In the SDMX-ML measure example above, the properties 359 - 360 -//minOccurs=”1” maxOccurs=”1” usage=”mandatory”// specify that OBS_VALUE must be 198 reported, and can only consist of a single value. 361 - 362 362 === Attributes relationship to measures === 363 363 364 364 In addition to attaching attributes to a specific level within the dataset, their relationship 202 to measures can also be defined.