Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 11.2
edited by Helena
on 2025/05/14 14:51
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
... ... @@ -271,48 +271,47 @@
271 271  * TITLE – a multi-lingual data attribute
272 272  * SOURCE_AGENCY – a multi-value data attribute
273 273  
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>
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>
282 282  
283 -<Comp id="SOURCE_AGENCY" xsi:type="ns1:SOURCE_AGENCY_ATTRIBUTE">
284 -<Value>4F0</Value>
285 -<Value>4D0</Value>
286 -<Value>CZ2</Value>
287 -</Comp>
288 -<!—- metadata attributes are reported like in metadata messages ~-~->
289 -<Metadata>
290 -<Attribute id="COLLECTION">
291 -<Attribute id="METHOD">
292 -<Text lang="en">AAA</Text>
293 -</Attribute>
294 -</Attribute>
295 -<Attribute id="CONTACT">
296 -<Value>CONTACT 1</Value>
297 -<Attribute id="NAME">
298 -<Value>Contact 1 Name 1</Value>
299 -</Attribute>
300 -<Attribute id="NAME">
301 -<Value>Contact 1 Name 2</Value>
302 -</Attribute>
303 -</Attribute>
304 -<Attribute id="CONTACT">
305 -<Value>CONTACT 2</Value>
306 -<Attribute id="NAME">
307 -<Value>Contact 2 Name 1</Value>
308 -</Attribute>
309 -<Attribute id="NAME">
310 -<Value>Contact 2 Name 2</Value>
311 -</Attribute>
312 -</Attribute>
313 -</Metadata>
314 -</Obs>
315 -
316 316  === New - Metadata Provision Agreement ===
317 317  
318 318  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.
... ... @@ -337,29 +337,25 @@
337 337  
338 338  MeasureDimension behaviour as illustrated in the SDMX-ML example below:
339 339  
340 -<str:MeasureList id=”MeasureDescriptor”>
341 -<str:Measure id=”OBS_VALUE” minOccurs=”1” maxOccurs=”1” usage=”mandatory” > <str:ConceptIdentity>
342 -<Ref id=”OBS_VALUE” maintainableParentID=”CONCEPTS” agencyID=”SDMX” maintainableParentVersion=”1.0.0” />
343 -</str:ConceptIdentity>
344 -<str:LocalRepresentation>
345 -<str:TextFormat textType=”String” isMultiLingual=”true” />
346 -</str:LocalRepresentation>
347 -<str:ConceptRole>
348 -<Ref id=”MEASURE” maintainableParentID=”SDMX_CONCEPT_ROLES” agencyID=”SDMX” maintainableParentVersion=”1.0.0” />
349 -</str:ConceptRole>
350 -</str:Measure>
351 -...
352 -<str:Measure>
353 -</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>
354 354  
355 355  === Multi-value measures and attributes ===
356 356  
357 -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.
358 358  
359 -//mandatory// or optional. In the SDMX-ML measure example above, the properties
360 -
361 -//minOccurs=”1” maxOccurs=”1” usage=”mandatory”// specify that OBS_VALUE must be 198 reported, and can only consist of a single value.
362 -
363 363  === Attributes relationship to measures ===
364 364  
365 365  In addition to attaching attributes to a specific level within the dataset, their relationship 202 to measures can also be defined.
... ... @@ -391,8 +391,8 @@
391 391  
392 392  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.
393 393  
394 -==== Many-to-many source and target components ====
395 -
389 +(% class="wikigeneratedid" id="HMany-to-manysourceandtargetcomponents" %)
390 +**Many-to-many source and target components**
396 396  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:
397 397  
398 398  Set the output component INDICATOR=”DE_A” if the input components are FREQ=”A” and REF_AREA=”DE”.
... ... @@ -402,19 +402,18 @@
402 402  Set the output components FREQ=”A”, REF_AREA=”DE” if the input component INDICATOR=”DE_A”.
403 403  
404 404  **Fixed source and target**
405 -
406 406  The Structure Map may now define input or output components which have a fixed value.
407 407  
408 -==== Time representations mapping ====
409 -
402 +(% class="wikigeneratedid" id="HTimerepresentationsmapping" %)
403 +**Time representations mapping**
410 410  Non SDMX time representations may now be described in a Structure Map, allowing them to be mapped into SDMX time formats.
411 411  
412 -==== Regular expression and substring mappings ====
413 -
406 +(% class="wikigeneratedid" id="HRegularexpressionandsubstringmappings" %)
407 +**Regular expression and substring mappings**
414 414  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.
415 415  
416 -==== Item maps validity period ====
417 -
410 +(% class="wikigeneratedid" id="HItemmapsvalidityperiod" %)
411 +**Item maps validity period**
418 418  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.
419 419  
420 420  == 3.8 Constraints ==