Wiki source code of Part IV. Data

Version 4.3 by Helena on 2025/06/24 14:47

version	line-number	content
4.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, where format is either generic or structured (i.e. the structure specific formats). This also applies to the message names as well, where the names follow the pattern of FormatData (e.g. StructuredData and GenericMetadata).
	8
	9	The various data messages which existed in the standard have been harmonised into two general formats; generic and structured data. The generic data is much like it has been previously, only slightly modified to conform with the harmonised view on data. The structured data combined the principles of the previous versions compact and cross sectional formats into one more generalised format.
	10
	11	The major shift from the previous version is now that 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 placed at the observation level. This in effect, combined the abilities of the time series and cross sectional formats in the a single data format. This format also allows for multiple measure to be expressed when the observation dimension is the measure dimension defined in the data structured. The key differences from the previous versions is that this all is possible in a single data structure definition specific format, as well as being possible in the generic format as well. The goal was to make the structures as homogenous as possible.
	12
	13	Another shift from the previous version in the manner in which the base data structure specific format is defined. In previous versions there was not structure defined, so one had to understand all of the requirements and read the specification in order to understand what could be expected in any structure specific format. In this version, that issue has been addressed. The base structures now impose a strict format on the data structure specific schemas. This is achieved much like the referencing structure in the common namespace through the use of unqualified elements. By the elements not existing in a namespace, the structure specific schemas can place the necessary restrictions of them while still being forced to adhere to prescribed structure. This means that not only are the structures able to perform the validation that is required, but that the messages will be much simpler to process as the format will always use the same element names.
	14
	15	Finally, in order to allow for systems which wish to not process the new more flexible data format, time series only variations of both the generic and structured data sets exist. It is important to note that these structures are derived via restriction from the more generalised format. This means that a data set in the general format with the time dimension at the observation level will have exactly the same content as a time series only data set. The result of this is that there is no additional burden for processing the time series specific format it a system can process the more generalised format. These time series only data sets allow for time series only data messages to exist. These messages make it simple for system which, in the previous version of the standard, only used the time series formats to continue to do so.
	16
	17	These same principles have been applied to the reference data messages as well. In the previous version of the standard there were major differences between the generic and metadata structure-specific formats; some of the differences caused some metadata sets were incompatible between versions. In this version the structures of the generic and metadata structure specific formats have been harmonised to the point where they are nearly identical. Yet, the structured format still provides the strong validation against the metadata structure that is intended. And, as with the data, the base metadata structure specific format now imposes a stricter structure on the generated schemas, making the structure specific instance simpler to process in a generic manner.
	18
	19	= 2. Schema Documentation =
	20
	21	== 2.1 Generic Data Namespace ==
	22
	23	http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/generic
	24
	25	=== 2.1.1 Summary ===
	26
	27	Referenced Namespaces:
	28
	29	\|Namespace\|Prefix
	30	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common\|com
	31	\|http:~/~/www.w3.org/2001/XMLSchema\|xs
	32
	33	Contents:
	34	13 Complex Types
	35
	36	=== 2.1.2 Complex Types ===
	37
	38	DataSetType: DataSetType defines the structure of the generic data set. Data is organised into either a collection of series (grouped observations) or a collection of un-grouped observations. The organisation used is dependent on the structure specification in the header of the data message (which is referenced via the structureRef attribute). The structure specification states which data occurs at the observation level. If this dimension is "AllDimensions" then the data set 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 (attribute values). 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.
	39
	40	Derivation:
	41
	42	* //com:AnnotableType// (extension)
	43	** DataSetType
	44
	45	Attributes:
	46	structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?
	47
	48	Content:
	49	com:Annotations?, DataProvider?, Attributes?, Group*, (Series+ \| Obs+)?
	50
	51	Attribute Documentation:
	52
	53	\|Name\|Type\|Documentation
	54	\|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).
	55	\|setID\|com:IDType\|The setID provides an identification of the data or metadata set.
	56	\|action\|com:ActionType\|The action attribute indicates whether the file is appending, replacing, or deleting.
	57	\|reportingBeginDate\|com: BasicTimePeriodType\|The reportingBeginDate indicates the inclusive start time of the data reported in the data or metadata set.
	58	\|reportingEndDate\|com: BasicTimePeriodType\|The reportingEndDate indicates the inclusive end time of the data reported in the data or metadata set.
	59	\|validFromDate\|xs:dateTime\|The validFromDate indicates the inclusive start time indicating the validity of the information in the data or metadata set.
	60	\|validToDate\|xs:dateTime\|The validToDate indicates the inclusive end time indicating the validity of the information in the data or metadata set.
	61	\|publicationYear\|xs:gYear\|The publicationYear holds the ISO 8601 four-digit year.
	62	\|publicationPeriod\|com: ObservationalTimePer iodType\|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).
	63
	64	Element Documentation:
	65
	66	\|Name\|Type\|Documentation
	67	\|com:Annotations\|com: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 my reference it.
	68	\|DataProvider\|com: DataProviderReferenc eType\|DataProvider contains a reference to the provider for the data set.
	69	\|Attributes\|ValuesType\|Attributes contains the collection of attribute values for attributes defined in the data structure definition which do not have an attribute relationship with any other data structure definition components.
	70	\|Group\|GroupType\|Group contains a references 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 which is declared in the structure specification to be at the observation level. In addition to the key and observations, the series contains values for 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\|ObsOnlyType\|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 attributes which have an association with the primary measure or any dimension (so long as it does not specify a group attachment).
	73
	74	GroupType: GroupType 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.
	75
	76	Derivation:
	77	* //com:AnnotableType// (extension)
	78	** GroupType
	79
	80	Attributes:
	81	type
	82
	83	Content:
	84	com:Annotations?, GroupKey?, Attributes
	85
	86	Attribute Documentation:
	87
	88	\|Name\|Type\|Documentation
	89	\|type\|com:IDType\|The type attribute holds the identifier assigned to the group in the data structure definition for which attribute values are being provided.
	90
	91	Element Documentation:
	92
	93	\|Name\|Type\|Documentation
	94	\|com:Annotations\|com: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 my reference it.
	95	\|GroupKey\|ValuesType\|GroupKey contains the values for each dimension defined as being a member of the referenced group in the data structure definition. A value must be provided for every group dimension. This is optional, and not used if the group is defined as an association to an attachment constraint rather than a subset of the data structure definition dimensions.
	96	\|Attributes\|ValuesType\|Attributes contains the set of attribute values which are reported for group. The attribute values provided here apply to all data matching the partial key defined by the group key or the key sets of the associated attachment constraint.
	97
	98	SeriesType: SeriesType 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. In addition to observations, values can be provided for 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 an relationship with the observation dimension). It is possible for the series to contain only observations or only attribute values, or both.
	99
	100	Derivation:
	101
	102	* //com:AnnotableType// (extension)
	103	** SeriesType
	104
	105	Content:
	106	com:Annotations?, SeriesKey, Attributes?, Obs*
	107
	108	Element Documentation:
	109	\|Name\|Type\|Documentation
	110	\|com:Annotations\|com: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 my reference it.
	111	\|SeriesKey\|ValuesType\|SeriesKey contains the values for each all dimensions defined in the data structure definition, except for that which is declared to be at the observation level for this data set. This key is required, and every dimension must be provided a value.
	112	\|Attributes\|ValuesType\|Attributes contains the values for attributes which are associated with the dimensions which make up the series key, so long as the attributes do not also specify an attachment group or have a relationship with the observation dimension.
	113	\|Obs\|ObsType\|Obs contains an observation which shares the dimensionality of the series key. These observations are disambiguated from one another within this series by a single dimension value provided for each dimension. The dimension which provides this observation key is declared in the structure specification for the data set, which is provided in the header of the data message.
	114
	115	ObsOnlyType: ObsOnlyType defines the structure for an un-grouped observation. Unlike a group observation, an un-grouped must provided a full set of values for every dimension declared in the data structure definition. The observation can contain an observed value and/or a collection of attribute values.
	116
	117	Derivation:
	118
	119	* //com:AnnotableType// (extension)
	120	** ObsOnlyType
	121
	122	Content:
	123	com:Annotations?, ObsKey, ObsValue?, Attributes?
	124
	125	Element Documentation:
	126	\|Name\|Type\|Documentation
	127	\|com:Annotations\|com: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 my reference it.
	128	\|ObsKey\|ValuesType\|ObsKey contains the values for every dimension defined in the data structure definition. A value must be provided for each dimension. This key serves to disambiguate the un-grouped observation within the data set.
	129	\|ObsValue\|ObsValueType\|ObsValue type contains the value for the observation.
	130	\|Attributes\|ValuesType\|Attributes contains the set of values reported for the attributes which have an association with the primary measure or any dimension in the data structure definition (so long as an attachment group is not also specified).
	131
	132	ObsType: ObsType defines the structure of a grouped observation. The observation must be provided a value for the dimension which is declared to be at the observation level for this data set. This dimension value should disambiguate the observation within the series in which it is defined (i.e. there should not be another observation with the same dimension value). The observation can contain an observed value and/or attribute values.
	133
	134	Derivation:
	135
	136	* //com:AnnotableType// (extension)
	137	** ObsType
	138
	139	Content:
	140	com:Annotations?, ObsDimension, ObsValue?, Attributes?
	141
	142	Element Documentation:
	143	\|Name\|Type\|Documentation
	144	\|com:Annotations\|com: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 my reference it.
	145	\|ObsDimension\|BaseValueType\|ObsDimension holds the key for the grouped observation, i.e. the value of the observation dimension. Note that in this element, the reference to the dimension is optional, since it can be inferred from the structure specification for the data set. This saves having to repeat the value unnecessarily. It is assumed that any application processing the data set will have the information from the structure specification available, so that if a dimension identifier is not supplied here, the proper reference can be applied.
	146	\|ObsValue\|ObsValueType\|ObsValue type contains the value for the observation.
	147	\|Attributes\|ValuesType\|Attributes contains the set of values reported for the attributes which have an association with the primary measure or the observations dimension (so long as an attachment group is not also specified).
	148
	149	ValuesType: ValuesType is a general structure which contains a collection of data structure definition component values. This type is used to provide both key and attribute collection values.
	150
	151	Content:
	152	Value+
	153
	154	Element Documentation:
	155	\|Name\|Type\|Documentation
	156	\|Value\|ComponentValueType\|Value contains a component value and a reference to the component for which a value is being provided.
	157
	158	BaseValueType: BaseValueType is a general structure which contains a reference to a data structure definition component and a value for that component. In this structure the reference to the component is optional to allow for usages where the actual reference might be provided in another context.
	159
	160	Attributes:
	161	id?, value
	162
	163	Content:
	164	{Empty}
	165
	166	Attribute Documentation:
	167	\|Name\|Type\|Documentation
	168	\|id\|com:NCNameIDType\|The id attribute contains the identifier for the component for which a value is being provided.
	169	\|value\|xs:anySimpleType\|The value attribute contains the provided component value.
	170
	171	ObsValueType: ObsValueType is a derivation of the BaseValueType which is used to provide an observation value. Since an observation value is always associated with the data structure definition primary measure, and the identifier for the primary measure is fixed, the component reference for this structure is fixed. Note that this means that it is not necessary to provide a value in an instance as the fixed value will be provided in the post validation information set.
	172
	173	Derivation:
	174
4.3	175	* BaseValueType (restriction)
	176	** ObsValueType
4.2	177
	178	Attributes:
	179	id?, value
	180
	181	Content:
	182	{Empty}
	183
	184	Attribute Documentation:
	185	\|Name\|Type\|Documentation
	186	\|id (fixed: OBS_VALUE)\|com:NCNameIDType\|The id attribute contains a fixed reference to the primary measure component of the data structure definition.
	187	\|value\|xs:string\|The value attribute contains the provided component value.
	188
	189	ComponentValueType: ComponentValueType is a derivation of the BaseValueType which requires that the component reference be provided. This is used when the identification of the component cannot be inferred from another context.
	190
	191	Derivation:
4.3	192	* BaseValueType (restriction)
	193	** ComponentValueType
4.2	194
	195	Attributes:
	196	id, value
	197
	198	Content:
	199	{Empty}
	200
	201	Attribute Documentation:
	202	\|Name\|Type\|Documentation
	203	\|id\|com:NCNameIDType\|The id attribute contains the identifier for the component for which a value is being provided.
	204	\|value\|xs:string\|The value attribute contains the provided component value.
	205
	206	TimeSeriesDataSetType: TimeSeriesDataSetType is a derivation of the base DataSetType of the generic format the restricts the data set to only allow for grouped observations where the dimension at the observation level is the time dimension of the data structure definition. This means that unlike the base data set structure, there can be no un-grouped observations. Because this derivation is achieved using restriction, data sets conforming to this type will inherently conform to the base data set structure as well. In fact, data structured here will be identical to data in the base data set when the time dimension is the observation dimension. This means that the data contained in this structure can be processed in exactly the same manner as the base structure.
	207
	208	Derivation:
	209
	210	//com:AnnotableType// (extension)
	211	[[image:1750765436901-853.png]]DataSetType (restriction)
	212	[[image:1750765436906-461.png]]TimeSeriesDataSetType
	213
	214	Attributes:
	215
	216	structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?
	217
	218	Content:
	219
	220	com:Annotations?, DataProvider?, Attributes?, Group, Series
	221
	222	Attribute Documentation:
	223
	224	\|Name\|Type\|Documentation
	225	\|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).
	226	\|setID\|com:IDType\|The setID provides an identification of the data or metadata set.
	227	\|action\|com:ActionType\|The action attribute indicates whether the file is appending, replacing, or deleting.
	228	\|reportingBeginDate\|com: BasicTimePeriodType\|The reportingBeginDate indicates the inclusive start time of the data reported in the data or metadata set.
	229	\|reportingEndDate\|com: BasicTimePeriodType\|The reportingEndDate indicates the inclusive end time of the data reported in the data or metadata set.
	230	\|validFromDate\|xs:dateTime\|The validFromDate indicates the inclusive start time indicating the validity of the information in the data or metadata set.
	231	\|validToDate\|xs:dateTime\|The validToDate indicates the inclusive end time indicating the validity of the information in the data or metadata set.
	232	\|publicationYear\|xs:gYear\|The publicationYear holds the ISO 8601 four-digit year.
	233	\|publicationPeriod\|com: ObservationalTimePer iodType\|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).
	234
	235	Element Documentation:
	236
	237	\|Name\|Type\|Documentation
	238	\|com:Annotations\|com: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 my reference it.
	239	\|DataProvider\|com: DataProviderReferenc eType\|DataProvider contains a reference to the provider for the data set.
	240	\|Attributes\|ValuesType\|Attributes contains the collection of attribute values for attributes defined in the data structure definition which do not have an attribute relationship with any other data structure definition components.
	241	\|Group\|GroupType\|Group contains a references 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.
	242	\|Series\|TimeSeriesType\|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 time dimension. In addition to the key and observations, the series contains values for 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 time dimension.
	243
	244	TimeSeriesType: TimeSeriesType defines a structure which is used to group a collection of observations which have a key in common, organised by time. The key for a series is every dimension defined in the data structure definition, save the time dimension. In addition to observations, values can be provided for 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 an relationship with the time dimension). It is possible for the series to contain only observations or only attribute values, or both.
	245
	246	Derivation:
	247
	248	//com:AnnotableType// (extension)
	249	[[image:1750765436911-979.png]]SeriesType (restriction)
	250	[[image:1750765436912-452.png]]TimeSeriesType
	251
	252	Content:
	253
	254	com:Annotations?, SeriesKey, Attributes?, Obs*
	255
	256	Element Documentation:
	257
	258	\|Name\|Type\|Documentation
	259	\|com:Annotations\|com: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 my reference it.
	260	\|SeriesKey\|ValuesType\|SeriesKey contains the values for each all dimensions defined in the data structure definition, except for that which is declared to be at the observation level for this data set. This key is required, and every dimension must be provided a value.
	261	\|Attributes\|ValuesType\|Attributes contains the values for attributes which are associated with the dimensions which make up the series key, so long as the attributes do not also specify an attachment group or have a relationship with the observation dimension.
	262	\|Obs\|TimeSeriesObsType\|Obs contains an observation which shares the dimensionality of the series key. These observations are disambiguated from one another within this series by a time value.
	263
	264	TimeSeriesObsType: TimeSeriesObsType defines the structure of a time series observation. The observation must be provided a value for the time dimension. This time value should disambiguate the observation within the series in which it is defined (i.e. there should not be another observation with the same time value). The observation can contain an observed value and/or attribute values.
	265
	266	Derivation:
	267
	268	//com:AnnotableType// (extension)
	269	[[image:1750765436913-909.png]]ObsType (restriction)
	270	[[image:1750765436914-333.png]]TimeSeriesObsType
	271
	272	Content:
	273
	274	com:Annotations?, ObsDimension, ObsValue?, Attributes?
	275
	276	Element Documentation:
	277
	278	\|Name\|Type\|Documentation
	279	\|com:Annotations\|com: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 my reference it.
	280	\|ObsDimension\|TimeValueType\|ObsDimension holds the key for the grouped observation, i.e. the value of the observation dimension. Note that in this element, the reference to the dimension is optional, since it can be inferred from the structure specification for the data set. This saves having to repeat the value unnecessarily. It is assumed that any application processing the data set will have the information from the structure specification available, so that if a dimension identifier is not supplied here, the proper reference can be applied.
	281	\|ObsValue\|ObsValueType\|ObsValue type contains the value for the observation.
	282	\|Attributes\|ValuesType\|Attributes contains the set of values reported for the attributes which have an association with the primary measure or the time dimension (so long as an attachment group is not also specified).
	283
	284	TimeValueType: TimeValueType is a derivation of the BaseValueType which is used to provide a value for the time dimension. Since the identifier for the time dimension is fixed, the component reference for this structure is fixed. Note that this means that it is not necessary to provide a value in an instance as the fixed value will be provided in the post validation information set.
	285
	286	Derivation:
	287
	288	BaseValueType (restriction)
	289	[[image:1750765436914-771.png]]TimeValueType
	290
	291	Attributes:
	292
	293	id?, value
	294
	295	Content:
	296
	297	{Empty}
	298
	299	Attribute Documentation:
	300
	301	\|Name\|Type\|Documentation
	302	\|id (fixed: TIME_PERIOD)\|com:NCNameIDType\|The id attribute contains the identifier for the component for which a value is being provided.
	303	\|value\|com: ObservationalTimePer iodType\|The value attribute contains the provided component value.
	304
	305	1.
	306	11. Structure Specific Data Namespace
	307
	308	http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/structurespecific
	309
	310	1.
	311	11.
	312	111. Summary
	313
	314	Referenced Namespaces:
	315
	316	\|Namespace\|Prefix
	317	\| \|
	318	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common\|com
	319	\|http:~/~/www.w3.org/2001/XMLSchema\|xs
	320
	321	Contents:
	322
	323	7 Complex Types
	324	1 Simple Type
	325
	326	1.
	327	11.
	328	111. Complex Types
	329
	330	//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 and whether explicit measures should be used). 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 (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, and observation 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. The data set can contain values for attributes which do not have an attribute relationship with any data structure definition components. These attribute values will exist in XML attributes in this element based on this type (DataSet). This is specified in the content model with the declaration of anyAttributes in the "local" namespace. The derived data set 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). To allow for generic processing, it is required that the only unqualified XML attributes in the derived data set type (outside of the standard data set attributes) be for 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 attribute.
	331
	332	Derivation:
	333
	334	//com:AnnotableType// (extension)
	335	[[image:1750765436915-836.png]]//DataSetType//
	336
	337	Attributes:
	338
	339	structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?, dataScope, REPORTING_YEAR_START_DAY?
	340
	341	Content:
	342
	343	com:Annotations?, DataProvider?, Group*, (Series+ \| Obs+)?
	344
	345	Attribute Documentation:
	346
	347	\|Name\|Type\|Documentation
	348	\|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).
	349	\|setID\|com:IDType\|The setID provides an identification of the data or metadata set.
	350	\|action\|com:ActionType\|The action attribute indicates whether the file is appending, replacing, or deleting.
	351	\|reportingBeginDate\|com: BasicTimePeriodType\|The reportingBeginDate indicates the inclusive start time of the data reported in the data or metadata set.
	352	\|reportingEndDate\|com: BasicTimePeriodType\|The reportingEndDate indicates the inclusive end time of the data reported in the data or metadata set.
	353	\|validFromDate\|xs:dateTime\|The validFromDate indicates the inclusive start time indicating the validity of the information in the data or metadata set.
	354	\|validToDate\|xs:dateTime\|The validToDate indicates the inclusive end time indicating the validity of the information in the data or metadata set.
	355	\|publicationYear\|xs:gYear\|The publicationYear holds the ISO 8601 four-digit year.
	356	\|publicationPeriod\|com: ObservationalTimePer iodType\|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).
	357	\|dataScope\|DataScopeType\|The dataScope attribute indicates the scope at which the data is meant to be validated. These scopes are hierarchical and are (from the top down); DataStructure, ConstrainedDataStructure, Dataflow, and ProvisionAgreement. the hierarchy of these scopes represent the cascading level of constraints, which can restrict the valid values for components. For example, a data structure defines a dimension with a coded representation. A data flow might have a constraint associated with it which further restricts the values allowed from the referenced code list to a subset of the values allowed by the data structure definition. A provision agreement that is based on the dataflow might also have a constraint, which further restricts the subset of the codelist from the dataflow. Therefore, the allowed content becomes stricter lower in the hierarchy. Data that is given a scope of one value is stated to be valid at that level and all levels below it. Therefore, this scope serves to state that data that is meant to be structured simply against the data structure definition is not meant to be validated against the a dataflow, where constraints might be applied.
	358	\|REPORTING_YEAR_START_DAY\|xs:gMonthDay\|The REPORTING_YEAR_START_DAY attribute is an explict attribute for the reporting year start day, which provides context to the time dimension when its value contains a reporting period (e.g. 2010-Q1). This attribute is used to state the month and day that the reporting year begins (e.g. ~-~-07-01 for July 1st). In the absence of an explicit value provided in this attribute, all reporting period values will be assumed to be based on a reporting year start day of January 1. This is declared in the base schema since it has a fixed identifier and representation. The derived data set type may either require or prohibit this attribute, depending on whether the data structure declared the reporting year start day attribute and if so, the attribute relationship and assignment status assigned to it.
	359
	360	Element Documentation:
	361
	362	\|Name\|Type\|Documentation
	363	\|com:Annotations\|com: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 my reference it.
	364	\|DataProvider\|com: DataProviderReferenc eType\|DataProvider contains a reference to the provider for the data set.
	365	\|Group\|//GroupType//\|Group contains a references 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.
	366	\|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 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.
	367	\|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 attributes which have an association with the primary measure or any dimension (so long as it does not specify a group attachment).
	368
	369	//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 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.
	370
	371	Derivation:
	372
	373	//com:AnnotableType// (extension)
	374	[[image:1750765436916-983.png]]//GroupType//
	375
	376	Attributes:
	377
	378	type?, REPORTING_YEAR_START_DAY?
	379
	380	Content:
	381
	382	com:Annotations?
	383
	384	Attribute Documentation:
	385
	386	\|Name\|Type\|Documentation
	387	\|type\|com:IDType\|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.
	388	\|REPORTING_YEAR_START_DAY\|xs:gMonthDay\|The REPORTING_YEAR_START_DAY attribute is an explict attribute for the reporting year start day, which provides context to the time dimension when its value contains a reporting period (e.g. 2010-Q1). This attribute is used to state the month and day that the reporting year begins (e.g. ~-~-07-01 for July 1st). In the absence of an explicit value provided in this attribute, all reporting period values will be assumed to be based on a reporting year start day of January 1. This is declared in the base schema since it has a fixed identifier and representation. The derived group types may either require or prohibit this attribute, depending on whether the data structure declared the reporting year start day attribute and if so, the attribute relationship and assignment status assigned to it.
	389
	390	Element Documentation:
	391
	392	\|Name\|Type\|Documentation
	393	\|com:Annotations\|com: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 my reference it.
	394
	395	//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. In addition to observations, values can be provided for 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 an 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 drive 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.
	396
	397	Derivation:
	398
	399	//com:AnnotableType// (extension)
	400	//SeriesType//
	401
	402	Attributes:
	403
	404	TIME_PERIOD?, REPORTING_YEAR_START_DAY?
	405
	406	Content:
	407
	408	com:Annotations?, Obs*
	409
	410	Attribute Documentation:
	411
	412	\|Name\|Type\|Documentation
	413	\|TIME_PERIOD\|com: ObservationalTimePer iodType\|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.
	414	\|REPORTING_YEAR_START_DAY\|xs:gMonthDay\|The REPORTING_YEAR_START_DAY attribute is an explict attribute for the reporting year start day, which provides context to the time dimension when its value contains a reporting period (e.g. 2010-Q1). This attribute is used to state the month and day that the reporting year begins (e.g. ~-~-07-01 for July 1st). In the absence of an explicit value provided in this attribute, all reporting period values will be assumed to be based on a reporting year start day of January 1. This is declared in the base schema since it has a fixed identifier and representation. The derived series type may either require or prohibit this attribute, depending on whether the data structure declared the reporting year start day attribute and if so, the attribute relationship and assignment status assigned to it.
	415
	416	Element Documentation:
	417
	418	\|Name\|Type\|Documentation
	419	\|com:Annotations\|com: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 my reference it.
	420	\|Obs\|//ObsType//\|
	421
	422	//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 drive 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 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. If the data structure definition specific schema requires that explicit measures be used (only possible when the measure dimension is specified at the observation), then there will be types derived for each measure defined by the measure dimension. In this case, the types will be specific to each measure, which is to say that the representation of the primary measure (i.e. the observed value) will be restricted to that which is specified by the specific measure.
	423
	424	Derivation:
	425
	426	//com:AnnotableType// (extension)
	427	//ObsType//
	428
	429	Attributes:
	430
	431	type?, TIME_PERIOD?, REPORTING_YEAR_START_DAY?, OBS_VALUE?
	432
	433	Content:
	434
	435	com:Annotations?
	436
	437	Attribute Documentation:
	438
	439	\|Name\|Type\|Documentation
	440	\|type\|com:IDType\|The type attribute is used when the derived format requires that explicit measure be used. In this case, the derived type based on the measure will fix this value to be the identification of the measure concept. This will not be required, but since it is fixed it will be available in the post validation information set which will allow for generic processing of the data. If explicit measures are not used, then the derived type will prohibit the use of this attribute.
	441	\|TIME_PERIOD\|com: ObservationalTimePer iodType\|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.
	442	\|REPORTING_YEAR_START_DAY\|xs:gMonthDay\|The REPORTING_YEAR_START_DAY attribute is an explict attribute for the reporting year start day, which provides context to the time dimension when its value contains a reporting period (e.g. 2010-Q1). This attribute is used to state the month and day that the reporting year begins (e.g. ~-~-07-01 for July 1st). In the absence of an explicit value provided in this attribute, all reporting period values will be assumed to be based on a reporting year start day of January 1. This is declared in the base schema since it has a fixed identifier and representation. The derived observation type may either require or prohibit this attribute, depending on whether the data structure declared the reporting year start day attribute and if so, the attribute relationship and assignment status assigned to it.
	443	\|OBS_VALUE\|xs:anySimpleType\|The OBS_VALUE attribute is an explicit attribute for the primary measure, which is intended to hold the value for the observation. This is declared in the base schema since it has a fixed identifier. This attribute is un-typed, since the representation of the observed value can vary widely. Derived types will restrict this to be a type based on the representation of the primary measure. In the case that an explicit measure is used, the derived type for a given measure might further restrict the type of the primary measure to be more specific to the core representation for the measure concept. Note that it is required that in the case of multiple measures being used, that the representation of the primary measure is broad enough to handle the various representations of the measure concepts.
	444
	445	Element Documentation:
	446
	447	\|Name\|Type\|Documentation
	448	\|com:Annotations\|com: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 my reference it.
	449
	450	//TimeSeriesDataSetType//: TimeSeriesDataSetType is the abstract type which defines the base structure for any data structure definition specific time series based data set. A derived data set type will be created that is specific to a data structure definition. Unlike the base format, only one variation of this is allowed for a data structure definition. This variation is the time dimension as the observation dimension. Data is organised into a collection of time series. Because this derivation is achieved using restriction, data sets conforming to this type will inherently conform to the base data set structure as well. In fact, data structure specific here will be identical to data in the base data set when the time dimension is the observation dimension, even for the derived data set types. This means that the data contained in this structure can be processed in exactly the same manner as the base structure. The same rules for derivation as the base data set type apply to this specialized data set.
	451
	452	Derivation:
	453
	454	//com:AnnotableType// (extension)
	455	//DataSetType// (restriction)
	456	//TimeSeriesDataSetType//
	457
	458	Attributes:
	459
	460	structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?, dataScope, REPORTING_YEAR_START_DAY?
	461
	462	Content:
	463
	464	com:Annotations?, DataProvider?, Group, Series
	465
	466	Attribute Documentation:
	467
	468	\|Name\|Type\|Documentation
	469	\|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).
	470	\|setID\|com:IDType\|The setID provides an identification of the data or metadata set.
	471	\|action\|com:ActionType\|The action attribute indicates whether the file is appending, replacing, or deleting.
	472	\|reportingBeginDate\|com: BasicTimePeriodType\|The reportingBeginDate indicates the inclusive start time of the data reported in the data or metadata set.
	473	\|reportingEndDate\|com: BasicTimePeriodType\|The reportingEndDate indicates the inclusive end time of the data reported in the data or metadata set.
	474	\|validFromDate\|xs:dateTime\|The validFromDate indicates the inclusive start time indicating the validity of the information in the data or metadata set.
	475	\|validToDate\|xs:dateTime\|The validToDate indicates the inclusive end time indicating the validity of the information in the data or metadata set.
	476	\|publicationYear\|xs:gYear\|The publicationYear holds the ISO 8601 four-digit year.
	477	\|publicationPeriod\|com: ObservationalTimePer iodType\|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).
	478	\|dataScope\|DataScopeType\|The dataScope attribute indicates the scope at which the data is meant to be validated. These scopes are hierarchical and are (from the top down); DataStructure, ConstrainedDataStructure, Dataflow, and ProvisionAgreement. the hierarchy of these scopes represent the cascading level of constraints, which can restrict the valid values for components. For example, a data structure defines a dimension with a coded representation. A data flow might have a constraint associated with it which further restricts the values allowed from the referenced code list to a subset of the values allowed by the data structure definition. A provision agreement that is based on the dataflow might also have a constraint, which further restricts the subset of the codelist from the dataflow. Therefore, the allowed content becomes stricter lower in the hierarchy. Data that is given a scope of one value is stated to be valid at that level and all levels below it. Therefore, this scope serves to state that data that is meant to be structured simply against the data structure definition is not meant to be validated against the a dataflow, where constraints might be applied.
	479	\|REPORTING_YEAR_START_DAY\|xs:gMonthDay\|The REPORTING_YEAR_START_DAY attribute is an explict attribute for the reporting year start day, which provides context to the time dimension when its value contains a reporting period (e.g. 2010-Q1). This attribute is used to state the month and day that the reporting year begins (e.g. ~-~-07-01 for July 1st). In the absence of an explicit value provided in this attribute, all reporting period values will be assumed to be based on a reporting year start day of January 1. This is declared in the base schema since it has a fixed identifier and representation. The derived data set type may either require or prohibit this attribute, depending on whether the data structure declared the reporting year start day attribute and if so, the attribute relationship and assignment status assigned to it.
	480
	481	Element Documentation:
	482
	483	\|Name\|Type\|Documentation
	484	\|com:Annotations\|com: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 my reference it.
	485	\|DataProvider\|com: DataProviderReferenc eType\|DataProvider contains a reference to the provider for the data set.
	486	\|Group\|//GroupType//\|Group contains a references 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.
	487	\|Series\|TimeSeriesType\|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 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.
	488
	489	TimeSeriesType: TimeSeriesType defines an abstract structure which is used to group a collection of observations which have a key in common, organised by time. The key for a series is every dimension defined in the data structure definition, save the time dimension. In addition to observations, values can be provided for 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 an relationship with the time dimension). It is possible for the series to contain only observations or only attribute values, or both. The same rules for derivation as the base series type apply to this specialized series.
	490
	491	Derivation:
	492
	493	//com:AnnotableType// (extension)
	494	//SeriesType// (restriction)
	495	TimeSeriesType
	496
	497	Attributes:
	498
	499	REPORTING_YEAR_START_DAY?
	500
	501	Content:
	502
	503	com:Annotations?, Obs*
	504
	505	Attribute Documentation:
	506
	507	\|Name\|Type\|Documentation
	508	\|REPORTING_YEAR_START_DAY\|xs:gMonthDay\|The REPORTING_YEAR_START_DAY attribute is an explict attribute for the reporting year start day, which provides context to the time dimension when its value contains a reporting period (e.g. 2010-Q1). This attribute is used to state the month and day that the reporting year begins (e.g. ~-~-07-01 for July 1st). In the absence of an explicit value provided in this attribute, all reporting period values will be assumed to be based on a reporting year start day of January 1. This is declared in the base schema since it has a fixed identifier and representation. The derived series type may either require or prohibit this attribute, depending on whether the data structure declared the reporting year start day attribute and if so, the attribute relationship and assignment status assigned to it.
	509
	510	Element Documentation:
	511
	512	\|Name\|Type\|Documentation
	513	\|com:Annotations\|com: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 my reference it.
	514	\|Obs\|//TimeSeriesObsType//\|
	515
	516	//TimeSeriesObsType//: TimeSeriesObsType defines the abstract structure of a time series observation. The observation must be provided a value for the time dimension. This time value should disambiguate the observation within the series in which it is defined (i.e. there should not be another observation with the same time value). The observation can contain an observed value and/or attribute values. The same rules for derivation as the base observation type apply to this specialized observation.
	517
	518	Derivation:
	519
	520	//com:AnnotableType// (extension)
	521	//ObsType// (restriction)
	522	//TimeSeriesObsType//
	523
	524	Attributes:
	525
	526	TIME_PERIOD, REPORTING_YEAR_START_DAY?, OBS_VALUE?
	527
	528	Content:
	529
	530	com:Annotations?
	531
	532	Attribute Documentation:
	533
	534	\|Name\|Type\|Documentation
	535	\|TIME_PERIOD\|com: ObservationalTimePer iodType\|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. Since this data is structured to be time series only, this attribute is always required. If the time dimension specifies a more specific representation of time the derived type will restrict the type definition to the appropriate type.
	536	\|REPORTING_YEAR_START_DAY\|xs:gMonthDay\|The REPORTING_YEAR_START_DAY attribute is an explict attribute for the reporting year start day, which provides context to the time dimension when its value contains a reporting period (e.g. 2010-Q1). This attribute is used to state the month and day that the reporting year begins (e.g. ~-~-07-01 for July 1st). In the absence of an explicit value provided in this attribute, all reporting period values will be assumed to be based on a reporting year start day of January 1. This is declared in the base schema since it has a fixed identifier and representation. The derived observation type may either require or prohibit this attribute, depending on whether the data structure declared the reporting year start day attribute and if so, the attribute relationship and assignment status assigned to it.
	537	\|OBS_VALUE\|xs:anySimpleType\|The OBS_VALUE attribute is an explicit attribute for the primary measure, which is intended to hold the value for the observation. This is declared in the base schema since it has a fixed identifier. This attribute is un-typed, since the representation of the observed value can vary widely. Derived types will restrict this to be a type based on the representation of the primary measure. In the case that an explicit measure is used, the derived type for a given measure might further restrict the type of the primary measure to be more specific to the core representation for the measure concept. Note that it is required that in the case of multiple measures being used, that the representation of the primary measure is broad enough to handle the various representations of the measure concepts.
	538
	539	Element Documentation:
	540
	541	\|Name\|Type\|Documentation
	542	\|com:Annotations\|com: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 my reference it.
	543
	544	1.
	545	11.
	546	111. Simple Types
	547
	548	DataScopeType: DataScopeType is an enumeration of the possible validity scopes for a data set. These scopes indicate the level at which the data is stated to be valid.
	549
	550	Derived by restriction of xs:string .
	551
	552	Enumerations:
	553
	554	\|Value\|Documentation
	555	\|DataStructure\|The data set conforms simply to the data structure definition as it is defined, without regard to any constraints.
	556	\|ConstrainedDataStructure\|The data set conforms to the known allowable content constraints applied to the data structure definition.
	557	\|Dataflow\|The data set conforms to the known allowable content constraints applied to the dataflow.
	558	\|ProvisionAgreement\|The data set conforms to the known allowable content constraints applied to the provision agreement.
	559
	560	1.
	561	11. Generic Metadata Namespace
	562
	563	http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/generic
	564
	565	1.
	566	11.
	567	111. Summary
	568
	569	Referenced Namespaces:
	570
	571	\|Namespace\|Prefix
	572	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common\|com
	573	\|http:~/~/www.w3.org/2001/XMLSchema\|xs
	574
	575	Contents:
	576
	577	6 Complex Types
	578
	579	1.
	580	11.
	581	111. Complex Types
	582
	583	MetadataSetType: MetadataSetType describes the structure for a metadata set, which contains a collection of reported metadata against a set of values for a given full or partial target identifier, as described in a metadata structure definition. The metadata set may contain reported metadata for multiple report structures defined in a metadata structure definition.
	584
	585	Derivation:
	586
	587	//com:AnnotableType// (extension)
	588	MetadataSetType
	589
	590	Attributes:
	591
	592	structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?
	593
	594	Content:
	595
	596	com:Annotations?, com:Name*, DataProvider?, Report+
	597
	598	Attribute Documentation:
	599
	600	\|Name\|Type\|Documentation
	601	\|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).
	602	\|setID\|com:IDType\|The setID provides an identification of the data or metadata set.
	603	\|action\|com:ActionType\|The action attribute indicates whether the file is appending, replacing, or deleting.
	604	\|reportingBeginDate\|com: BasicTimePeriodType\|The reportingBeginDate indicates the inclusive start time of the data reported in the data or metadata set.
	605	\|reportingEndDate\|com: BasicTimePeriodType\|The reportingEndDate indicates the inclusive end time of the data reported in the data or metadata set.
	606	\|validFromDate\|xs:dateTime\|The validFromDate indicates the inclusive start time indicating the validity of the information in the data or metadata set.
	607	\|validToDate\|xs:dateTime\|The validToDate indicates the inclusive end time indicating the validity of the information in the data or metadata set.
	608	\|publicationYear\|xs:gYear\|The publicationYear holds the ISO 8601 four-digit year.
	609	\|publicationPeriod\|com: ObservationalTimePer iodType\|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).
	610
	611	Element Documentation:
	612
	613	\|Name\|Type\|Documentation
	614	\|com:Annotations\|com: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 my reference it.
	615	\|com:Name\|com:TextType\|Name is a reusable element, used for providing a human-readable name for an object.
	616	\|DataProvider\|com: DataProviderReferenc eType\|DataProviderReference provides a references to an organisation with the role of data provider that is providing this metadata set.
	617	\|Report\|ReportType\|Report contains the details of a the reported metadata, including the identification of the target and the report attributes.
	618
	619	ReportType: ReportType contains a set of report attributes and identifies a target objects] to which they apply.
	620
	621	Derivation:
	622
	623	//com:AnnotableType// (extension)
	624	ReportType
	625
	626	Attributes:
	627
	628	id
	629
	630	Content:
	631
	632	com:Annotations?, Target, AttributeSet
	633
	634	Attribute Documentation:
	635
	636	\|Name\|Type\|Documentation
	637	\|id\|com:IDType\|The id attribute holds the identifier of the report structure as defined in the metadata structure definition. This identifies the report structure which defines the structure of metadata that is being reported.
	638
	639	Element Documentation:
	640
	641	\|Name\|Type\|Documentation
	642	\|com:Annotations\|com: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 my reference it.
	643	\|Target\|TargetType\|Target contains a set of target reference values which when taken together, identify the object or objects to which the reported metadata apply.
	644	\|AttributeSet\|AttributeSetType\|AttributeSet contains the reported metadata attribute values for the reported metadata.
	645
	646	TargetType: TargetType defines the structure of a target. It contains a set of target reference values which when taken together, identify the object or objects to which the reported metadata apply.
	647
	648	Attributes:
	649
	650	id
	651
	652	Content:
	653
	654	ReferenceValue+
	655
	656	Attribute Documentation:
	657
	658	\|Name\|Type\|Documentation
	659	\|id\|com:IDType\|The id attribute holds the identifier of the metadata target as defined in the metadata structure definition. This identifies the metadata target of the report structure that identifies the target object(s) of the reported metadata.
	660
	661	Element Documentation:
	662
	663	\|Name\|Type\|Documentation
	664	\|ReferenceValue\|ReferenceValueType\|ReferenceValue contains a value for a target reference object reference. When this is taken with its sibling elements, they identify the object or objects to which the reported metadata apply. The content of this will either be a reference to an identifiable object, a data key, a reference to a data set, or a report period.
	665
	666	ReferenceValueType: ReferenceValueType defines the structure of a target object reference value. A target reference value will either be a reference to an identifiable object, a data key, a reference to a data set, or a report period.
	667
	668	Attributes:
	669
	670	id
	671
	672	Content:
	673
	674	(ObjectReference \| DataKey \| DataSetReference \| ConstraintContentReference \| ReportPeriod)
	675
	676	Attribute Documentation:
	677
	678	\|Name\|Type\|Documentation
	679	\|id\|com:IDType\|The id attribute holds the identifier of the target reference object as defined in the metadata structure definition. This identifies the target reference of the metadata target that identifes one of the target references, that when taken together, identify the target of the reported metadata.
	680
	681	Element Documentation:
	682
	683	\|Name\|Type\|Documentation
	684	\|ObjectReference\|com: ObjectReferenceType\|ObjectReference provides a reference to an identifiable object in the SDMX information model. An identifiable object target will utilize this option as the representation of the target reference value.
	685	\|DataKey\|com:DataKeyType\|ObjectReference provides a set of dimension references and values for those dimension for the purpose of reporting metadata against a set of data. A key descriptor values target will utilize this option as the representation of the target reference value.
	686	\|DataSetReference\|com:SetReferenceType\|DataSetReference provides a reference to a data set for the purpose of reporting metadata against the data. A data set target will utilize this option as the representation of the target reference value.
	687	\|ConstraintContentRef erence\|com: AttachmentConstraint ReferenceType\|ConstraintContentReference provides a reference to an attachment constraint for the purpose of reporting metadata against the data identified in the key sets and/or cube regions identified by the constraint. A constraint target will utilize this option as the representation of the target reference value.
	688	\|ReportPeriod\|com: ObservationalTimePer iodType\|ReportPeriod provides a report period for the purpose of qualifying the target reporting period of reported metadata. A report period target will utilize this option as the representation of the target reference value.
	689
	690	AttributeSetType: AttributeSetType defines the structure for a collection of reported metadata attributes.
	691
	692	Content:
	693
	694	ReportedAttribute+
	695
	696	Element Documentation:
	697
	698	\|Name\|Type\|Documentation
	699	\|ReportedAttribute\|ReportedAttributeTyp e\|ReportedAttribute provides the details of a reported attribute, including a value and/or child reported attributes.
	700
	701	ReportedAttributeType: ReportedAttributeType defines the structure for a reported metadata attribute. A value for the attribute can be supplied as either a single value, or multi-lingual text values (either structured or unstructured). An optional set of child metadata attributes is also available if the metadata attribute definition defines nested metadata attributes.
	702
	703	Derivation:
	704
	705	//com:AnnotableType// (extension)
	706	ReportedAttributeType
	707
	708	Attributes:
	709
	710	id, value?
	711
	712	Content:
	713
	714	com:Annotations?, (com:Text+ \| com:StructuredText+)?, AttributeSet?
	715
	716	Attribute Documentation:
	717
	718	\|Name\|Type\|Documentation
	719	\|id\|com:IDType\|The id attribute identifies the metadata attribute that the value is being reported for.
	720	\|value\|xs:string\|The value attribute holds any simple value for the metadata attribute.
	721
	722	Element Documentation:
	723
	724	\|Name\|Type\|Documentation
	725	\|com:Annotations\|com: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 my reference it.
	726	\|com:Text\|com:TextType\|Text is used to supply parallel multi-lingual textual values for the reported metadata attribute. This will be used if the text format of the metadata attribute has a type of string and the multi-lingual value is set to true.
	727	\|com:StructuredText\|com:XHTMLType\|StructuredText is used to supply parallel multi-lingual structured (as XHTML) textual values for the reported metadata attribute. This will be used if the text format of the metadata attribute has a type of XHTML and the multi-lingual value is set to true.
	728	\|AttributeSet\|AttributeSetType\|AttributeSet contains the reported metadata attribute values for the child metadata attributes.
	729
	730	1.
	731	11. Structure Specific Metadata Namespace
	732
	733	http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/structurespecific
	734
	735	1.
	736	11.
	737	111. Summary
	738
	739	Referenced Namespaces:
	740
	741	\|Namespace\|Prefix
	742	\| \|
	743	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common\|com
	744	\|http:~/~/www.w3.org/2001/XMLSchema\|xs
	745
	746	Contents:
	747
	748	5 Complex Types
	749
	750	1.
	751	11.
	752	111. Complex Types
	753
	754	//MetadataSetType//: MetadataSetType is an abstract base type the forms the basis for a metadata structure specific metadata set. It is restricted by the metadata structure definition specific schema to meet its needs.
	755
	756	Derivation:
	757
	758	//com:AnnotableType// (extension)
	759	//MetadataSetType//
	760
	761	Attributes:
	762
	763	structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?
	764
	765	Content:
	766
	767	com:Annotations?, com:Name*, DataProvider?, Report+
	768
	769	Attribute Documentation:
	770
	771	\|Name\|Type\|Documentation
	772	\|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).
	773	\|setID\|com:IDType\|The setID provides an identification of the data or metadata set.
	774	\|action\|com:ActionType\|The action attribute indicates whether the file is appending, replacing, or deleting.
	775	\|reportingBeginDate\|com: BasicTimePeriodType\|The reportingBeginDate indicates the inclusive start time of the data reported in the data or metadata set.
	776	\|reportingEndDate\|com: BasicTimePeriodType\|The reportingEndDate indicates the inclusive end time of the data reported in the data or metadata set.
	777	\|validFromDate\|xs:dateTime\|The validFromDate indicates the inclusive start time indicating the validity of the information in the data or metadata set.
	778	\|validToDate\|xs:dateTime\|The validToDate indicates the inclusive end time indicating the validity of the information in the data or metadata set.
	779	\|publicationYear\|xs:gYear\|The publicationYear holds the ISO 8601 four-digit year.
	780	\|publicationPeriod\|com: ObservationalTimePer iodType\|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).
	781
	782	Element Documentation:
	783
	784	\|Name\|Type\|Documentation
	785	\|com:Annotations\|com: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 my reference it.
	786	\|com:Name\|com:TextType\|Name is a reusable element, used for providing a human-readable name for an object.
	787	\|DataProvider\|com: DataProviderReferenc eType\|>DataProviderReference provides a references to an organisation with the role of data provider that is providing this metadata set.
	788	\|Report\|//ReportType//\|Report contains the details of a the reported metadata, including the identification of the target and the report attributes. This element is unqualified so that the metadata structure definition specific schema can refine the type of the element such that it requires types built according to the metadata structure definition. This allows the metadata structure definition to validate the structure of the reported metadata against the metadata structure definition while still allowing the content to be processed in a generic manner.
	789
	790	//ReportType//: ReportType is an abstract base type the forms the basis for a metadata structure definition specific report, based on the defined report structures. This type is restricted in the metadata structure definition specific schema so that the Target and AttributeSet conform to the prescribed report structure.
	791
	792	Derivation:
	793
	794	//com:AnnotableType// (extension)
	795	//ReportType//
	796
	797	Attributes:
	798
	799	id?
	800
	801	Content:
	802
	803	com:Annotations?, Target, AttributeSet
	804
	805	Attribute Documentation:
	806
	807	\|Name\|Type\|Documentation
	808	\|id\|com:IDType\|The id attribute holds the identifier of the report structure as defined in the metadata structure definition. This identifies the report structure which defines the structure of metadata that is being reported. This is optional and not expected to be supplied as the metadata structure definition specific schema will specify a fixed value such that the reference to the report structure will always be available if required for processing.
	809
	810	Element Documentation:
	811
	812	\|Name\|Type\|Documentation
	813	\|com:Annotations\|com: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 my reference it.
	814	\|Target\|//TargetType//\|Target contains a set of target reference values which when taken together, identify the object or objects to which the reported metadata apply. This element is unqualified so that the metadata structure definition specific schema can refine the type of the element such that the references values can be validated against those defined in the metadata targets for the report structure.
	815	\|AttributeSet\|xs:anyType\|AttributeSet contains the reported metadata attribute values for the reported metadata. This element is unqualified and un-typed so that it can refined by the metadata structure definition specific schema to validate that the reported metadata attributes conform to those prescribed by the report structure. The content of this must be element only, and these elements must always represent a reported attribute. Since this can not be strictly enforced in XML Schema, additional steps have been added to make generic processing of this element simpler. When processing this element, any element found with the attribute isMetadataAttribute in this target namespace is assumed to be a reported metadata attribute and can be processed as such.
	816
	817	//TargetType//: TargetType is an abstract base type that forms the basis of a the metadata report's metadata target value. This type is restricted in the metadata structure definition specific schema so that the ReferenceValue elements conform to the targets specified in the metadata target defined in the metadata structure definition.
	818
	819	Attributes:
	820
	821	id?
	822
	823	Content:
	824
	825	ReferenceValue+
	826
	827	Attribute Documentation:
	828
	829	\|Name\|Type\|Documentation
	830	\|id\|com:IDType\|The id attribute holds the identifier of the metadata target as defined in the metadata structure definition. This identifies the metadata target of the report structure that identifies the target object(s) of the reported metadata. This is optional and not expected to be supplied as the metadata structure definition specific schema will specify a fixed value such that the reference to the metadata target will always be available if required for processing.
	831
	832	Element Documentation:
	833
	834	\|Name\|Type\|Documentation
	835	\|ReferenceValue\|//ReferenceValueType//\|ReferenceValue contains a value for a target reference. When this is taken with its sibling elements, they identify the object or objects to which the reported metadata apply. The content of this will either be a reference to an identifiable object, a data key, a reference to a data set, or a report period. This element is unqualified so that the metadata structure definition specific schema can refine the type of the element such that value can be validated against the format defined in the metadata structure definition.
	836
	837	//ReferenceValueType//: ReferenceValueType is an abstract base type that forms the basis of a target reference value. A target reference value will either be a reference to an identifiable object, a data key, a reference to a data set, or a report period. The choice of these options will be refined to only one according to the definition of the target in the metadata structure definition.
	838
	839	Attributes:
	840
	841	id?
	842
	843	Content:
	844
	845	(ObjectReference \| DataKey \| DataSetReference \| ConstraintContentReference \| ReportPeriod)
	846
	847	Attribute Documentation:
	848
	849	\|Name\|Type\|Documentation
	850	\|id\|com:IDType\|The id attribute holds the identifier of the target reference object reference as defined in the metadata structure definition. This identifies the target reference of the metadata target that identifes one of the target references, that when taken together, identify the target of the reported metadata. This is optional and not expected to be supplied as the metadata structure definition specific schema will specify a fixed value such that the reference to the target object definition will always be available if required for processing.
	851
	852	Element Documentation:
	853
	854	\|Name\|Type\|Documentation
	855	\|ObjectReference\|//com:ReferenceType//\|ObjectReference provides a reference to an identifiable object in the SDMX information model. An identifiable object target will utilize this option as the representation of the target reference value. This element is unqualified so that the metadata structure definition specific schema can refine the type of the element such that the type of reference is valid according to the object type specified in the identifiable object target in the metadata structure definition. At the very least, the reference will be specific to the type of object being referenced so that a complete set of reference fields must be provided. In cases where an item object is restricted to be from a particular scheme, this type will be further restricted so that only a valid item reference can be supplied. The structure of this reference is such that it can be generically processed without needing to know what the intended target object type is prior to processing, as this information is part of the reference.
	856	\|DataKey\|com:DataKeyType\|ObjectReference provides a set of dimension references and values for those dimension for the purpose of reporting metadata against a set of data. A key descriptor values target will utilize this option as the representation of the target reference value. It is not expect that the metadata structure definition specific schema would refine this, but none the less, it is an unqualified element.
	857	\|DataSetReference\|com:SetReferenceType\|DataSetReference provides a reference to a data set for the purpose of reporting metadata against the data. A data set target will utilize this option as the representation of the target reference value.
	858	\|ConstraintContentRef erence\|com: AttachmentConstraint ReferenceType\|ConstraintContentReference provides a reference to an attachment constraint for the purpose of reporting metadata against the data identified in the key sets and/or cube regions identified by the constraint. A constraint target will utilize this option as the representation of the target reference value.
	859	\|ReportPeriod\|com: ObservationalTimePer iodType\|ReportPeriod provides a report period for the purpose of qualifying the target reporting period of reported metadata. A report period target will utilize this option as the representation of the target reference value. It is not expect that the metadata structure definition specific schema would refine this, but none the less, it is an unqualified element. This element is unqualified so that the metadata structure definition specific schema can refine the type of the element such that the specific type of time value prescribed in the metadata structure definition can be validated.
	860
	861	//ReportedAttributeType//: ReportedAttributeType is an abstract base type that forms the basis for a metadata structure specific metadata attribute. A value for the attribute can be supplied as either a single value, or multi-lingual text values (either structured or unstructured). An optional set of child metadata attributes is also available if the metadata attribute definition defines nested metadata attributes. The metadata structure definition specific schema will refine this type for each metadata attribute such that the content can be validation against what is defined in the metadata structure definition.
	862
	863	Derivation:
	864
	865	//com:AnnotableType// (extension)
	866	//ReportedAttributeType//
	867
	868	Attributes:
	869
	870	id?, value?, isMetadataAttribute?
	871
	872	Content:
	873
	874	com:Annotations?, (com:Text+ \| com:StructuredText+)?, AttributeSet?
	875
	876	Attribute Documentation:
	877
	878	\|Name\|Type\|Documentation
	879	\|id\|com:IDType\|The id attribute identifies the metadata attribute that the value is being reported for. This is optional and not expected to be supplied as the metadata structure definition specific schema will specify a fixed value such that the reference to the metadata attribute will always be available if required for processing.
	880	\|value\|xs:anySimpleType\|The value attribute holds any simple value for the metadata attribute. This attribute is un-typed such that the metadata structure definition specific schema can specify any simple type according the text format / local representation defined by the metadata structure definition.
	881	\|isMetadataAttribute (fixed: true)\|xs:boolean\|The isMetadataAttribute attribute is a fixed boolean (true) and is intended to designate to processing applications that a given element represents a reported attribute. This attribute is qualified (meaning that it will be qualified in an instance with the target namespace) to ensure that it can be properly identified by applications. The purpose of this is to allow applications to identify elements with unknown names as reported attributes so that they may process a metadata structure definition specific instance without knowledge of the underlying metadata structure definition.
	882
	883	Element Documentation:
	884
	885	\|Name\|Type\|Documentation
	886	\|com:Annotations\|com: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 my reference it.
	887	\|com:Text\|com:TextType\|Text is used to supply parallel multi-lingual textual values for the reported metadata attribute. This will be used if the text format of the metadata attribute has a type of string and the multi-lingual value is set to true.
	888	\|com:StructuredText\|com:XHTMLType\|StructuredText is used to supply parallel multi-lingual structured (as XHTML) textual values for the reported metadata attribute. This will be used if the text format of the metadata attribute has a type of XHTML and the multi-lingual value is set to true. If the multi-lingual flag is not set to true, it is expected that the maximum occurrence of this will be refined to be 1 in the metadata structure definition specific schema.
	889	\|AttributeSet\|xs:anyType\|AttributeSet contains the reported metadata attribute values for the child metadata attributes. This element is unqualified and un-typed so that it can refined by the metadata structure definition specific schema to validate that the reported metadata attributes conform to those prescribed by the metadata attribute definition. The content of this must be element only, and these elements must always represent a reported attribute. Since this can not be strictly enforced in XML Schema, additional steps have been added to make generic processing of this element simpler. When processing this element, any element found with the attribute isMetadataAttribute in this target namespace is assumed to be a reported metadata attribute and can be processed as such.
	890
	891	1. Mapping to Structure-Specific Schemas
	892	11. General
	893
	894	Data structure and metadata structure-specific schemas are each based on one single core construct found in their respective structure-specific namespaces;
	895
	896	Data - http:~/~/www.SDMX.org/resources/SDMXML/schemas/v2_1/data/structurespecific
	897
	898	Metadata - http:~/~/www.SDMX.org/resources/SDMXML/schemas/v2_1/data/structurespecific
	899
	900	For a metadata structure, only a single schema will be created for the entire structure definition. For data structures, many variations of the base schema are possible, each specific as to how the data is organised. This will be discussed in more details in the specific rules for the data structure schemas.
	901
	902	1.
	903	11.
	904	111. Basic Terminology
	905
	906	In the subsequent sections, the following namespace prefixes are used:
	907
	908	\|Namespace\|Prefix
	909	\|http:~/~/www.w3.org/2001/XMLSchema\|xs
	910	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common\|common
	911	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/ v2_1/data/structurespecific\|dsd
	912	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/ v2_1/metadata/structurespecific\|msd
	913
	914	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:
	915
	916	Schema: Refers to the format specific schema in general, and in particular the root xs:schema element of that schema file.
	917
	918	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).
	919
	920	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).
	921
	922	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.
	923
	924	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).
	925
	926	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).
	927
	928	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.
	929
	930	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.
	931
	932	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.
	933
	934	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)
	935
	936	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).
	937
	938	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).
	939
	940	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).
	941
	942	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).
	943
	944	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.
	945
	946	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).
	947
	948	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).
	949
	950	1.
	951	11. Namespace Rules
	952
	953	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.
	954
	955	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.
	956
	957	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".
	958
	959	1.
	960	11. General Rules
	961
	962	The following section details the general rules which apply to all structure specific schema creation.
	963
	964	1.
	965	11.
	966	111. Component Name Determination
	967
	968	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 is as follows:
	969
	970	1. If the component defines an identifier, the element or attribute name is the value of that identifier
	971	1. 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 identifer).
	972	11.
	973	111. Representation Determination
	974
	975	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).
	976
	977	The representation of a component is determined by the following precedence:
	978
	979	1. The local representation defined by the component
	980	1. The core representation defined in the concept from which the component takes its semantic
	981	1. A default representation of an un-faceted text format with a data type of String.
	982
	983	The representation will either define a text format, or an enumeration with an enumeration format.
	984
	985	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 an item scheme, for which an enumerated list of possible values can be created.
	986
	987	1.
	988	11.
	989	111. Simple / Primitive Type Determination
	990
	991	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>>path:#_Representation_Determination:]].
	992
	993	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.
	994
	995	1.
	996	11.
	997	111. Representation with Enumeration
	998
	999	A representation which defines an enumeration will result in a simple type that is a restriction of the common:IDType. The simple type will define enumerations for each item in the item scheme. 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:
	1000
	1001
	1002	<xs:simpleType name="ESTAT.CL_COUNTRY.1.0">
	1003
	1004	<xs:restriction base="common:IDType">
	1005
	1006	<xs:enumeration value="BE">
	1007
	1008	<xs:annotation>
	1009
	1010	<xs:documentation xml:lang="en">Belgium</xs:documentation>
	1011
	1012	</xs:annotation>
	1013
	1014	</xs:enumeration>
	1015
	1016
	1017	1.
	1018	11.
	1019	111. Representation with Text Format
	1020
	1021	A representation which defines a text format will result in a simple type or primitive type. The first step is to determine the base type from the text format data type:
	1022
	1023	\|SDMX Data Type\|XML Schema Data Type
	1024	\|String\|xs:string
	1025	\|AlphaNumeric\|common:AlphaNumericType
	1026	\|Alpha\|common:AlphaType
	1027	\|Numeric\|common:NumericType
	1028	\|BigInteger\|xs:integer
	1029	\|Integer\|xs:int
	1030	\|Long\|xs:long
	1031	\|Short\|xs:short
	1032	\|Decimal\|xs:decimal
	1033	\|Float\|xs:float
	1034	\|Double\|xs:double
	1035	\|Boolean\|xs:boolean
	1036	\|URI\|xs:anyURI
	1037	\|Count\|xs:integer
	1038	\|InclusiveValueRange\|xs:decimal
	1039	\|ExclusiveValueRange\|xs: decimal
	1040	\|Incremental\|xs: decimal
	1041	\|ObservationalTimePeriod\|common:ObservationalTimePeriodType
	1042	\|StandardTimePeriod\|common:StandardTimePeriodType
	1043	\|BasicTimePeriod\|common:BasicTimePeriodType
	1044	\|GregorianTimePeriod\|common:GregorianTimePeriodType
	1045	\|GregorianYear\|xs:gYear
	1046	\|GregorianYearMonth\|xs:gYearMonth
	1047	\|GregorianDay\|xs:date
	1048	\|ReportingTimePeriod\|common:ReportingTimePeriodType
	1049	\|ReportingYear\|common:ReportingYearType
	1050	\|ReportingSemester\|common:ReportingSemesterType
	1051	\|ReportingTrimester\|common:ReportingTrimesterType
	1052	\|ReportingQuarter\|common:ReportingQuarterType
	1053	\|ReportingMonth\|common:ReportingMonthType
	1054	\|ReportingWeek\|common:ReportingWeekType
	1055	\|ReportingDay\|common:ReportingDayType
	1056	\|DateTime\|xs:dateTime
	1057	\|TimeRange\|common:TimeRangeType
	1058	\|Month\|xs:gMonth
	1059	\|MonthDay\|xs:gMonthDay
	1060	\|Day\|xs:gDay
	1061	\|Time\|xs:time
	1062	\|Duration\|xs:duration
	1063	\|XHTML\|N/A[[~[1~]>>path:#_ftn1]]
	1064	\|KeyValues\|N/A^^1^^
	1065	\|IdentifiableReference\|N/A^^1^^
	1066	\|DataSetReference\|N/A^^1^^
	1067	\|AttachmentConstraintReference\|N/A^^1^^
	1068
	1069	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):
	1070
	1071	\|SDMX Facet\|XML Schema Facet
	1072	\|minLength\|xs:minLength
	1073	\|maxLength\|xs:maxLength
	1074	\|minValue[[~[2~]>>path:#_ftn2]]\|if ExclusiveValueRange: xs:minExclusives, else: xs:minInclusive
	1075	\|maxValue^^2^^\|if ExclusiveValueRange: xs:maxExclusives, else: xs:maxInclusive
	1076	\|decimals^^2^^\|xs:fractionDigits
	1077	\|pattern\|xs:pattern
	1078
	1079	Any other facets are informational only, and will not affect the determined type.
	1080
	1081	1.
	1082	11.
	1083	111. //Type Names//
	1084
	1085	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.
	1086
	1087	* 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]
	1088	* 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]
	1089	* If the type is based on a text format of a component local representation, and;
	1090	** 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]
	1091	** 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]
	1092	**1. Type Reuse
	1093
	1094	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.
	1095
	1096	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:
	1097
	1098	Does the component define a local type?
	1099
	1100	Yes: Is that type enumerated?
	1101
	1102	Yes: Type is the qualified type name for the item scheme
	1103
	1104	No: Generate simple type for text format
	1105
	1106	No: Type is the qualified name for the concept from which the component takes its semantic.
	1107
	1108	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.
	1109
	1110	1.
	1111	11. Data Structure Specific Schema
	1112
	1113	Separate schemas will be created for the data structure depending on which dimension occurs at the observation level, and whether explicit measures are used in the case that the observation dimension is the measure dimension. The recommended target namespace of the data structured specific schema is: [Data Structure URN]:ObsLevelDim:[Observation Dimensions](:explicit)?. Note that the explicit trailer is only used when the measure dimension is used at the observation level and the explicit measure concepts are to be used.
	1114
	1115	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, observation). Each section will state the rules for each variation of the structure specific format.
	1116
	1117	1.
	1118	11.
	1119	111. DataSetType
	1120
	1121	A complex type named DataSetType must be created. Its content model will be derived via restriction. If the dimension at the observation level is the time dimension (TIME_PERIOD) the base type of the restriction is dsd:TimeSeriesDataSetType. Otherwise, the base type of the restriction is dsd:DataSetType. The complex type content model will be as follows:
	1122
	1123	1. A sequence consisting of:
	1124	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1125	11. A local element named DataProvider with the type common:DataProviderReferenceType, a form of unqualified and a minimum occurrence of 0
	1126	11. If the data structure defines groups, a local element named Group with a form of unqualified, a minimum occurrence of 0, and a maximum occurrence of unbounded. The type of this element should be the type that is described in the GroupType section which follows.
	1127	11. A choice with a minimum occurrence of 0 consisting of:
	1128	111. If the dimension at the observation level is not AllDimensions, a local element named Series with a form of unqualified, a maximum occurrence of unbounded, and a type of SeriesType (as defined in the SeriesType section which follows)
	1129	111. If the dimension at the observation level is AllDimensions, a local element named Obs with a form of unqualified, a maximum occurrence of unbounded, and a type of ObsType (as defined in the ObsType section which follows)
	1130	1. If the reporting year start day attribute is not declared in the data structure definition or if it is declared but does not declare an attribute relationship of None, an attribute named REPORTING_YEAR_START_DAY with a type of xs:gMonthDay and a usage of prohibited
	1131	1. An attribute for each attribute defined in the data structured definition that declares an attribute relationship of None. The XML attribute [[name>>path:#_Component_Name_Determination]] and [[type>>path:#_Simple_/_Primitive]] are defined according to the general rules defined in the previous section, and the usage is optional
	1132	11.
	1133	111. GroupType
	1134
	1135	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:
	1136
	1137	1. A sequence consisting of:
	1138	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1139	1. An attribute for each dimension referenced by the group. The XML attribute [[name>>path:#_Component_Name_Determination]] and [[type>>path:#_Simple_/_Primitive]] are defined according to the general rules defined in the previous section, and the usage is required
	1140	1. If the reporting year start day attribute is not declared in the data structure definition or if it is declared but does not declare an attribute relationship with the group and does not specify the group as an attachment group, an attribute named REPORTING_YEAR_START_DAY with a type of xs:gMonthDay and a usage of prohibited
	1141	1. An attribute for each attribute 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>>path:#_Component_Name_Determination]] and [[type>>path:#_Simple_/_Primitive]] are defined according to the general rules defined in the previous section, and the usage is optional
	1142	1. An attribute named type with a type of common:IDType, usage of optional, and a fixed value of the identifier of the group
	1143
	1144	If the data structure definitions 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:
	1145
	1146	1. A sequence consisting of:
	1147	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1148	1. An attribute named type with a type of Group.ID, and a usage of optional
	1149	1. An anyAttribute declaration with a namespace of ~#~#local
	1150
	1151	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.
	1152
	1153	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:
	1154
	1155	1. A sequence consisting of:
	1156	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1157	1. An attribute for each dimension referenced by the group. The XML attribute [[name>>path:#_Component_Name_Determination]] and [[type>>path:#_Simple_/_Primitive]] are defined according to the general rules defined in the previous section, and the usage is required
	1158	1. If the reporting year start day attribute is not declared in the data structure definition or if it is declared but does not declare an attribute relationship with the group and does not specify the group as an attachment group, an attribute named REPORTING_YEAR_START_DAY with a type of xs:gMonthDay and a usage of prohibited
	1159	1. An attribute for each attribute 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>>path:#_Component_Name_Determination]] and [[type>>path:#_Simple_/_Primitive]] are defined according to the general rules defined in the previous section, and the usage is optional
	1160	1. An attribute named type with a type of Group.ID, usage of optional, and a fixed value of the identifier of the group
	1161	11.
	1162	111. SeriesType
	1163
	1164	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. If the dimension at the observation level is the time dimension (TIME_PERIOD) the base type of the restriction is dsd:TimeSeriesType. Otherwise, the base type of the restriction is dsd:SeriesType. The complex type content model will be as follows:
	1165
	1166	1. A sequence consisting of:
	1167	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1168	11. 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)
	1169	1. An attribute for each dimension defined by the data structure definition, except for the dimension at the observation level. The XML attribute [[name>>path:#_Component_Name_Determination]] and [[type>>path:#_Simple_/_Primitive]] are defined according to the general rules defined in the previous section, and the usage is required
	1170	1. If the reporting year start day attribute is not declared in the data structure definition or if it is declared and declares an attribute relationship of None, or with a group, or the dimension at the observation level, or specifies a group as an attachment group, an attribute named REPORTING_YEAR_START_DAY with a type of xs:gMonthDay and a usage of prohibited
	1171	1. An attribute for each attribute defined 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>>path:#_Component_Name_Determination]] and [[type>>path:#_Simple_/_Primitive]] are defined according to the general rules defined in the previous section, and the usage is optional
	1172	11.
	1173	111. ObsType
	1174
	1175	A complex type name ObsType must be created. Its content model will be derived via restriction. If the dimension at the observation level is the time dimension (TIME_PERIOD) the base type of the restriction is dsd:TimeSeriesObsType. Otherwise, the base type of the restriction is dsd:ObsType. If the explicit measure option is used, this complex type must be abstract. The complex type content model will be as follows:
	1176
	1177	1. A sequence consisting of:
	1178	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1179	1. If the dimension at the observation level is not the time dimension (TIME_PERIOD) an attribute named TIME_PERIOD with a type of common:TimePeriodType and a usage of prohibited
	1180	1. If the dimension at the observation level is not the time dimension (TIME_PERIOD) an attribute for the dimension at the observation level. The XML attribute [[name>>path:#_Component_Name_Determination]] and [[type>>path:#_Simple_/_Primitive]] are defined according to the general rules defined in the previous section, and the usage is required
	1181	1. An attribute for the primary measure (OBS_VALUE) defined by the data structure definition. The XML attribute [[name>>path:#_Component_Name_Determination]] and [[type>>path:#_Simple_/_Primitive]] is defined according to the general rules defined in the previous section, and the usage is optional
	1182	1. An attribute for each attribute defined in the data structure that declares an attribute relationship with the dimension at the observation level or the primary measure (OBS_VALUE). The XML attribute [[name>>path:#_Component_Name_Determination]] and [[type>>path:#_Simple_/_Primitive]] are defined according to the general rules defined in the previous section, and the usage is optional
	1183	1. An attribute named type. If the explicit measure option is not used, this attribute must have a type of common:IDType and a usage of prohibited. If the explicit measure option is used, this attribute must have a type of the simple type generated for the representation of the measure dimension that is the dimension at the observation level (this will be an simple type with enumerations with values of the concept identifiers which make up the concept scheme that is the representation of the measure dimension) a and a usage of optional
	1184
	1185	If the explicit measure option is used, then complex type must be created for every concept which make up the representation of the measure dimension which is the dimension at the observation level. The name of this complex type will be taken from the identifier of the concept. Its content model will be derived via restriction of the ObsType. The complex type content model will be as follows:
	1186
	1187	1. A sequence consisting of:
	1188	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1189	1. If the core representation of the Concept differs from that of the primary measure, an attribute for the primary measure (OBS_VALUE) defined by the data structure definition, except for the dimension at the observation level. The XML [[name>>path:#_Component_Name_Determination]] is defined according to the general rules defined in the previous section, and the usage is optional. The type of the attribute is the type that is generated for the core representation of the measure concept. Note that this representation type must have an explicit derivation from the type resulting from the primary measure. For example, if the primary measure type is xyz:CodeType, then the simple type which is defined for the core representation of the concept must restrict xyz:CodeType or one another type which restricts it
	1190	1. An attribute named type with a type of the simple type generated for the representation of the measure dimension that is the dimension at the observation level, a usage of optional, and a fixed value of the concept identifier.
	1191	11. Metadata Structure Specific Schema
	1192
	1193	One schema will be created for each metadata structure. This schema will define the contents of all report structures defined by the metadata structure. The recommended target namespace of the data structured specific schema is the URN of the metadata structure.
	1194
	1195	The rules for generating the data structure specific-schema are broken into sections based on the level within the structure (i.e. metadata set, metadata targets, reports, metadata attributes). These rules will recommend names for generated types, and will refer back to these names throughout the description. These names are simply recommendations that should produce a unique name, but there is no requirement to use them. When a name is required, it will be made clear this is the case.
	1196
	1197	1.
	1198	11.
	1199	111. MetadataSetType
	1200
	1201	A complex type that must be named MetadataSetType must be created. Its content model will be derived via restriction of the base type, msd:MetadataSetType. The complex type content model will be as follows:
	1202
	1203	1. A sequence consisting of:
	1204	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1205	11. An element reference to common:Name, with a minimum occurrence of 0 and a maximum occurrence of unbounded
	1206	11. A local element named DataProvider with the type common:DataProviderReferenceType, a form of unqualified and a minimum occurrence of 0
	1207	11. A local element named Report with a type ReportType, a form of unqualified, a minimum occurrence of 0, and a maximum occurrence of unbounded.
	1208	111. TargetType
	1209
	1210	An abstract complex type with a recommended name of TargetType must be created. Its content model will be derived via restriction of the msd:TargetType. The complex type content model will be as follows:
	1211
	1212	1. A sequence consisting of:
	1213	11. A local element named ReferenceValue with a type of msd:ReferenceValueType, a form of unqualified, and a maximum occurrence of unbounded
	1214	1. An attribute named id with a type of Target.ID, and a usage of optional
	1215
	1216	A simple type with a recommended name of Target.ID must be created. This should restrict the common:IDType. For each report structure defined by the metadata structure definition, an enumeration will be created within the restriction with a value of the report structure identifier.
	1217
	1218	A simple type with a recommended name of [metadata target identifier].TargetObject.ID must be created. This should restrict the Target.ID type. For each target object defined by the metadata target, an enumeration will be created within the restriction with a value of the target object identifier.
	1219
	1220	An abstract complex type with a recommended name of [metadata target identifier].ReferenceValueType will be created. Its content model will be derived via restriction of the msd:ReferenceValueType. The complex type content model will be as follows:
	1221
	1222	1. A choice consisting of:
	1223	11. A local element named ObjectReference with a type of common:ReferenceType, and a form of unqualified
	1224	11. A local element named DataKey with a type of common:DataKeyType, and a form of unqualified
	1225	11. A local element named DataSetReference with a type of common:SetReferenceType, and a form of unqualified
	1226	11. A local element named ReportPeriod with a type of common:ObservationalTimePeriodType, and a form of unqualified
	1227	1. An attribute named id with the type defined previously as [metadata target identifier].TargetObject.ID, and a usage of optional
	1228
	1229	For each metadata target defined in the metadata structure definition, a content group with a recommended name of [metadata target identifier] with be defined. Its content model will be as follows:
	1230
	1231	1. A sequence consisting of:
	1232	11. A local element named ReferenceValue with the type previously defined as [metadata target identifier].ReferenceValueType, a form of unqualified, and a minimum and maximum occurrence of the number of target objects defined within the metadata target
	1233
	1234	For each target object defined by the metadata target, a complex type that must be named [metadata target identifier].[target object identifier] must be created. Its content model will be derived via restriction of the type previously created as [metadata target identifier].ReferenceValueType type created prior to this. The complex type content model will be as follows:
	1235
	1236	1. A choice consisting of:
	1237	11. If the target object is an identifiable object target, a local element named ObjectReference with a type determined as defined in Identifiable Object Target Type Determination:
	1238	11. If the target object is an key descriptor values target, a local element named DataKey with a type of common:DataKeyType, and a form of unqualified
	1239	11. If the target object is a data set target, a local element named DataSetReference with a type of common:SetReferenceType, and a form of unqualified
	1240	11. If the target object is a constraint target, a local element named ConstraintReference with a type of common:AttachmentConstraintReferenceType, and a form of unqualified
	1241	11. If the target object is report period target, a local element named ReportPeriod with a form of unqualified, and a [[type>>path:#_Simple_/_Primitive]] as defined based on the data type of the local representation according to the general rules defined in the previous section
	1242	1. An attribute named id with a type previously created as [metadata target identifier].TargetObject.ID, a usage of optional, and fixed value of the target object identifier
	1243
	1244	The final complex type (which will be the determined type) is derived by restriction from the reference type determined above. The suggested name of this type is [metadata target identifier].[target object identifier].Reference. The content model of this type will be as follows:
	1245
	1246	1. A choice consisting of:
	1247	11. A sequence consisting of
	1248	111. A local element named Ref, with a form of unqualified and a the type defined above as is [metadata target].[target object].Ref
	1249	111. A local element named URN, with a form of unqualified, a minimum occurrence of 0, and the type defined above as [item scheme agency].[item scheme identifier].[item scheme version].URN
	1250	11. A local element named URN, with a form of unqualified, and the type defined above as [item scheme agency].[item scheme identifier].[item scheme version].URN
	1251	111.
	1252	1111. Identifiable Object Target Type Determination
	1253
	1254	An identifiable object target is meant to reference an SDMX identifiable object. In the metadata structure specific schema, the complex type which defines the reference is restricted according to the local representation and object type of the identifiable object target. If the identifiable object target does not provide an enumeration in its local representation, then the complex type for the target object is the specific reference type from the common namespace, based on the object type defined by the target object. For example, if the object type is DataProivder, the type will be common:DataProviderReferenceType. The general rule for the name of this type is common:[object type]ReferenceType.
	1255
	1256	If the target object defines an enumeration in its local representation, then the declared object type must be for the items contained the enumeration's referenced item scheme. If this is not true, the reference type as defined above is the type for the target object.
	1257
	1258	If the object type does correspond with the enumeration item scheme, then the type is complex type which restricts the reference to the allowable values. In order to construct this type, the following must be created:
	1259
	1260	A simple type which enumerates with URNs of the items contained in the items scheme referenced from the enumeration. The recommended name is [item scheme agency].[item scheme identifier].[item scheme version].URN. This simple type should restrict the xs:anyURI type an contain enumerations with values of the URN of every item defined by the scheme.
	1261
	1262	A second simple type which enumerates the IDs of the items contained in the items scheme referenced from the enumeration. The recommended name is [item scheme agency].[item scheme identifier].[item scheme version].ID. This simple type should restrict the either the common:NestedIDType for hierarchical items or the common:IDType for flat items. The restriction should contain enumerations with values of the ID of every item defined by the scheme. For hierarchical items (such as categories), the id should be nested to reflect the full path (e.g. A.C.D.F).
	1263
	1264	A complex type which restricts the full set of reference fields for the item to be reference must be created. The recommended name is [metadata target].[target object].Ref. This type is derived via restriction of the type which defines the full set of reference fields for the item referenced by the target object. For example, if the object type is Category, the type that is the base of the restriction is common:CategoryRefType. . The general rule for the name of this type is common:[object type]RefType. The content model of this type must be as follows:
	1265
	1266	1. An attribute named agencyID with a type of common:NestNCNameIDType, a use of required, and a fixed value of the item scheme referenced from the enumeration
	1267	1. An attribute named maintinableParentID with a type of common:IDType, a use of required, and a fixed value of the identifier of the item scheme referenced from the enumeration
	1268	1. An attribute named maintainableParentVersion with a type of common:VersionType, a use of optional, and a fixed value of the version of the item scheme referenced from the enumeration
	1269	1. An attribute named id, with a use of option, and the type defined above as [item scheme agency].[item scheme identifier].[item scheme version].ID.
	1270	11.
	1271	111. ReportType
	1272
	1273	A simple type with a recommend name of Report.ID must be created. This must restrict the common:IDType. For each report structure defined by the metadata structure definition, an enumeration will be created within the restriction with a value of the report structure identifier.
	1274
	1275	An abstract complex type with a recommended name of ReportType must be created. Its content model will be derived via restriction of the msd:ReportType. The complex type content model will be as follows:
	1276
	1277	1. A sequence consisting of:
	1278	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1279	11. A local element named Target with the type previously defined as TargetType and a form of unqualified
	1280	11. A local element named AttributeSet with no type assigned and a form of unqualified
	1281	1. An attribute named id with a type previously defined as Report.ID, and a usage of optional
	1282
	1283	For each report structure defined in the metadata structure definition, a complex type with its name taken from the report structure identifier must be defined. In order to construct this type, some other complex type must be defined first.
	1284
	1285	A simple type with a recommended name of [report structure identifier].Target.ID must be created. This must restrict the type previously created as Target.ID. For each metadata target referenced by the report structure, an enumeration will be created within the restriction with a value of the metadata target identifier.
	1286
	1287	An abstract complex type must be create, with a recommended name of [report structure identifier].TargetType. Its content model will be derived by restriction of the type previously created as TargetType. The content model of this type must be as follows:
	1288
	1289	1. A sequence consisting of:
	1290	11. A local element named ReferenceValue with a type of msd:ReferenceValueType, a form of unqualified, and a maximum occurrence of unbounded
	1291	1. An attribute named id with the type previously created as [report structure identifier].Target.ID, and a use of optional
	1292
	1293	For each metadata target referenced from the report structure, a complex type that must be named [report structure identifier].[metadata target identifier] must be created. This type must derived its content by restriction of the type previously defined as [report structure identifier].TargetType. The content model is as follows:
	1294
	1295	1. A reference to the content group that was previously created as [metadata target identifier] for this metadata target
	1296	1. An attribute named id with the type create previously as [report structure identifier].Target.ID, a use of optional, and a fixed value of [metadata target identifier]
	1297
	1298	For every metadata attribute defined by the report structure a complex type must be created with the recommended name of [report structure identifier].[nested metadata attribute identifier]. Note that the recommend name assumes the metadata attribute identifier is the nested identifier for the full hierarchy in which the metadata attribute was defined. This content model of this type is derived from restriction of the msd:ReportedAttributeType. The content of this must consists be as follows:
	1299
	1300	1. A sequence consisting of:
	1301	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1302	11. If the isPresentational flag is not set to true:
	1303	111. If the [[determined representation>>path:#_Representation_Determination:]] has data type of XHTML, an element reference to common:StructuredText with a maximum occurrence of unbounded
	1304	111. If the [[determined representation>>path:#_Representation_Determination:]] has is not XHTML, but has a facet of isMultiLinguale, an element reference to common: Text with a maximum occurrence of unbounded
	1305	11. If the metadata attribute defines which child metadata attributes, a local element named AttributeSet with a form of unqualified, and a type as defined according to the rules defined in Attribute Set Complex Type Creation
	1306	1. An attribute named id with a type of common:IDType, a use of optional, and a fixed value of [metadata attribute identifier], where this identifier is not nested
	1307	1. If the isPresentational flag is not set to true, and the [[determined representation>>path:#_Representation_Determination:]] is not XHTML and does not have a facet of isMultiLingual, an attribute named value where the [[type>>path:#_Simple_/_Primitive]] is defined according to the general rules defined in the previous section, and the use is required
	1308
	1309	For each report structure defined in the metadata structure, a complex type that must be named [report structure identifier] must be created. Its content model will be derived via restriction of the previously defined ReportType. The complex type content model will be as follows:
	1310
	1311	1. A sequence consisting of:
	1312	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1313	11. A local element named Target with the type previously defined as [report structure identifier].TargetType, and a form of unqualified. This element must define a uniqueness constraint with a recommended name of [report structure identifier].Target.ReferenceValue.Unique. This uniqueness constraint must contain:
	1314	111. A selector with an xpath of "*"
	1315	111. A field with an xpath of "@id"
	1316
	1317	1.
	1318	11. A local element named AttributeSet with a form of unqualified and a type as defined according to the rules defined in Attribute Set Complex Type Creation
	1319	1. An attribute named id with the type previously defined as Report.ID, a use of optional, and a fixed value of [report structure identifier]
	1320	11.
	1321	111.
	1322	1111. Attribute Set Complex Type Creation
	1323
	1324	An attribute set is created for a report structure or a metadata attribute which contains child metadata attributes. This type is a complex type with a recommend name of [report structure identifier].[nested metadata attribute identifier].AttributeSet, where the metadata attribute section only applies to attribute sets created for metadata attributes and is assumed to consist of the full hierarchy of the metadata attribute's definition. This complex type must consists of:
	1325
	1326	1. A sequence consisting of:
	1327	11. A local element for each metadata attribute defined as a direct child of the object for which the attribute set is being created. The recommended name of this element is [metadata attribute identifier] and it has a form of unqualified. If the metadata attribute defines a minOccurs and maxOccurs, these values are translated to this element. The type of this element is the type previously created as [report structure identifier].[nested metadata attribute identifier].
	1328
	1329	1. Special data functions
	1330	11. Updates
	1331
	1332	Both the generic and the structure-specific data messages allow for incremental updating of data. This purpose is noted in the action for the data set, which is either inherited from the header of the data message or explicitly stated at the data set level.
	1333
	1334
	1335	A dataset with an action of Append is assumed to be an incremental update. This means that one the information provided explicitly in the message should be altered. Any data attribute or observation value that is to be changed must be provided. However, the absence of an observation value or a data attribute at any level does not imply deletion; instead it is simply implied that the value is to remain unchanged. Therefore, it is valid and acceptable to send a data message with an action of Append which contains only a Series elements with attribute values. In this case, the values for the attributes will be updated. Note that it is not permissible to update data attributes using partial keys (outside of those associated with defined groups). In order to update an attribute, a full key must always be provided even if the message format does not require this.
	1336
	1337	1.
	1338	11. Deletes
	1339
	1340	Both the generic and the structure-specific data messages allow for incremental deletion of data. This purpose is noted in the action for the data set, which is either inherited from the header of the data message or explicitly stated at the data set level.
	1341
	1342
	1343	A dataset with an action of Delete is assumed to be an incremental deletion. The deletion is assumed to take place of the lowest level of detail provided in the message. For example, if a delete message is sent with only a data set element, the entire data set will be deleted. On the other hand, if that data set contains a data attribute, only that data attribute value will be deleted. This same dynamic continues through the data set hierarchy. A data set containing only a series with no data attributes or observations will result in that entire series (all observations and data attributes) being deleted. If the series contains data attributes, only the supplied data attributes for that series will be deleted. Finally, if a series contains observations, then only the specified observations will be deleted. If an entire observation is to be deleted (value and data attributes), only the observation dimension should be provided. If only the observation value or particular data attributes are to be deleted, then these should be specified for the observation. Note that a group can only be used to delete the data attributes associated with it. Although the format might not require it, a full key must be provided to delete a series or observation. It is not permissible to wild card a key in order to delete more than one series or observation. Finally, to delete a data attribute or observation value it is recommended that the value to be deleted be supplied; however, it is only required that any valid value be provided.
	1344
	1345
	1346	----
	1347
	1348	[[~[1~]>>path:#_ftnref1]] These types are only used in complex types and will be discussed within their appropriate context.
	1349
	1350	[[~[2~]>>path:#_ftnref2]] Note that these options only apply to numeric representations and should be ignored if the data type is non-numeric