Changes for page Part IV. Data and Reference Metadata Namespaces

Last modified by Elena on 2025/09/10 11:19

From 2.4 to 2.3 From 3.1 to 2.32

From version 2.32

edited by Helena
on 2025/07/02 15:35

Change comment: There is no comment for this version

To version 2.4

edited by Helena
on 2025/07/02 14:52

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -99,7 +99,7 @@
  |Comp|//CompType//|(% style="width:717px" %)Comp contains the details of group level attributes that have complex representation and cannot be expressed as XML attributes.
  |Metadata|MetadataSetType|(% style="width:717px" %)Allows for attachment of reference metadata against to the group.
--//**SeriesType:**// SeriesType is the abstract type which defines a structure which is used to group a collection of observations which have a key in common. The key for a series is every dimension defined in the data structure definition save the dimension declared to be at the observation level for this data set. Note, if the schema is generated against a dataflow with a dimension constraint, they key includes only the dimensions defined in the dimension constraint. In addition to observations, values can be provided for data and metadata attributes which are associated with the dimensions which make up this series key (so long as the attributes do not specify a group attachment or also have a relationship with the observation dimension). It is possible for the series to contain only observations or only attribute values, or both. Data structure definition schemas will derive a type based on this that is specific to the data structure definition and the variation of the format being expressed in the schema. Both the dimension values which make up the key and the attribute values associated with the key dimensions will be represented with XML attributes. This is specified in the content model with the declaration of anyAttributes in the "local" namespace. The derived series type will refine this structure so that the attributes are explicit. The XML attributes will be given a name based on the attribute's identifier. These XML attributes will be unqualified (meaning they do not have a namespace associated with them). The dimension XML attributes will be required while the attribute XML attributes will be optional. To allow for generic processing, it is required that the only unqualified XML attributes in the derived group type be for the series dimensions and attributes declared in the data structure definition. If additional attributes are required, these should be qualified with a namespace so that a generic application can easily distinguish them as not being meant to represent a data structure definition dimension or attribute.
++***SeriesType*:** SeriesType is the abstract type which defines a structure which is used to group a collection of observations which have a key in common. The key for a series is every dimension defined in the data structure definition save the dimension declared to be at the observation level for this data set. Note, if the schema is generated against a dataflow with a dimension constraint, they key includes only the dimensions defined in the dimension constraint. In addition to observations, values can be provided for data and metadata attributes which are associated with the dimensions which make up this series key (so long as the attributes do not specify a group attachment or also have a relationship with the observation dimension). It is possible for the series to contain only observations or only attribute values, or both. Data structure definition schemas will derive a type based on this that is specific to the data structure definition and the variation of the format being expressed in the schema. Both the dimension values which make up the key and the attribute values associated with the key dimensions will be represented with XML attributes. This is specified in the content model with the declaration of anyAttributes in the "local" namespace. The derived series type will refine this structure so that the attributes are explicit. The XML attributes will be given a name based on the attribute's identifier. These XML attributes will be unqualified (meaning they do not have a namespace associated with them). The dimension XML attributes will be required while the attribute XML attributes will be optional. To allow for generic processing, it is required that the only unqualified XML attributes in the derived group type be for the series dimensions and attributes declared in the data structure definition. If additional attributes are required, these should be qualified with a namespace so that a generic application can easily distinguish them as not being meant to represent a data structure definition dimension or attribute.
  Derivation:
@@ -114,20 +114,18 @@
  Attribute Documentation:
--(% style="width:1084.29px" %)
--|**Name**|**Type**|**Documentation**
--|TIME_PERIOD|ObservationalTimePeriodType|The TIME_PERIOD attribute is an explict attribute for the time dimension. This is declared in the base schema since it has a fixed identifier and representation. The derived series type will either require or prohibit this attribute, depending on whether time is the observation dimension. If the time dimension specifies a more specific representation of time the derived type will restrict the type definition to the appropriate type.
++|**Name**|**Type**|**Documentation**|
++|TIME_PERIOD|ObservationalTimePeriodType|The TIME_PERIOD attribute is an explict attribute for the time dimension. This is declared in the base schema since it has a fixed identifier and representation. The derived series type will either require or prohibit this attribute, depending on whether time is the observation dimension. If the time dimension specifies a more specific representation of time the derived type will restrict the type definition to the appropriate type.|
  Element Documentation:
--(% style="width:1093.29px" %)
--|**Name**|**Type**|**Documentation**
--|Annotations|AnnotationsType|Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType may reference it.
--|Comp|//CompType//|Comp contains the details of series level attributes that have complex representation and cannot be expressed as XML attributes.
--|Obs|//ObsType//|
--|Metadata|MetadataSetType|Allows for attachment of reference metadata against to the series.
++|**Name**|**Type**|**Documentation**|
++|Annotations|AnnotationsType|Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType may reference it.|
++|Comp|*CompType*|Comp contains the details of series level attributes that have complex representation and cannot be expressed as XML attributes.|
++|Obs|*ObsType*| |
++|Metadata|MetadataSetType|Allows for attachment of reference metadata against to the series.|
--//**CompType:**// CompType is the abstract base for any component value (e.g. a data or metadata attribute, or a measure) that cannot be represented as an XML attribute. For example, a repeated value, a text value in multiple languages, or a value with structured text (XHTML) cannot be expressed as an XML attribute. This type is meant to be restricted based on the component to restrict the cardinality and type of its Value element to conform to the component definition. The type of the value element should be restricted to common:SimpleValueType, common:TextValueType, or common:StructuredValueType. In addition, the id attribute should be restricted to be a fixed value with the component identifier. This restricted type based on the component can then be used on Comp elements by using the xsi:type to state the component being expressed and refine the contents of the element to the values allowed by the component.
++***CompType*:** CompType is the abstract base for any component value (e.g. a data or metadata attribute, or a measure) that cannot be represented as an XML attribute. For example, a repeated value, a text value in multiple languages, or a value with structured text (XHTML) cannot be expressed as an XML attribute. This type is meant to be restricted based on the component to restrict the cardinality and type of its Value element to conform to the component definition. The type of the value element should be restricted to common:SimpleValueType, common:TextValueType, or common:StructuredValueType. In addition, the id attribute should be restricted to be a fixed value with the component identifier. This restricted type based on the component can then be used on Comp elements by using the xsi:type to state the component being expressed and refine the contents of the element to the values allowed by the component.
  Derivation:
@@ -142,18 +142,16 @@
  Attribute Documentation:
--(% style="width:1007.29px" %)
--|(% style="width:157px" %)**Name**|(% style="width:291px" %)**Type**|(% style="width:556px" %)**Documentation**
--|(% style="width:157px" %)id|(% style="width:291px" %)NCNameIDType|(% style="width:556px" %)
++|**Name**|**Type**|**Documentation**|
++|id|NCNameIDType| |
  Element Documentation:
--(% style="width:1015.29px" %)
--|**Name**|**Type**|(% style="width:684px" %)**Documentation**
--|Annotations|AnnotationsType|(% style="width:684px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType may reference it.
--|Value|//ValueType//|(% style="width:684px" %)
++|**Name**|**Type**|**Documentation**|
++|Annotations|AnnotationsType|Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType may reference it.|
++|Value|*ValueType*| |
--//**ObsType:**// ObsType is the abstract type which defines the structure of a grouped or un-grouped observation. The observation must be provided a key, which is either a value for the dimension which is declared to be at the observation level if the observation is grouped, or a full set of values for all dimensions in the data structure definition if the observation is un-grouped. This key should disambiguate the observation within the context in which it is defined (e.g. there should not be another observation with the same dimension value in a series). The observation can contain an observed value and/or attribute values. Data structure definition schemas will derive a type or types based on this that is specific to the data structure definition and the variation of the format being expressed in the schema. The dimension value(s) which make up the key and the data and metadata attribute values associated with the key dimension(s) or the primary measure will be represented with XML attributes. This is specified in the content model with the declaration of anyAttributes in the "local" namespace. The derived observation type will refine this structure so that the attributes are explicit. The XML attributes will be given a name based on the attribute's identifier. These XML attributes will be unqualified (meaning they do not have a namespace associated with them). The dimension XML attribute(s) will be required while the attribute XML attributes will be optional. To allow for generic processing, it is required that the only unqualified XML attributes in the derived observation type be for the observation dimension(s) and attributes declared in the data structure definition. If additional attributes are required, these should be qualified with a namespace so that a generic application can easily distinguish them as not being meant to represent a data structure definition dimension or attribute.
++***ObsType*:** ObsType is the abstract type which defines the structure of a grouped or un-grouped observation. The observation must be provided a key, which is either a value for the dimension which is declared to be at the observation level if the observation is grouped, or a full set of values for all dimensions in the data structure definition if the observation is un-grouped. This key should disambiguate the observation within the context in which it is defined (e.g. there should not be another observation with the same dimension value in a series). The observation can contain an observed value and/or attribute values. Data structure definition schemas will derive a type or types based on this that is specific to the data structure definition and the variation of the format being expressed in the schema. The dimension value(s) which make up the key and the data and metadata attribute values associated with the key dimension(s) or the primary measure will be represented with XML attributes. This is specified in the content model with the declaration of anyAttributes in the "local" namespace. The derived observation type will refine this structure so that the attributes are explicit. The XML attributes will be given a name based on the attribute's identifier. These XML attributes will be unqualified (meaning they do not have a namespace associated with them). The dimension XML attribute(s) will be required while the attribute XML attributes will be optional. To allow for generic processing, it is required that the only unqualified XML attributes in the derived observation type be for the observation dimension(s) and attributes declared in the data structure definition. If additional attributes are required, these should be qualified with a namespace so that a generic application can easily distinguish them as not being meant to represent a data structure definition dimension or attribute.
  Derivation:
@@ -168,18 +168,16 @@
  Attribute Documentation:
--(% style="width:1008.29px" %)
--|**Name**|**Type**|(% style="width:648px" %)**Documentation**
--|type|IDType|(% style="width:648px" %)The type attribute is used when the derived format requires that explicit measure be used. In this case, the derived type based on the measure will fix this value to be the identification of the measure concept. This will not be required, but since it is fixed it will be available in the post validation information set which will allow for generic processing of the data. If explicit measures are not used, then the derived type will prohibit the use of this attribute.
--|TIME_PERIOD|ObservationalTimePeriodType|(% style="width:648px" %)The TIME_PERIOD attribute is an explicit attribute for the time dimension. This is declared in the base schema since it has a fixed identifier and representation. The derived series type will either require or prohibit this attribute, depending on whether time is the observation dimension. If the time dimension specifies a more specific representation of time the derived type will restrict the type definition to the appropriate type.
++|**Name**|**Type**|**Documentation**|
++|type|IDType|The type attribute is used when the derived format requires that explicit measure be used. In this case, the derived type based on the measure will fix this value to be the identification of the measure concept. This will not be required, but since it is fixed it will be available in the post validation information set which will allow for generic processing of the data. If explicit measures are not used, then the derived type will prohibit the use of this attribute.|
++|TIME_PERIOD|ObservationalTimePeriodType|The TIME_PERIOD attribute is an explicit attribute for the time dimension. This is declared in the base schema since it has a fixed identifier and representation. The derived series type will either require or prohibit this attribute, depending on whether time is the observation dimension. If the time dimension specifies a more specific representation of time the derived type will restrict the type definition to the appropriate type.|
  Element Documentation:
--(% style="width:1020.29px" %)
--|**Name**|**Type**|**Documentation**
--|Annotations|AnnotationsType|Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType may reference it.
--|Comp|//CompType//|Comp contains the details of observation measures or attributes that have complex representation and cannot be expressed as XML attributes.
--|Metadata|MetadataSetType|Allows for attachment of reference metadata against to the observation.
++|**Name**|**Type**|**Documentation**|
++|Annotations|AnnotationsType|Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType may reference it.|
++|Comp|*CompType*|Comp contains the details of observation measures or attributes that have complex representation and cannot be expressed as XML attributes.|
++|Metadata|MetadataSetType|Allows for attachment of reference metadata against to the observation.|
  ***AttsType*:** AttsType is the abstract type which defines a structure which is used to group a collection of data or metadata attributes which have a key in common. The key for a attribute collection is a subset of the dimension defined in the data structure definition. This is also used for data set level attributes (i.e. those with an attribute relationship of none). In this case, the subset of dimensions is empty. Data structure definition schemas will derive a type based on this that is specific to the data structure definition. The dimension values which make up the key will be represented with local (non-namespace qualified) XML attributes. The metadata attribute values associated with the key dimensions will be expressed as XML local (non-namespace qualified) attributes if they are simple values (e.g. enumerated, dates, numbers) and are not repeatable. Metadata attributes that are repeatable, or do not have simple values (e.g. text) will be expressed using the Comp element. These dimensions and simple attributes are specified in the content model with the declaration of anyAttributes in the "local" namespace. The derived series type will refine this structure so that the attributes are explicit. The XML attributes will be given a name based on the attribute's identifier. These XML attributes will be unqualified (meaning they do not have a namespace associated with them). The dimension XML attributes will be required while the attribute XML attributes will be optional. To allow for generic processing, it is required that the only unqualified XML attributes in the derived group type be for the series dimensions and attributes declared in the data structure definition. If additional attributes are required, these should be qualified with a namespace so that a generic application can easily distinguish them as not being meant to represent a data structure definition dimension or attribute.
@@ -196,31 +196,29 @@
  Attribute Documentation:
--(% style="width:1013.29px" %)
--|**Name**|**Type**|**Documentation**
--|TIME_PERIOD|ObservationalTimePeriodType|The TIME_PERIOD attribute is an explict attribute for the time dimension. This is declared in the base schema since it has a fixed identifier and representation. The derived series type will either require or prohibit this attribute, depending on whether time is the observation dimension. If the time dimension specifies a more specific representation of time the derived type will restrict the type definition to the appropriate type.
++|**Name**|**Type**|**Documentation**|
++|TIME_PERIOD|ObservationalTimePeriodType|The TIME_PERIOD attribute is an explict attribute for the time dimension. This is declared in the base schema since it has a fixed identifier and representation. The derived series type will either require or prohibit this attribute, depending on whether time is the observation dimension. If the time dimension specifies a more specific representation of time the derived type will restrict the type definition to the appropriate type.|
  Element Documentation:
--(% style="width:1020.29px" %)
--|**Name**|**Type**|**Documentation**
--|Annotations|AnnotationsType|Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType may reference it.
--|Comp|//CompType//|Comp contains the details of the data or metadata attributes that have complex representation and cannot be expressed as XML attributes.
++|**Name**|**Type**|**Documentation**|
++|Annotations|AnnotationsType|Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType may reference it.|
++|Comp|*CompType*|Comp contains the details of the data or metadata attributes that have complex representation and cannot be expressed as XML attributes.|
  == 2.2 Generic Reference Metadata Namespace ==
--[[http:~~/~~/www.sdmx.org/resources/sdmxml/schemas/v3_1/metadata/generic>>http://www.sdmx.org/resources/sdmxml/schemas/v3_1/metadata/generic**]]
++**http://www.sdmx.org/resources/sdmxml/schemas/v3_1/metadata/generic****
  === 2.2.1 Summary ===
  Referenced Namespaces:
--(% style="width:1037.29px" %)
--|(% style="width:516px" %)**Namespace**|(% style="width:518px" %)**Prefix**
--|(% style="width:516px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v3\_1/common|(% style="width:518px" %)common
--|(% style="width:516px" %)<http:~/~/www.w3.org/2001/XMLSchema>|(% style="width:518px" %)xs
++|**Namespace**|**Prefix**|
++|http://www.sdmx.org/resources/sdmxml/schemas/v3\_1/common|common|
++|<http://www.w3.org/2001/XMLSchema>|xs|
  Contents:
++
 Global Element
 Complex Types
@@ -250,28 +250,26 @@
  Attribute Documentation:
--(% style="width:1051.29px" %)
--|**Name**|**Type**|(% style="width:669px" %)**Documentation**
--|id|IDType|(% style="width:669px" %)The id is the identifier for the object.
--|urn|MetadataSetUrnType|(% style="width:669px" %)The urn attribute holds a valid SDMX Registry URN (see SDMX Registry Specification for details).
--|uri|xs:anyURI|(% style="width:669px" %)The uri attribute holds a URI that contains a link to a resource with additional information about the object, such as a web page. This uri is not a SDMX message.
--|version|VersionType|(% style="width:669px" %)This version attribute holds a version number (see common:VersionType definition for details). If not supplied, artefact is considered to be un-versioned.
--|validFrom|xs:dateTime|(% style="width:669px" %)The validFrom attribute provides the inclusive start date for providing supplemental validity information about the version.
--|validTo|xs:dateTime|(% style="width:669px" %)The validTo attribute provides the inclusive end date for providing supplemental validity information about the version.
--|agencyID|NestedNCNameIDType|(% style="width:669px" %)The agencyID must be provided and identifies the maintenance agency of the object.
--|isExternalReference (default: false)|xs:boolean|(% style="width:669px" %)The isExternalReference attribute, if true, indicates that the actual object is not defined the corresponding element, rather its full details are defined elsewhere - indicated by either the registryURL, the repositoryURL, or the structureURL. The purpose of this is so that each structure message does not have to redefine object that are already defined elsewhere. If the isExternalReference attribute is not set, then it is assumed to be false, and the object should contain the full definition of its contents. If more than one of the registryURL, the repositoryURL, and the structureURL are supplied, then the application processing the object can choose the method it finds best suited to retrieve the details of the object.
--|serviceURL|xs:anyURI|(% style="width:669px" %)The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface.
--|structureURL|xs:anyURI|(% style="width:669px" %)The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.
--|isPartialLanguage (default: false)|xs:boolean|(% style="width:669px" %)The isPartialLanguage attribute, if true, indicates that the object doesn't contain the complete set of all available languages, e.g., when obtained as a response to a GET query that requested specific languages through the HTTP header Accept-Language.
++|**Name**|**Type**|**Documentation**|
++|id|IDType|The id is the identifier for the object.|
++|urn|MetadataSetUrnType|The urn attribute holds a valid SDMX Registry URN (see SDMX Registry Specification for details).|
++|uri|xs:anyURI|The uri attribute holds a URI that contains a link to a resource with additional information about the object, such as a web page. This uri is not a SDMX message.|
++|version|VersionType|This version attribute holds a version number (see common:VersionType definition for details). If not supplied, artefact is considered to be un-versioned.|
++|validFrom|xs:dateTime|The validFrom attribute provides the inclusive start date for providing supplemental validity information about the version.|
++|validTo|xs:dateTime|The validTo attribute provides the inclusive end date for providing supplemental validity information about the version.|
++|agencyID|NestedNCNameIDType|The agencyID must be provided and identifies the maintenance agency of the object.|
++|isExternalReference (default: false)|xs:boolean|The isExternalReference attribute, if true, indicates that the actual object is not defined the corresponding element, rather its full details are defined elsewhere - indicated by either the registryURL, the repositoryURL, or the structureURL. The purpose of this is so that each structure message does not have to redefine object that are already defined elsewhere. If the isExternalReference attribute is not set, then it is assumed to be false, and the object should contain the full definition of its contents. If more than one of the registryURL, the repositoryURL, and the structureURL are supplied, then the application processing the object can choose the method it finds best suited to retrieve the details of the object.|
++|serviceURL|xs:anyURI|The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface.|
++|structureURL|xs:anyURI|The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.|
++|isPartialLanguage (default: false)|xs:boolean|The isPartialLanguage attribute, if true, indicates that the object doesn't contain the complete set of all available languages, e.g., when obtained as a response to a GET query that requested specific languages through the HTTP header Accept-Language.|
  Element Documentation:
--(% style="width:1057.29px" %)
--|**Name**|**Type**|**Documentation**
--|Annotations|AnnotationsType|Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType may reference it.
--|Link|LinkType|Allows for the linking of other resources to identifiable objects. For example, if there is reference metadata associated with a structure, a link to the metadata report can be dynamically inserted in the structure metadata.
--|Name|TextType|Name provides for a human-readable name for the object. This may be provided in multiple, parallel language-equivalent forms.
--|Description|TextType|Description provides for a longer human-readable description of the object. This may be provided in multiple, parallel language-equivalent forms.
++|**Name**|**Type**|**Documentation**|
++|Annotations|AnnotationsType|Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType may reference it.|
++|Link|LinkType|Allows for the linking of other resources to identifiable objects. For example, if there is reference metadata associated with a structure, a link to the metadata report can be dynamically inserted in the structure metadata.|
++|Name|TextType|Name provides for a human-readable name for the object. This may be provided in multiple, parallel language-equivalent forms.|
++|Description|TextType|Description provides for a longer human-readable description of the object. This may be provided in multiple, parallel language-equivalent forms.|
  **MetadataSetType:** MetadataSetType describes the structure for a metadata set, which contains a collection of reported metadata against a set of targets. The targets should conform to the restrictions described by the metadata provision or the metadataflow. Note that this is maintainable, and as such must specify in agency. In this case, the agency is the metadata provider. If a metadata provision agreement is referenced, it is assumed that the metadata provider described in the provision will be the same as the agency for this set.
@@ -294,36 +294,34 @@
  Attribute Documentation:
--(% style="width:1050.29px" %)
--|**Name**|**Type**|(% style="width:622px" %)**Documentation**
--|id|IDType|(% style="width:622px" %)The id is the identifier for the object.
--|urn|MetadataSetUrnType|(% style="width:622px" %)The urn attribute holds a valid SDMX Registry URN (see SDMX Registry Specification for details).
--|uri|xs:anyURI|(% style="width:622px" %)The uri attribute holds a URI that contains a link to a resource with additional information about the object, such as a web page. This uri is not a SDMX message.
--|version|VersionType|(% style="width:622px" %)This version attribute holds a version number (see common:VersionType definition for details). If not supplied, artefact is considered to be un-versioned.
--|validFrom|xs:dateTime|(% style="width:622px" %)The validFrom attribute provides the inclusive start date for providing supplemental validity information about the version.
--|validTo|xs:dateTime|(% style="width:622px" %)The validTo attribute provides the inclusive end date for providing supplemental validity information about the version.
--|agencyID|NestedNCNameIDType|(% style="width:622px" %)The agencyID must be provided and identifies the maintenance agency of the object.
--|isExternalReference (default: false)|xs:boolean|(% style="width:622px" %)The isExternalReference attribute, if true, indicates that the actual object is not defined the corresponding element, rather its full details are defined elsewhere - indicated by either the registryURL, the repositoryURL, or the structureURL. The purpose of this is so that each structure message does not have to redefine object that are already defined elsewhere. If the isExternalReference attribute is not set, then it is assumed to be false, and the object should contain the full definition of its contents. If more than one of the registryURL, the repositoryURL, and the structureURL are supplied, then the application processing the object can choose the method it finds best suited to retrieve the details of the object.
--|serviceURL|xs:anyURI|(% style="width:622px" %)The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface.
--|structureURL|xs:anyURI|(% style="width:622px" %)The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.
--|isPartialLanguage (default: false)|xs:boolean|(% style="width:622px" %)The isPartialLanguage attribute, if true, indicates that the object doesn't contain the complete set of all available languages, e.g., when obtained as a response to a GET query that requested specific languages through the HTTP header Accept-Language.
--|reportingBeginDate|BasicTimePeriodType|(% style="width:622px" %)The reportingBeginDate indicates the inclusive start time of the data reported in the data or metadata set.
--|reportingEndDate|BasicTimePeriodType|(% style="width:622px" %)The reportingEndDate indicates the inclusive end time of the data reported in the data or metadata set.
--|publicationYear|xs:gYear|(% style="width:622px" %)The publicationYear holds the ISO 8601 four-digit year.
--|publicationPeriod|ObservationalTimePeriodType|(% style="width:622px" %)The publicationPeriod specifies the period of publication of the data or metadata in terms of whatever provisioning agreements might be in force (i.e., "Q1 2005" if that is the time of publication for a data set published on a quarterly basis).
++|**Name**|**Type**|**Documentation**|
++|id|IDType|The id is the identifier for the object.|
++|urn|MetadataSetUrnType|The urn attribute holds a valid SDMX Registry URN (see SDMX Registry Specification for details).|
++|uri|xs:anyURI|The uri attribute holds a URI that contains a link to a resource with additional information about the object, such as a web page. This uri is not a SDMX message.|
++|version|VersionType|This version attribute holds a version number (see common:VersionType definition for details). If not supplied, artefact is considered to be un-versioned.|
++|validFrom|xs:dateTime|The validFrom attribute provides the inclusive start date for providing supplemental validity information about the version.|
++|validTo|xs:dateTime|The validTo attribute provides the inclusive end date for providing supplemental validity information about the version.|
++|agencyID|NestedNCNameIDType|The agencyID must be provided and identifies the maintenance agency of the object.|
++|isExternalReference (default: false)|xs:boolean|The isExternalReference attribute, if true, indicates that the actual object is not defined the corresponding element, rather its full details are defined elsewhere - indicated by either the registryURL, the repositoryURL, or the structureURL. The purpose of this is so that each structure message does not have to redefine object that are already defined elsewhere. If the isExternalReference attribute is not set, then it is assumed to be false, and the object should contain the full definition of its contents. If more than one of the registryURL, the repositoryURL, and the structureURL are supplied, then the application processing the object can choose the method it finds best suited to retrieve the details of the object.|
++|serviceURL|xs:anyURI|The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface.|
++|structureURL|xs:anyURI|The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.|
++|isPartialLanguage (default: false)|xs:boolean|The isPartialLanguage attribute, if true, indicates that the object doesn't contain the complete set of all available languages, e.g., when obtained as a response to a GET query that requested specific languages through the HTTP header Accept-Language.|
++|reportingBeginDate|BasicTimePeriodType|The reportingBeginDate indicates the inclusive start time of the data reported in the data or metadata set.|
++|reportingEndDate|BasicTimePeriodType|The reportingEndDate indicates the inclusive end time of the data reported in the data or metadata set.|
++|publicationYear|xs:gYear|The publicationYear holds the ISO 8601 four-digit year.|
++|publicationPeriod|ObservationalTimePeriodType|The publicationPeriod specifies the period of publication of the data or metadata in terms of whatever provisioning agreements might be in force (i.e., "Q1 2005" if that is the time of publication for a data set published on a quarterly basis).|
  Element Documentation:
--(% style="width:1054.29px" %)
--|**Name**|(% style="width:185px" %)**Type**|(% style="width:412px" %)**Documentation**
--|Annotations|(% style="width:185px" %)AnnotationsType|(% style="width:412px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType may reference it.
--|Link|(% style="width:185px" %)LinkType|(% style="width:412px" %)Allows for the linking of other resources to identifiable objects. For example, if there is reference metadata associated with a structure, a link to the metadata report can be dynamically inserted in the structure metadata.
--|Name|(% style="width:185px" %)TextType|(% style="width:412px" %)Name provides for a human-readable name for the object. This may be provided in multiple, parallel language-equivalent forms.
--|Description|(% style="width:185px" %)TextType|(% style="width:412px" %)Description provides for a longer human-readable description of the object. This may be provided in multiple, parallel language-equivalent forms.
--|MetadataProvision<br/>Agreement|(% style="width:185px" %)MetadataProvisionAgree<br/>mentReferenceType|(% style="width:412px" %)Metadataflow provides a reference to the metadata provision agreement the metadata set is being reported against.
--|Metadataflow|(% style="width:185px" %)MetadataflowReference<br/>Type|(% style="width:412px" %)Metadataflow provides a reference to the metadataflow the metadata set is being reported against.
--|Target|(% style="width:185px" %)WildcardUrnType|(% style="width:412px" %)Target references the target structures for which metadata is being reported. These must conform with the constraints defined by the metadata provision agreement and/or the metadataflow.
--|Attribute|(% style="width:185px" %)AttributeType|(% style="width:412px" %)Att elements hold the reported metadata attribute values being reported in the metadata set. These conform to the metadata structure definition.
++|**Name**|**Type**|**Documentation**|
++|Annotations|AnnotationsType|Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType may reference it.|
++|Link|LinkType|Allows for the linking of other resources to identifiable objects. For example, if there is reference metadata associated with a structure, a link to the metadata report can be dynamically inserted in the structure metadata.|
++|Name|TextType|Name provides for a human-readable name for the object. This may be provided in multiple, parallel language-equivalent forms.|
++|Description|TextType|Description provides for a longer human-readable description of the object. This may be provided in multiple, parallel language-equivalent forms.|
++|MetadataProvision<br/>Agreement|MetadataProvisionAgree<br/>mentReferenceType|Metadataflow provides a reference to the metadata provision agreement the metadata set is being reported against.|
++|Metadataflow|MetadataflowReference<br/>Type|Metadataflow provides a reference to the metadataflow the metadata set is being reported against.|
++|Target|WildcardUrnType|Target references the target structures for which metadata is being reported. These must conform with the constraints defined by the metadata provision agreement and/or the metadataflow.|
++|Attribute|AttributeType|Att elements hold the reported metadata attribute values being reported in the metadata set. These conform to the metadata structure definition.|
  **AttributeType:** AttributeType defines the structure for a reported metadata attribute. A value for the attribute can be supplied as either a single value (enumerated or non-enumerated single value), or multi-lingual text values (either structured or unstructured). Optional child attributes are also available if the metadata attribute definition defines nested metadata attributes.
@@ -340,19 +340,17 @@
  Attribute Documentation:
--(% style="width:1037.29px" %)
--|(% style="width:113px" %)**Name**|(% style="width:162px" %)**Type**|(% style="width:760px" %)**Documentation**
--|(% style="width:113px" %)id|(% style="width:162px" %)IDType|(% style="width:760px" %)The id attribute identifies the metadata attribute that the value is being reported for.
++|**Name**|**Type**|**Documentation**|
++|id|IDType|The id attribute identifies the metadata attribute that the value is being reported for.|
  Element Documentation:
--(% style="width:1095.29px" %)
--|**Name**|**Type**|(% style="width:821px" %)**Documentation**
--|Annotations|AnnotationsType|(% style="width:821px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType may reference it.
--|Value|xs:anySimpleType|(% style="width:821px" %)Value holds any simple value (enumerated or not) for the metadata attribute. It can be repeated if this metadata attribute allows for multiple values.
--|Text|TextType|(% style="width:821px" %)Text is used to supply parallel multi-lingual textual values for the reported metadata attribute. This will be used if the text format of the metadata attribute has a type of string, and the multi-lingual value is set to true.
--|StructuredText|XHTMLType|(% style="width:821px" %)StructuredText is used to supply parallel multi-lingual structured (as XHTML) textual values for the reported metadata attribute. This will be used if the text format of the metadata attribute has a type of XHTML, and the multi-lingual value is set to true.
--|Attribute|AttributeType|(% style="width:821px" %)Att contains the reported metadata attribute values for the child metadata attributes.
++|**Name**|**Type**|**Documentation**|
++|Annotations|AnnotationsType|Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType may reference it.|
++|Value|xs:anySimpleType|Value holds any simple value (enumerated or not) for the metadata attribute. It can be repeated if this metadata attribute allows for multiple values.|
++|Text|TextType|Text is used to supply parallel multi-lingual textual values for the reported metadata attribute. This will be used if the text format of the metadata attribute has a type of string, and the multi-lingual value is set to true.|
++|StructuredText|XHTMLType|StructuredText is used to supply parallel multi-lingual structured (as XHTML) textual values for the reported metadata attribute. This will be used if the text format of the metadata attribute has a type of XHTML, and the multi-lingual value is set to true.|
++|Attribute|AttributeType|Att contains the reported metadata attribute values for the child metadata attributes.|
  = 3 Mapping to Structure-Specific Schemas =
@@ -367,10 +367,10 @@
  In the subsequent sections, the following namespace prefixes are used:
  |**Namespace**|**Prefix**|
--|http:~/~/www.w3.org/2001/XMLSchema|xs|
--|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v3_1/common|common|
--|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v3_1/data/structurespecific|dsd|
--|<http:~/~/www.sdmx.org/resources/sdmxml/schemas/v3_1/metadata/generic>|metadata|
++|http://www.w3.org/2001/XMLSchema|xs|
++|http://www.sdmx.org/resources/sdmxml/schemas/v3_1/common|common|
++|http://www.sdmx.org/resources/sdmxml/schemas/v3_1/data/structurespecific|dsd|
++|<http://www.sdmx.org/resources/sdmxml/schemas/v3_1/metadata/generic>|metadata|
  It is assumed that in order to use this guide, the reader is familiar with schema terminology. However, for convenience the following is list of the terminology used here:
@@ -434,8 +434,8 @@
  The representation of a component is determined by the following precedence:
 . The local representation defined by the component
--1. The core representation defined in the concept from which the component takes its semantic
--1. A default representation of an un-faceted text format with a data type of String.
++2. The core representation defined in the concept from which the component takes its semantic
++3. A default representation of an un-faceted text format with a data type of String.
  The representation will either define a text format, an enumeration with an enumeration format, or a union of the former with the value of a irrelevant representation ‘’ (tilde).
@@ -460,6 +460,7 @@
              </xs:annotation>
           </xs:enumeration>
++
  === 3.3.5 Representation with Value List Enumeration ===
  A representation which defines an enumeration from a value list will result in a simple type that is a restriction of the xs:string data type. The simple type will define enumerations for each value item in the value list. The value for these enumerations will be identifier of the item. If desired, the names of the item may be placed in the documentation of the enumeration, but this is not required.
@@ -474,61 +474,61 @@
  If the representation is not simple, see the rules in the following section for complex text formats. If the representation is simple, the first step is to determine the base type from the text format data type:
--(% style="width:679.294px" %)
--|(% style="width:286px" %)**SDMX Data Type**|(% style="width:390px" %)**XML Schema Data Type**
--|(% style="width:286px" %)String|(% style="width:390px" %)xs:string
--|(% style="width:286px" %)AlphaNumeric|(% style="width:390px" %)common:AlphaNumericType
--|(% style="width:286px" %)Alpha|(% style="width:390px" %)common:AlphaType
--|(% style="width:286px" %)Numeric|(% style="width:390px" %)common:NumericType
--|(% style="width:286px" %)BigInteger|(% style="width:390px" %)xs:integer
--|(% style="width:286px" %)Integer|(% style="width:390px" %)xs:int
--|(% style="width:286px" %)Long|(% style="width:390px" %)xs:long
--|(% style="width:286px" %)Short|(% style="width:390px" %)xs:short
--|(% style="width:286px" %)Decimal|(% style="width:390px" %)xs:decimal
--|(% style="width:286px" %)Float|(% style="width:390px" %)xs:float
--|(% style="width:286px" %)Double|(% style="width:390px" %)xs:double
--|(% style="width:286px" %)Boolean|(% style="width:390px" %)xs:Boolean
--|(% style="width:286px" %)URI|(% style="width:390px" %)xs:anyURI
--|(% style="width:286px" %)Count|(% style="width:390px" %)xs:integer
--|(% style="width:286px" %)InclusiveValueRange|(% style="width:390px" %)xs:decimal
--|(% style="width:286px" %)ExclusiveValueRange|(% style="width:390px" %)xs: decimal
--|(% style="width:286px" %)Incremental|(% style="width:390px" %)xs: decimal
--|(% style="width:286px" %)ObservationalTimePeriod|(% style="width:390px" %)common:ObservationalTimePeriodType
--|(% style="width:286px" %)StandardTimePeriod|(% style="width:390px" %)common:StandardTimePeriodType
--|(% style="width:286px" %)BasicTimePeriod|(% style="width:390px" %)common:BasicTimePeriodType
--|(% style="width:286px" %)GregorianTimePeriod|(% style="width:390px" %)common:GregorianTimePeriodType
--|(% style="width:286px" %)GregorianYear|(% style="width:390px" %)xs:gYear
--|(% style="width:286px" %)GregorianYearMonth|(% style="width:390px" %)xs:gYearMonth
--|(% style="width:286px" %)GregorianDay|(% style="width:390px" %)xs:date
--|(% style="width:286px" %)ReportingTimePeriod|(% style="width:390px" %)common:ReportingTimePeriodType
--|(% style="width:286px" %)ReportingYear|(% style="width:390px" %)common:ReportingYearType
--|(% style="width:286px" %)ReportingSemester|(% style="width:390px" %)common:ReportingSemesterType
--|(% style="width:286px" %)ReportingTrimester|(% style="width:390px" %)common:ReportingTrimesterType
--|(% style="width:286px" %)ReportingQuarter|(% style="width:390px" %)common:ReportingQuarterType
--|(% style="width:286px" %)ReportingMonth|(% style="width:390px" %)common:ReportingMonthType
--|(% style="width:286px" %)ReportingWeek|(% style="width:390px" %)common:ReportingWeekType
--|(% style="width:286px" %)ReportingDay|(% style="width:390px" %)common:ReportingDayType
--|(% style="width:286px" %)DateTime|(% style="width:390px" %)xs:dateTime
--|(% style="width:286px" %)TimeRange|(% style="width:390px" %)common:TimeRangeType
--|(% style="width:286px" %)Month|(% style="width:390px" %)xs:gMonth
--|(% style="width:286px" %)MonthDay|(% style="width:390px" %)xs:gMonthDay
--|(% style="width:286px" %)Day|(% style="width:390px" %)xs:gDay
--|(% style="width:286px" %)Time|(% style="width:390px" %)xs:time
--|(% style="width:286px" %)Duration|(% style="width:390px" %)xs:duration
--|(% style="width:286px" %)GeospatialInformation|(% style="width:390px" %)xs:string
--|(% style="width:286px" %)XHTML|(% style="width:390px" %)See the following section for complex representations
++|**SDMX Data Type**|**XML Schema Data Type**|
++|String|xs:string|
++|AlphaNumeric|common:AlphaNumericType|
++|Alpha|common:AlphaType|
++|Numeric|common:NumericType|
++|BigInteger|xs:integer|
++|Integer|xs:int|
++|Long|xs:long|
++|Short|xs:short|
++|Decimal|xs:decimal|
++|Float|xs:float|
++|Double|xs:double|
++|Boolean|xs:Boolean|
++|URI|xs:anyURI|
++|Count|xs:integer|
++|InclusiveValueRange|xs:decimal|
++|ExclusiveValueRange|xs: decimal|
++|Incremental|xs: decimal|
++|ObservationalTimePeriod|common:ObservationalTimePeriodType|
++|StandardTimePeriod|common:StandardTimePeriodType|
++|BasicTimePeriod|common:BasicTimePeriodType|
++|GregorianTimePeriod|common:GregorianTimePeriodType|
++|GregorianYear|xs:gYear|
++|GregorianYearMonth|xs:gYearMonth|
++|GregorianDay|xs:date|
++|ReportingTimePeriod|common:ReportingTimePeriodType|
++|ReportingYear|common:ReportingYearType|
++|ReportingSemester|common:ReportingSemesterType|
++|ReportingTrimester|common:ReportingTrimesterType|
++|ReportingQuarter|common:ReportingQuarterType|
++|ReportingMonth|common:ReportingMonthType|
++|ReportingWeek|common:ReportingWeekType|
++|ReportingDay|common:ReportingDayType|
++|DateTime|xs:dateTime|
++|TimeRange|common:TimeRangeType|
++|Month|xs:gMonth|
++|MonthDay|xs:gMonthDay|
++|Day|xs:gDay|
++|Time|xs:time|
++|Duration|xs:duration|
++|GeospatialInformation|xs:string|
++|XHTML|See the following section for complex representations|
  If the text format does not specify any further facets, then the determined type is the listed type or a type which derives from the listed type without placing any addition restrictions on it. However, if one or more facets are specified, then a simple type based on the listed type is necessary. The simple type derives via restriction from the listed type and adds facets according to the following table (the values are mapped as is):
--(% style="width:1007.29px" %)
--|(% style="width:267px" %)**SDMX Facet**|(% style="width:729px" %)**XML Schema Facet**
--|(% style="width:267px" %)minLength|(% style="width:729px" %)xs:minLength
--|(% style="width:267px" %)maxLength|(% style="width:729px" %)xs:maxLength
--|(% style="width:267px" %)minValue{{footnote}}Note that these options only apply to numeric representations and should be ignored if the data type is non-numeric.{{/footnote}}|(% style="width:729px" %)if ExclusiveValueRange: xs:minExclusives, else: xs:minInclusive
--|(% style="width:267px" %)maxValue^^1^^|(% style="width:729px" %)if ExclusiveValueRange: xs:maxExclusives, else: xs:maxInclusive
--|(% style="width:267px" %)decimals^^1^^|(% style="width:729px" %)xs:fractionDigits
--|(% style="width:267px" %)pattern|(% style="width:729px" %)xs:pattern
++|**SDMX Facet**|**XML Schema Facet**|
++|minLength|xs:minLength|
++|maxLength|xs:maxLength|
++|minValue[^1]|if ExclusiveValueRange: xs:minExclusives, else: xs:minInclusive|
++|maxValue[^1]|if ExclusiveValueRange: xs:maxExclusives, else: xs:maxInclusive|
++|decimals[^1]|xs:fractionDigits|
++|pattern|xs:pattern|
++[^1]: Note that these options only apply to numeric representations and should be ignored if the data type is non-numeric.
++
  Any other facets are informational only and will not affect the determined type.
  === 3.3.7 Representation for Not Applicable Dimensions ===
@@ -563,36 +563,35 @@
  For convenience the common schema provides the union types for the following data types.
--(% style="width:747.294px" %)
--|**SDMX Data Type**|(% style="width:418px" %)**XML Schema Data Type**
--|AlphaNumeric|(% style="width:418px" %)common:AlphaNumericOrNotApplicableType
--|Alpha|(% style="width:418px" %)common:AlphaOrNotApplicableType
--|Numeric|(% style="width:418px" %)common:NumericOrNotApplicableType
--|BigInteger|(% style="width:418px" %)common:IntegerOrNotApplicableType
--|Integer|(% style="width:418px" %)common:IntOrNotApplicableType
--|Long|(% style="width:418px" %)common:LongOrNotApplicableType
--|Short|(% style="width:418px" %)common:ShortOrNotApplicableType
--|Decimal|(% style="width:418px" %)common:DecimalOrNotApplicableType
--|Float|(% style="width:418px" %)common:FloatOrNotApplicableType
--|Double|(% style="width:418px" %)common:DoubleOrNotApplicableType
--|Boolean|(% style="width:418px" %)common:BooleanOrNotApplicableType
--|Count|(% style="width:418px" %)common:IntegerOrNotApplicableType
--|InclusiveValueRange|(% style="width:418px" %)common:DecimalOrNotApplicableType
--|ExclusiveValueRange|(% style="width:418px" %)common:DecimalOrNotApplicableType
--|Incremental|(% style="width:418px" %)common:DecimalOrNotApplicableType
--|ObservationalTimePeriod|(% style="width:418px" %)common:ObservationalTimePeriodOrNotApplicableType
--|StandardTimePeriod|(% style="width:418px" %)common:StandardTimePeriodOrNotApplicableType
--|BasicTimePeriod|(% style="width:418px" %)common:BasicTimePeriodType
--|GregorianTimePeriod|(% style="width:418px" %)common:GregorianTimePeriodOrNotApplicableType
--|ReportingTimePeriod|(% style="width:418px" %)common:ReportingTimePeriodOrNotApplicableType
--|ReportingYear|(% style="width:418px" %)common:ReportingYearOrNotApplicableType
--|ReportingSemester|(% style="width:418px" %)common:ReportingSemesterOrNotApplicableType
--|ReportingTrimester|(% style="width:418px" %)common:ReportingTrimesterOrNotApplicableType
--|ReportingQuarter|(% style="width:418px" %)common:ReportingQuarterOrNotApplicableType
--|ReportingMonth|(% style="width:418px" %)common:ReportingMonthOrNotApplicableType
--|ReportingWeek|(% style="width:418px" %)common:ReportingWeekOrNotApplicableType
--|ReportingDay|(% style="width:418px" %)common:ReportingDayOrNotApplicableType
--|TimeRange|(% style="width:418px" %)common:TimeRangeOrNotApplicableType
++|**SDMX Data Type**|**XML Schema Data Type**|
++|AlphaNumeric|common:AlphaNumericOrNotApplicableType|
++|Alpha|common:AlphaOrNotApplicableType|
++|Numeric|common:NumericOrNotApplicableType|
++|BigInteger|common:IntegerOrNotApplicableType|
++|Integer|common:IntOrNotApplicableType|
++|Long|common:LongOrNotApplicableType|
++|Short|common:ShortOrNotApplicableType|
++|Decimal|common:DecimalOrNotApplicableType|
++|Float|common:FloatOrNotApplicableType|
++|Double|common:DoubleOrNotApplicableType|
++|Boolean|common:BooleanOrNotApplicableType|
++|Count|common:IntegerOrNotApplicableType|
++|InclusiveValueRange|common:DecimalOrNotApplicableType|
++|ExclusiveValueRange|common:DecimalOrNotApplicableType|
++|Incremental|common:DecimalOrNotApplicableType|
++|ObservationalTimePeriod|common:ObservationalTimePeriodOrNotApplicableType|
++|StandardTimePeriod|common:StandardTimePeriodOrNotApplicableType|
++|BasicTimePeriod|common:BasicTimePeriodType|
++|GregorianTimePeriod|common:GregorianTimePeriodOrNotApplicableType|
++|ReportingTimePeriod|common:ReportingTimePeriodOrNotApplicableType|
++|ReportingYear|common:ReportingYearOrNotApplicableType|
++|ReportingSemester|common:ReportingSemesterOrNotApplicableType|
++|ReportingTrimester|common:ReportingTrimesterOrNotApplicableType|
++|ReportingQuarter|common:ReportingQuarterOrNotApplicableType|
++|ReportingMonth|common:ReportingMonthOrNotApplicableType|
++|ReportingWeek|common:ReportingWeekOrNotApplicableType|
++|ReportingDay|common:ReportingDayOrNotApplicableType|
++|TimeRange|common:TimeRangeOrNotApplicableType|
  === 3.3.8 Representation for Intentionally Missing Measure and Attribute Values ===
@@ -631,36 +631,35 @@
  For convenience the common schema provides the union types for the following data types.
--(% style="width:804.294px" %)
--|(% style="width:279px" %)**SDMX Data Type**|(% style="width:522px" %)**XML Schema Data Type**
--|(% style="width:279px" %)AlphaNumeric|(% style="width:522px" %)common:AlphaNumericOrMissingType
--|(% style="width:279px" %)Alpha|(% style="width:522px" %)common:AlphaOrMissingType
--|(% style="width:279px" %)Numeric|(% style="width:522px" %)common:NumericOrMissingType
--|(% style="width:279px" %)BigInteger|(% style="width:522px" %)common:IntegerOrMissingType
--|(% style="width:279px" %)Integer|(% style="width:522px" %)common:IntOrMissingType
--|(% style="width:279px" %)Long|(% style="width:522px" %)common:LongOrMissingType
--|(% style="width:279px" %)Short|(% style="width:522px" %)common:ShortOrMissingType
--|(% style="width:279px" %)Decimal|(% style="width:522px" %)common:DecimalOrMissingType
--|(% style="width:279px" %)Float|(% style="width:522px" %)common:FloatOrMissingType
--|(% style="width:279px" %)Double|(% style="width:522px" %)common:DoubleOrMissingType
--|(% style="width:279px" %)Boolean|(% style="width:522px" %)common:BooleanOrMissingType
--|(% style="width:279px" %)Count|(% style="width:522px" %)common:IntegerOrMissingType
--|(% style="width:279px" %)InclusiveValueRange|(% style="width:522px" %)common:DecimalOrMissingType
--|(% style="width:279px" %)ExclusiveValueRange|(% style="width:522px" %)common:DecimalOrMissingType
--|(% style="width:279px" %)Incremental|(% style="width:522px" %)common:DecimalOrMissingType
--|(% style="width:279px" %)ObservationalTimePeriod|(% style="width:522px" %)common:ObservationalTimePeriodOrMissingType
--|(% style="width:279px" %)StandardTimePeriod|(% style="width:522px" %)common:StandardTimePeriodOrMissingType
--|(% style="width:279px" %)BasicTimePeriod|(% style="width:522px" %)common:BasicTimePeriodType
--|(% style="width:279px" %)GregorianTimePeriod|(% style="width:522px" %)common:GregorianTimePeriodOrMissingType
--|(% style="width:279px" %)ReportingTimePeriod|(% style="width:522px" %)common:ReportingTimePeriodOrMissingType
--|(% style="width:279px" %)ReportingYear|(% style="width:522px" %)common:ReportingYearOrMissingType
--|(% style="width:279px" %)ReportingSemester|(% style="width:522px" %)common:ReportingSemesterOrMissingType
--|(% style="width:279px" %)ReportingTrimester|(% style="width:522px" %)common:ReportingTrimesterOrMissingType
--|(% style="width:279px" %)ReportingQuarter|(% style="width:522px" %)common:ReportingQuarterOrMissingType
--|(% style="width:279px" %)ReportingMonth|(% style="width:522px" %)common:ReportingMonthOrMissingType
--|(% style="width:279px" %)ReportingWeek|(% style="width:522px" %)common:ReportingWeekOrMissingType
--|(% style="width:279px" %)ReportingDay|(% style="width:522px" %)common:ReportingDayOrMissingType
--|(% style="width:279px" %)TimeRange|(% style="width:522px" %)common:TimeRangeOrMissingType
++|**SDMX Data Type**|**XML Schema Data Type**|
++|AlphaNumeric|common:AlphaNumericOrMissingType|
++|Alpha|common:AlphaOrMissingType|
++|Numeric|common:NumericOrMissingType|
++|BigInteger|common:IntegerOrMissingType|
++|Integer|common:IntOrMissingType|
++|Long|common:LongOrMissingType|
++|Short|common:ShortOrMissingType|
++|Decimal|common:DecimalOrMissingType|
++|Float|common:FloatOrMissingType|
++|Double|common:DoubleOrMissingType|
++|Boolean|common:BooleanOrMissingType|
++|Count|common:IntegerOrMissingType|
++|InclusiveValueRange|common:DecimalOrMissingType|
++|ExclusiveValueRange|common:DecimalOrMissingType|
++|Incremental|common:DecimalOrMissingType|
++|ObservationalTimePeriod|common:ObservationalTimePeriodOrMissingType|
++|StandardTimePeriod|common:StandardTimePeriodOrMissingType|
++|BasicTimePeriod|common:BasicTimePeriodType|
++|GregorianTimePeriod|common:GregorianTimePeriodOrMissingType|
++|ReportingTimePeriod|common:ReportingTimePeriodOrMissingType|
++|ReportingYear|common:ReportingYearOrMissingType|
++|ReportingSemester|common:ReportingSemesterOrMissingType|
++|ReportingTrimester|common:ReportingTrimesterOrMissingType|
++|ReportingQuarter|common:ReportingQuarterOrMissingType|
++|ReportingMonth|common:ReportingMonthOrMissingType|
++|ReportingWeek|common:ReportingWeekOrMissingType|
++|ReportingDay|common:ReportingDayOrMissingType|
++|TimeRange|common:TimeRangeOrMissingType|
  === 3.3.9 Representation with Complex Text Format ===
@@ -717,39 +717,34 @@
  A complex type named DataSetType must be created. Its content model will be derived via restriction. The base type of the restriction is dsd:DataSetType. The complex type content model will be as follows:
--~1. A sequence consisting of:
++1. A sequence consisting of:
++1. An element reference to common:Annotations, with a minimum occurrence of 0
++   2. A local element named DataProvider with the type common:DataProviderReferenceType, a form of unqualified and a minimum occurrence of 0
++   3. A choice with a minimum occurrence of 0 and a maximum occurrence of unbounded consisting of:
++1. A local element named Atts with a form of unqualified and a type of AttsType (as defined in the AttsType section which follows)
++      2. If the data structure defines groups, a local element named Group with a form of unqualified. The type of this element should be the type that is described in the GroupType section which follows.
++      3. If the dimension at the observation level is not AllDimensions, a local element named Series with a form of unqualified and a type of SeriesType (as defined in the SeriesType section which follows)
++      4. If the dimension at the observation level is AllDimensions, a local element named Obs with a form of unqualified and a type of ObsType (as defined in the ObsType section which follows)
++   4. If any metadata attribute usages defined in the data structure that declares an attribute relationship of dataflow, a local element named Metadata with the type metadata:MetadataSetType a form of unqualified, and a minimum occurences of 0
--* i. An element reference to common:Annotations, with a minimum occurrence of 0
--* ii   A local element named DataProvider with the type common:DataProviderReferenceType, a form of unqualified and a minimum occurrence of 0
--* iii  A choice with a minimum occurrence of 0 and a maximum occurrence of unbounded consisting of:
--** a.  A local element named Atts with a form of unqualified and a type of AttsType (as defined in the AttsType section which follows)
--** b. If the data structure defines groups, a local element named Group with a form of unqualified. The type of this element should be the type that is described in the GroupType section which follows.
--** c. If the dimension at the observation level is not AllDimensions, a local element named Series with a form of unqualified and a type of SeriesType (as defined in the SeriesType section which follows)
--** d. If the dimension at the observation level is AllDimensions, a local element named Obs with a form of unqualified and a type of ObsType (as defined in the ObsType section which follows)
--* iv. If any metadata attribute usages defined in the data structure that declares an attribute relationship of dataflow, a local element named Metadata with the type metadata:MetadataSetType a form of unqualified, and a minimum occurences of 0
--
  === 3.4.2 GroupType ===
  If the data structure definition defines only one group, a complex type with its name taken from the identifier of the lone group must be defined. This type is used for the Group element in the DataSetType. Its content model will be derived via restriction of the dsd:GroupType. The complex type content model will be as follows:
--~1. A sequence consisting of:
--
--* i. An element reference to common:Annotations, with a minimum occurrence of 0
--* ii. If any attributes defined in the data structure that declares an attribute relationship with the group, a Comp element with a form of unqualified, a minimum occurrence of 0, a maximum occurrence of unbounded, and a type of dsd:CompType
--* iii. If any metadata attribute usages defined in the data structure that declares an attribute relationship with the group, a local element named Metadata with the type metadata:MetadataSetType a form of unqualified, and a minimum occurrence of 0
--
--2. An attribute for each dimension referenced by the group. The XML attribute name and type are defined according to the general rules defined in the previous section, and the usage is required
--3. An attribute for each data attribute with simple representation defined in the data structure that declares an attribute relationship with the group or specifies the group as an attachment group. The XML attribute name and type are defined according to the general rules defined in the previous section, and the usage is optional
++1. A sequence consisting of:
++1. An element reference to common:Annotations, with a minimum occurrence of 0
++   2. If any attributes defined in the data structure that declares an attribute relationship with the group, a Comp element with a form of unqualified, a minimum occurrence of 0, a maximum occurrence of unbounded, and a type of dsd:CompType
++   3. If any metadata attribute usages defined in the data structure that declares an attribute relationship with the group, a local element named Metadata with the type metadata:MetadataSetType a form of unqualified, and a minimum occurrence of 0
++2. An attribute for each dimension referenced by the group. 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
++3. An attribute for each data attribute with simple representation defined in the data structure that declares an attribute relationship with the group or specifies the group as an attachment group. 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
 . An attribute named type with a type of common:IDType, usage of optional, and a fixed value of the identifier of the group
  If the data structure definition defines more than one group, an abstract complex type with name GroupType must be created. This type is used for the Group element in the DataSetType. Its content model will be derived via restriction of the dsd:GroupType. The complex type content model will be as follows:
--~1. A sequence consisting of:
--
--* i. An element reference to common:Annotations, with a minimum occurrence of 0
--* ii. If any attributes defined in the data structure that declares an attribute relationship with a group, a Comp element with a form of unqualified, a minimum occurrence of 0, a maximum occurrence of unbounded, and a type of dsd:CompType
--* iii. If any metadata attribute usages defined in the data structure that declares an attribute relationship with any group, a local element named Metadata with the type metadata:MetadataSetType a form of unqualified, and a minimum occurrence of 0
--
++1. A sequence consisting of:
++1. An element reference to common:Annotations, with a minimum occurrence of 0
++   2. If any attributes defined in the data structure that declares an attribute relationship with a group, a Comp element with a form of unqualified, a minimum occurrence of 0, a maximum occurrence of unbounded, and a type of dsd:CompType
++   3. If any metadata attribute usages defined in the data structure that declares an attribute relationship with any group, a local element named Metadata with the type metadata:MetadataSetType a form of unqualified, and a minimum occurrence of 0
 . An attribute named type with a type of Group.ID, and a usage of optional
 . An anyAttribute declaration with a namespace of ##local##
@@ -757,14 +757,12 @@
  For each group defined in the data structure definition, a complex type with its name taken from the group identifier is defined. Its content model will be derived via restriction of the previously defined GroupType. The complex type content model will be as follows:
--~1. A sequence consisting of:
--
--* i. An element reference to common:Annotations, with a minimum occurrence of 0
--* ii. If any attributes with complex representation defined in the data structure declares an attribute relationship with the group, a Comp element with a form of unqualified, a minimum occurrence of 0, a maximum occurrence of unbounded, and a type of dsd:CompType
--* iii. If any metadata attribute usages defined in the data structure that declares an attribute relationship with the group, a local element named Metadata with the type metadata:MetadataSetType a form of unqualified, and a minimum occurrence of 0
--
--2. An attribute for each dimension referenced by the group. The XML attribute name and type are defined according to the general rules defined in the previous section, and the usage is required
--3. An attribute for each data attribute with simple representation defined in the data structure that declares an attribute relationship with the group or specifies the group as an attachment group. The XML attribute name and type are defined according to the general rules defined in the previous section, and the usage is optional
++1. A sequence consisting of:
++1. An element reference to common:Annotations, with a minimum occurrence of 0
++   2. If any attributes with complex representation defined in the data structure declares an attribute relationship with the group, a Comp element with a form of unqualified, a minimum occurrence of 0, a maximum occurrence of unbounded, and a type of dsd:CompType
++   3. If any metadata attribute usages defined in the data structure that declares an attribute relationship with the group, a local element named Metadata with the type metadata:MetadataSetType a form of unqualified, and a minimum occurrence of 0
++2. An attribute for each dimension referenced by the group. 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
++3. An attribute for each data attribute with simple representation defined in the data structure that declares an attribute relationship with the group or specifies the group as an attachment group. 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
 . An attribute named type with a type of Group.ID, usage of optional, and a fixed value of the identifier of the group
  === 3.4.3 SeriesType ===
@@ -771,46 +771,40 @@
  If the dimension at the observation is not AllDimensions, a complex type name SeriesType must be created. Its content model will be derived via restriction of dsd:SeriesType. The complex type content model will be as follows:
--~1. A sequence consisting of:
--
--* i. An element reference to common:Annotations, with a minimum occurrence of 0
--* ii. If any attributes with complex representation defined in the data structure declares an attribute relationship with a dimension that is not at the observation level, a Comp element with a form of unqualified, a minimum occurrence of 0, a maximum occurrence of unbounded, and a type of dsd:CompType
--* iii. A local element named Obs with a form of unqualified, a minimum occurrence of 0, a maximum occurrence of unbounded, and a type of ObsType (as defined in the ObsType section which follows)
--* iv. If any metadata attribute usages defined in the data structure that declares an attribute relationship with the series, a local element named Metadata with the type metadata:MetadataSetType a form of unqualified, and a minimum occurrence of 0
--
++1. A sequence consisting of:
++1. An element reference to common:Annotations, with a minimum occurrence of 0
++   2. If any attributes with complex representation defined in the data structure declares an attribute relationship with a dimension that is not at the observation level, a Comp element with a form of unqualified, a minimum occurrence of 0, a maximum occurrence of unbounded, and a type of dsd:CompType
++   3. A local element named Obs with a form of unqualified, a minimum occurrence of 0, a maximum occurrence of unbounded, and a type of ObsType (as defined in the ObsType section which follows)
++   4. If any metadata attribute usages defined in the data structure that declares an attribute relationship with the series, a local element named Metadata with the type metadata:MetadataSetType a form of unqualified, and a minimum occurrence of 0
 . An attribute named TIME\_PERIOD with a type of common:ObservationalTimePeriod. If the dimension at the observation level is the time dimension (TIME\_PERIOD) or there is no time dimension defined by the data structure, a usage of prohibited; otherwise, a usage of required
--3. An attribute for each dimension defined by the data structure definition, except for the dimension at the observation level and 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
--4. An attribute for each data attribute defined with simple representation in the data structure that declares an attribute relationship with any dimension outside of the dimension at the observation level (so long as it does not also declare an attachment group). The XML attribute name and type are defined according to the general rules defined in the previous section, and the usage is optional
++3. An attribute for each dimension defined by the data structure definition, except for the dimension at the observation level and 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
++4. An attribute for each data attribute defined with simple representation in the data structure that declares an attribute relationship with any dimension outside of the dimension at the observation level (so long as it does not also declare an attachment group). 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
  === 3.4.4 AttsType ===
  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:
--~1. A sequence consisting of:
--
--* i. An element reference to common:Annotations, with a minimum occurrence of 0
--* 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
--
++1. A sequence consisting of:
++1. An element reference to common:Annotations, with a minimum occurrence of 0
++   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
 . 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
--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 optional
--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
++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
++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
  === 3.4.5 ObsType ===
  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:
--~1. A sequence consisting of:
--
--* i. An element reference to common:Annotations, with a minimum occurrence of 0
--* 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
--* 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
--
++1. A sequence consisting of:
++1. An element reference to common:Annotations, with a minimum occurrence of 0
++   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
++   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
 . An attribute named TIME\_PERIOD with a type of common:
     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
--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 required
--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
--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 optional
--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
++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
++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
++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
++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
  === 3.4.6 CompType ===
@@ -841,7 +841,7 @@
  === 4.1.2 Replace Action ===
--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).
++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).
  Only non-dimensional components (measure, attribute or reference metadata values) can be **omitted** (null or absent). Bulk replacing is thus not supported.
@@ -849,9 +849,9 @@
  Replacing non-existing elements is not resulting in an error.
--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.
++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.
--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.
++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.
  === 4.1.3 Delete Action ===
@@ -871,59 +871,58 @@
  The following convention is used to indicate the state of components in data messages:
--(% style="width:1364.29px" %)
--| | |(% style="width:260px" %)**Dimension value is**|(% style="width:391px" %) |(% style="width:383px" %)**Measure, attribute or reference metadata value is**|(% style="width:184px" %)
--| | |(% style="width:260px" %)**Omitted**|(% style="width:391px" %)**switched off**|(% style="width:383px" %)**Omitted**|(% style="width:184px" %)**Present**
--|Action|Delete|(% style="width:260px" %)bulk deletion: dimension value doesn't matter|(% style="width:391px" %)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:383px" %)to be deleted only if **all** non-dimension components are omitted|(% style="width:184px" %)to be deleted
--| |Merge|(% style="width:260px" %)//bulk merge is not permitted//|(% style="width:391px" %)(see above)|(% style="width:383px" %)not to be changed|(% style="width:184px" %)to be updated/inserted
--| |Replace|(% style="width:260px" %)//bulk replace is not permitted//|(% style="width:391px" %)(see above)|(% style="width:383px" %)at permitted replacement levels: to be deleted, otherwise not to be changed|(% style="width:184px" %)to be updated/inserted
--|Format|XML|(% style="width:260px" %)xml element/attribute is absent|(% style="width:391px" %)~|xml element/attribute is absent|(% style="width:383px" %)any valid or intentionally missing value|(% style="width:184px" %)
--| |JSON|(% style="width:260px" %)\<empty\>|(% style="width:391px" %)““|(% style="width:383px" %)NULL or absent|(% style="width:184px" %)(see above)
--| |CSV|(% style="width:260px" %)\<empty\> cell or column is absent|(% style="width:391px" %)~|<empty> cell or column is absent|(% style="width:383px" %)(see above)|(% style="width:184px" %)
++| | |**Dimension value is**| |**Measure, attribute or reference metadata value is**| |
++| | |**Omitted**|**switched off**|**Omitted**|**Present**|
++|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|
++| |Merge|*bulk merge is not permitted*|(see above)|not to be changed|to be updated/inserted|
++| |Replace|*bulk replace is not permitted*|(see above)|at permitted replacement levels: to be deleted, otherwise not to be changed|to be updated/inserted|
++|Format|XML|xml element/attribute is absent|~|xml element/attribute is absent|any valid or intentionally missing value|
++| |JSON|\<empty\>|““|NULL or absent|(see above)|
++| |CSV|\<empty\> cell or column is absent|~|<empty> cell or column is absent|(see above)|
  **Important notes:**
--The terms “//delete//”, “//merge//” and “//replace//” do **not** imply a physical replacement or deletion of values in the underlying database. To minimize the physical resource requirements, SDMX web service implementations that do not support the //includeHistory// and //asOf// URL parameters might physically replace the existing values in the database. SDMX web services that neither support the *updatedAfter* URL parameter might also implement physical deletions. However, SDMX web services that support these parameters (or other time-machine features), would not overwrite or delete the physical values.
++The terms “*delete*”, “*merge*” and “*replace*” do **not** imply a physical replacement or deletion of values in the underlying database. To minimize the physical resource requirements, SDMX web service implementations that do not support the *includeHistory* and *asOf* URL parameters might physically replace the existing values in the database. SDMX web services that neither support the *updatedAfter* URL parameter might also implement physical deletions. However, SDMX web services that support these parameters (or other time-machine features), would not overwrite or delete the physical values.
--SDMX web services that support the //includeHistory// or //asOf// URL parameters should never allow deleting their **historic** data content because this would interfere with the interests of data consumers, such as data aggregators. Therefore, a specific feature to physically delete previous (outdated) content is intentionally not added to the SDMX standard syntax. If such a feature is required by an organisation, then it needs to be implemented as a custom feature outside the SDMX standard.
++SDMX web services that support the *includeHistory* or *asOf* URL parameters should never allow deleting their **historic** data content because this would interfere with the interests of data consumers, such as data aggregators. Therefore, a specific feature to physically delete previous (outdated) content is intentionally not added to the SDMX standard syntax. If such a feature is required by an organisation, then it needs to be implemented as a custom feature outside the SDMX standard.
--Likewise, all SDMX-compliant systems that do (or are configured to) support the //updatedAfter// URL parameter need to systematically retain the information about deleted data (or data-related reference metadata).
++Likewise, all SDMX-compliant systems that do (or are configured to) support the *updatedAfter* URL parameter need to systematically retain the information about deleted data (or data-related reference metadata).
--All datasets – even with varying actions – within a single data message have always to be treated as **ACID transaction** to guarantee “transactional safety” (full data consistency and validity despite errors, power failures, and other mishaps). These datasets are to be processed in the order of appearance in the message. The advantage of such data messages is thus the ability to bundle separate //delete// and //replace// or //merge// actions into one transactional data message.
++All datasets – even with varying actions – within a single data message have always to be treated as **ACID transaction** to guarantee “transactional safety” (full data consistency and validity despite errors, power failures, and other mishaps). These datasets are to be processed in the order of appearance in the message. The advantage of such data messages is thus the ability to bundle separate *delete* and *replace* or *merge* actions into one transactional data message.
--**Recommended{{footnote}}So far this is recommended for systems that do not require backward-compatibility. Later, with SDMX 4.0, this may generally be made mandatory{{/footnote}} dataset actions in SDMX web service responses to GET data queries:**
++**Recommended[^2] dataset actions in SDMX web service responses to GET data queries:**
--~1. Without the //updatedAfter//, //includeHistory//, //detail//, //attributes// or //measures// URL parameters:
++1. Without the *updatedAfter*, *includeHistory*, *detail*, *attributes* or *measures* URL parameters:
++
++   The response message should contain the retrieved data in a *Replace* dataset (instead of the previous *information* dataset).
--The response message should contain the retrieved data in a //Replace// dataset (instead of the previous *information* dataset).
++1. Without the *updatedAfter* and *includeHistory*, but with *detail*, *attributes* or *measures* URL parameters:
++
++   The response message should contain the retrieved data in a *Merge* dataset (instead of the previous *Information* dataset).
--2. Without the //updatedAfter// and //includeHistory//, but with //detail//, //attributes// or //measures// URL parameters:
++1. With the *updatedAfter* URL parameter:
++
++   The response must include the information of all previously updated, inserted and deleted data or data-related reference metadata, even if bulk deletions have been used. One of the two approaches are possible:
--The response message should contain the retrieved data in a //Merge// dataset (instead of the previous *Information* dataset).
++* a *Delete* dataset for entirely deleted observations and for entirely deleted sets of (data-related reference metadata) attribute values attached to specific dimension combinations and
++   a *Replace* dataset for all other changed observations and changed attribute and data-related reference metadata values attached to specific dimension combinations, or
++* a *Delete* dataset for entirely deleted observations, for entirely deleted sets of (data-related reference metadata) attribute values attached to specific dimension combinations and for individually deleted mesure, attribute and reference metadata values and
++   a *Merge* dataset for all other updated or inserted observation, attribute and data-related reference metadata values.
++
++   The DB synchronization use case requires that the generated response must always allow achieving to replicate the exact same punctual data content as currently stored in the queried data source.
--3. With the //updatedAfter// URL parameter:
++1. With the *includeHistory* URL parameter:
++
++   Using a number of datasets with *Delete*, *Replace* or *Merge* actions and limited in their validity time span that allow achieving to replicate the exact same punctual data contents as previously stored in the queried data source.
--The response must include the information of all previously updated, inserted and deleted data or data-related reference metadata, even if bulk deletions have been used. One of the two approaches are possible:
++1. With the *asOf* URL parameter:
++
++   The recommendations of 1 and 2 apply depending on the other parameters. In addition, the returned dataset should have its validity time span limited to the point in time requested in the *asOf* parameter.
--* a //Delete// dataset for entirely deleted observations and for entirely deleted sets of (data-related reference metadata) attribute values attached to specific dimension combinations and
--a //Replace// dataset for all other changed observations and changed attribute and data-related reference metadata values attached to specific dimension combinations, or
--* a //Delete// dataset for entirely deleted observations, for entirely deleted sets of (data-related reference metadata) attribute values attached to specific dimension combinations and for individually deleted mesure, attribute and reference metadata values and
--a //Merge// dataset for all other updated or inserted observation, attribute and data-related reference metadata values.
++[^2]: So far this is recommended for systems that do not require backward-compatibility. Later, with SDMX 4.0, this may generally be made mandatory.
--The DB synchronization use case requires that the generated response must always allow achieving to replicate the exact same punctual data content as currently stored in the queried data source.
--
--~1. With the *includeHistory* URL parameter:
--
--Using a number of datasets with *Delete*, *Replace* or *Merge* actions and limited in their validity time span that allow achieving to replicate the exact same punctual data contents as previously stored in the queried data source.
--
--2. With the *asOf* URL parameter:
--
--The recommendations of 1 and 2 apply depending on the other parameters. In addition, the returned dataset should have its validity time span limited to the point in time requested in the *asOf* parameter.
--
  == 4.2 Reference Metadata Actions ==
  Reference metadata defined by a Metadataflow or a MetadataProvisionAgreement are exchanged within reference metadatasets, which are maintainable and thus for actions behave like structural metadata (artefacts): When interacting with SDMX Rest web services, the HTTP action verbs GET, PUT and POST are used to indicate the intended action per web request. Consequently, different actions cannot be bundled and executed with “transactional ACIDity”. Note that metadatasets retrieved using the HTTP header “Accept-Language” may contain only partial languages, and thus should be marked with its *isPartialLanguage* property set to true. Submitting such a partial metadataset to update an SDMX storage system will only add or update the included languages but not change other languages.
  The former message header or metadataset property *DataSetAction* is deprecated. To avoid conflicts, it is now ignored if still present.
--
--{{putFootnotes/}}