Wiki source code of Part IV. Data

Version 2.17 by Helena on 2025/07/02 15:24

version	line-number	content
2.2	1	{{box title="Contents"}}
	2	{{toc/}}
	3	{{/box}}
	4
	5	= 1 Introduction =
	6
	7	The first change in the data and metadata message is one of terminology. In order to foster consistency in the standard, the names and namespaces of the data and metadata message have been changed. The namespaces now have a uniform format of /data/format and /metadata/format. This also applies to the message names as well, where the names follow the pattern of FormatData (e.g. StructuredData and GenericMetadata).
	8
	9	For data messages, since (% style="color:#e74c3c" %)version(%%) 3.0 only the (data-)structure-specific format is maintained, the generic format being deprecated. The structure-specific data message combines the principles of the former compact and cross-sectional formats into one more generalised format. All data can be exchanged as either an un-grouped collection of observations, each specifying a full key, or it can be exchanged as data grouped into series with any single [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] placed at the observation level.
	10
	11	A base schema now imposes a strict format for the generated structure-specific schemas. This not only allows performing the required validations, but the messages will also be much simpler to process as the format will always use the same element names.
	12
	13	For metadata messages, since (% style="color:#e74c3c" %)version(%%) 3.0, in opposite, only the generic format is maintained, the (metadata-)structure-specific format being deprecated.
	14
	15	= 2 Schema Documentation =
	16
	17	== 2.1 Structure-Specific Data Namespace ==
	18
	19	http://www.sdmx.org/resources/sdmxml/schemas/v3_1/data/structurespecific
	20
	21	=== 2.1.1 Summary ===
	22
	23	Referenced Namespaces:
	24
	25	(% style="width:987.294px" %)
	26	\|(% style="width:593px" %)Namespace\|(% style="width:391px" %)Prefix
	27	\|(% style="width:593px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v3\_1/common\|(% style="width:391px" %)common
	28	\|(% style="width:593px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v3\_1/metadata/generic\|(% style="width:391px" %)metadata
	29	\|(% style="width:593px" %)http:~/~/www.w3.org/2001/XMLSchema\|(% style="width:391px" %)xs
	30
	31	Contents:
	32	6 Complex Types
	33
	34	=== 2.1.2 Complex Types ===
	35
2.3	36	//DataSetType:// DataSetType is the abstract type which defines the base structure for any data structure definition specific data set. A derived data set type will be created that is specific to a data structure definition and the details of the organisation of the data (i.e. which dimension is the observation dimension). Data is organised into either a collection of series (grouped observations) or a collection of un-grouped observations. The derived data set type will restrict this choice to be either grouped or un-grouped observations. If this dimension is "AllDimensions" then the derived data set type must consist of a collection of un-grouped observations; otherwise, the data set will contain a collection of series with the observations in the series disambiguated by the specified dimension at the observation level. This data set is capable of containing data (observed values) and/or documentation (data and metadata attribute values) and can be used for incremental updates and deletions (i.e. only the relevant updates or deletes are exchanged). It is assumed that each series or un-grouped observation will be distinct in its purpose. For example, if series contains both data and documentation, it assumed that each series will have a unique key. If the series contains only data or only documentation, then it is possible that another series with the same key might exist, but with not with the same purpose (i.e. to provide data or documentation) as the first series. This base type is designed such that derived types can be processed in a generic manner; it assures that data structure definition specific data will have a consistent structure. The group, series, obs, and atts elements are unqualified, meaning that they are not qualified with a namespace in an instance. This means that in the derived data set types, the elements will always be the same, regardless of the target namespace of the schemas which defines these derived types. This allows for consistent processing of the structure without regard to what the namespace might be for the data structure definition specific schema.
2.2	37
	38	Derivation:
	39
	40	AnnotableType (extension)
	41	DataSetType
	42
	43	Attributes:
	44	structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?
	45
	46	Content:
	47	Annotations?, DataProvider?, (Atts\|Group\|Series\|Obs)*, Metadata?
	48
	49	Attribute Documentation:
	50
2.4	51	(% style="width:1152.29px" %)
	52	\|Name\|Type\|Documentation
	53	\|structureRef\|xs:IDREF\|The structureRef contains a reference to a structural specification in the header of a data or reference metadata message. The structural specification details which structure the data or reference metadata conforms to, as well as providing additional information such as how the data is structure (e.g. which dimension occurs at the observation level for a data set).
	54	\|setID\|IDType\|The setID provides an identification of the data or metadata set.
	55	\|action\|ActionType\|The action attribute indicates whether the file is merging, replacing, or deleting.
	56	\|reportingBeginDate\|BasicTimePeriodType\|The reportingBeginDate indicates the inclusive start time of the data reported in the data or metadata set.
	57	\|reportingEndDate\|BasicTimePeriodType\|The reportingEndDate indicates the inclusive end time of the data reported in the data or metadata set.
	58	\|validFromDate\|xs:dateTime\|The validFromDate indicates the inclusive start time indicating the validity of the information in the data or metadata set.
	59	\|validToDate\|xs:dateTime\|The validToDate indicates the inclusive end time indicating the validity of the information in the data or metadata set.
	60	\|publicationYear\|xs:gYear\|The publicationYear holds the ISO 8601 four-digit year.
	61	\|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).
2.2	62
	63	Element Documentation:
	64
2.4	65	(% style="width:1154.29px" %)
	66	\|Name\|Type\|Documentation
	67	\|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.
	68	\|DataProvider\|DataProviderReferenceType\|DataProvider contains a reference to the provider for the data set.
	69	\|Atts\|AttsType\|Atts contains a set of data or metadata attribute values with an attachment level of none (i.e. data set level) or reported against a partial set of dimension values.
	70	\|Group\|GroupType\|Group contains a reference to a defined group in the data structure definition along with its key (if necessary) and values for the attributes which are associated with the group. An attribute is associated to a group by either an explicit group relationship or by a group attachment when the attribute has a relationship with a dimension which is a member of this group.
	71	\|Series\|SeriesType\|Series contains a collection of observations that share a common key (set of dimension values). The key of a series is every dimension defined in the data structure definition, save the dimension at the observation level. In addition to the key and observations, the series contains values for data and metadata attributes which have a relationship with any dimension that is part of the series key, so long as the attribute does not specify an attachment group or also has a relationship with the dimension declared to be at the observation level.
	72	\|Obs\|ObsType\|Obs is an un-grouped observation. This observation has a key which is a set of values for all dimensions declared in the data structure definition. In addition to the key, the value of the observation can be provided along with values for all data and metadata attributes which have an association with the observation or any dimension (so long as it does not specify a group attachment).
	73	\|Metadata\|MetadataSetType\|Allows for attachment of reference metadata against to the data set.
2.2	74
2.4	75	//GroupType:// GroupType is the abstract type which defines a structure which is used to communicate attribute values for a group defined in a data structure definition. The group can consist of either a subset of the dimensions defined by the data structure definition, or an association to an attachment constraint, which in turn defines key sets to which attributes can be attached. In the case that the group is based on an attachment constraint, only the identification of group is provided. It is expected that a system which is processing this will relate that identifier to the key sets defined in the constraint and apply the values provided for the attributes appropriately. Data structure definition schemas will drive types based on this for each group defined in the data structure definition. Both the dimension values which make up the key (if applicable) and the attribute values associated with the group will be represented with XML attributes. This is specified in the content model with the declaration of anyAttributes in the "local" namespace. The derived group 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 group dimensions and data or metadata 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.
2.2	76
	77	Derivation:
	78
	79	AnnotableType (extension)
	80	GroupType
	81
	82	Attributes:
	83	type?
	84
	85	Content:
	86	Annotations?, Comp*, Metadata?
	87
	88	Attribute Documentation:
	89
2.4	90	(% style="width:1044.29px" %)
	91	\|Name\|Type\|(% style="width:913px" %)Documentation
	92	\|type\|IDType\|(% style="width:913px" %)The type attribute reference the identifier of the group as defined in the data structure definition. This is optional, but derived group types will provide a fixed value for this so that it always available in the post validation information set. This allows the group to be processed in a generic manner.
2.2	93
	94	Element Documentation:
	95
2.4	96	(% style="width:1055.29px" %)
	97	\|Name\|Type\|(% style="width:717px" %)Documentation
	98	\|Annotations\|AnnotationsType\|(% style="width:717px" %)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.
	99	\|Comp\|//CompType//\|(% style="width:717px" %)Comp contains the details of group level attributes that have complex representation and cannot be expressed as XML attributes.
	100	\|Metadata\|MetadataSetType\|(% style="width:717px" %)Allows for attachment of reference metadata against to the group.
2.2	101
2.5	102	//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.
2.2	103
	104	Derivation:
	105
	106	AnnotableType (extension)
	107	SeriesType
	108
	109	Attributes:
	110	TIME_PERIOD?
	111
	112	Content:
	113	Annotations?, Comp, Obs, Metadata?
	114
	115	Attribute Documentation:
	116
2.5	117	(% style="width:1084.29px" %)
	118	\|Name\|Type\|Documentation
	119	\|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.
2.2	120
	121	Element Documentation:
	122
2.6	123	(% style="width:1093.29px" %)
	124	\|Name\|Type\|Documentation
	125	\|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.
	126	\|Comp\|//CompType//\|Comp contains the details of series level attributes that have complex representation and cannot be expressed as XML attributes.
	127	\|Obs\|//ObsType//\|
	128	\|Metadata\|MetadataSetType\|Allows for attachment of reference metadata against to the series.
2.2	129
2.6	130	//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.
2.2	131
	132	Derivation:
	133
	134	AnnotableType (extension)
	135	CompType
	136
	137	Attributes:
	138	id
	139
	140	Content:
	141	Annotations?, Value
	142
	143	Attribute Documentation:
	144
2.6	145	(% style="width:1007.29px" %)
	146	\|(% style="width:157px" %)Name\|(% style="width:291px" %)Type\|(% style="width:556px" %)Documentation
	147	\|(% style="width:157px" %)id\|(% style="width:291px" %)NCNameIDType\|(% style="width:556px" %)
2.2	148
	149	Element Documentation:
	150
2.6	151	(% style="width:1015.29px" %)
	152	\|Name\|Type\|(% style="width:684px" %)Documentation
	153	\|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.
	154	\|Value\|//ValueType//\|(% style="width:684px" %)
2.2	155
2.6	156	//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.
2.2	157
	158	Derivation:
	159
	160	AnnotableType (extension)
	161	ObsType
	162
	163	Attributes:
	164	type?, TIME_PERIOD?
	165
	166	Content:
	167	Annotations?, Comp*, Metadata?
	168
	169	Attribute Documentation:
	170
2.6	171	(% style="width:1008.29px" %)
	172	\|Name\|Type\|(% style="width:648px" %)Documentation
	173	\|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.
	174	\|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.
2.2	175
	176	Element Documentation:
	177
2.6	178	(% style="width:1020.29px" %)
	179	\|Name\|Type\|Documentation
	180	\|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.
	181	\|Comp\|//CompType//\|Comp contains the details of observation measures or attributes that have complex representation and cannot be expressed as XML attributes.
	182	\|Metadata\|MetadataSetType\|Allows for attachment of reference metadata against to the observation.
2.2	183
	184	**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.
	185
	186	Derivation:
	187
	188	AnnotableType (extension)
	189	AttsType
	190
	191	Attributes:
	192	TIME_PERIOD?
	193
	194	Content:
	195	Annotations?, Comp
	196
	197	Attribute Documentation:
	198
2.6	199	(% style="width:1013.29px" %)
	200	\|Name\|Type\|Documentation
	201	\|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.
2.2	202
	203	Element Documentation:
	204
2.6	205	(% style="width:1020.29px" %)
	206	\|Name\|Type\|Documentation
	207	\|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.
	208	\|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	209
	210	== 2.2 Generic Reference Metadata Namespace ==
	211
2.6	212	[[http:~~/~~/www.sdmx.org/resources/sdmxml/schemas/v3_1/metadata/generic>>http://www.sdmx.org/resources/sdmxml/schemas/v3_1/metadata/generic**]]
2.2	213
	214	=== 2.2.1 Summary ===
	215
	216	Referenced Namespaces:
	217
2.7	218	(% style="width:1037.29px" %)
	219	\|(% style="width:516px" %)Namespace\|(% style="width:518px" %)Prefix
	220	\|(% style="width:516px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v3\_1/common\|(% style="width:518px" %)common
	221	\|(% style="width:516px" %)<http:~/~/www.w3.org/2001/XMLSchema>\|(% style="width:518px" %)xs
2.2	222
	223	Contents:
	224	1 Global Element
	225	3 Complex Types
	226
	227	=== 2.2.2 Global Elements ===
	228
	229	Attribute (AttributeType): Att elements hold the reported values for a given metadata attribute. These values conform to the definition of the metadata attribute in the metadata structure definition.
	230
	231	=== 2.2.3 Complex Types ===
	232
	233	**MetadataSetBaseType:** MetadataSetBaseType defines the base refinement of the MetadataSetType. Its purpose is to restrict the urn attribute.
	234
	235	Derivation:
	236
	237	AnnotableType (extension)
	238	IdentifiableType (extension)
	239	NameableType (extension)
	240	VersionableType (restriction)
	241	MaintainableBaseType (extension)
	242	MaintainableType (restriction)
	243	MetadataSetBaseType
	244
	245	Attributes:
	246	id, urn?, uri?, version?, validFrom?, validTo?, agencyID, isPartialLanguage?, isExternalReference?, serviceURL?, structureURL?
	247
	248	Content:
	249	Annotations?, Link*, Name+, Description
	250
	251	Attribute Documentation:
	252
2.7	253	(% style="width:1051.29px" %)
	254	\|Name\|Type\|(% style="width:669px" %)Documentation
	255	\|id\|IDType\|(% style="width:669px" %)The id is the identifier for the object.
	256	\|urn\|MetadataSetUrnType\|(% style="width:669px" %)The urn attribute holds a valid SDMX Registry URN (see SDMX Registry Specification for details).
	257	\|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.
	258	\|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.
	259	\|validFrom\|xs:dateTime\|(% style="width:669px" %)The validFrom attribute provides the inclusive start date for providing supplemental validity information about the version.
	260	\|validTo\|xs:dateTime\|(% style="width:669px" %)The validTo attribute provides the inclusive end date for providing supplemental validity information about the version.
	261	\|agencyID\|NestedNCNameIDType\|(% style="width:669px" %)The agencyID must be provided and identifies the maintenance agency of the object.
	262	\|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.
	263	\|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.
	264	\|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.
	265	\|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.
2.2	266
	267	Element Documentation:
	268
2.7	269	(% style="width:1057.29px" %)
	270	\|Name\|Type\|Documentation
	271	\|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.
	272	\|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.
	273	\|Name\|TextType\|Name provides for a human-readable name for the object. This may be provided in multiple, parallel language-equivalent forms.
	274	\|Description\|TextType\|Description provides for a longer human-readable description of the object. This may be provided in multiple, parallel language-equivalent forms.
2.2	275
	276	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.
	277
	278	Derivation:
	279
	280	AnnotableType (extension)
	281	IdentifiableType (extension)
	282	NameableType (extension)
	283	VersionableType (restriction)
	284	MaintainableBaseType (extension)
	285	MaintainableType (restriction)
	286	MetadataSetBaseType (extension)
	287	MetadataSetType
	288
	289	Attributes:
	290	id, urn?, uri?, version?, validFrom?, validTo?, agencyID, isPartialLanguage?, isExternalReference?, serviceURL?, structureURL?, reportingBeginDate?, reportingEndDate?, publicationYear?, publicationPeriod?
	291
	292	Content:
	293	Annotations?, Link, Name+, Description, ( (MetadataProvisionAgreement\|Metadataflow), Target+, Attribute+)?
	294
	295	Attribute Documentation:
	296
2.7	297	(% style="width:1050.29px" %)
	298	\|Name\|Type\|(% style="width:622px" %)Documentation
	299	\|id\|IDType\|(% style="width:622px" %)The id is the identifier for the object.
	300	\|urn\|MetadataSetUrnType\|(% style="width:622px" %)The urn attribute holds a valid SDMX Registry URN (see SDMX Registry Specification for details).
	301	\|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.
	302	\|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.
	303	\|validFrom\|xs:dateTime\|(% style="width:622px" %)The validFrom attribute provides the inclusive start date for providing supplemental validity information about the version.
	304	\|validTo\|xs:dateTime\|(% style="width:622px" %)The validTo attribute provides the inclusive end date for providing supplemental validity information about the version.
	305	\|agencyID\|NestedNCNameIDType\|(% style="width:622px" %)The agencyID must be provided and identifies the maintenance agency of the object.
	306	\|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.
	307	\|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.
	308	\|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.
	309	\|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.
	310	\|reportingBeginDate\|BasicTimePeriodType\|(% style="width:622px" %)The reportingBeginDate indicates the inclusive start time of the data reported in the data or metadata set.
	311	\|reportingEndDate\|BasicTimePeriodType\|(% style="width:622px" %)The reportingEndDate indicates the inclusive end time of the data reported in the data or metadata set.
	312	\|publicationYear\|xs:gYear\|(% style="width:622px" %)The publicationYear holds the ISO 8601 four-digit year.
	313	\|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).
2.2	314
	315	Element Documentation:
	316
2.7	317	(% style="width:1054.29px" %)
	318	\|Name\|(% style="width:185px" %)Type\|(% style="width:412px" %)Documentation
	319	\|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.
	320	\|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.
	321	\|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.
	322	\|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.
	323	\|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.
	324	\|Metadataflow\|(% style="width:185px" %)MetadataflowReference<br/>Type\|(% style="width:412px" %)Metadataflow provides a reference to the metadataflow the metadata set is being reported against.
	325	\|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.
	326	\|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.
2.2	327
	328	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.
	329
	330	Derivation:
	331
	332	AnnotableType (extension)
	333	AttributeType
	334
	335	Attributes:
	336	id
	337
	338	Content:
	339	Annotations?, (Value+\|Text+\|StructuredText+)?, Attribute
	340
	341	Attribute Documentation:
	342
2.8	343	(% style="width:1037.29px" %)
	344	\|(% style="width:113px" %)Name\|(% style="width:162px" %)Type\|(% style="width:760px" %)Documentation
	345	\|(% 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.
2.2	346
	347	Element Documentation:
	348
2.8	349	(% style="width:1095.29px" %)
	350	\|Name\|Type\|(% style="width:821px" %)Documentation
	351	\|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.
	352	\|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.
	353	\|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.
	354	\|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.
	355	\|Attribute\|AttributeType\|(% style="width:821px" %)Att contains the reported metadata attribute values for the child metadata attributes.
2.2	356
	357	= 3 Mapping to Structure-Specific Schemas =
	358
	359	== 3.1 General ==
	360
	361	Data-structure-specific schemas are each based on one single core construct found in the structure-specific namespace:
	362
	363	Data - http://www.SDMX.org/resources/SDMXML/schemas/v3_1/data/structurespecific
	364
	365	=== 3.1.1 Basic Terminology ===
	366
	367	In the subsequent sections, the following namespace prefixes are used:
	368
	369	\|Namespace\|Prefix\|
2.8	370	\|http:~/~/www.w3.org/2001/XMLSchema\|xs\|
	371	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v3_1/common\|common\|
	372	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v3_1/data/structurespecific\|dsd\|
	373	\|<http:~/~/www.sdmx.org/resources/sdmxml/schemas/v3_1/metadata/generic>\|metadata\|
2.2	374
	375	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:
	376
	377	Schema: Refers to the format specific schema in general, and in particular the root xs:schema element of that schema file.
	378
	379	Global Element: Refers to an element definition at the top level of the schema (i.e. an xs:element element in the root xs:schema element). It will define a name and type (name and type attributes) and possibly a substitution group (substitutionGroup attribute).
	380
	381	Local Element: Refers to an element definition within a complex type (i.e. an xs:element element contained within a xs:sequence element that is contained in a xs:complexType element). A local element must define a name and type (name and type attributes) and may also specify a minimum and maximum occurrence (minOccurs and maxOccurs attribute).
	382
	383	Qualified/Unqualified Element: A qualified element is an element that must be referred to by the namespace in which it was defined. An unqualified element does not have a namespace associated with it. The structure-specific schemas make use of unqualified elements to that the structure-specific schemas can restrict the base content to meet the specific needs of the structure, while maintaining as much of the original document structure as possible.
	384
	385	Element Reference: Refers to an element definition within a complex type that is a reference to a global element (i.e. an xs:element element contained within a xs:sequence element that is contained in a xs:complexType element). An element reference must reference a global element (via its ref attribute) and may also specify a minimum and maximum occurrence (minOccurs and maxOccurs attribute).
	386
	387	Complex Type: Refers to a complex type definition. In this context, all complex type definitions occur at the top level of the schema (i.e. an xs:complexType element in the root xs:schema element). A complex type must define a name (name attribute) and may be made abstract (via the abstract attribute’s boolean value).
	388
	389	Simple Type: Refers to a simple type definition. In this context, all simple type definitions occur at the top level of the schema (i.e. an xs:simpleType element in the root xs:schema element). In this context, a simple type will always be defined via a restriction (an xs:restriction element in the xs:simpleType element). The restriction will reference a base type.
	390
	391	Anonymous Type: A complex or simple type definition which occurs within an element definition. The method is sometimes referred to a the "Russian-doll" technique as it creates nested constructs. Anonymous types are not given names and cannot be abstract. The can however, be derived from other types.
	392
	393	Content Group: A group which defines a content model for reuse. This is contained in the xs:group element and is defined at the root of the schema. It allows for a common sequence or choice of elements to be reused across multiple types without having to redefine the sequence or choice in each type.
	394
	395	Uniqueness Constraint: A uniqueness constraint is defined within an element and is used to force descendent elements to be unique based on some criteria of it fields (elements or attributes). This is defined in an \<xs:unique\> element and has content of an \<xs:selector\> and multiple \<xs:field\> elements. The selector designates the descendants that must be unique (with an xpath attribute) and the field specifies which property of the selected element must be unique (also with an xpath attribute)
	396
	397	Extension: Refers to the definition of a complex type that is an extension of another complex type. The extension will always make a reference to a base. In the schema, this is defined within the xs:complexType element as a child xs:complexContent element containing an xs:extension element (with a base attribute).
	398
	399	Restriction: Refers to the definition of a simple or complex type that is a restriction of another type of the same variety. The restriction will always make a reference to a base. In the schema, this is defined with an xs:restriction element (with a base attribute).
	400
	401	Sequence: Refers to a sequence of elements that may be defined as the root of a complex type content model, or as part of the content of a choice or another sequence. This is defined as an xs:sequence element. The sequence may specify a minimum and maximum occurrence (minOccurs and maxOccurs attribute).
	402
	403	Choice: Refers to a choice of elements that may be defined as the root of a complex type content model, or as part of the content of a sequence or another choice. This is defined as an xs:choice element. The sequence may specify a minimum and maximum occurrence (minOccurs and maxOccurs attribute).
	404
	405	Facet: Refers to a single detail of a simple type restriction. This is represented by elements such as xs:minInclusive, xs:totalDigits, xs:minLength, and is contained in the xs:restriction element of a simple type definition. The value of the facet is contained in a value attribute of the particular element.
	406
	407	Enumeration: Refers to an enumerated value of a simple type definition. It is represented by an xs:enumeration element contained within an xs:restriction element of a simple type definition. An enumeration defines a value (in the value attribute) and documentation (in xs:documentation elements contained in an xs:annotation element).
	408
	409	XML Attribute: Refers to the definition of an XML attribute for a complex type (i.e. and xs:attribute element in a xs:complexType element). An attribute must define a name and type (name and type attributes) and may also specify a usage (use attribute).
	410
	411	== 3.2 Namespace Rules ==
	412
	413	Each format specific schema will specify its namespace in the target namespace of the schema (the targetNamespace attribute of the schema). This document also assumes that the root namespace (that which is defined by the xmlns attribute) of the schema will be the same as the target namespace. Therefore, any types or global elements referenced in these descriptions without a namespace prefix are assumed to be in the format specific namespace.
	414
	415	The format specific schemas will incorporate the core format namespace and the common namespace by importing the schemas (via the xs:import element). If necessary, additional namespaces may be imported and referenced.
	416
	417	For the purpose of the descriptions here, the default element form for the schema (as specified in the elementFormDefault attribute of the schema) is "qualified", and the default attribute form (as specified in the attributeFormDefault attribute of the schema) is "unqualified".
	418
	419	== 3.3 General Rules ==
	420
	421	The following section details the general rules which apply to all structure-specific schema creation.
	422
	423	=== 3.3.1 Component Name Determination ===
	424
	425	When required to create an XML element or attribute, the name for a component is always its identifier. However, the identifier may be inherited. Therefore, the general rules are as follows:
	426
	427	1. If the component defines an identifier, the element or attribute name is the value of that identifier
	428	2. Otherwise, the element or attribute name is the identifier of the concept from which it takes its semantic (Note that this is technically the component identifier).
	429
	430	=== 3.3.2 Representation Determination ===
	431
	432	Every component has a representation associated with it, whether it is defined as a local representation in the component definition, or it is inherited from the concept from which the component takes it semantic (as defined in the concept identity of the component).
	433
	434	The representation of a component is determined by the following precedence:
	435
	436	1. The local representation defined by the component
2.8	437	1. The core representation defined in the concept from which the component takes its semantic
	438	1. A default representation of an un-faceted text format with a data type of String.
2.2	439
	440	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).
	441
	442	A text format consists of a data type and an optional collection of facets. It is the combination of these which determine the exact nature of the component representation. An enumeration consists of a reference to a codelist, hierarchy, or value list, for which an enumerated list of possible values can be created.
	443
	444	=== 3.3.3 Simple / Primitive Type Determination ===
	445
	446	For any given representation, there exist rules for determining the simple or primitive type which should be used to validate the value. There are no specific requirements to how a simple type is named or if it is referenced or used as an anonymous type. This section simply serves to state the requirements of the type for a component based on its [determined representation](#332-Representation-Determination).
	447
	448	For example, a dimension may inherit its representation for a concept, and the data type of a representation data type may be a String. The simplest solution would be to use the xs:string primitive type. However, an implementer may have chosen to generate simple types for all concepts to avoid having to look up the concept core representation for very component. In this case, the type may be given a name based on the concept and be a simple derivation from the xs:string type that places no further restrictions. The result would be that the type that is actually used for the dimension, although named after the concept, is effectively the required xs:string. These rules are meant to allow such flexibility in how types are created. The only requirement is that the type meet the requirements stated here.
	449
	450	=== 3.3.4 Representation with Codelist Enumeration ===
	451
	452	A representation which defines an enumeration from a codelist or hierarchy will result in a simple type that is a restriction of the common:IDType. The simple type will define enumerations for each code in the codelist or hierarchy, accounting for extensions. 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. Example:
	453
	454	xml
	455	<xs:simpleType name="ESTAT.CL\_COUNTRY.1.0">
	456	<xs:restriction base="common:IDType">
	457	<xs:enumeration value="BE">
	458	<xs:annotation>
	459	<xs:documentation xml:lang="en">Belgium</xs:documentation>
	460	</xs:annotation>
	461	</xs:enumeration>
	462
	463	=== 3.3.5 Representation with Value List Enumeration ===
	464
	465	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.
	466
	467	=== 3.3.6 Representation with Simple Text Format ===
	468
	469	A representation which defines a simple text format will result in a simple type or primitive type. The representation is simple if none of the following conditions are true:
	470
	471	* representation max occurs is greater than 1
	472	* text format data type is XHMTL
	473	* text format is multi-lingual
	474
	475	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:
	476
2.10	477	(% style="width:679.294px" %)
	478	\|(% style="width:286px" %)SDMX Data Type\|(% style="width:390px" %)XML Schema Data Type
	479	\|(% style="width:286px" %)String\|(% style="width:390px" %)xs:string
	480	\|(% style="width:286px" %)AlphaNumeric\|(% style="width:390px" %)common:AlphaNumericType
	481	\|(% style="width:286px" %)Alpha\|(% style="width:390px" %)common:AlphaType
	482	\|(% style="width:286px" %)Numeric\|(% style="width:390px" %)common:NumericType
	483	\|(% style="width:286px" %)BigInteger\|(% style="width:390px" %)xs:integer
	484	\|(% style="width:286px" %)Integer\|(% style="width:390px" %)xs:int
	485	\|(% style="width:286px" %)Long\|(% style="width:390px" %)xs:long
	486	\|(% style="width:286px" %)Short\|(% style="width:390px" %)xs:short
	487	\|(% style="width:286px" %)Decimal\|(% style="width:390px" %)xs:decimal
	488	\|(% style="width:286px" %)Float\|(% style="width:390px" %)xs:float
	489	\|(% style="width:286px" %)Double\|(% style="width:390px" %)xs:double
	490	\|(% style="width:286px" %)Boolean\|(% style="width:390px" %)xs:Boolean
	491	\|(% style="width:286px" %)URI\|(% style="width:390px" %)xs:anyURI
	492	\|(% style="width:286px" %)Count\|(% style="width:390px" %)xs:integer
	493	\|(% style="width:286px" %)InclusiveValueRange\|(% style="width:390px" %)xs:decimal
	494	\|(% style="width:286px" %)ExclusiveValueRange\|(% style="width:390px" %)xs: decimal
	495	\|(% style="width:286px" %)Incremental\|(% style="width:390px" %)xs: decimal
	496	\|(% style="width:286px" %)ObservationalTimePeriod\|(% style="width:390px" %)common:ObservationalTimePeriodType
	497	\|(% style="width:286px" %)StandardTimePeriod\|(% style="width:390px" %)common:StandardTimePeriodType
	498	\|(% style="width:286px" %)BasicTimePeriod\|(% style="width:390px" %)common:BasicTimePeriodType
	499	\|(% style="width:286px" %)GregorianTimePeriod\|(% style="width:390px" %)common:GregorianTimePeriodType
	500	\|(% style="width:286px" %)GregorianYear\|(% style="width:390px" %)xs:gYear
	501	\|(% style="width:286px" %)GregorianYearMonth\|(% style="width:390px" %)xs:gYearMonth
	502	\|(% style="width:286px" %)GregorianDay\|(% style="width:390px" %)xs:date
	503	\|(% style="width:286px" %)ReportingTimePeriod\|(% style="width:390px" %)common:ReportingTimePeriodType
	504	\|(% style="width:286px" %)ReportingYear\|(% style="width:390px" %)common:ReportingYearType
	505	\|(% style="width:286px" %)ReportingSemester\|(% style="width:390px" %)common:ReportingSemesterType
	506	\|(% style="width:286px" %)ReportingTrimester\|(% style="width:390px" %)common:ReportingTrimesterType
	507	\|(% style="width:286px" %)ReportingQuarter\|(% style="width:390px" %)common:ReportingQuarterType
	508	\|(% style="width:286px" %)ReportingMonth\|(% style="width:390px" %)common:ReportingMonthType
	509	\|(% style="width:286px" %)ReportingWeek\|(% style="width:390px" %)common:ReportingWeekType
	510	\|(% style="width:286px" %)ReportingDay\|(% style="width:390px" %)common:ReportingDayType
	511	\|(% style="width:286px" %)DateTime\|(% style="width:390px" %)xs:dateTime
	512	\|(% style="width:286px" %)TimeRange\|(% style="width:390px" %)common:TimeRangeType
	513	\|(% style="width:286px" %)Month\|(% style="width:390px" %)xs:gMonth
	514	\|(% style="width:286px" %)MonthDay\|(% style="width:390px" %)xs:gMonthDay
	515	\|(% style="width:286px" %)Day\|(% style="width:390px" %)xs:gDay
	516	\|(% style="width:286px" %)Time\|(% style="width:390px" %)xs:time
	517	\|(% style="width:286px" %)Duration\|(% style="width:390px" %)xs:duration
	518	\|(% style="width:286px" %)GeospatialInformation\|(% style="width:390px" %)xs:string
	519	\|(% style="width:286px" %)XHTML\|(% style="width:390px" %)See the following section for complex representations
2.2	520
	521	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):
	522
2.10	523	(% style="width:1007.29px" %)
	524	\|(% style="width:267px" %)SDMX Facet\|(% style="width:729px" %)XML Schema Facet
	525	\|(% style="width:267px" %)minLength\|(% style="width:729px" %)xs:minLength
	526	\|(% style="width:267px" %)maxLength\|(% style="width:729px" %)xs:maxLength
	527	\|(% style="width:267px" %)minValue[^1]\|(% style="width:729px" %)if ExclusiveValueRange: xs:minExclusives, else: xs:minInclusive
	528	\|(% style="width:267px" %)maxValue[^1]\|(% style="width:729px" %)if ExclusiveValueRange: xs:maxExclusives, else: xs:maxInclusive
	529	\|(% style="width:267px" %)decimals[^1]\|(% style="width:729px" %)xs:fractionDigits
	530	\|(% style="width:267px" %)pattern\|(% style="width:729px" %)xs:pattern
2.2	531
	532	[^1]: Note that these options only apply to numeric representations and should be ignored if the data type is non-numeric.
	533
	534	Any other facets are informational only and will not affect the determined type.
	535
	536	=== 3.3.7 Representation for Not Applicable Dimensions ===
	537
	538	Not applicable dimensions, i.e., when reported measures or attributes are not attached to those dimensions, take as value the tilde ‘’ character. This is required for datasets defined by a DSD that has the ‘evolving structure’ property set to true and that includes data from dataflows, which only use a subset of dimensions as defined by a dimension constraint. This is also required for data-related higher-level (i.e., attached to dataflow or partial list of Dimensions) reference metadata attributes that don’t have a fixed pre-defined attachment.
	539
	540	To support a specific type and allow for a not applicable dimension value, the structure-specific schema must union the type with the common:NotApplicableType, which enumerates the tilde ‘’ character. This is as shown in the following example:
	541
	542	xml
	543	<xs:simpleType name="DecimalOrNotApplicableType">
	544	<xs:union memberTypes="xs:decimal common:NotApplicableType"/>
	545	</xs:simpleType>
	546
	547	For enumerated types, the generated structure-specific schema can include the special value in the enumeration or create a union between the enumerated type and the common:NotApplicableType.
	548
	549	Option 1: Augmenting the enumeration with the special value
	550
	551	xml
	552	<xs:simpleType name="CL\_SUBINDICATOR\_OR\_NOT\_APPLICABLE">
	553	<xs:union memberTypes="CL\_SUBINDICATOR common:NotApplicableType"/>
	554	</xs:simpleType>
	555
	556	Option 2: Extending the enumeration with the special value
	557
	558	xml
	559	<xs:simpleType name="CL\_ SUBINDICATOR ">
	560	<xs:restriction base="xs:string">
	561	<xs:enumeration value="A"/>
	562	<xs:enumeration value=""/>
	563	<xs:restriction>
	564	</xs:simpleType>
	565
	566	For convenience the common schema provides the union types for the following data types.
	567
2.10	568	(% style="width:747.294px" %)
	569	\|SDMX Data Type\|(% style="width:418px" %)XML Schema Data Type
	570	\|AlphaNumeric\|(% style="width:418px" %)common:AlphaNumericOrNotApplicableType
	571	\|Alpha\|(% style="width:418px" %)common:AlphaOrNotApplicableType
	572	\|Numeric\|(% style="width:418px" %)common:NumericOrNotApplicableType
	573	\|BigInteger\|(% style="width:418px" %)common:IntegerOrNotApplicableType
	574	\|Integer\|(% style="width:418px" %)common:IntOrNotApplicableType
	575	\|Long\|(% style="width:418px" %)common:LongOrNotApplicableType
	576	\|Short\|(% style="width:418px" %)common:ShortOrNotApplicableType
	577	\|Decimal\|(% style="width:418px" %)common:DecimalOrNotApplicableType
	578	\|Float\|(% style="width:418px" %)common:FloatOrNotApplicableType
	579	\|Double\|(% style="width:418px" %)common:DoubleOrNotApplicableType
	580	\|Boolean\|(% style="width:418px" %)common:BooleanOrNotApplicableType
	581	\|Count\|(% style="width:418px" %)common:IntegerOrNotApplicableType
	582	\|InclusiveValueRange\|(% style="width:418px" %)common:DecimalOrNotApplicableType
	583	\|ExclusiveValueRange\|(% style="width:418px" %)common:DecimalOrNotApplicableType
	584	\|Incremental\|(% style="width:418px" %)common:DecimalOrNotApplicableType
	585	\|ObservationalTimePeriod\|(% style="width:418px" %)common:ObservationalTimePeriodOrNotApplicableType
	586	\|StandardTimePeriod\|(% style="width:418px" %)common:StandardTimePeriodOrNotApplicableType
	587	\|BasicTimePeriod\|(% style="width:418px" %)common:BasicTimePeriodType
	588	\|GregorianTimePeriod\|(% style="width:418px" %)common:GregorianTimePeriodOrNotApplicableType
	589	\|ReportingTimePeriod\|(% style="width:418px" %)common:ReportingTimePeriodOrNotApplicableType
	590	\|ReportingYear\|(% style="width:418px" %)common:ReportingYearOrNotApplicableType
	591	\|ReportingSemester\|(% style="width:418px" %)common:ReportingSemesterOrNotApplicableType
	592	\|ReportingTrimester\|(% style="width:418px" %)common:ReportingTrimesterOrNotApplicableType
	593	\|ReportingQuarter\|(% style="width:418px" %)common:ReportingQuarterOrNotApplicableType
	594	\|ReportingMonth\|(% style="width:418px" %)common:ReportingMonthOrNotApplicableType
	595	\|ReportingWeek\|(% style="width:418px" %)common:ReportingWeekOrNotApplicableType
	596	\|ReportingDay\|(% style="width:418px" %)common:ReportingDayOrNotApplicableType
	597	\|TimeRange\|(% style="width:418px" %)common:TimeRangeOrNotApplicableType
2.2	598
	599	=== 3.3.8 Representation for Intentionally Missing Measure and Attribute Values ===
	600
	601	For intentionally missing measure and attribute values, even if mandatory, the following special values can be used:
	602
	603	* NaN for all numeric types (float, double)
	604	* #N/A for all other types
	605
	606	To support a specific type and allow for an intentionally missing measure or attribute value, the structure-specific schema must union the type with the common:MissingType, which enumerates the #N/A string. Note that XML natively already supports NaN for float and double values.
	607
	608	This union is as shown in the following example:
	609
	610	xml
	611	<xs:simpleType name="DecimalOrMissingType">
	612	<xs:union memberTypes="xs:decimal common:MissingType"/>
	613	</xs:simpleType>
	614
	615	For enumerated types, the generated structure-specific schema can include the special value in the enumeration or create a union between the enumerated type and the common:MissingType.
	616
	617	Option 1: Augmenting the enumeration with the special value
	618
	619	xml
	620	<xs:simpleType name="CL\_SUBINDICATOR\_OR\_NOT\_APPLICABLE">
	621	<xs:union memberTypes="CL\_SUBINDICATOR common:MissingType"/>
	622	</xs:simpleType>
	623
	624	Option 2: Extending the enumeration with the special value
	625
	626	xml
	627	<xs:simpleType name="CL\_ SUBINDICATOR ">
	628	<xs:restriction base="xs:string">
	629	<xs:enumeration value="A"/>
	630	<xs:enumeration value="#N/A"/>
	631	<xs:restriction>
	632	</xs:simpleType>
	633
	634	For convenience the common schema provides the union types for the following data types.
	635
2.10	636	(% style="width:804.294px" %)
	637	\|(% style="width:279px" %)SDMX Data Type\|(% style="width:522px" %)XML Schema Data Type
	638	\|(% style="width:279px" %)AlphaNumeric\|(% style="width:522px" %)common:AlphaNumericOrMissingType
	639	\|(% style="width:279px" %)Alpha\|(% style="width:522px" %)common:AlphaOrMissingType
	640	\|(% style="width:279px" %)Numeric\|(% style="width:522px" %)common:NumericOrMissingType
	641	\|(% style="width:279px" %)BigInteger\|(% style="width:522px" %)common:IntegerOrMissingType
	642	\|(% style="width:279px" %)Integer\|(% style="width:522px" %)common:IntOrMissingType
	643	\|(% style="width:279px" %)Long\|(% style="width:522px" %)common:LongOrMissingType
	644	\|(% style="width:279px" %)Short\|(% style="width:522px" %)common:ShortOrMissingType
	645	\|(% style="width:279px" %)Decimal\|(% style="width:522px" %)common:DecimalOrMissingType
	646	\|(% style="width:279px" %)Float\|(% style="width:522px" %)common:FloatOrMissingType
	647	\|(% style="width:279px" %)Double\|(% style="width:522px" %)common:DoubleOrMissingType
	648	\|(% style="width:279px" %)Boolean\|(% style="width:522px" %)common:BooleanOrMissingType
	649	\|(% style="width:279px" %)Count\|(% style="width:522px" %)common:IntegerOrMissingType
	650	\|(% style="width:279px" %)InclusiveValueRange\|(% style="width:522px" %)common:DecimalOrMissingType
	651	\|(% style="width:279px" %)ExclusiveValueRange\|(% style="width:522px" %)common:DecimalOrMissingType
	652	\|(% style="width:279px" %)Incremental\|(% style="width:522px" %)common:DecimalOrMissingType
	653	\|(% style="width:279px" %)ObservationalTimePeriod\|(% style="width:522px" %)common:ObservationalTimePeriodOrMissingType
	654	\|(% style="width:279px" %)StandardTimePeriod\|(% style="width:522px" %)common:StandardTimePeriodOrMissingType
	655	\|(% style="width:279px" %)BasicTimePeriod\|(% style="width:522px" %)common:BasicTimePeriodType
	656	\|(% style="width:279px" %)GregorianTimePeriod\|(% style="width:522px" %)common:GregorianTimePeriodOrMissingType
	657	\|(% style="width:279px" %)ReportingTimePeriod\|(% style="width:522px" %)common:ReportingTimePeriodOrMissingType
	658	\|(% style="width:279px" %)ReportingYear\|(% style="width:522px" %)common:ReportingYearOrMissingType
	659	\|(% style="width:279px" %)ReportingSemester\|(% style="width:522px" %)common:ReportingSemesterOrMissingType
	660	\|(% style="width:279px" %)ReportingTrimester\|(% style="width:522px" %)common:ReportingTrimesterOrMissingType
	661	\|(% style="width:279px" %)ReportingQuarter\|(% style="width:522px" %)common:ReportingQuarterOrMissingType
	662	\|(% style="width:279px" %)ReportingMonth\|(% style="width:522px" %)common:ReportingMonthOrMissingType
	663	\|(% style="width:279px" %)ReportingWeek\|(% style="width:522px" %)common:ReportingWeekOrMissingType
	664	\|(% style="width:279px" %)ReportingDay\|(% style="width:522px" %)common:ReportingDayOrMissingType
	665	\|(% style="width:279px" %)TimeRange\|(% style="width:522px" %)common:TimeRangeOrMissingType
2.2	666
	667	=== 3.3.9 Representation with Complex Text Format ===
	668
	669	A representation which defines a complex text format will result in a complex type. The representation is complex if any of the following conditions are true:
	670
	671	* representation max occurs is greater than 1
	672	* text format data type is XHMTL
	673	* text format is multi-lingual
	674
	675	The resulting complex type will be derived via restriction of the common:ValueType. In simple cases, there are pre-defined types that can be used:
	676
	677	* if the text format data type is XHTML, common:StructuredTextValueType can be used; note that this type cannot be further restricted – all other facets are ignored
	678	* if the text format is multi-lingual, common:TextValueType can be used; note that this type cannot be further restricted – all other facets are ignored
	679	* if the text format has no additional facets and the data type is:
	680	+ Boolean, common:BooleanValueType can be used
	681	+ String, common:StringValueType can be used
	682	+ Integer, common:IntValueType can be used
	683	+ Double, common:DoubleValueType can be used
	684	+ ObservationalTimePeriod, common:ObservationalTimePeriodValueType can be used
	685
	686	If a pre-defined type cannot be used, one will have to be created. The complex type must define a simple content restriction of the common:ValueType. The restriction should define an anonymous simple type based on the text format data type and facets as described in the previous section.
	687
	688	=== 3.3.10 Type Names ===
	689
	690	These rules will only dictate type names where absolutely necessary. In all other cases, it is the decision of the implementer as to how to name or use the type. It is also the implementer's requirement to ensure that any type name is properly unique within its scope. To assist in this, the following recommendations are offered for naming types such that they are unique.
	691
	692	* It the type is an enumeration from an item scheme, the recommended name is [Item Scheme Class].[Maintenance Agency].[Item Scheme ID].[Item Scheme Version]
	693	* If the type is based on a text format of a concept core representation, the recommended name is Concept.[Maintenance Agency].[Concept Scheme ID].[Concept Scheme Version].[Concept ID]
	694	* If the type is based on a text format of a component local representation, and;
	695	+ The component id is required to be unique for all components within the scope of the structure which defines it (e.g. a dimension), the recommended name is [Component ID]
	696	+ The component id is only required to be unique within the component list and which defines it (e.g. a metadata attribute), the recommend name is [Component List ID].[Parent Component ID]\*.[Component ID]
	697
	698	=== 3.3.11 Type Reuse ===
	699
	700	It is possible that organisations that manage a large number of structure-specific schemas my wish to take advantage of the reuse of previously defined type in order to simply the structure-specific schema creation and lessen the number of schema elements which are created. The structure-specific formats are designed in such a way that this would be allowed without any adverse affects.
	701
	702	For example, an organisation my create predefined types for all of codelists and concept schemes which their structures utilize. These could be contained in a common schema with any namespace deemed appropriate. This would allow the structure-specific schemas generation process to recognize the reused components and not be concerned with regenerating types. The logical flow for setting the representation of a component might be as follows:
	703
	704	Does the component define a local type?
	705	Yes: Is that type enumerated?
	706	Yes: Type is the qualified type name for the item scheme
	707	No: Generate simple type for text format
	708	No: Type is the qualified name for the concept from which the component takes its semantic.
	709
	710	Only the constructs that will be detailed in the data and metadata structure-specific rules below are required to be in the specified target namespace of the structure-specific schema. So long as any other generated type conforms to the rules specified, it may exist in any namespace.
	711
	712	== 3.4 Data-Structure-Specific Schema ==
	713
	714	Separate schemas will be created for the data structure depending on which dimension occurs at the observation level. The recommended target namespace of the data structured specific schema is: [Data Structure URN]:ObsLevelDim:[Observation Dimensions].
	715
	716	The rules for generating the data-structure-specific-schema are broken into sections based on the level within the structure (i.e. data set, group, series, attributes, observation). Each section will state the rules for each variation of the structure-specific format.
	717
	718	=== 3.4.1 DataSetType ===
	719
	720	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:
	721
2.10	722	~1. A sequence consisting of:
2.2	723
2.10	724	* i. An element reference to common:Annotations, with a minimum occurrence of 0
	725	* ii A local element named DataProvider with the type common:DataProviderReferenceType, a form of unqualified and a minimum occurrence of 0
	726	* iii A choice with a minimum occurrence of 0 and a maximum occurrence of unbounded consisting of:
	727	** a. A local element named Atts with a form of unqualified and a type of AttsType (as defined in the AttsType section which follows)
	728	** 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.
	729	** 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)
	730	** 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)
	731	* 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
	732
2.2	733	=== 3.4.2 GroupType ===
	734
	735	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:
	736
2.11	737	~1. A sequence consisting of:
	738
	739	* i. An element reference to common:Annotations, with a minimum occurrence of 0
	740	* 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
	741	* 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
	742
	743	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
	744	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
2.2	745	4. An attribute named type with a type of common:IDType, usage of optional, and a fixed value of the identifier of the group
	746
	747	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:
	748
2.12	749	~1. A sequence consisting of:
	750
	751	* i. An element reference to common:Annotations, with a minimum occurrence of 0
	752	* 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
	753	* 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
	754
2.2	755	2. An attribute named type with a type of Group.ID, and a usage of optional
	756	3. An anyAttribute declaration with a namespace of ##local##
	757
	758	A simple type named Group.ID must be created. This should restrict the common:IDType. For each group defined by the data structure definition, an enumeration will be created within the restriction with a value of the group identifier.
	759
	760	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:
	761
2.13	762	~1. A sequence consisting of:
	763
	764	* i. An element reference to common:Annotations, with a minimum occurrence of 0
	765	* 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
	766	* 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
	767
	768	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
	769	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
2.2	770	4. An attribute named type with a type of Group.ID, usage of optional, and a fixed value of the identifier of the group
	771
	772	=== 3.4.3 SeriesType ===
	773
	774	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:
	775
2.14	776	~1. A sequence consisting of:
	777
	778	* i. An element reference to common:Annotations, with a minimum occurrence of 0
	779	* 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
	780	* 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)
	781	* 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
	782
2.2	783	2. 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
2.14	784	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
	785	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
2.2	786
	787	=== 3.4.4 AttsType ===
	788
	789	A complex type named AttsType must be created. Its content model will be derived via restriction of dsd:AttsType. The complex type content model will be as follows:
	790
2.15	791	~1. A sequence consisting of:
	792
	793	* i. An element reference to common:Annotations, with a minimum occurrence of 0
	794	* ii. If any attributes with complex representation are defined in the data structure, a Comp element with a form of unqualified, a minimum occurrence of 0, a maximum occurrence of unbounded, and a type of dsd:CompType
	795
2.2	796	2. If there is no dimension (TIME\_PERIOD) defined by the data structure, an attribute named TIME\_PERIOD with a type of common:ObservationalTimePeriod, and a usage of prohibited
2.15	797	3. An attribute for all dimension defined by the data structure definition. The XML attribute name and type are defined according to the general rules defined in the previous section, and the usage is optional
	798	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
2.2	799
	800	=== 3.4.5 ObsType ===
	801
	802	A complex type name ObsType must be created. Its content model will be derived via restriction of the base type dsd:ObsType. The complex type content model will be as follows:
	803
2.16	804	~1. A sequence consisting of:
	805
	806	* i. An element reference to common:Annotations, with a minimum occurrence of 0
	807	* ii. If any measures with complex representations are defined in the data structure, any attributes with complex representation that declare an attribute relationship with the observation, a Comp element with a form of unqualified, a minimum occurrence of 0, a maximum occurrence of unbounded, and a type of dsd:CompType
	808	* iii. If any metadata attribute usages defined in the data structure that declares an attribute relationship with the observation, a local element named Metadata with the type metadata:MetadataSetType a form of unqualified, and a minimum occurrence of 0
	809
2.2	810	2. An attribute named TIME\_PERIOD with a type of common:
	811	ObservationalTimePeriodValueType. If the dimension at the observation level is the time dimension (TIME\_PERIOD) or all dimensions and the time dimension is defined by the data structure, a usage of required; otherwise, a usage of prohibited
2.16	812	3. If the dimension at the observation level is not all dimensions or the time dimension (TIME\_PERIOD), an attribute for the dimension at the observation level. The XML attribute name and type are defined according to the general rules defined in the previous section, and the usage is required
	813	4. If the dimension at the observation level is all dimensions, an attribute for each dimension defined by the data structure definition, except for the time dimension (TIME\_PERIOD). The XML attribute name and type are defined according to the general rules defined in the previous section, and the usage is required
	814	5. An attribute for each measure with simple representation defined by the data structure definition. The XML attribute name and type is defined according to the general rules defined in the previous section, and the usage is optional
	815	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
2.2	816
	817	=== 3.4.6 CompType ===
	818
	819	For every measure and data attribute with complex representation defined by the data structure definition, a complex type must be derived from the restriction of the dsd:CompType. The complex type content model will be as follows:
	820
	821	1. A sequence consisting of:
	822	1. An element reference to common:Annotations, with a minimum occurrence of 0
	823	2. A Value element with a form of unqualified, with a minimum occurrence of 0, a maximum occurrence defined by the representation, and a type based on the [complex representation type](#339-Representation-with-Complex-Text-Format) defined according to the general rules defined in the previous section
	824	2. An attribute named id with a type of common: NCNameIDType, usage of required, and a fixed value of the identifier of the measure or attribute
	825
	826	= 4 Data and Reference Metadata Actions =
	827
	828	== 4.1 Data Actions ==
	829
	830	Data messages allow indicating intended actions when used to update an SDMX storage system. This purpose is noted in the action of the data set, which is either inherited from the header of the data message or explicitly stated at the data set level.
	831
	832	Note that the former Append and Information actions are deprecated. When used to update an SDMX storage system, the Merge action is assumed.
	833
	834	=== 4.1.1 Merge Action ===
	835
	836	Data or data-related reference metadata is to be merged, through either update or insertion depending on already existing information. This operation does not allow deleting any component values. Updating individual values in multi-valued measure, attribute or data-related reference metadata values is not supported either. The complete multi-valued value is to be provided.
	837
	838	Only non-dimensional components (measure, attribute or data-related reference metadata values) can be omitted (null or absent) as long as at least one of those components is present. Bulk merges are thus not supported. Only the provided values are merged.
	839
	840	Dimension values for higher-level (data-related reference metadata) attributes can be switched-off (using ) when those are not attached to these dimensions.
	841
	842	All observations as well as the sets of data-related reference metadata attributes at specific dimension combinations impacted by the Merge action change their time stamp when used to update an SDMX storage system.
	843
	844	=== 4.1.2 Replace Action ===
	845
	846	Data or data-related reference metadata is to be replaced, through either update, insert or delete depending on already existing information. A full replacement is hereby assumed to take place at specific “replacement levels”: for entire observations and for any specific dimension combination for data-related reference metadata attributes. Within these “replacement levels” the provided values are inserted or updated, and omitted values are deleted. Values provided for the other attributes (those above the observation level) are merged (see Merge action).
	847
	848	Only non-dimensional components (measure, attribute or reference metadata values) can be omitted (null or absent). Bulk replacing is thus not supported.
	849
	850	Dimension values for higher-level (data-related reference metadata) attributes can be switched-off (using ) when those are not attached to these dimensions.
	851
	852	Replacing non-existing elements is not resulting in an error.
	853
2.17	854	All observations as well as the sets of data-related reference metadata attributes at specific dimension combinations impacted by the //Replace// action change their time stamp when used to update an SDMX storage system.
2.2	855
2.17	856	Because the //replace// action always takes place at specific levels, it cannot be used to replace a whole dataset or a whole series. However, a //“replace all”// effect can be achieved by combining a //Delete// dataset containing a completely wildcarded key (where all dimension values are omitted) with a //Merge// or //Replace// dataset within the same data message. Similarly, to replace a whole series, a message can combine a delete dataset containing only the partial key of the series (where the not used dimension values are omitted) with a //Merge// or //Replace// dataset for that series.
2.2	857
	858	=== 4.1.3 Delete Action ===
	859
	860	Data or data-related reference metadata is to be deleted. Deletion is hereby assumed to take place at the lowest level of detail provided in the message.
	861
	862	Any component (including dimensions) can be omitted (dimensions: empty, others: null or absent). Omitting dimension values allows for bulk deletions. Partially omitting non-dimension component values allows restricting the deletion of measure, attribute or data-related reference metadata values to the ones being present. Instead of real values for non-dimensional components, it is sufficient to use any valid value.
	863
	864	With this, whole datasets, any slices of observations for dimension groups such as time series, observations or individual measure, attribute and data-related reference metadata attributes values can be deleted.
	865
	866	Dimension values for higher-level (data-related reference metadata) attributes can be switched-off (using ) when those are not attached to these dimensions.
	867
	868	Deleting non-existing elements or values is not resulting in an error.
	869
	870	All observations as well as the sets of attributes and data-related reference metadata at higher partial keys impacted by the Delete action change their time stamp when used to update an SDMX storage system.
	871
	872	=== 4.1.4 Further Details ===
	873
	874	The following convention is used to indicate the state of components in data messages:
	875
	876	\| \| \|Dimension value is\| \|Measure, attribute or reference metadata value is\| \|
	877	\| \| \|Omitted\|switched off\|Omitted\|Present\|
	878	\|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\|
	879	\| \|Merge\|bulk merge is not permitted\|(see above)\|not to be changed\|to be updated/inserted\|
	880	\| \|Replace\|bulk replace is not permitted\|(see above)\|at permitted replacement levels: to be deleted, otherwise not to be changed\|to be updated/inserted\|
	881	\|Format\|XML\|xml element/attribute is absent\|~\|xml element/attribute is absent\|any valid or intentionally missing value\|
	882	\| \|JSON\|\<empty\>\|““\|NULL or absent\|(see above)\|
	883	\| \|CSV\|\<empty\> cell or column is absent\|~\|<empty> cell or column is absent\|(see above)\|
	884
	885	Important notes:
	886
	887	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.
	888
	889	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.
	890
	891	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).
	892
	893	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.
	894
	895	Recommended[^2] dataset actions in SDMX web service responses to GET data queries:
	896
	897	1. Without the updatedAfter, includeHistory, detail, attributes or measures URL parameters:
	898
	899	The response message should contain the retrieved data in a Replace dataset (instead of the previous information dataset).
	900
	901	1. Without the updatedAfter and includeHistory, but with detail, attributes or measures URL parameters:
	902
	903	The response message should contain the retrieved data in a Merge dataset (instead of the previous Information dataset).
	904
	905	1. With the updatedAfter URL parameter:
	906
	907	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:
	908
	909	* 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
	910	a Replace dataset for all other changed observations and changed attribute and data-related reference metadata values attached to specific dimension combinations, or
	911	* 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
	912	a Merge dataset for all other updated or inserted observation, attribute and data-related reference metadata values.
	913
	914	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.
	915
	916	1. With the includeHistory URL parameter:
	917
	918	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.
	919
	920	1. With the asOf URL parameter:
	921
	922	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.
	923
	924	[^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.
	925
	926	== 4.2 Reference Metadata Actions ==
	927
	928	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.
	929
	930	The former message header or metadataset property DataSetAction is deprecated. To avoid conflicts, it is now ignored if still present.