Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 15.4
edited by Helena
on 2025/05/16 13:15
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
... ... @@ -351,18 +351,20 @@
351 351  > <str:Measure>
352 352  > </str:MeasureList>
353 353  
354 -(% class="wikigeneratedid" id="HMulti-valuemeasuresandattributes" %)
355 -**Multi-value measures and attributes**
354 +=== Multi-value measures and attributes ===
355 +
356 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 -(% class="wikigeneratedid" id="HAttributesrelationshiptomeasures" %)
359 -**Attributes relationship to measures**
358 +=== Attributes relationship to measures ===
359 +
360 360  In addition to attaching attributes to a specific level within the dataset, their relationship 202 to measures can also be defined.
361 361  
362 -(% class="wikigeneratedid" id="HValuelists" %)
363 -**Value lists**
364 -Value lists help in modelling microdata by providing an enumeration similar to code lists 206 but allowing any string values without being restricted to the rules of SDMX identifiers. That allows ValueItems (the equivalent to Code) to contain symbols like ‘¥’ and ‘€’, but also means they are not identifiable.
362 +=== Value lists ===
365 365  
364 +Value lists help in modelling microdata by providing an enumeration similar to code lists 206 but allowing any string values without being restricted to the rules of SDMX identifiers.
365 +
366 +That allows ValueItems (the equivalent to Code) to contain symbols like ‘¥’ and ‘€’, but 208 also means they are not identifiable.
367 +
366 366  == 3.6 Geospatial Data Exchange ==
367 367  
368 368  The version 3.0 model has been extended to provide explicit support for geospatial data.