Changes for page Part IV. Data and Reference Metadata Namespaces
Last modified by Elena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -531,34 +531,37 @@ 531 531 |(% style="width:267px" %)decimals^^1^^|(% style="width:729px" %)xs:fractionDigits 532 532 |(% style="width:267px" %)pattern|(% style="width:729px" %)xs:pattern 533 533 534 -Any other [[facets>>doc:sdmx:Glossary.Facet.WebHome]]are informational only and will not affect the determined type.534 +Any other facets are informational only and will not affect the determined type. 535 535 536 536 === 3.3.7 Representation for Not Applicable Dimensions === 537 537 538 -Not applicable [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]], i.e., when reported[[measures>>doc:sdmx:Glossary.Measure.WebHome]]or[[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]are not attached to those[[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]], take as value the tilde ‘’ character. This is required for[[datasets>>doc:sdmx:Glossary.Dataset.WebHome]]defined by a[[DSD>>doc:sdmx:Glossary.Datastructure definition.WebHome]] that has the ‘evolving structure’ property set to true and that includes data from[[dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]], which only use a subset of[[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]]as defined by a[[dimension>>doc:sdmx:Glossary.Dimension.WebHome]](% style="color:#e74c3c" %)constraint(%%). This is also required for data-related higher-(% style="color:#e74c3c" %)level(%%)(i.e., attached to[[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]or partial list of[[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]])[[reference metadata>>doc:sdmx:Glossary.Referencemetadata.WebHome]] [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]that don’t have a fixed pre-defined attachment.538 +Not applicable dimensions, i.e., when reported measures or attributes are not attached to those dimensions, take as value the tilde ‘’ character. This is required for datasets defined by a DSD that has the ‘evolving structure’ property set to true and that includes data from dataflows, which only use a subset of dimensions as defined by a dimension constraint. This is also required for data-related higher-level (i.e., attached to dataflow or partial list of Dimensions) reference metadata attributes that don’t have a fixed pre-defined attachment. 539 539 540 -To support a specific type and allow for a not applicable [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]value, the structure-specific schema must union the type with the common:NotApplicableType, which enumerates the tilde ‘’ character. This is as shown in the following example:540 +To support a specific type and allow for a not applicable dimension value, the structure-specific schema must union the type with the common:NotApplicableType, which enumerates the tilde ‘’ character. This is as shown in the following example: 541 541 542 -> <xs:simpleType name="DecimalOrNotApplicableType"> 543 -> <xs:union memberTypes="xs:decimal common:NotApplicableType"/> 544 -> </xs:simpleType> 542 +xml 543 + <xs:simpleType name="DecimalOrNotApplicableType"> 544 + <xs:union memberTypes="xs:decimal common:NotApplicableType"/> 545 + </xs:simpleType> 545 545 546 546 For enumerated types, the generated structure-specific schema can include the special value in the enumeration or create a union between the enumerated type and the common:NotApplicableType. 547 547 548 548 Option 1: Augmenting the enumeration with the special value 549 549 550 -> <xs:simpleType name="CL\_SUBINDICATOR\_OR\_NOT\_APPLICABLE"> 551 -> <xs:union memberTypes="CL\_SUBINDICATOR common:NotApplicableType"/> 552 -> </xs:simpleType> 551 +xml 552 + <xs:simpleType name="CL\_SUBINDICATOR\_OR\_NOT\_APPLICABLE"> 553 + <xs:union memberTypes="CL\_SUBINDICATOR common:NotApplicableType"/> 554 + </xs:simpleType> 553 553 554 554 Option 2: Extending the enumeration with the special value 555 555 556 -> <xs:simpleType name="CL\_ SUBINDICATOR "> 557 -> <xs:restriction base="xs:string"> 558 -> <xs:enumeration value="A"/> 559 -> <xs:enumeration value=""/> 560 -> <xs:restriction> 561 -> </xs:simpleType> 558 +xml 559 + <xs:simpleType name="CL\_ SUBINDICATOR "> 560 + <xs:restriction base="xs:string"> 561 + <xs:enumeration value="A"/> 562 + <xs:enumeration value=""/> 563 + <xs:restriction> 564 + </xs:simpleType> 562 562 563 563 For convenience the common schema provides the union types for the following data types. 564 564 ... ... @@ -595,35 +595,38 @@ 595 595 596 596 === 3.3.8 Representation for Intentionally Missing Measure and Attribute Values === 597 597 598 -For intentionally missing [[measure>>doc:sdmx:Glossary.Measure.WebHome]]and[[attribute>>doc:sdmx:Glossary.Attribute.WebHome]]values, even if mandatory, the following special values can be used:601 +For intentionally missing measure and attribute values, even if mandatory, the following special values can be used: 599 599 600 600 * NaN for all numeric types (float, double) 601 601 * #N/A for all other types 602 602 603 -To support a specific type and allow for an intentionally missing [[measure>>doc:sdmx:Glossary.Measure.WebHome]]or[[attribute>>doc:sdmx:Glossary.Attribute.WebHome]]value, the structure-specific schema must union the type with the common:MissingType, which enumerates the #N/A string. Note that XML natively already supports NaN for float and double values.606 +To support a specific type and allow for an intentionally missing measure or attribute value, the structure-specific schema must union the type with the common:MissingType, which enumerates the #N/A string. Note that XML natively already supports NaN for float and double values. 604 604 605 605 This union is as shown in the following example: 606 606 607 -> <xs:simpleType name="DecimalOrMissingType"> 608 -> <xs:union memberTypes="xs:decimal common:MissingType"/> 609 -> </xs:simpleType> 610 +xml 611 + <xs:simpleType name="DecimalOrMissingType"> 612 + <xs:union memberTypes="xs:decimal common:MissingType"/> 613 + </xs:simpleType> 610 610 611 611 For enumerated types, the generated structure-specific schema can include the special value in the enumeration or create a union between the enumerated type and the common:MissingType. 612 612 613 613 Option 1: Augmenting the enumeration with the special value 614 614 615 - > <xs:simpleType name="CL\_SUBINDICATOR\_OR\_NOT\_APPLICABLE"> 616 - > <xs:union memberTypes="CL\_SUBINDICATOR common:MissingType"/> 617 - > </xs:simpleType> 619 +xml 620 + <xs:simpleType name="CL\_SUBINDICATOR\_OR\_NOT\_APPLICABLE"> 621 + <xs:union memberTypes="CL\_SUBINDICATOR common:MissingType"/> 622 + </xs:simpleType> 618 618 619 619 Option 2: Extending the enumeration with the special value 620 620 621 -> <xs:simpleType name="CL\_ SUBINDICATOR "> 622 -> <xs:restriction base="xs:string"> 623 -> <xs:enumeration value="A"/> 624 -> <xs:enumeration value="#N/A"/> 625 -> <xs:restriction> 626 -> </xs:simpleType> 626 +xml 627 + <xs:simpleType name="CL\_ SUBINDICATOR "> 628 + <xs:restriction base="xs:string"> 629 + <xs:enumeration value="A"/> 630 + <xs:enumeration value="#N/A"/> 631 + <xs:restriction> 632 + </xs:simpleType> 627 627 628 628 For convenience the common schema provides the union types for the following data types. 629 629