Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 13.3
edited by Helena
on 2025/05/14 15:03
Change comment: There is no comment for this version
To version 15.3
edited by Helena
on 2025/05/16 13:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -285,31 +285,31 @@
285 285  > <Value>CZ2</Value>
286 286  > </Comp>
287 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>
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 313  > </Obs>
314 314  
315 315  === New - Metadata Provision Agreement ===
... ... @@ -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.
... ... @@ -390,8 +390,8 @@
390 390  
391 391  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.
392 392  
393 -=== Many-to-many source and target components ===
394 -
389 +(% class="wikigeneratedid" id="HMany-to-manysourceandtargetcomponents" %)
390 +**Many-to-many source and target components**
395 395  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:
396 396  
397 397  Set the output component INDICATOR=”DE_A” if the input components are FREQ=”A” and REF_AREA=”DE”.
... ... @@ -401,19 +401,18 @@
401 401  Set the output components FREQ=”A”, REF_AREA=”DE” if the input component INDICATOR=”DE_A”.
402 402  
403 403  **Fixed source and target**
404 -
405 405  The Structure Map may now define input or output components which have a fixed value.
406 406  
407 -=== Time representations mapping ===
408 -
402 +(% class="wikigeneratedid" id="HTimerepresentationsmapping" %)
403 +**Time representations mapping**
409 409  Non SDMX time representations may now be described in a Structure Map, allowing them to be mapped into SDMX time formats.
410 410  
411 -=== Regular expression and substring mappings ===
412 -
406 +(% class="wikigeneratedid" id="HRegularexpressionandsubstringmappings" %)
407 +**Regular expression and substring mappings**
413 413  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.
414 414  
415 -=== Item maps validity period ===
416 -
410 +(% class="wikigeneratedid" id="HItemmapsvalidityperiod" %)
411 +**Item maps validity period**
417 417  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.
418 418  
419 419  == 3.8 Constraints ==