Wiki source code of Part IV. Data

Version 4.5 by Helena on 2025/06/24 14:51

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:
4.4	209	* //com:AnnotableType// (extension)
	210	** DataSetType (restriction)
	211	*** TimeSeriesDataSetType
4.2	212
	213	Attributes:
	214	structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?
	215
	216	Content:
	217	com:Annotations?, DataProvider?, Attributes?, Group, Series
	218
	219	Attribute Documentation:
	220	\|Name\|Type\|Documentation
	221	\|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).
	222	\|setID\|com:IDType\|The setID provides an identification of the data or metadata set.
	223	\|action\|com:ActionType\|The action attribute indicates whether the file is appending, replacing, or deleting.
	224	\|reportingBeginDate\|com: BasicTimePeriodType\|The reportingBeginDate indicates the inclusive start time of the data reported in the data or metadata set.
	225	\|reportingEndDate\|com: BasicTimePeriodType\|The reportingEndDate indicates the inclusive end time of the data reported in the data or metadata set.
	226	\|validFromDate\|xs:dateTime\|The validFromDate indicates the inclusive start time indicating the validity of the information in the data or metadata set.
	227	\|validToDate\|xs:dateTime\|The validToDate indicates the inclusive end time indicating the validity of the information in the data or metadata set.
	228	\|publicationYear\|xs:gYear\|The publicationYear holds the ISO 8601 four-digit year.
	229	\|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).
	230
	231	Element Documentation:
	232
	233	\|Name\|Type\|Documentation
	234	\|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.
	235	\|DataProvider\|com: DataProviderReferenc eType\|DataProvider contains a reference to the provider for the data set.
	236	\|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.
	237	\|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.
	238	\|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.
	239
	240	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.
	241
	242	Derivation:
4.4	243	* //com:AnnotableType// (extension)
	244	** SeriesType (restriction)
	245	*** TimeSeriesType
4.2	246
	247	Content:
	248	com:Annotations?, SeriesKey, Attributes?, Obs*
	249
	250	Element Documentation:
	251	\|Name\|Type\|Documentation
	252	\|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.
	253	\|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.
	254	\|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.
	255	\|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.
	256
	257	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.
	258
	259	Derivation:
4.4	260	* //com:AnnotableType// (extension)
	261	** ObsType (restriction)
	262	*** TimeSeriesObsType
4.2	263
	264	Content:
	265	com:Annotations?, ObsDimension, ObsValue?, Attributes?
	266
	267	Element Documentation:
	268	\|Name\|Type\|Documentation
	269	\|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.
	270	\|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.
	271	\|ObsValue\|ObsValueType\|ObsValue type contains the value for the observation.
	272	\|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).
	273
	274	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.
	275
	276	Derivation:
4.4	277	* BaseValueType (restriction)
	278	** TimeValueType
4.2	279
	280	Attributes:
	281	id?, value
	282
	283	Content:
	284	{Empty}
	285
	286	Attribute Documentation:
	287	\|Name\|Type\|Documentation
	288	\|id (fixed: TIME_PERIOD)\|com:NCNameIDType\|The id attribute contains the identifier for the component for which a value is being provided.
	289	\|value\|com: ObservationalTimePer iodType\|The value attribute contains the provided component value.
	290
4.4	291	== 2.2 Structure Specific Data Namespace ==
4.2	292
	293	http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/structurespecific
	294
4.4	295	=== Summary ===
4.2	296
	297	Referenced Namespaces:
	298	\|Namespace\|Prefix
	299	\| \|
	300	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common\|com
	301	\|http:~/~/www.w3.org/2001/XMLSchema\|xs
	302
	303	Contents:
	304	7 Complex Types
	305	1 Simple Type
	306
4.4	307	=== Complex Types ===
4.2	308
	309	//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.
	310
	311	Derivation:
4.4	312	* //com:AnnotableType// (extension)
	313	** //DataSetType//
4.2	314
	315	Attributes:
	316	structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?, dataScope, REPORTING_YEAR_START_DAY?
	317
	318	Content:
	319	com:Annotations?, DataProvider?, Group*, (Series+ \| Obs+)?
	320
	321	Attribute Documentation:
	322	\|Name\|Type\|Documentation
	323	\|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).
	324	\|setID\|com:IDType\|The setID provides an identification of the data or metadata set.
	325	\|action\|com:ActionType\|The action attribute indicates whether the file is appending, replacing, or deleting.
	326	\|reportingBeginDate\|com: BasicTimePeriodType\|The reportingBeginDate indicates the inclusive start time of the data reported in the data or metadata set.
	327	\|reportingEndDate\|com: BasicTimePeriodType\|The reportingEndDate indicates the inclusive end time of the data reported in the data or metadata set.
	328	\|validFromDate\|xs:dateTime\|The validFromDate indicates the inclusive start time indicating the validity of the information in the data or metadata set.
	329	\|validToDate\|xs:dateTime\|The validToDate indicates the inclusive end time indicating the validity of the information in the data or metadata set.
	330	\|publicationYear\|xs:gYear\|The publicationYear holds the ISO 8601 four-digit year.
	331	\|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).
	332	\|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.
	333	\|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.
	334
	335	Element Documentation:
	336
	337	\|Name\|Type\|Documentation
	338	\|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.
	339	\|DataProvider\|com: DataProviderReferenc eType\|DataProvider contains a reference to the provider for the data set.
	340	\|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.
	341	\|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.
	342	\|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).
	343
	344	//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.
	345
	346	Derivation:
4.4	347	* //com:AnnotableType// (extension)
	348	** //GroupType//
4.2	349
	350	Attributes:
	351	type?, REPORTING_YEAR_START_DAY?
	352
	353	Content:
	354	com:Annotations?
	355
	356	Attribute Documentation:
	357	\|Name\|Type\|Documentation
	358	\|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.
	359	\|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.
	360
	361	Element Documentation:
	362
	363	\|Name\|Type\|Documentation
	364	\|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.
	365
	366	//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.
	367
	368	Derivation:
4.4	369	* //com:AnnotableType// (extension)
	370	** //SeriesType//
4.2	371
	372	Attributes:
	373	TIME_PERIOD?, REPORTING_YEAR_START_DAY?
	374
	375	Content:
	376	com:Annotations?, Obs*
	377
	378	Attribute Documentation:
	379	\|Name\|Type\|Documentation
	380	\|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.
	381	\|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.
	382
	383	Element Documentation:
	384
	385	\|Name\|Type\|Documentation
	386	\|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.
	387	\|Obs\|//ObsType//\|
	388
	389	//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.
	390
	391	Derivation:
4.5	392	* //com:AnnotableType// (extension)
	393	** //ObsType//
4.2	394
	395	Attributes:
	396	type?, TIME_PERIOD?, REPORTING_YEAR_START_DAY?, OBS_VALUE?
	397
	398	Content:
	399	com:Annotations?
	400
	401	Attribute Documentation:
	402	\|Name\|Type\|Documentation
	403	\|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.
	404	\|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.
	405	\|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.
	406	\|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.
	407
	408	Element Documentation:
	409
	410	\|Name\|Type\|Documentation
	411	\|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.
	412
	413	//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.
	414
	415	Derivation:
4.5	416	* //com:AnnotableType// (extension)
	417	** //DataSetType// (restriction)
	418	*** //TimeSeriesDataSetType//
4.2	419
	420	Attributes:
	421	structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?, dataScope, REPORTING_YEAR_START_DAY?
	422
	423	Content:
	424	com:Annotations?, DataProvider?, Group, Series
	425
	426	Attribute Documentation:
	427	\|Name\|Type\|Documentation
	428	\|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).
	429	\|setID\|com:IDType\|The setID provides an identification of the data or metadata set.
	430	\|action\|com:ActionType\|The action attribute indicates whether the file is appending, replacing, or deleting.
	431	\|reportingBeginDate\|com: BasicTimePeriodType\|The reportingBeginDate indicates the inclusive start time of the data reported in the data or metadata set.
	432	\|reportingEndDate\|com: BasicTimePeriodType\|The reportingEndDate indicates the inclusive end time of the data reported in the data or metadata set.
	433	\|validFromDate\|xs:dateTime\|The validFromDate indicates the inclusive start time indicating the validity of the information in the data or metadata set.
	434	\|validToDate\|xs:dateTime\|The validToDate indicates the inclusive end time indicating the validity of the information in the data or metadata set.
	435	\|publicationYear\|xs:gYear\|The publicationYear holds the ISO 8601 four-digit year.
	436	\|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).
	437	\|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.
	438	\|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.
	439
	440	Element Documentation:
	441
	442	\|Name\|Type\|Documentation
	443	\|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.
	444	\|DataProvider\|com: DataProviderReferenc eType\|DataProvider contains a reference to the provider for the data set.
	445	\|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.
	446	\|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.
	447
	448	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.
	449
	450	Derivation:
4.5	451	* //com:AnnotableType// (extension)
	452	** //SeriesType// (restriction)
	453	*** TimeSeriesType
4.2	454
	455	Attributes:
	456	REPORTING_YEAR_START_DAY?
	457
	458	Content:
	459	com:Annotations?, Obs*
	460
	461	Attribute Documentation:
	462	\|Name\|Type\|Documentation
	463	\|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.
	464
	465	Element Documentation:
	466
	467	\|Name\|Type\|Documentation
	468	\|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.
	469	\|Obs\|//TimeSeriesObsType//\|
	470
	471	//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.
	472
	473	Derivation:
	474
	475	//com:AnnotableType// (extension)
	476	//ObsType// (restriction)
	477	//TimeSeriesObsType//
	478
	479	Attributes:
	480
	481	TIME_PERIOD, REPORTING_YEAR_START_DAY?, OBS_VALUE?
	482
	483	Content:
	484
	485	com:Annotations?
	486
	487	Attribute Documentation:
	488
	489	\|Name\|Type\|Documentation
	490	\|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.
	491	\|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.
	492	\|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.
	493
	494	Element Documentation:
	495
	496	\|Name\|Type\|Documentation
	497	\|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.
	498
	499	1.
	500	11.
	501	111. Simple Types
	502
	503	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.
	504
	505	Derived by restriction of xs:string .
	506
	507	Enumerations:
	508
	509	\|Value\|Documentation
	510	\|DataStructure\|The data set conforms simply to the data structure definition as it is defined, without regard to any constraints.
	511	\|ConstrainedDataStructure\|The data set conforms to the known allowable content constraints applied to the data structure definition.
	512	\|Dataflow\|The data set conforms to the known allowable content constraints applied to the dataflow.
	513	\|ProvisionAgreement\|The data set conforms to the known allowable content constraints applied to the provision agreement.
	514
	515	1.
	516	11. Generic Metadata Namespace
	517
	518	http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/generic
	519
	520	1.
	521	11.
	522	111. Summary
	523
	524	Referenced Namespaces:
	525
	526	\|Namespace\|Prefix
	527	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common\|com
	528	\|http:~/~/www.w3.org/2001/XMLSchema\|xs
	529
	530	Contents:
	531
	532	6 Complex Types
	533
	534	1.
	535	11.
	536	111. Complex Types
	537
	538	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.
	539
	540	Derivation:
	541
	542	//com:AnnotableType// (extension)
	543	MetadataSetType
	544
	545	Attributes:
	546
	547	structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?
	548
	549	Content:
	550
	551	com:Annotations?, com:Name*, DataProvider?, Report+
	552
	553	Attribute Documentation:
	554
	555	\|Name\|Type\|Documentation
	556	\|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).
	557	\|setID\|com:IDType\|The setID provides an identification of the data or metadata set.
	558	\|action\|com:ActionType\|The action attribute indicates whether the file is appending, replacing, or deleting.
	559	\|reportingBeginDate\|com: BasicTimePeriodType\|The reportingBeginDate indicates the inclusive start time of the data reported in the data or metadata set.
	560	\|reportingEndDate\|com: BasicTimePeriodType\|The reportingEndDate indicates the inclusive end time of the data reported in the data or metadata set.
	561	\|validFromDate\|xs:dateTime\|The validFromDate indicates the inclusive start time indicating the validity of the information in the data or metadata set.
	562	\|validToDate\|xs:dateTime\|The validToDate indicates the inclusive end time indicating the validity of the information in the data or metadata set.
	563	\|publicationYear\|xs:gYear\|The publicationYear holds the ISO 8601 four-digit year.
	564	\|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).
	565
	566	Element Documentation:
	567
	568	\|Name\|Type\|Documentation
	569	\|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.
	570	\|com:Name\|com:TextType\|Name is a reusable element, used for providing a human-readable name for an object.
	571	\|DataProvider\|com: DataProviderReferenc eType\|DataProviderReference provides a references to an organisation with the role of data provider that is providing this metadata set.
	572	\|Report\|ReportType\|Report contains the details of a the reported metadata, including the identification of the target and the report attributes.
	573
	574	ReportType: ReportType contains a set of report attributes and identifies a target objects] to which they apply.
	575
	576	Derivation:
	577
	578	//com:AnnotableType// (extension)
	579	ReportType
	580
	581	Attributes:
	582
	583	id
	584
	585	Content:
	586
	587	com:Annotations?, Target, AttributeSet
	588
	589	Attribute Documentation:
	590
	591	\|Name\|Type\|Documentation
	592	\|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.
	593
	594	Element Documentation:
	595
	596	\|Name\|Type\|Documentation
	597	\|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.
	598	\|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.
	599	\|AttributeSet\|AttributeSetType\|AttributeSet contains the reported metadata attribute values for the reported metadata.
	600
	601	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.
	602
	603	Attributes:
	604
	605	id
	606
	607	Content:
	608
	609	ReferenceValue+
	610
	611	Attribute Documentation:
	612
	613	\|Name\|Type\|Documentation
	614	\|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.
	615
	616	Element Documentation:
	617
	618	\|Name\|Type\|Documentation
	619	\|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.
	620
	621	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.
	622
	623	Attributes:
	624
	625	id
	626
	627	Content:
	628
	629	(ObjectReference \| DataKey \| DataSetReference \| ConstraintContentReference \| ReportPeriod)
	630
	631	Attribute Documentation:
	632
	633	\|Name\|Type\|Documentation
	634	\|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.
	635
	636	Element Documentation:
	637
	638	\|Name\|Type\|Documentation
	639	\|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.
	640	\|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.
	641	\|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.
	642	\|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.
	643	\|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.
	644
	645	AttributeSetType: AttributeSetType defines the structure for a collection of reported metadata attributes.
	646
	647	Content:
	648
	649	ReportedAttribute+
	650
	651	Element Documentation:
	652
	653	\|Name\|Type\|Documentation
	654	\|ReportedAttribute\|ReportedAttributeTyp e\|ReportedAttribute provides the details of a reported attribute, including a value and/or child reported attributes.
	655
	656	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.
	657
	658	Derivation:
	659
	660	//com:AnnotableType// (extension)
	661	ReportedAttributeType
	662
	663	Attributes:
	664
	665	id, value?
	666
	667	Content:
	668
	669	com:Annotations?, (com:Text+ \| com:StructuredText+)?, AttributeSet?
	670
	671	Attribute Documentation:
	672
	673	\|Name\|Type\|Documentation
	674	\|id\|com:IDType\|The id attribute identifies the metadata attribute that the value is being reported for.
	675	\|value\|xs:string\|The value attribute holds any simple value for the metadata attribute.
	676
	677	Element Documentation:
	678
	679	\|Name\|Type\|Documentation
	680	\|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.
	681	\|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.
	682	\|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.
	683	\|AttributeSet\|AttributeSetType\|AttributeSet contains the reported metadata attribute values for the child metadata attributes.
	684
	685	1.
	686	11. Structure Specific Metadata Namespace
	687
	688	http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/structurespecific
	689
	690	1.
	691	11.
	692	111. Summary
	693
	694	Referenced Namespaces:
	695
	696	\|Namespace\|Prefix
	697	\| \|
	698	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common\|com
	699	\|http:~/~/www.w3.org/2001/XMLSchema\|xs
	700
	701	Contents:
	702
	703	5 Complex Types
	704
	705	1.
	706	11.
	707	111. Complex Types
	708
	709	//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.
	710
	711	Derivation:
	712
	713	//com:AnnotableType// (extension)
	714	//MetadataSetType//
	715
	716	Attributes:
	717
	718	structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod?
	719
	720	Content:
	721
	722	com:Annotations?, com:Name*, DataProvider?, Report+
	723
	724	Attribute Documentation:
	725
	726	\|Name\|Type\|Documentation
	727	\|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).
	728	\|setID\|com:IDType\|The setID provides an identification of the data or metadata set.
	729	\|action\|com:ActionType\|The action attribute indicates whether the file is appending, replacing, or deleting.
	730	\|reportingBeginDate\|com: BasicTimePeriodType\|The reportingBeginDate indicates the inclusive start time of the data reported in the data or metadata set.
	731	\|reportingEndDate\|com: BasicTimePeriodType\|The reportingEndDate indicates the inclusive end time of the data reported in the data or metadata set.
	732	\|validFromDate\|xs:dateTime\|The validFromDate indicates the inclusive start time indicating the validity of the information in the data or metadata set.
	733	\|validToDate\|xs:dateTime\|The validToDate indicates the inclusive end time indicating the validity of the information in the data or metadata set.
	734	\|publicationYear\|xs:gYear\|The publicationYear holds the ISO 8601 four-digit year.
	735	\|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).
	736
	737	Element Documentation:
	738
	739	\|Name\|Type\|Documentation
	740	\|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.
	741	\|com:Name\|com:TextType\|Name is a reusable element, used for providing a human-readable name for an object.
	742	\|DataProvider\|com: DataProviderReferenc eType\|>DataProviderReference provides a references to an organisation with the role of data provider that is providing this metadata set.
	743	\|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.
	744
	745	//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.
	746
	747	Derivation:
	748
	749	//com:AnnotableType// (extension)
	750	//ReportType//
	751
	752	Attributes:
	753
	754	id?
	755
	756	Content:
	757
	758	com:Annotations?, Target, AttributeSet
	759
	760	Attribute Documentation:
	761
	762	\|Name\|Type\|Documentation
	763	\|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.
	764
	765	Element Documentation:
	766
	767	\|Name\|Type\|Documentation
	768	\|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.
	769	\|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.
	770	\|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.
	771
	772	//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.
	773
	774	Attributes:
	775
	776	id?
	777
	778	Content:
	779
	780	ReferenceValue+
	781
	782	Attribute Documentation:
	783
	784	\|Name\|Type\|Documentation
	785	\|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.
	786
	787	Element Documentation:
	788
	789	\|Name\|Type\|Documentation
	790	\|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.
	791
	792	//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.
	793
	794	Attributes:
	795
	796	id?
	797
	798	Content:
	799
	800	(ObjectReference \| DataKey \| DataSetReference \| ConstraintContentReference \| ReportPeriod)
	801
	802	Attribute Documentation:
	803
	804	\|Name\|Type\|Documentation
	805	\|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.
	806
	807	Element Documentation:
	808
	809	\|Name\|Type\|Documentation
	810	\|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.
	811	\|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.
	812	\|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.
	813	\|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.
	814	\|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.
	815
	816	//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.
	817
	818	Derivation:
	819
	820	//com:AnnotableType// (extension)
	821	//ReportedAttributeType//
	822
	823	Attributes:
	824
	825	id?, value?, isMetadataAttribute?
	826
	827	Content:
	828
	829	com:Annotations?, (com:Text+ \| com:StructuredText+)?, AttributeSet?
	830
	831	Attribute Documentation:
	832
	833	\|Name\|Type\|Documentation
	834	\|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.
	835	\|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.
	836	\|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.
	837
	838	Element Documentation:
	839
	840	\|Name\|Type\|Documentation
	841	\|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.
	842	\|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.
	843	\|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.
	844	\|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.
	845
	846	1. Mapping to Structure-Specific Schemas
	847	11. General
	848
	849	Data structure and metadata structure-specific schemas are each based on one single core construct found in their respective structure-specific namespaces;
	850
	851	Data - http:~/~/www.SDMX.org/resources/SDMXML/schemas/v2_1/data/structurespecific
	852
	853	Metadata - http:~/~/www.SDMX.org/resources/SDMXML/schemas/v2_1/data/structurespecific
	854
	855	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.
	856
	857	1.
	858	11.
	859	111. Basic Terminology
	860
	861	In the subsequent sections, the following namespace prefixes are used:
	862
	863	\|Namespace\|Prefix
	864	\|http:~/~/www.w3.org/2001/XMLSchema\|xs
	865	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common\|common
	866	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/ v2_1/data/structurespecific\|dsd
	867	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/ v2_1/metadata/structurespecific\|msd
	868
	869	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:
	870
	871	Schema: Refers to the format specific schema in general, and in particular the root xs:schema element of that schema file.
	872
	873	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).
	874
	875	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).
	876
	877	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.
	878
	879	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).
	880
	881	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).
	882
	883	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.
	884
	885	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.
	886
	887	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.
	888
	889	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)
	890
	891	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).
	892
	893	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).
	894
	895	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).
	896
	897	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).
	898
	899	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.
	900
	901	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).
	902
	903	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).
	904
	905	1.
	906	11. Namespace Rules
	907
	908	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.
	909
	910	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.
	911
	912	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".
	913
	914	1.
	915	11. General Rules
	916
	917	The following section details the general rules which apply to all structure specific schema creation.
	918
	919	1.
	920	11.
	921	111. Component Name Determination
	922
	923	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:
	924
	925	1. If the component defines an identifier, the element or attribute name is the value of that identifier
	926	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).
	927	11.
	928	111. Representation Determination
	929
	930	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).
	931
	932	The representation of a component is determined by the following precedence:
	933
	934	1. The local representation defined by the component
	935	1. The core representation defined in the concept from which the component takes its semantic
	936	1. A default representation of an un-faceted text format with a data type of String.
	937
	938	The representation will either define a text format, or an enumeration with an enumeration format.
	939
	940	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.
	941
	942	1.
	943	11.
	944	111. Simple / Primitive Type Determination
	945
	946	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:]].
	947
	948	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.
	949
	950	1.
	951	11.
	952	111. Representation with Enumeration
	953
	954	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:
	955
	956
	957	<xs:simpleType name="ESTAT.CL_COUNTRY.1.0">
	958
	959	<xs:restriction base="common:IDType">
	960
	961	<xs:enumeration value="BE">
	962
	963	<xs:annotation>
	964
	965	<xs:documentation xml:lang="en">Belgium</xs:documentation>
	966
	967	</xs:annotation>
	968
	969	</xs:enumeration>
	970
	971
	972	1.
	973	11.
	974	111. Representation with Text Format
	975
	976	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:
	977
	978	\|SDMX Data Type\|XML Schema Data Type
	979	\|String\|xs:string
	980	\|AlphaNumeric\|common:AlphaNumericType
	981	\|Alpha\|common:AlphaType
	982	\|Numeric\|common:NumericType
	983	\|BigInteger\|xs:integer
	984	\|Integer\|xs:int
	985	\|Long\|xs:long
	986	\|Short\|xs:short
	987	\|Decimal\|xs:decimal
	988	\|Float\|xs:float
	989	\|Double\|xs:double
	990	\|Boolean\|xs:boolean
	991	\|URI\|xs:anyURI
	992	\|Count\|xs:integer
	993	\|InclusiveValueRange\|xs:decimal
	994	\|ExclusiveValueRange\|xs: decimal
	995	\|Incremental\|xs: decimal
	996	\|ObservationalTimePeriod\|common:ObservationalTimePeriodType
	997	\|StandardTimePeriod\|common:StandardTimePeriodType
	998	\|BasicTimePeriod\|common:BasicTimePeriodType
	999	\|GregorianTimePeriod\|common:GregorianTimePeriodType
	1000	\|GregorianYear\|xs:gYear
	1001	\|GregorianYearMonth\|xs:gYearMonth
	1002	\|GregorianDay\|xs:date
	1003	\|ReportingTimePeriod\|common:ReportingTimePeriodType
	1004	\|ReportingYear\|common:ReportingYearType
	1005	\|ReportingSemester\|common:ReportingSemesterType
	1006	\|ReportingTrimester\|common:ReportingTrimesterType
	1007	\|ReportingQuarter\|common:ReportingQuarterType
	1008	\|ReportingMonth\|common:ReportingMonthType
	1009	\|ReportingWeek\|common:ReportingWeekType
	1010	\|ReportingDay\|common:ReportingDayType
	1011	\|DateTime\|xs:dateTime
	1012	\|TimeRange\|common:TimeRangeType
	1013	\|Month\|xs:gMonth
	1014	\|MonthDay\|xs:gMonthDay
	1015	\|Day\|xs:gDay
	1016	\|Time\|xs:time
	1017	\|Duration\|xs:duration
	1018	\|XHTML\|N/A[[~[1~]>>path:#_ftn1]]
	1019	\|KeyValues\|N/A^^1^^
	1020	\|IdentifiableReference\|N/A^^1^^
	1021	\|DataSetReference\|N/A^^1^^
	1022	\|AttachmentConstraintReference\|N/A^^1^^
	1023
	1024	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):
	1025
	1026	\|SDMX Facet\|XML Schema Facet
	1027	\|minLength\|xs:minLength
	1028	\|maxLength\|xs:maxLength
	1029	\|minValue[[~[2~]>>path:#_ftn2]]\|if ExclusiveValueRange: xs:minExclusives, else: xs:minInclusive
	1030	\|maxValue^^2^^\|if ExclusiveValueRange: xs:maxExclusives, else: xs:maxInclusive
	1031	\|decimals^^2^^\|xs:fractionDigits
	1032	\|pattern\|xs:pattern
	1033
	1034	Any other facets are informational only, and will not affect the determined type.
	1035
	1036	1.
	1037	11.
	1038	111. //Type Names//
	1039
	1040	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.
	1041
	1042	* 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]
	1043	* 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]
	1044	* If the type is based on a text format of a component local representation, and;
	1045	** 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]
	1046	** 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]
	1047	**1. Type Reuse
	1048
	1049	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.
	1050
	1051	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:
	1052
	1053	Does the component define a local type?
	1054
	1055	Yes: Is that type enumerated?
	1056
	1057	Yes: Type is the qualified type name for the item scheme
	1058
	1059	No: Generate simple type for text format
	1060
	1061	No: Type is the qualified name for the concept from which the component takes its semantic.
	1062
	1063	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.
	1064
	1065	1.
	1066	11. Data Structure Specific Schema
	1067
	1068	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.
	1069
	1070	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.
	1071
	1072	1.
	1073	11.
	1074	111. DataSetType
	1075
	1076	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:
	1077
	1078	1. A sequence consisting of:
	1079	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1080	11. A local element named DataProvider with the type common:DataProviderReferenceType, a form of unqualified and a minimum occurrence of 0
	1081	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.
	1082	11. A choice with a minimum occurrence of 0 consisting of:
	1083	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)
	1084	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)
	1085	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
	1086	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
	1087	11.
	1088	111. GroupType
	1089
	1090	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:
	1091
	1092	1. A sequence consisting of:
	1093	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1094	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
	1095	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
	1096	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
	1097	1. An attribute named type with a type of common:IDType, usage of optional, and a fixed value of the identifier of the group
	1098
	1099	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:
	1100
	1101	1. A sequence consisting of:
	1102	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1103	1. An attribute named type with a type of Group.ID, and a usage of optional
	1104	1. An anyAttribute declaration with a namespace of ~#~#local
	1105
	1106	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.
	1107
	1108	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:
	1109
	1110	1. A sequence consisting of:
	1111	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1112	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
	1113	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
	1114	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
	1115	1. An attribute named type with a type of Group.ID, usage of optional, and a fixed value of the identifier of the group
	1116	11.
	1117	111. SeriesType
	1118
	1119	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:
	1120
	1121	1. A sequence consisting of:
	1122	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1123	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)
	1124	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
	1125	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
	1126	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
	1127	11.
	1128	111. ObsType
	1129
	1130	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:
	1131
	1132	1. A sequence consisting of:
	1133	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1134	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
	1135	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
	1136	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
	1137	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
	1138	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
	1139
	1140	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:
	1141
	1142	1. A sequence consisting of:
	1143	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1144	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
	1145	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.
	1146	11. Metadata Structure Specific Schema
	1147
	1148	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.
	1149
	1150	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.
	1151
	1152	1.
	1153	11.
	1154	111. MetadataSetType
	1155
	1156	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:
	1157
	1158	1. A sequence consisting of:
	1159	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1160	11. An element reference to common:Name, with a minimum occurrence of 0 and a maximum occurrence of unbounded
	1161	11. A local element named DataProvider with the type common:DataProviderReferenceType, a form of unqualified and a minimum occurrence of 0
	1162	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.
	1163	111. TargetType
	1164
	1165	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:
	1166
	1167	1. A sequence consisting of:
	1168	11. A local element named ReferenceValue with a type of msd:ReferenceValueType, a form of unqualified, and a maximum occurrence of unbounded
	1169	1. An attribute named id with a type of Target.ID, and a usage of optional
	1170
	1171	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.
	1172
	1173	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.
	1174
	1175	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:
	1176
	1177	1. A choice consisting of:
	1178	11. A local element named ObjectReference with a type of common:ReferenceType, and a form of unqualified
	1179	11. A local element named DataKey with a type of common:DataKeyType, and a form of unqualified
	1180	11. A local element named DataSetReference with a type of common:SetReferenceType, and a form of unqualified
	1181	11. A local element named ReportPeriod with a type of common:ObservationalTimePeriodType, and a form of unqualified
	1182	1. An attribute named id with the type defined previously as [metadata target identifier].TargetObject.ID, and a usage of optional
	1183
	1184	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:
	1185
	1186	1. A sequence consisting of:
	1187	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
	1188
	1189	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:
	1190
	1191	1. A choice consisting of:
	1192	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:
	1193	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
	1194	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
	1195	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
	1196	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
	1197	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
	1198
	1199	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:
	1200
	1201	1. A choice consisting of:
	1202	11. A sequence consisting of
	1203	111. A local element named Ref, with a form of unqualified and a the type defined above as is [metadata target].[target object].Ref
	1204	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
	1205	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
	1206	111.
	1207	1111. Identifiable Object Target Type Determination
	1208
	1209	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.
	1210
	1211	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.
	1212
	1213	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:
	1214
	1215	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.
	1216
	1217	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).
	1218
	1219	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:
	1220
	1221	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
	1222	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
	1223	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
	1224	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.
	1225	11.
	1226	111. ReportType
	1227
	1228	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.
	1229
	1230	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:
	1231
	1232	1. A sequence consisting of:
	1233	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1234	11. A local element named Target with the type previously defined as TargetType and a form of unqualified
	1235	11. A local element named AttributeSet with no type assigned and a form of unqualified
	1236	1. An attribute named id with a type previously defined as Report.ID, and a usage of optional
	1237
	1238	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.
	1239
	1240	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.
	1241
	1242	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:
	1243
	1244	1. A sequence consisting of:
	1245	11. A local element named ReferenceValue with a type of msd:ReferenceValueType, a form of unqualified, and a maximum occurrence of unbounded
	1246	1. An attribute named id with the type previously created as [report structure identifier].Target.ID, and a use of optional
	1247
	1248	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:
	1249
	1250	1. A reference to the content group that was previously created as [metadata target identifier] for this metadata target
	1251	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]
	1252
	1253	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:
	1254
	1255	1. A sequence consisting of:
	1256	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1257	11. If the isPresentational flag is not set to true:
	1258	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
	1259	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
	1260	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
	1261	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
	1262	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
	1263
	1264	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:
	1265
	1266	1. A sequence consisting of:
	1267	11. An element reference to common:Annotations, with a minimum occurrence of 0
	1268	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:
	1269	111. A selector with an xpath of "*"
	1270	111. A field with an xpath of "@id"
	1271
	1272	1.
	1273	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
	1274	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]
	1275	11.
	1276	111.
	1277	1111. Attribute Set Complex Type Creation
	1278
	1279	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:
	1280
	1281	1. A sequence consisting of:
	1282	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].
	1283
	1284	1. Special data functions
	1285	11. Updates
	1286
	1287	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.
	1288
	1289
	1290	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.
	1291
	1292	1.
	1293	11. Deletes
	1294
	1295	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.
	1296
	1297
	1298	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.
	1299
	1300
	1301	----
	1302
	1303	[[~[1~]>>path:#_ftnref1]] These types are only used in complex types and will be discussed within their appropriate context.
	1304
	1305	[[~[2~]>>path:#_ftnref2]] Note that these options only apply to numeric representations and should be ignored if the data type is non-numeric