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
-
... ... @@ -788,31 +788,27 @@ 788 788 789 789 A complex type named AttsType must be created. Its content model will be derived via restriction of dsd:AttsType. The complex type content model will be as follows: 790 790 791 -~1. A sequence consisting of: 792 - 793 -* i. An element reference to common:Annotations, with a minimum occurrence of 0 794 -* ii. If any attributes with complex representation are defined in the data structure, a Comp element with a form of unqualified, a minimum occurrence of 0, a maximum occurrence of unbounded, and a type of dsd:CompType 795 - 791 +1. A sequence consisting of: 792 +1. An element reference to common:Annotations, with a minimum occurrence of 0 793 + 2. If any attributes with complex representation are defined in the data structure, a Comp element with a form of unqualified, a minimum occurrence of 0, a maximum occurrence of unbounded, and a type of dsd:CompType 796 796 2. If there is no dimension (TIME\_PERIOD) defined by the data structure, an attribute named TIME\_PERIOD with a type of common:ObservationalTimePeriod, and a usage of prohibited 797 -3. An attribute for all dimension defined by the data structure definition. The XML attribute name and type are defined according to the general rules defined in the previous section, and the usage is optional798 -4. An attribute for each data attribute defined with simple representation in the data structure. The XML attribute name and type are defined according to the general rules defined in the previous section, and the usage is optional 795 +3. An attribute for all dimension defined by the data structure definition. The XML attribute [name](#331-Component-Name-Determination) and [type](#333-Simple--Primitive-Type-Determination) are defined according to the general rules defined in the previous section, and the usage is optional 796 +4. An attribute for each data attribute defined with simple representation in the data structure. The XML attribute [name](#331-Component-Name-Determination) and [type](#333-Simple--Primitive-Type-Determination) are defined according to the general rules defined in the previous section, and the usage is optional 799 799 800 800 === 3.4.5 ObsType === 801 801 802 802 A complex type name ObsType must be created. Its content model will be derived via restriction of the base type dsd:ObsType. The complex type content model will be as follows: 803 803 804 -~1. A sequence consisting of: 805 - 806 -* i. An element reference to common:Annotations, with a minimum occurrence of 0 807 -* ii. If any measures with complex representations are defined in the data structure, any attributes with complex representation that declare an attribute relationship with the observation, a Comp element with a form of unqualified, a minimum occurrence of 0, a maximum occurrence of unbounded, and a type of dsd:CompType 808 -* iii. If any metadata attribute usages defined in the data structure that declares an attribute relationship with the observation, a local element named Metadata with the type metadata:MetadataSetType a form of unqualified, and a minimum occurrence of 0 809 - 802 +1. A sequence consisting of: 803 +1. An element reference to common:Annotations, with a minimum occurrence of 0 804 + 2. If any measures with complex representations are defined in the data structure, any attributes with complex representation that declare an attribute relationship with the observation, a Comp element with a form of unqualified, a minimum occurrence of 0, a maximum occurrence of unbounded, and a type of dsd:CompType 805 + 3. If any metadata attribute usages defined in the data structure that declares an attribute relationship with the observation, a local element named Metadata with the type metadata:MetadataSetType a form of unqualified, and a minimum occurrence of 0 810 810 2. An attribute named TIME\_PERIOD with a type of common: 811 811 ObservationalTimePeriodValueType. If the dimension at the observation level is the time dimension (TIME\_PERIOD) or all dimensions and the time dimension is defined by the data structure, a usage of required; otherwise, a usage of prohibited 812 -3. If the dimension at the observation level is not all dimensions or the time dimension (TIME\_PERIOD), an attribute for the dimension at the observation level. The XML attribute name and type are defined according to the general rules defined in the previous section, and the usage is required813 -4. If the dimension at the observation level is all dimensions, an attribute for each dimension defined by the data structure definition, except for the time dimension (TIME\_PERIOD). The XML attribute name and type are defined according to the general rules defined in the previous section, and the usage is required 814 -5. An attribute for each measure with simple representation defined by the data structure definition. The XML attribute name and type is defined according to the general rules defined in the previous section, and the usage is optional815 -6. An attribute for each data attribute with simple representation defined in the data structure that declares an attribute relationship with the observation. The XML attribute name and type are defined according to the general rules defined in the previous section, and the usage is optional 808 +3. If the dimension at the observation level is not all dimensions or the time dimension (TIME\_PERIOD), an attribute for the dimension at the observation level. The XML attribute [name](#331-Component-Name-Determination) and [type](#333-Simple--Primitive-Type-Determination) are defined according to the general rules defined in the previous section, and the usage is required 809 +4. If the dimension at the observation level is all dimensions, an attribute for each dimension defined by the data structure definition, except for the time dimension (TIME\_PERIOD). The XML attribute [name](#331-Component-Name-Determination) and [type](#333-Simple--Primitive-Type-Determination) are defined according to the general rules defined in the previous section, and the usage is required 810 +5. An attribute for each measure with simple representation defined by the data structure definition. The XML attribute [name](#331-Component-Name-Determination) and [type](#333-Simple--Primitive-Type-Determination) is defined according to the general rules defined in the previous section, and the usage is optional 811 +6. An attribute for each data attribute with simple representation defined in the data structure that declares an attribute relationship with the observation. The XML attribute [name](#331-Component-Name-Determination) and [type](#333-Simple--Primitive-Type-Determination) are defined according to the general rules defined in the previous section, and the usage is optional 816 816 817 817 === 3.4.6 CompType === 818 818 ... ... @@ -843,7 +843,7 @@ 843 843 844 844 === 4.1.2 Replace Action === 845 845 846 -Data or data-related reference metadata is to be replaced, through either update, insert or delete depending on already existing information. A full replacement is hereby assumed to take place at specific “ //replacement levels//”: for entire observations and for any specific dimension combination for data-related reference metadata attributes. Within these “replacement levels” the provided values are inserted or updated, and omitted values are deleted. Values provided for the other attributes (those above the observation level) are merged (see//Merge//action).842 +Data or data-related reference metadata is to be replaced, through either update, insert or delete depending on already existing information. A full replacement is hereby assumed to take place at specific “replacement levels”: for entire observations and for any specific dimension combination for data-related reference metadata attributes. Within these “replacement levels” the provided values are inserted or updated, and omitted values are deleted. Values provided for the other attributes (those above the observation level) are merged (see *Merge* action). 847 847 848 848 Only non-dimensional components (measure, attribute or reference metadata values) can be **omitted** (null or absent). Bulk replacing is thus not supported. 849 849 ... ... @@ -851,9 +851,9 @@ 851 851 852 852 Replacing non-existing elements is not resulting in an error. 853 853 854 -All observations as well as the sets of data-related reference metadata attributes at specific dimension combinations impacted by the //Replace//action change their time stamp when used to update an SDMX storage system.850 +All observations as well as the sets of data-related reference metadata attributes at specific dimension combinations impacted by the *Replace* action change their time stamp when used to update an SDMX storage system. 855 855 856 -Because the //replace//action always takes place at specific levels, it cannot be used to replace a whole dataset or a whole series. However, a//“replace all”//effect can be achieved by combining a//Delete//dataset containing a completely wildcarded key (where all dimension values are omitted) with a//Merge//or//Replace//dataset within the same data message. Similarly, to replace a whole series, a message can combine a//delete//dataset containing only the partial key of the series (where the not used dimension values are omitted) with a//Merge//or//Replace//dataset for that series.852 +Because the *replace* action always takes place at specific levels, it cannot be used to replace a whole dataset or a whole series. However, a “*replace all*” effect can be achieved by combining a *Delete* dataset containing a completely wildcarded key (where all dimension values are omitted) with a *Merge* or *Replace* dataset within the same data message. Similarly, to replace a whole series, a message can combine a *delete* dataset containing only the partial key of the series (where the not used dimension values are omitted) with a *Merge* or *Replace* dataset for that series. 857 857 858 858 === 4.1.3 Delete Action === 859 859 ... ... @@ -873,15 +873,14 @@ 873 873 874 874 The following convention is used to indicate the state of components in data messages: 875 875 876 -(% style="width:1591.29px" %) 877 -| | |**Dimension value is**|(% style="width:384px" %) |(% style="width:598px" %)**Measure, attribute or reference metadata value is**|(% style="width:201px" %) 878 -| | |**Omitted**|(% style="width:384px" %)**switched off**|(% style="width:598px" %)**Omitted**|(% style="width:201px" %)**Present** 879 -|Action|Delete|bulk deletion: dimension value doesn't matter|(% style="width:384px" %)only for irrelevant dimensions:1) higher-level (reference metadata) attributes not attached to this dimension(incl. TIME\_PERIOD)2) measures and attributes not attached to this dimension if the DSD allows for an ‘evolving structure’ (excl. TIME\_PERIOD)|(% style="width:598px" %)to be deleted only if **all** non-dimension components are omitted|(% style="width:201px" %)to be deleted 880 -| |Merge|//bulk merge is not permitted//|(% style="width:384px" %)(see above)|(% style="width:598px" %)not to be changed|(% style="width:201px" %)to be updated/inserted 881 -| |Replace|//bulk replace is not permitted//|(% style="width:384px" %)(see above)|(% style="width:598px" %)at permitted replacement levels: to be deleted, otherwise not to be changed|(% style="width:201px" %)to be updated/inserted 882 -|Format|XML|xml element/attribute is absent|(% style="width:384px" %)~|xml element/attribute is absent|(% style="width:598px" %)any valid or intentionally missing value|(% style="width:201px" %) 883 -| |JSON|\<empty\>|(% style="width:384px" %)““|(% style="width:598px" %)NULL or absent|(% style="width:201px" %)(see above) 884 -| |CSV|\<empty\> cell or column is absent|(% style="width:384px" %)~|<empty> cell or column is absent|(% style="width:598px" %)(see above)|(% style="width:201px" %) 872 +| | |**Dimension value is**| |**Measure, attribute or reference metadata value is**| | 873 +| | |**Omitted**|**switched off**|**Omitted**|**Present**| 874 +|Action|Delete|bulk deletion: dimension value doesn't matter|only for irrelevant dimensions:1) higher-level (reference metadata) attributes not attached to this dimension(incl. TIME\_PERIOD)2) measures and attributes not attached to this dimension if the DSD allows for an ‘evolving structure’ (excl. TIME\_PERIOD)|to be deleted only if **all** non-dimension components are omitted|to be deleted| 875 +| |Merge|*bulk merge is not permitted*|(see above)|not to be changed|to be updated/inserted| 876 +| |Replace|*bulk replace is not permitted*|(see above)|at permitted replacement levels: to be deleted, otherwise not to be changed|to be updated/inserted| 877 +|Format|XML|xml element/attribute is absent|~|xml element/attribute is absent|any valid or intentionally missing value| 878 +| |JSON|\<empty\>|““|NULL or absent|(see above)| 879 +| |CSV|\<empty\> cell or column is absent|~|<empty> cell or column is absent|(see above)| 885 885 886 886 **Important notes:** 887 887