Changes for page Part I. Message Namespace

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Tags

...	...	@@ -1,1 +1,0 @@
1		-Attribute|Category scheme|Code|Code list|Concept scheme|Contact phone number|Data set|Data source|Data structure definition|Dataflow|Dimension|Hierarchical code list|Metadata set|Metadata structure definition|Metadataflow|Notification|Provision agreement|Reference metadata|Reference period|Reporting taxonomy|SDMX Registry|SDMX-ML|Statistical data and metadata exchange|Structural metadata|Structure set|Subscription|Time period|Validation and transformation language

Content

...	...	@@ -8,7 +8,7 @@
8	8
9	9	**~1. Problem**
10	10
11		-Various parts of the the documentation refer to stand-alone (% style="color:#e74c3c" %)concepts(%%), which were part of earlier draft releases but ultimately excluded from the final release of the standard.
	11	+Various parts of the the documentation refer to stand-alone concepts, which were part of earlier draft releases but ultimately excluded from the final release of the standard.
12	12
13	13	**Rectification**
14	14
...	...	@@ -16,11 +16,11 @@
16	16
17	17	= 1. Introduction =
18	18
19		-At the core of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] XML messages are the message namespaces. These namespaces define the general structure of all messages and define the specific messages that are available for exchange in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]].
	19	+At the core of the SDMX XML messages are the message namespaces. These namespaces define the general structure of all messages and define the specific messages that are available for exchange in SDMX.
20	20
21		-There are two namespaces associated with the messages. The main namespace schema which defines every message in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] is http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message. Associated with this is another sub-namespace, http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer. This namespace defines footer (% style="color:#e74c3c" %)level(%%) information that is available in messages which might require non-standard payload information to be transmitted.
	21	+There are two namespaces associated with the messages. The main namespace schema which defines every message in SDMX is http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message. Associated with this is another sub-namespace, http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer. This namespace defines footer level information that is available in messages which might require non-standard payload information to be transmitted.
22	22
23		-In general, every message in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] follows common format of:
	23	+In general, every message in SDMX follows common format of:
24	24
25	25	* Header
26	26	* Payload (0..n)
...	...	@@ -52,6 +52,7 @@
52	52	|(% style="width:612px" %)http:~/~/www.w3.org/2001/XMLSchema|(% style="width:173px" %)xs
53	53
54	54	Contents:
	55	+
55	55	50 Global Elements
56	56	62 Complex Types
57	57	1 Simple Type
...	...	@@ -58,103 +58,103 @@
58	58
59	59	=== 2.1.2 Global Elements ===
60	60
61		-**Structure (StructureType): **Structure is a message that contains [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. It may contain any of the following; categorisations, [[category schemes>>doc:sdmx:Glossary.Category scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], (% style="color:#e74c3c" %)concepts(%%) ([[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]]), (% style="color:#e74c3c" %)constraints(%%) (attachment and content) [[data flows>>doc:sdmx:Glossary.Dataflow.WebHome]], [[hierarchical code lists>>doc:sdmx:Glossary.Hierarchical code list.WebHome]], [[metadata flows>>doc:sdmx:Glossary.Metadataflow.WebHome]], [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], organisation schemes, processes, [[reporting taxonomies>>doc:sdmx:Glossary.Reporting taxonomy.WebHome]], and structure sets.
	62	+**Structure (StructureType): **Structure is a message that contains structural metadata. It may contain any of the following; categorisations, category schemes, code lists, concepts (concept schemes), constraints (attachment and content) data flows, hierarchical code lists, metadata flows, metadata structure definitions, organisation schemes, processes, reporting taxonomies, and structure sets.
62	62
63		-**GenericData (GenericDataType): **GenericData is used to convey data in a non data structure specific form. [[Data sets>>doc:sdmx:Glossary.Data set.WebHome]] in this message will be each have a related structure specification in the header, which states the data structure the data conforms to and how the data is organised (i.e. the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]).
	64	+**GenericData (GenericDataType): **GenericData is used to convey data in a non data structure specific form. Data sets in this message will be each have a related structure specification in the header, which states the data structure the data conforms to and how the data is organised (i.e. the observation dimension).
64	64
65		-**GenericTimeSeriesData (GenericTimeSeriesDataType): **GenericTimeSeriesData is a special derivation of the generic data message which only allows for time series oriented date (i.e. the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] must be time). Although this is a different message, the content of this message will be exactly the same as a generic data message that specifies time as the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
	66	+**GenericTimeSeriesData (GenericTimeSeriesDataType): **GenericTimeSeriesData is a special derivation of the generic data message which only allows for time series oriented date (i.e. the observation dimension must be time). Although this is a different message, the content of this message will be exactly the same as a generic data message that specifies time as the observation dimension; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
66	66
67		-**StructureSpecificData (StructureSpecificDataType): **StructureSpecificData is used to convey data structure specific according to [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]. The payload of this message (i.e. the [[data sets>>doc:sdmx:Glossary.Data set.WebHome]]) will be based on XML schemas which are specific to the [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] and the orientation (i.e. the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]) of the data.
	68	+**StructureSpecificData (StructureSpecificDataType): **StructureSpecificData is used to convey data structure specific according to data structure definition. The payload of this message (i.e. the data sets) will be based on XML schemas which are specific to the data structure definition and the orientation (i.e. the observation dimension) of the data.
68	68
69		-**StructureSpecificTimeSeriesData (StructureSpecificTimeSeriesDataType): **StructureSpecificTimeSeriesData is a special derivation of the structure specific data message which only allows for time series oriented date (i.e. the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] must be time). Although this is a different message, the content of this message will be exactly the same as a structure specific data message that specifies time as the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
	70	+**StructureSpecificTimeSeriesData (StructureSpecificTimeSeriesDataType): **StructureSpecificTimeSeriesData is a special derivation of the structure specific data message which only allows for time series oriented date (i.e. the observation dimension must be time). Although this is a different message, the content of this message will be exactly the same as a structure specific data message that specifies time as the observation dimension; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
70	70
71		-**GenericMetadata (GenericMetadataType): **GenericMetadata contains reported metadata in a format which supports any [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]].
	72	+**GenericMetadata (GenericMetadataType): **GenericMetadata contains reported metadata in a format which supports any metadata structure definition.
72	72
73		-**StructureSpecificMetadata (StructureSpecificMetadataType): **StructureSpecificMetadata contains reported metadata in a format which is specific to the [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] which define the structure of the metadata being reported. This format allows for validation of the metadata against the intended structure. Note that the each [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]] provided will be based on a metadata structure specific schema.
	74	+**StructureSpecificMetadata (StructureSpecificMetadataType): **StructureSpecificMetadata contains reported metadata in a format which is specific to the metadata structure definitions which define the structure of the metadata being reported. This format allows for validation of the metadata against the intended structure. Note that the each metadata set provided will be based on a metadata structure specific schema.
74	74
75		-**RegistryInterface (RegistryInterfaceType): **RegistryInterface is used to conduct all interactions with the [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] Services.
	76	+**RegistryInterface (RegistryInterfaceType): **RegistryInterface is used to conduct all interactions with the SDMX Registry Services.
76	76
77		-**SubmitRegistrationsRequest (SubmitRegistrationsRequestType): **SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request on or more registrations for a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]]. The [[data source>>doc:sdmx:Glossary.Data source.WebHome]] to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
	78	+**SubmitRegistrationsRequest (SubmitRegistrationsRequestType): **SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request on or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
78	78
79	79	**SubmitRegistrationsResponse (SubmitRegistrationsResponseType): **SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a registration requests. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
80	80
81		-**QueryRegistrationRequest (QueryRegistrationRequestType): **QueryRegistrationRequest is used to query the contents of a registry for [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]]. It specifies whether the result set should include [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], or both. The search can be characterized by providing (% style="color:#e74c3c" %)constraints(%%) including [[reference periods>>doc:sdmx:Glossary.Reference period.WebHome]], data regions, and data keys.
	82	+**QueryRegistrationRequest (QueryRegistrationRequestType): **QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys.
82	82
83	83	**QueryRegistrationResponse (QueryRegistrationResponseType): **QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.
84	84
85		-**SubmitStructureRequest (SubmitStructureRequestType): **SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, (% style="color:#e74c3c" %)concepts(%%) and [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], etc.) to be submitted may be communicated in-line or be supplied in a referenced [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Structure messages external to the registry. A response will indicate status and contain any relevant error information.
	86	+**SubmitStructureRequest (SubmitStructureRequestType): **SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information.
86	86
87	87	**SubmitStructureResponse (SubmitStructureResponseType): **SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
88	88
89	89	**SubmitSubscriptionsRequest (SubmitSubscriptionsRequestType): **SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
90	90
91		-**SubmitSubscriptionsResponse (SubmitSubscriptionsResponseType): **SubmitSubscriptionsResponse is the response to a submit [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] request. It contains information which describes the success or failure of each [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request, providing any error messages in the event of failure. If successful, it returns the registry URN of the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]], and the subscriber-assigned ID.
	92	+**SubmitSubscriptionsResponse (SubmitSubscriptionsResponseType): **SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID.
92	92
93		-**QuerySubscriptionRequest (QuerySubscriptionRequestType): **QuerySubscriptionRequest is used to query the registry for the [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] of a given organisation.
	94	+**QuerySubscriptionRequest (QuerySubscriptionRequestType): **QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
94	94
95		-**QuerySubscriptionResponse (QuerySubscriptionResponseType): **QuerySubscriptionResponse is sent as a response to a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] query. If the query is successful, the details of all [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] for the requested organisation are sent.
	96	+**QuerySubscriptionResponse (QuerySubscriptionResponseType): **QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent.
96	96
97		-**NotifyRegistryEvent (NotifyRegistryEventType): **NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] that triggered the [[notification>>doc:sdmx:Glossary.Notification.WebHome]] are always sent. Optionally, the details of the changed object may also be provided.
	98	+**NotifyRegistryEvent (NotifyRegistryEventType): **NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided.
98	98
99		-**StructureSpecificDataQuery (DataQueryType): **StructureSpecificDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for structure specific data.
	100	+**StructureSpecificDataQuery (DataQueryType): **StructureSpecificDataQuery is used to query SDMX compliant databases or web services for structure specific data.
100	100
101		-**GenericDataQuery (GenericDataQueryType): **GenericDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for generic data. This is actually a specialization of the structured data query, and therefore can be processed in the same manner.
	102	+**GenericDataQuery (GenericDataQueryType): **GenericDataQuery is used to query SDMX compliant databases or web services for generic data. This is actually a specialization of the structured data query, and therefore can be processed in the same manner.
102	102
103		-**GenericTimeSeriesDataQuery (GenericTimeSeriesDataQueryType): **GenericTimeSeriesDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for time series only generic data. This is actually a specialization of the generic data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
	104	+**GenericTimeSeriesDataQuery (GenericTimeSeriesDataQueryType): **GenericTimeSeriesDataQuery is used to query SDMX compliant databases or web services for time series only generic data. This is actually a specialization of the generic data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
104	104
105		-**StructureSpecificTimeSeriesDataQuery (StructureSpecificTimeSeriesDataQueryType): **StructureSpecificTimeSeriesDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for time series only structure specific data. This is actually a specialization of the structure specific data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
	106	+**StructureSpecificTimeSeriesDataQuery (StructureSpecificTimeSeriesDataQueryType): **StructureSpecificTimeSeriesDataQuery is used to query SDMX compliant databases or web services for time series only structure specific data. This is actually a specialization of the structure specific data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
106	106
107		-**GenericMetadataQuery (MetadataQueryType): **GenericMetadataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for generic format [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]].
	108	+**GenericMetadataQuery (MetadataQueryType): **GenericMetadataQuery is used to query SDMX compliant databases or web services for generic format reference metadata.
108	108
109		-**StructureSpecificMetadataQuery (MetadataQueryType): **StructureSpecificMetadataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for metadata structure specific [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]].
	110	+**StructureSpecificMetadataQuery (MetadataQueryType): **StructureSpecificMetadataQuery is used to query SDMX compliant databases or web services for metadata structure specific reference metadata.
110	110
111		-**DataSchemaQuery (DataSchemaQueryType): **DataSchemaQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for data structure specific schemas for the purpose of validating structured data.
	112	+**DataSchemaQuery (DataSchemaQueryType): **DataSchemaQuery is used to query SDMX compliant databases or web services for data structure specific schemas for the purpose of validating structured data.
112	112
113		-**MetadataSchemaQuery (MetadataSchemaQueryType): **MetadataSchemaQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for metadata structure specific schemas for the purpose of validating structured metadata.
	114	+**MetadataSchemaQuery (MetadataSchemaQueryType): **MetadataSchemaQuery is used to query SDMX compliant databases or web services for metadata structure specific schemas for the purpose of validating structured metadata.
114	114
115		-**StructuresQuery (StructuresQueryType): **StructuresQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for any structures based on simple maintainable object properties (e.g. all objects maintained by a maintenance agency).
	116	+**StructuresQuery (StructuresQueryType): **StructuresQuery is used to query SDMX compliant databases or web services for any structures based on simple maintainable object properties (e.g. all objects maintained by a maintenance agency).
116	116
117		-**DataflowQuery (DataflowQueryType): **DataflowQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for dataflows.
	118	+**DataflowQuery (DataflowQueryType): **DataflowQuery is used to query SDMX compliant databases or web services for dataflows.
118	118
119		-**MetadataflowQuery (MetadataflowQueryType): **MetadataflowQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[metadata flows>>doc:sdmx:Glossary.Metadataflow.WebHome]].
	120	+**MetadataflowQuery (MetadataflowQueryType): **MetadataflowQuery is used to query SDMX compliant databases or web services for metadata flows.
120	120
121		-**DataStructureQuery (DataStructureQueryType): **DataStructureQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for data structures definitions.
	122	+**DataStructureQuery (DataStructureQueryType): **DataStructureQuery is used to query SDMX compliant databases or web services for data structures definitions.
122	122
123		-**MetadataStructureQuery (MetadataStructureQueryType): **MetadataStructureQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]].
	124	+**MetadataStructureQuery (MetadataStructureQueryType): **MetadataStructureQuery is used to query SDMX compliant databases or web services for metadata structure definitions.
124	124
125		-**CategorySchemeQuery (CategorySchemeQueryType): **CategorySchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[category schemes>>doc:sdmx:Glossary.Category scheme.WebHome]].
	126	+**CategorySchemeQuery (CategorySchemeQueryType): **CategorySchemeQuery is used to query SDMX compliant databases or web services for category schemes.
126	126
127		-**ConceptSchemeQuery (ConceptSchemeQueryType): **ConceptSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]].
	128	+**ConceptSchemeQuery (ConceptSchemeQueryType): **ConceptSchemeQuery is used to query SDMX compliant databases or web services for concept schemes.
128	128
129		-**CodelistQuery (CodelistQueryType): **CodelistQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for codelists.
	130	+**CodelistQuery (CodelistQueryType): **CodelistQuery is used to query SDMX compliant databases or web services for codelists.
130	130
131		-**HierarchicalCodelistQuery (HierarchicalCodelistQueryType): **HierarchicalCodelistQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for hierarchical codelists.
	132	+**HierarchicalCodelistQuery (HierarchicalCodelistQueryType): **HierarchicalCodelistQuery is used to query SDMX compliant databases or web services for hierarchical codelists.
132	132
133		-**OrganisationSchemeQuery (OrganisationSchemeQueryType): **OrganisationSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for organisation schemes.
	134	+**OrganisationSchemeQuery (OrganisationSchemeQueryType): **OrganisationSchemeQuery is used to query SDMX compliant databases or web services for organisation schemes.
134	134
135		-**ReportingTaxonomyQuery (ReportingTaxonomyQueryType): **ReportingTaxonomyQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[reporting taxonomies>>doc:sdmx:Glossary.Reporting taxonomy.WebHome]].
	136	+**ReportingTaxonomyQuery (ReportingTaxonomyQueryType): **ReportingTaxonomyQuery is used to query SDMX compliant databases or web services for reporting taxonomies.
136	136
137		-**StructureSetQuery (StructureSetQueryType): **StructureSetQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for structure sets.
	138	+**StructureSetQuery (StructureSetQueryType): **StructureSetQuery is used to query SDMX compliant databases or web services for structure sets.
138	138
139		-**ProcessQuery (ProcessQueryType): **ProcessQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for processes.
	140	+**ProcessQuery (ProcessQueryType): **ProcessQuery is used to query SDMX compliant databases or web services for processes.
140	140
141		-**CategorisationQuery (CategorisationQueryType): **CategorisationQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for categorisations.
	142	+**CategorisationQuery (CategorisationQueryType): **CategorisationQuery is used to query SDMX compliant databases or web services for categorisations.
142	142
143		-**ProvisionAgreementQuery (ProvisionAgreementQueryType): **ProvisionAgreementQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for provision agreements.
	144	+**ProvisionAgreementQuery (ProvisionAgreementQueryType): **ProvisionAgreementQuery is used to query SDMX compliant databases or web services for provision agreements.
144	144
145		-**ConstraintQuery (ConstraintQueryType): **ConstraintQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for (% style="color:#e74c3c" %)constraints(%%).
	146	+**ConstraintQuery (ConstraintQueryType): **ConstraintQuery is used to query SDMX compliant databases or web services for constraints.
146	146
147		-**TransformationSchemeQuery (TransformationSchemeQueryType): **TransformationSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for transformation schemes.
	148	+**TransformationSchemeQuery (TransformationSchemeQueryType): **TransformationSchemeQuery is used to query SDMX compliant databases or web services for transformation schemes.
148	148
149		-**VtlMappingSchemeQuery (VtlMappingSchemeQueryType): **VtlMappingSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] mapping schemes.
	150	+**VtlMappingSchemeQuery (VtlMappingSchemeQueryType): **VtlMappingSchemeQuery is used to query SDMX compliant databases or web services for VTL mapping schemes.
150	150
151		-**NamePersonalisationSchemeQuery (NamePersonalisationSchemeQueryType): **NamePersonalisationSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for name personalisation schemes.
	152	+**NamePersonalisationSchemeQuery (NamePersonalisationSchemeQueryType): **NamePersonalisationSchemeQuery is used to query SDMX compliant databases or web services for name personalisation schemes.
152	152
153		-**RulesetSchemeQuery (RulesetSchemeQueryType): **RulesetSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for ruleset schemes.
	154	+**RulesetSchemeQuery (RulesetSchemeQueryType): **RulesetSchemeQuery is used to query SDMX compliant databases or web services for ruleset schemes.
154	154
155		-**UserDefinedOperatorSchemeQuery (UserDefinedOperatorSchemeQueryType): **UserDefinedOperatorSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for user defined schemes.
	156	+**UserDefinedOperatorSchemeQuery (UserDefinedOperatorSchemeQueryType): **UserDefinedOperatorSchemeQuery is used to query SDMX compliant databases or web services for user defined schemes.
156	156
157		-**CustomTypeSchemeQuery (CustomTypeSchemeQueryType): **CustomTypeSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for custom type schemes.
	158	+**CustomTypeSchemeQuery (CustomTypeSchemeQueryType): **CustomTypeSchemeQuery is used to query SDMX compliant databases or web services for custom type schemes.
158	158
159	159	**Error (ErrorType): **Error is used to communicate that an error has occurred when responding to a request in an non-registry environment. The content will be a collection of error messages.
160	160
...	...	@@ -168,19 +168,19 @@
168	168
169	169	Element Documentation:
170	170
171		-(% style="width:1004.83px" %)
172		-|**Name**|**Type**|(% style="width:631px" %)**Documentation**
173		-|Header|//BaseHeaderType//|(% style="width:631px" %)
174		-|ftr:Footer|ftr:FooterType|(% style="width:631px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
	172	+|**Name**|**Type**|**Documentation**
	173	+|Header|//BaseHeaderType//|
	174	+|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
175	175
176	176	**StructureType: **StructureType defines the contents of a structure message. The payload is optional since this message may be returned from a web service with only information in the footer.
177	177
178	178	Derivation:
179	179
180		-* //MessageType// (restriction)
181		-** StructureType
	180	+//MessageType// (restriction)
	181	+ StructureType
182	182
183	183	Content:
	184	+
184	184	Header, Structures?, ftr:Footer?
185	185
186	186	Element Documentation:
...	...	@@ -195,18 +195,19 @@
195	195
196	196	Derivation:
197	197
198		-* //MessageType// (restriction)
199		-** GenericDataType
	199	+//MessageType// (restriction)
	200	+ GenericDataType
200	200
201	201	Content:
202		-Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer?
203	203
	204	+Header, DataSet*, ftr:Footer?
	205	+
204	204	Element Documentation:
205	205
206	206	(% style="width:847.294px" %)
207	207	|**Name**|(% style="width:227px" %)**Type**|(% style="width:450px" %)**Documentation**
208	208	|Header|(% style="width:227px" %)GenericDataHeaderTyp e|(% style="width:450px" %)
209		-|[[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:227px" %)dat:DataSetType|(% style="width:450px" %)
	211	+|DataSet|(% style="width:227px" %)dat:DataSetType|(% style="width:450px" %)
210	210	|ftr:Footer|(% style="width:227px" %)ftr:FooterType|(% style="width:450px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
211	211
212	212	**GenericTimeSeriesDataType: **GenericTimeSeriesDataType defines the structure of the generic time series data message.
...	...	@@ -218,17 +218,18 @@
218	218	*** GenericTimeSeriesDataType
219	219
220	220	Content:
221		-Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer?
222	222
	224	+Header, DataSet*, ftr:Footer?
	225	+
223	223	Element Documentation:
224	224
225	225	(% style="width:856.294px" %)
226	226	|**Name**|(% style="width:239px" %)**Type**|(% style="width:458px" %)**Documentation**
227	227	|Header|(% style="width:239px" %)GenericTimeSeriesDat aHeaderType|(% style="width:458px" %)
228		-|[[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:239px" %)dat: TimeSeriesDataSetTyp e|(% style="width:458px" %)
	231	+|DataSet|(% style="width:239px" %)dat: TimeSeriesDataSetTyp e|(% style="width:458px" %)
229	229	|ftr:Footer|(% style="width:239px" %)ftr:FooterType|(% style="width:458px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
230	230
231		-**StructureSpecificDataType: **StructureSpecificDataType defines the structure of the structure specific data message. Note that the [[data set>>doc:sdmx:Glossary.Data set.WebHome]] payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known.
	234	+**StructureSpecificDataType: **StructureSpecificDataType defines the structure of the structure specific data message. Note that the data set payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known.
232	232
233	233	Derivation:
234	234
...	...	@@ -236,14 +236,15 @@
236	236	** StructureSpecificDataType
237	237
238	238	Content:
239		-Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer?
240	240
	243	+Header, DataSet*, ftr:Footer?
	244	+
241	241	Element Documentation:
242	242
243	243	(% style="width:828.294px" %)
244	244	|**Name**|(% style="width:247px" %)**Type**|(% style="width:420px" %)**Documentation**
245	245	|Header|(% style="width:247px" %)StructureSpecificDat aHeaderType|(% style="width:420px" %)
246		-|[[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:247px" %)//dsd:DataSetType//|(% style="width:420px" %)
	250	+|DataSet|(% style="width:247px" %)//dsd:DataSetType//|(% style="width:420px" %)
247	247	|ftr:Footer|(% style="width:247px" %)ftr:FooterType|(% style="width:420px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
248	248
249	249	**StructureSpecificTimeSeriesDataType: **StructureSpecificTimeSeriesDataType defines the structure of the structure specific time series data message.
...	...	@@ -255,14 +255,15 @@
255	255	*** StructureSpecificTimeSeriesDataType
256	256
257	257	Content:
258		-Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer?
259	259
	263	+Header, DataSet*, ftr:Footer?
	264	+
260	260	Element Documentation:
261	261
262	262	(% style="width:839.294px" %)
263	263	|**Name**|(% style="width:256px" %)**Type**|(% style="width:434px" %)**Documentation**
264	264	|Header|(% style="width:256px" %)StructureSpecificTim eSeriesDataHeaderTyp e|(% style="width:434px" %)
265		-|[[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:256px" %)//dsd: TimeSeriesDataSetTyp e//|(% style="width:434px" %)
	270	+|DataSet|(% style="width:256px" %)//dsd: TimeSeriesDataSetTyp e//|(% style="width:434px" %)
266	266	|ftr:Footer|(% style="width:256px" %)ftr:FooterType|(% style="width:434px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
267	267
268	268	**GenericMetadataType: **GenericMetadataType defines the contents of a generic metadata message.
...	...	@@ -273,6 +273,7 @@
273	273	** GenericMetadataType
274	274
275	275	Content:
	281	+
276	276	Header, MetadataSet*, ftr:Footer?
277	277
278	278	Element Documentation:
...	...	@@ -279,11 +279,11 @@
279	279
280	280	(% style="width:836.294px" %)
281	281	|(% style="width:181px" %)**Name**|(% style="width:225px" %)**Type**|(% style="width:427px" %)**Documentation**
282		-|(% style="width:181px" %)Header|(% style="width:225px" %)GenericMetadataHeaderType|(% style="width:427px" %)
	288	+|(% style="width:181px" %)Header|(% style="width:225px" %)GenericMetadataHeade rType|(% style="width:427px" %)
283	283	|(% style="width:181px" %)MetadataSet|(% style="width:225px" %)rep:MetadataSetType|(% style="width:427px" %)
284	284	|(% style="width:181px" %)ftr:Footer|(% style="width:225px" %)ftr:FooterType|(% style="width:427px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
285	285
286		-**StructureSpecificMetadataType: **StructureSpecificMetadataType defines the structure of a structure specific metadata message. Note that the [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]] payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known.
	292	+**StructureSpecificMetadataType: **StructureSpecificMetadataType defines the structure of a structure specific metadata message. Note that the metadata set payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known.
287	287
288	288	Derivation:
289	289
...	...	@@ -291,6 +291,7 @@
291	291	** StructureSpecificMetadataType
292	292
293	293	Content:
	300	+
294	294	Header, MetadataSet*, ftr:Footer?
295	295
296	296	Element Documentation:
...	...	@@ -297,7 +297,7 @@
297	297
298	298	(% style="width:841.294px" %)
299	299	|(% style="width:160px" %)**Name**|(% style="width:250px" %)**Type**|(% style="width:428px" %)**Documentation**
300		-|(% style="width:160px" %)Header|(% style="width:250px" %)StructureSpecificMetadataHeaderType|(% style="width:428px" %)
	307	+|(% style="width:160px" %)Header|(% style="width:250px" %)StructureSpecificMet adataHeaderType|(% style="width:428px" %)
301	301	|(% style="width:160px" %)MetadataSet|(% style="width:250px" %)//msd:MetadataSetType//|(% style="width:428px" %)
302	302	|(% style="width:160px" %)ftr:Footer|(% style="width:250px" %)ftr:FooterType|(% style="width:428px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
303	303
...	...	@@ -309,25 +309,26 @@
309	309	** RegistryInterfaceType
310	310
311	311	Content:
	319	+
312	312	Header, (SubmitRegistrationsRequest | SubmitRegistrationsResponse | QueryRegistrationRequest | QueryRegistrationResponse | SubmitStructureRequest | SubmitStructureResponse | SubmitSubscriptionsRequest | SubmitSubscriptionsResponse | QuerySubscriptionRequest | QuerySubscriptionResponse | NotifyRegistryEvent)?, ftr:Footer?
313	313
314	314	Element Documentation:
315	315
316		-(% style="width:1000.83px" %)
317		-|**Name**|(% style="width:317px" %)**Type**|(% style="width:491px" %)**Documentation**
318		-|Header|(% style="width:317px" %)BasicHeaderType|(% style="width:491px" %)
319		-|SubmitRegistrationsRequest|(% style="width:317px" %)ref: SubmitRegistrationsRequestType|(% style="width:491px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]]. The [[data source>>doc:sdmx:Glossary.Data source.WebHome]] to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
320		-|SubmitRegistrationsResponse|(% style="width:317px" %)ref: SubmitRegistrationsResponseType|(% style="width:491px" %)SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
321		-|QueryRegistrationRequest|(% style="width:317px" %)ref: QueryRegistrationRequestType|(% style="width:491px" %)QueryRegistrationRequest is used to query the contents of a registry for [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]]. It specifies whether the result set should include [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], or both. The search can be characterized by providing (% style="color:#e74c3c" %)constraints(%%) including [[reference periods>>doc:sdmx:Glossary.Reference period.WebHome]], data regions, and data keys.
322		-|QueryRegistrationResponse|(% style="width:317px" %)ref: QueryRegistrationResponseType|(% style="width:491px" %)QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.
323		-|SubmitStructureReque st|(% style="width:317px" %)ref: SubmitStructureReque stType|(% style="width:491px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, (% style="color:#e74c3c" %)concepts(%%) and [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], etc.) to be submitted may be communicated in-line or be supplied in a referenced [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Structure messages external to the registry. A response will indicate status and contain any relevant error information.
324		-|SubmitStructureRespo nse|(% style="width:317px" %)ref: SubmitStructureRespo nseType|(% style="width:491px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
325		-|SubmitSubscriptionsR equest|(% style="width:317px" %)ref: SubmitSubscriptionsR equestType|(% style="width:491px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
326		-|SubmitSubscriptionsR esponse|(% style="width:317px" %)ref: SubmitSubscriptionsR esponseType|(% style="width:491px" %)SubmitSubscriptionsResponse is the response to a submit [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] request. It contains information which describes the success or failure of each [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request, providing any error messages in the event of failure. If successful, it returns the registry URN of the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]], and the subscriber-assigned ID.
327		-|QuerySubscriptionReq uest|(% style="width:317px" %)ref: QuerySubscriptionReq uestType|(% style="width:491px" %)QuerySubscriptionRequest is used to query the registry for the [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] of a given organisation.
328		-|QuerySubscriptionRes ponse|(% style="width:317px" %)ref: QuerySubscriptionRes ponseType|(% style="width:491px" %)QuerySubscriptionResponse is sent as a response to a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] query. If the query is successful, the details of all [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] for the requested organisation are sent.
329		-|NotifyRegistryEvent|(% style="width:317px" %)ref: NotifyRegistryEventT ype|(% style="width:491px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] that triggered the [[notification>>doc:sdmx:Glossary.Notification.WebHome]] are always sent. Optionally, the details of the changed object may also be provided.
330		-|ftr:Footer|(% style="width:317px" %)ftr:FooterType|(% style="width:491px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
	324	+(% style="width:903.294px" %)
	325	+|**Name**|**Type**|(% style="width:441px" %)**Documentation**
	326	+|Header|BasicHeaderType|(% style="width:441px" %)
	327	+|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:441px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
	328	+|SubmitRegistrationsR esponse|ref: SubmitRegistrationsR esponseType|(% style="width:441px" %)SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
	329	+|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:441px" %)QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys.
	330	+|QueryRegistrationRes ponse|ref: QueryRegistrationRes ponseType|(% style="width:441px" %)QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.
	331	+|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:441px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information.
	332	+|SubmitStructureRespo nse|ref: SubmitStructureRespo nseType|(% style="width:441px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
	333	+|SubmitSubscriptionsR equest|ref: SubmitSubscriptionsR equestType|(% style="width:441px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
	334	+|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:441px" %)SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID.
	335	+|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|(% style="width:441px" %)QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
	336	+|QuerySubscriptionRes ponse|ref: QuerySubscriptionRes ponseType|(% style="width:441px" %)QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent.
	337	+|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|(% style="width:441px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided.
	338	+|ftr:Footer|ftr:FooterType|(% style="width:441px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
331	331
332	332	**SubmitRegistrationsRequestType: **SubmitRegistrationsRequestType defines the structure of a registry submit registration requests document.
333	333
...	...	@@ -338,14 +338,14 @@
338	338	*** SubmitRegistrationsRequestType
339	339
340	340	Content:
341		-Header, SubmitRegistrationsRequest
342	342
343		-Element Documentation:
	350	+* Header, SubmitRegistrationsRequest
	351	+* Element Documentation:
344	344
345	345	(% style="width:844.294px" %)
346	346	|**Name**|**Type**|(% style="width:377px" %)**Documentation**
347	347	|Header|BasicHeaderType|(% style="width:377px" %)
348		-|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:377px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]]. The [[data source>>doc:sdmx:Glossary.Data source.WebHome]] to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
	356	+|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:377px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
349	349
350	350	**SubmitRegistrationsResponseType: **SubmitRegistrationsResponseType defines the structure of a registry submit registration response document.
351	351
...	...	@@ -356,9 +356,9 @@
356	356	*** SubmitRegistrationsResponseType
357	357
358	358	Content:
359		-Header, SubmitRegistrationsResponse, ftr:Footer?
360	360
361		-Element Documentation:
	368	+* Header, SubmitRegistrationsResponse, ftr:Footer?
	369	+* Element Documentation:
362	362
363	363	(% style="width:847.294px" %)
364	364	|**Name**|(% style="width:210px" %)**Type**|(% style="width:408px" %)**Documentation**
...	...	@@ -375,14 +375,14 @@
375	375	*** QueryRegistrationRequestType
376	376
377	377	Content:
378		-Header, QueryRegistrationRequest
379	379
380		-Element Documentation:
	387	+* Header, QueryRegistrationRequest
	388	+* Element Documentation:
381	381
382	382	(% style="width:847.294px" %)
383	383	|**Name**|**Type**|(% style="width:397px" %)**Documentation**
384	384	|Header|BasicHeaderType|(% style="width:397px" %)
385		-|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:397px" %)QueryRegistrationRequest is used to query the contents of a registry for [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]]. It specifies whether the result set should include [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], or both. The search can be characterized by providing (% style="color:#e74c3c" %)constraints(%%) including [[reference periods>>doc:sdmx:Glossary.Reference period.WebHome]], data regions, and data keys.
	393	+|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:397px" %)QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys.
386	386
387	387	**QueryRegistrationResponseType: **SubmitRegistrationRequestType defines the structure of a registry submit registration response document.
388	388
...	...	@@ -393,6 +393,7 @@
393	393	*** QueryRegistrationResponseType
394	394
395	395	Content:
	404	+
396	396	Header, QueryRegistrationResponse, ftr:Footer?
397	397
398	398	Element Documentation:
...	...	@@ -412,6 +412,7 @@
412	412	*** SubmitStructureRequestType
413	413
414	414	Content:
	424	+
415	415	Header, SubmitStructureRequest
416	416
417	417	Element Documentation:
...	...	@@ -419,7 +419,7 @@
419	419	(% style="width:870.294px" %)
420	420	|**Name**|**Type**|(% style="width:453px" %)**Documentation**
421	421	|Header|BasicHeaderType|(% style="width:453px" %)
422		-|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:453px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, (% style="color:#e74c3c" %)concepts(%%) and [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], etc.) to be submitted may be communicated in-line or be supplied in a referenced [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Structure messages external to the registry. A response will indicate status and contain any relevant error information.
	432	+|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:453px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information.
423	423
424	424	**SubmitStructureResponseType: **SubmitStructureResponseType defines the structure of a registry submit registration response document.
425	425
...	...	@@ -430,9 +430,9 @@
430	430	*** SubmitStructureResponseType
431	431
432	432	Content:
433		-Header, SubmitStructureResponse, ftr:Footer?
434	434
435		-Element Documentation:
	444	+* Header, SubmitStructureResponse, ftr:Footer?
	445	+* Element Documentation:
436	436
437	437	(% style="width:835.294px" %)
438	438	|**Name**|(% style="width:246px" %)**Type**|(% style="width:366px" %)**Documentation**
...	...	@@ -440,7 +440,7 @@
440	440	|SubmitStructureRespo nse|(% style="width:246px" %)ref: SubmitStructureRespo nseType|(% style="width:366px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
441	441	|ftr:Footer|(% style="width:246px" %)ftr:FooterType|(% style="width:366px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
442	442
443		-**SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request document.
	453	+**SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit subscription request document.
444	444
445	445	Derivation:
446	446
...	...	@@ -449,9 +449,9 @@
449	449	*** SubmitSubscriptionsRequestType
450	450
451	451	Content:
452		-Header, SubmitSubscriptionsRequest
453	453
454		-Element Documentation:
	463	+* Header, SubmitSubscriptionsRequest
	464	+* Element Documentation:
455	455
456	456	(% style="width:832.294px" %)
457	457	|**Name**|(% style="width:227px" %)**Type**|(% style="width:319px" %)**Documentation**
...	...	@@ -458,7 +458,7 @@
458	458	|Header|(% style="width:227px" %)BasicHeaderType|(% style="width:319px" %)
459	459	|SubmitSubscriptionsR equest|(% style="width:227px" %)ref: SubmitSubscriptionsR equestType|(% style="width:319px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
460	460
461		-**SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] response document.
	471	+**SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit subscription response document.
462	462
463	463	Derivation:
464	464
...	...	@@ -467,17 +467,17 @@
467	467	*** SubmitSubscriptionsResponseType
468	468
469	469	Content:
470		-Header, SubmitSubscriptionsResponse, ftr:Footer?
471	471
472		-Element Documentation:
	481	+* Header, SubmitSubscriptionsResponse, ftr:Footer?
	482	+* Element Documentation:
473	473
474	474	(% style="width:843.294px" %)
475	475	|**Name**|**Type**|(% style="width:362px" %)**Documentation**
476	476	|Header|BasicHeaderType|(% style="width:362px" %)
477		-|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:362px" %)SubmitSubscriptionsResponse is the response to a submit [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] request. It contains information which describes the success or failure of each [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request, providing any error messages in the event of failure. If successful, it returns the registry URN of the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]], and the subscriber-assigned ID.
	487	+|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:362px" %)SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID.
478	478	|ftr:Footer|ftr:FooterType|(% style="width:362px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
479	479
480		-**QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request document.
	490	+**QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query subscription request document.
481	481
482	482	Derivation:
483	483
...	...	@@ -486,16 +486,16 @@
486	486	*** QuerySubscriptionRequestType
487	487
488	488	Content:
489		-Header, QuerySubscriptionRequest
490	490
491		-Element Documentation:
	500	+* Header, QuerySubscriptionRequest
	501	+* Element Documentation:
492	492
493	493	(% style="width:839.294px" %)
494	494	|(% style="width:230px" %)**Name**|(% style="width:254px" %)**Type**|(% style="width:352px" %)**Documentation**
495	495	|(% style="width:230px" %)Header|(% style="width:254px" %)BasicHeaderType|(% style="width:352px" %)
496		-|(% style="width:230px" %)QuerySubscriptionReq uest|(% style="width:254px" %)ref: QuerySubscriptionReq uestType|(% style="width:352px" %)QuerySubscriptionRequest is used to query the registry for the [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] of a given organisation.
	506	+|(% style="width:230px" %)QuerySubscriptionReq uest|(% style="width:254px" %)ref: QuerySubscriptionReq uestType|(% style="width:352px" %)QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
497	497
498		-**QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] response document.
	508	+**QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query subscription response document.
499	499
500	500	Derivation:
501	501
...	...	@@ -504,17 +504,17 @@
504	504	*** QuerySubscriptionResponseType
505	505
506	506	Content:
507		-Header, QuerySubscriptionResponse, ftr:Footer?
508	508
509		-Element Documentation:
	518	+* Header, QuerySubscriptionResponse, ftr:Footer?
	519	+* Element Documentation:
510	510
511	511	(% style="width:912.294px" %)
512	512	|**Name**|(% style="width:304px" %)**Type**|(% style="width:336px" %)**Documentation**
513	513	|Header|(% style="width:304px" %)BasicHeaderType|(% style="width:336px" %)
514		-|QuerySubscriptionRes ponse|(% style="width:304px" %)ref: QuerySubscriptionRes ponseType|(% style="width:336px" %)QuerySubscriptionResponse is sent as a response to a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] query. If the query is successful, the details of all [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] for the requested organisation are sent.
	524	+|QuerySubscriptionRes ponse|(% style="width:304px" %)ref: QuerySubscriptionRes ponseType|(% style="width:336px" %)QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent.
515	515	|ftr:Footer|(% style="width:304px" %)ftr:FooterType|(% style="width:336px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
516	516
517		-**NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry [[notification>>doc:sdmx:Glossary.Notification.WebHome]] document.
	527	+**NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry notification document.
518	518
519	519	Derivation:
520	520
...	...	@@ -523,14 +523,14 @@
523	523	*** NotifyRegistryEventType
524	524
525	525	Content:
526		-Header, NotifyRegistryEvent
527	527
528		-Element Documentation:
	537	+* Header, NotifyRegistryEvent
	538	+* Element Documentation:
529	529
530	530	(% style="width:836.294px" %)
531	531	|**Name**|**Type**|(% style="width:473px" %)**Documentation**
532	532	|Header|BasicHeaderType|(% style="width:473px" %)
533		-|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|(% style="width:473px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] that triggered the [[notification>>doc:sdmx:Glossary.Notification.WebHome]] are always sent. Optionally, the details of the changed object may also be provided.
	543	+|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|(% style="width:473px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided.
534	534
535	535	**DataQueryType: **DataQueryType defines the structure of a data query message.
536	536
...	...	@@ -540,9 +540,9 @@
540	540	** DataQueryType
541	541
542	542	Content:
543		-Header, Query
544	544
545		-Element Documentation:
	554	+* Header, Query
	555	+* Element Documentation:
546	546
547	547	(% style="width:839.294px" %)
548	548	|(% style="width:244px" %)**Name**|(% style="width:262px" %)**Type**|(% style="width:330px" %)**Documentation**
...	...	@@ -558,730 +558,730 @@
558	558	*** GenericDataQueryType
559	559
560	560	Content:
	571	+
561	561	Header, Query
562	562
563	563	Element Documentation:
564	564
565		-(% style="width:833.294px" %)
566		-|(% style="width:213px" %)**Name**|(% style="width:243px" %)**Type**|(% style="width:374px" %)**Documentation**
567		-|(% style="width:213px" %)Header|(% style="width:243px" %)BasicHeaderType|(% style="width:374px" %)
568		-|(% style="width:213px" %)Query|(% style="width:243px" %)qry: GenericDataQueryType|(% style="width:374px" %)
	576	+|**Name**|**Type**|**Documentation**
	577	+|Header|BasicHeaderType|
	578	+|Query|qry: GenericDataQueryType|
569	569
570	570	**GenericTimeSeriesDataQueryType: **GenericTimeSeriesDataQueryType defines the structure of a time series generic data query message.
571	571
572	572	Derivation:
573	573
574		-* //MessageType// (restriction)
575		-** DataQueryType (restriction)
576		-*** GenericDataQueryType (restriction)
577		-**** GenericTimeSeriesDataQueryType
	584	+//MessageType// (restriction)
	585	+ DataQueryType (restriction)
	586	+ GenericDataQueryType (restriction)
	587	+ GenericTimeSeriesDataQueryType
578	578
579	579	Content:
	590	+
580	580	Header, Query
581	581
582	582	Element Documentation:
583	583
584		-(% style="width:909.294px" %)
585		-|(% style="width:221px" %)**Name**|(% style="width:305px" %)**Type**|(% style="width:380px" %)**Documentation**
586		-|(% style="width:221px" %)Header|(% style="width:305px" %)BasicHeaderType|(% style="width:380px" %)
587		-|(% style="width:221px" %)Query|(% style="width:305px" %)qry: GenericTimeSeriesDat aQueryType|(% style="width:380px" %)
	595	+|**Name**|**Type**|**Documentation**
	596	+|Header|BasicHeaderType|
	597	+|Query|qry: GenericTimeSeriesDat aQueryType|
588	588
589	589	**StructureSpecificTimeSeriesDataQueryType: **StructureSpecificTimeSeriesDataQueryType defines the structure of a time series generic data query message.
590	590
591	591	Derivation:
592	592
593		-* //MessageType// (restriction)
594		-** DataQueryType (restriction)
595		-*** StructureSpecificTimeSeriesDataQueryType
	603	+//MessageType// (restriction)
	604	+ DataQueryType (restriction)
	605	+ StructureSpecificTimeSeriesDataQueryType
596	596
597	597	Content:
	608	+
598	598	Header, Query
599	599
600	600	Element Documentation:
601	601
602		-(% style="width:903.294px" %)
603		-|(% style="width:189px" %)**Name**|(% style="width:259px" %)**Type**|(% style="width:452px" %)**Documentation**
604		-|(% style="width:189px" %)Header|(% style="width:259px" %)BasicHeaderType|(% style="width:452px" %)
605		-|(% style="width:189px" %)Query|(% style="width:259px" %)qry: TimeSeriesDataQueryType|(% style="width:452px" %)
	613	+|**Name**|**Type**|**Documentation**
	614	+|Header|BasicHeaderType|
	615	+|Query|qry: TimeSeriesDataQueryT ype|
606	606
607		-**MetadataQueryType: **MetadataQueryType defines the structure of a [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] query message.
	617	+**MetadataQueryType: **MetadataQueryType defines the structure of a reference metadata query message.
608	608
609	609	Derivation:
610	610
611		-* //MessageType// (restriction)
612		-** MetadataQueryType
	621	+//MessageType// (restriction)
	622	+ MetadataQueryType
613	613
614	614	Content:
	625	+
615	615	Header, Query
616	616
617	617	Element Documentation:
618	618
619		-(% style="width:858.294px" %)
620		-|(% style="width:138px" %)**Name**|(% style="width:246px" %)**Type**|(% style="width:471px" %)**Documentation**
621		-|(% style="width:138px" %)Header|(% style="width:246px" %)BasicHeaderType|(% style="width:471px" %)
622		-|(% style="width:138px" %)Query|(% style="width:246px" %)qry: MetadataQueryType|(% style="width:471px" %)
	630	+|**Name**|**Type**|**Documentation**
	631	+|Header|BasicHeaderType|
	632	+|Query|qry: MetadataQueryType|
623	623
624	624	**DataSchemaQueryType: **DataSchemaQueryType defines the structure of a data schema query message.
625	625
626	626	Derivation:
627	627
628		-* //MessageType// (restriction)
629		-** DataSchemaQueryType
	638	+//MessageType// (restriction)
	639	+ DataSchemaQueryType
630	630
631	631	Content:
	642	+
632	632	Header, Query
633	633
634	634	Element Documentation:
635	635
636		-(% style="width:895.294px" %)
637		-|(% style="width:185px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:413px" %)**Documentation**
638		-|(% style="width:185px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:413px" %)
639		-|(% style="width:185px" %)Query|(% style="width:294px" %)qry: DataSchemaQueryType|(% style="width:413px" %)
	647	+|**Name**|**Type**|**Documentation**
	648	+|Header|BasicHeaderType|
	649	+|Query|qry: DataSchemaQueryType|
640	640
641	641	**MetadataSchemaQueryType: **MetadataSchemaQueryType defines the structure of a metadata schema query message.
642	642
643	643	Derivation:
644	644
645		-* //MessageType// (restriction)
646		-** MetadataSchemaQueryType
	655	+//MessageType// (restriction)
	656	+ MetadataSchemaQueryType
647	647
648	648	Content:
	659	+
649	649	Header, Query
650	650
651	651	Element Documentation:
652	652
653		-(% style="width:897.294px" %)
654		-|(% style="width:166px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:447px" %)**Documentation**
655		-|(% style="width:166px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:447px" %)
656		-|(% style="width:166px" %)Query|(% style="width:281px" %)qry: MetadataSchemaQueryType|(% style="width:447px" %)
	664	+|**Name**|**Type**|**Documentation**
	665	+|Header|BasicHeaderType|
	666	+|Query|qry: MetadataSchemaQueryT ype|
657	657
658	658	**StructuresQueryType: **StructuresQueryType defines the structure of a structures query message.
659	659
660	660	Derivation:
661	661
662		-* //MessageType// (restriction)
663		-** StructuresQueryType
	672	+//MessageType// (restriction)
	673	+ StructuresQueryType
664	664
665	665	Content:
	676	+
666	666	Header, Query
667	667
668	668	Element Documentation:
669	669
670		-(% style="width:886.294px" %)
671		-|(% style="width:223px" %)**Name**|(% style="width:255px" %)**Type**|(% style="width:405px" %)**Documentation**
672		-|(% style="width:223px" %)Header|(% style="width:255px" %)BasicHeaderType|(% style="width:405px" %)
673		-|(% style="width:223px" %)Query|(% style="width:255px" %)qry: StructuresQueryType|(% style="width:405px" %)
	681	+|**Name**|**Type**|**Documentation**
	682	+|Header|BasicHeaderType|
	683	+|Query|qry: StructuresQueryType|
674	674
675		-**DataflowQueryType: **DataflowQueryType defines the structure of a [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] query message.
	685	+**DataflowQueryType: **DataflowQueryType defines the structure of a dataflow query message.
676	676
677	677	Derivation:
678	678
679		-* //MessageType// (restriction)
680		-** DataflowQueryType
	689	+//MessageType// (restriction)
	690	+ DataflowQueryType
681	681
682	682	Content:
	693	+
683	683	Header, Query
684	684
685	685	Element Documentation:
686	686
687		-(% style="width:888.294px" %)
688		-|(% style="width:176px" %)**Name**|(% style="width:260px" %)**Type**|(% style="width:449px" %)**Documentation**
689		-|(% style="width:176px" %)Header|(% style="width:260px" %)BasicHeaderType|(% style="width:449px" %)
690		-|(% style="width:176px" %)Query|(% style="width:260px" %)qry: DataflowQueryType|(% style="width:449px" %)
	698	+|**Name**|**Type**|**Documentation**
	699	+|Header|BasicHeaderType|
	700	+|Query|qry: DataflowQueryType|
691	691
692		-**MetadataflowQueryType: **MetadataflowQueryType defines the structure of a [[metadata flow>>doc:sdmx:Glossary.Metadataflow.WebHome]] query message.
	702	+**MetadataflowQueryType: **MetadataflowQueryType defines the structure of a metadata flow query message.
693	693
694	694	Derivation:
695	695
696		-* //MessageType// (restriction)
697		-** MetadataflowQueryType
	706	+//MessageType// (restriction)
	707	+ MetadataflowQueryType
698	698
699	699	Content:
	710	+
700	700	Header, Query
701	701
702	702	Element Documentation:
703	703
704		-(% style="width:886.294px" %)
705		-|(% style="width:199px" %)**Name**|(% style="width:296px" %)**Type**|(% style="width:388px" %)**Documentation**
706		-|(% style="width:199px" %)Header|(% style="width:296px" %)BasicHeaderType|(% style="width:388px" %)
707		-|(% style="width:199px" %)Query|(% style="width:296px" %)qry: MetadataflowQueryType|(% style="width:388px" %)
	715	+|**Name**|**Type**|**Documentation**
	716	+|Header|BasicHeaderType|
	717	+|Query|qry: MetadataflowQueryTyp e|
708	708
709	709	**DataStructureQueryType: **KeyFamilyQueryType defines the structure of a data structure query message.
710	710
711	711	Derivation:
712	712
713		-* //MessageType// (restriction)
714		-** DataStructureQueryType
	723	+//MessageType// (restriction)
	724	+ DataStructureQueryType
715	715
716	716	Content:
	727	+
717	717	Header, Query
718	718
719	719	Element Documentation:
720	720
721		-(% style="width:901.294px" %)
722		-|(% style="width:202px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:393px" %)**Documentation**
723		-|(% style="width:202px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:393px" %)
724		-|(% style="width:202px" %)Query|(% style="width:303px" %)qry: DataStructureQueryType|(% style="width:393px" %)
	732	+|**Name**|**Type**|**Documentation**
	733	+|Header|BasicHeaderType|
	734	+|Query|qry: DataStructureQueryTy pe|
725	725
726	726	**MetadataStructureQueryType: **MetadataStructureQueryType defines the structure of a metadata structure query message.
727	727
728	728	Derivation:
729	729
730		-* //MessageType// (restriction)
731		-** MetadataStructureQueryType
	740	+//MessageType// (restriction)
	741	+ MetadataStructureQueryType
732	732
733	733	Content:
	744	+
734	734	Header, Query
735	735
736	736	Element Documentation:
737	737
738		-(% style="width:904.294px" %)
739		-|(% style="width:226px" %)**Name**|(% style="width:275px" %)**Type**|(% style="width:400px" %)**Documentation**
740		-|(% style="width:226px" %)Header|(% style="width:275px" %)BasicHeaderType|(% style="width:400px" %)
741		-|(% style="width:226px" %)Query|(% style="width:275px" %)qry: MetadataStructureQueryType|(% style="width:400px" %)
	749	+|**Name**|**Type**|**Documentation**
	750	+|Header|BasicHeaderType|
	751	+|Query|qry: MetadataStructureQue ryType|
742	742
743		-**CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] query message.
	753	+**CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a category scheme query message.
744	744
745	745	Derivation:
746	746
747		-* //MessageType// (restriction)
748		-** CategorySchemeQueryType
	757	+//MessageType// (restriction)
	758	+ CategorySchemeQueryType
749	749
750	750	Content:
	761	+
751	751	Header, Query
752	752
753	753	Element Documentation:
754	754
755		-(% style="width:915.294px" %)
756		-|(% style="width:196px" %)**Name**|(% style="width:347px" %)**Type**|(% style="width:369px" %)**Documentation**
757		-|(% style="width:196px" %)Header|(% style="width:347px" %)BasicHeaderType|(% style="width:369px" %)
758		-|(% style="width:196px" %)Query|(% style="width:347px" %)qry: CategorySchemeQueryType|(% style="width:369px" %)
	766	+|**Name**|**Type**|**Documentation**
	767	+|Header|BasicHeaderType|
	768	+|Query|qry: CategorySchemeQueryT ype|
759	759
760		-**ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] query message.
	770	+**ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a concept scheme query message.
761	761
762	762	Derivation:
763	763
764		-* //MessageType// (restriction)
765		-** ConceptSchemeQueryType
	774	+//MessageType// (restriction)
	775	+ ConceptSchemeQueryType
766	766
767	767	Content:
	778	+
768	768	Header, Query
769	769
770	770	Element Documentation:
771	771
772		-(% style="width:895.294px" %)
773		-|(% style="width:222px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:331px" %)**Documentation**
774		-|(% style="width:222px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:331px" %)
775		-|(% style="width:222px" %)Query|(% style="width:339px" %)qry: ConceptSchemeQueryType|(% style="width:331px" %)
	783	+|**Name**|**Type**|**Documentation**
	784	+|Header|BasicHeaderType|
	785	+|Query|qry: ConceptSchemeQueryTy pe|
776	776
777		-**CodelistQueryType: **CodelistQueryType defines the structure of a [[codelist>>doc:sdmx:Glossary.Code list.WebHome]] query message.
	787	+**CodelistQueryType: **CodelistQueryType defines the structure of a codelist query message.
778	778
779	779	Derivation:
780	780
781		-* //MessageType// (restriction)
782		-** CodelistQueryType
	791	+//MessageType// (restriction)
	792	+ CodelistQueryType
783	783
784	784	Content:
	795	+
785	785	Header, Query
786	786
787	787	Element Documentation:
788	788
789		-(% style="width:911.294px" %)
790		-|(% style="width:204px" %)**Name**|(% style="width:295px" %)**Type**|(% style="width:409px" %)**Documentation**
791		-|(% style="width:204px" %)Header|(% style="width:295px" %)BasicHeaderType|(% style="width:409px" %)
792		-|(% style="width:204px" %)Query|(% style="width:295px" %)qry:CodelistQueryType|(% style="width:409px" %)
	800	+|**Name**|**Type**|**Documentation**
	801	+|Header|BasicHeaderType|
	802	+|Query|qry: CodelistQueryType|
793	793
794		-**HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical [[codelist>>doc:sdmx:Glossary.Code list.WebHome]] query message.
	804	+**HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical codelist query message.
795	795
796	796	Derivation:
797	797
798		-* //MessageType// (restriction)
799		-** HierarchicalCodelistQueryType
	808	+//MessageType// (restriction)
	809	+ HierarchicalCodelistQueryType
800	800
801	801	Content:
	812	+
802	802	Header, Query
803	803
804	804	Element Documentation:
805	805
806		-(% style="width:906.294px" %)
807		-|(% style="width:191px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:430px" %)**Documentation**
808		-|(% style="width:191px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:430px" %)
809		-|(% style="width:191px" %)Query|(% style="width:281px" %)qry: HierarchicalCodelist QueryType|(% style="width:430px" %)
	817	+|**Name**|**Type**|**Documentation**
	818	+|Header|BasicHeaderType|
	819	+|Query|qry: HierarchicalCodelist QueryType|
810	810
811	811	**OrganisationSchemeQueryType: **OrganisationSchemeQueryType defines the structure of an organisation scheme query message.
812	812
813	813	Derivation:
814	814
815		-* //MessageType// (restriction)
816		-** OrganisationSchemeQueryType
	825	+//MessageType// (restriction)
	826	+ OrganisationSchemeQueryType
817	817
818	818	Content:
	829	+
819	819	Header, Query
820	820
821	821	Element Documentation:
822	822
823		-(% style="width:891.294px" %)
824		-|(% style="width:174px" %)**Name**|(% style="width:292px" %)**Type**|(% style="width:422px" %)**Documentation**
825		-|(% style="width:174px" %)Header|(% style="width:292px" %)BasicHeaderType|(% style="width:422px" %)
826		-|(% style="width:174px" %)Query|(% style="width:292px" %)qry: OrganisationSchemeQueryType|(% style="width:422px" %)
	834	+|**Name**|**Type**|**Documentation**
	835	+|Header|BasicHeaderType|
	836	+|Query|qry: OrganisationSchemeQu eryType|
827	827
828	828	**ReportingTaxonomyQueryType: **ReportingTaxonomyQueryType defines the structure of a reporting taxonomy query message.
829	829
830	830	Derivation:
831	831
832		-* //MessageType// (restriction)
833		-** ReportingTaxonomyQueryType
	842	+//MessageType// (restriction)
	843	+ ReportingTaxonomyQueryType
834	834
835	835	Content:
	846	+
836	836	Header, Query
837	837
838	838	Element Documentation:
839	839
840		-(% style="width:916.294px" %)
841		-|(% style="width:162px" %)**Name**|(% style="width:318px" %)**Type**|(% style="width:434px" %)**Documentation**
842		-|(% style="width:162px" %)Header|(% style="width:318px" %)BasicHeaderType|(% style="width:434px" %)
843		-|(% style="width:162px" %)Query|(% style="width:318px" %)qry: ReportingTaxonomyQueryType|(% style="width:434px" %)
	851	+|**Name**|**Type**|**Documentation**
	852	+|Header|BasicHeaderType|
	853	+|Query|qry: ReportingTaxonomyQue ryType|
844	844
845		-**StructureSetQueryType: **StructureSetQueryType defines the structure of a [[structure set>>doc:sdmx:Glossary.Structure set.WebHome]] query message.
	855	+**StructureSetQueryType: **StructureSetQueryType defines the structure of a structure set query message.
846	846
847	847	Derivation:
848	848
849		-* //MessageType// (restriction)
850		-** StructureSetQueryType
	859	+//MessageType// (restriction)
	860	+ StructureSetQueryType
851	851
852	852	Content:
	863	+
853	853	Header, Query
854	854
855	855	Element Documentation:
856	856
857		-(% style="width:896.294px" %)
858		-|(% style="width:182px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:417px" %)**Documentation**
859		-|(% style="width:182px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:417px" %)
860		-|(% style="width:182px" %)Query|(% style="width:294px" %)qry: StructureSetQueryType|(% style="width:417px" %)
	868	+|**Name**|**Type**|**Documentation**
	869	+|Header|BasicHeaderType|
	870	+|Query|qry: StructureSetQueryTyp e|
861	861
862	862	**ProcessQueryType: **CategorizationQueryType defines the structure of a categorization query message.
863	863
864	864	Derivation:
865	865
866		-* //MessageType// (restriction)
867		-** ProcessQueryType
	876	+//MessageType// (restriction)
	877	+ ProcessQueryType
868	868
869	869	Content:
	880	+
870	870	Header, Query
871	871
872	872	Element Documentation:
873	873
874		-(% style="width:907.294px" %)
875		-|(% style="width:189px" %)**Name**|(% style="width:394px" %)**Type**|(% style="width:321px" %)**Documentation**
876		-|(% style="width:189px" %)Header|(% style="width:394px" %)BasicHeaderType|(% style="width:321px" %)
877		-|(% style="width:189px" %)Query|(% style="width:394px" %)qry:ProcessQueryType|(% style="width:321px" %)
	885	+|**Name**|**Type**|**Documentation**
	886	+|Header|BasicHeaderType|
	887	+|Query|qry:ProcessQueryType|
878	878
879	879	**CategorisationQueryType: **CategorisationQueryType defines the structure of a categorisation query message.
880	880
881	881	Derivation:
882	882
883		-* //MessageType// (restriction)
884		-** CategorisationQueryType
	893	+//MessageType// (restriction)
	894	+ CategorisationQueryType
885	885
886	886	Content:
	897	+
887	887	Header, Query
888	888
889	889	Element Documentation:
890	890
891		-(% style="width:897.294px" %)
892		-|(% style="width:230px" %)**Name**|(% style="width:300px" %)**Type**|(% style="width:363px" %)**Documentation**
893		-|(% style="width:230px" %)Header|(% style="width:300px" %)BasicHeaderType|(% style="width:363px" %)
894		-|(% style="width:230px" %)Query|(% style="width:300px" %)qry: CategorisationQueryType|(% style="width:363px" %)
	902	+|**Name**|**Type**|**Documentation**
	903	+|Header|BasicHeaderType|
	904	+|Query|qry: CategorisationQueryT ype|
895	895
896		-**ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] query message.
	906	+**ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a provision agreement query message.
897	897
898	898	Derivation:
899	899
900		-* //MessageType// (restriction)
901		-** ProvisionAgreementQueryType
	910	+//MessageType// (restriction)
	911	+ ProvisionAgreementQueryType
902	902
903	903	Content:
	914	+
904	904	Header, Query
905	905
906	906	Element Documentation:
907	907
908		-(% style="width:902.294px" %)
909		-|(% style="width:142px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:418px" %)**Documentation**
910		-|(% style="width:142px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:418px" %)
911		-|(% style="width:142px" %)Query|(% style="width:339px" %)qry: ProvisionAgreementQueryType|(% style="width:418px" %)
	919	+|**Name**|**Type**|**Documentation**
	920	+|Header|BasicHeaderType|
	921	+|Query|qry: ProvisionAgreementQu eryType|
912	912
913		-**ConstraintQueryType: **ConstraintQueryType defines the structure of a (% style="color:#e74c3c" %)constraint(%%) query message.
	923	+**ConstraintQueryType: **ConstraintQueryType defines the structure of a constraint query message.
914	914
915	915	Derivation:
916	916
917		-* //MessageType// (restriction)
918		-** ConstraintQueryType
	927	+//MessageType// (restriction)
	928	+ ConstraintQueryType
919	919
920	920	Content:
	931	+
921	921	Header, Query
922	922
923	923	Element Documentation:
924	924
925		-(% style="width:902.294px" %)
926		-|(% style="width:167px" %)**Name**|(% style="width:287px" %)**Type**|(% style="width:445px" %)**Documentation**
927		-|(% style="width:167px" %)Header|(% style="width:287px" %)BasicHeaderType|(% style="width:445px" %)
928		-|(% style="width:167px" %)Query|(% style="width:287px" %)qry: ConstraintQueryType|(% style="width:445px" %)
	936	+|**Name**|**Type**|**Documentation**
	937	+|Header|BasicHeaderType|
	938	+|Query|qry: ConstraintQueryType|
929	929
930	930	**TransformationSchemeQueryType: **TransformationSchemeQueryType defines the structure of a transformation scheme query message.
931	931
932	932	Derivation:
933	933
934		-* //MessageType// (restriction)
935		-** TransformationSchemeQueryType
	944	+//MessageType// (restriction)
	945	+ TransformationSchemeQueryType
936	936
937	937	Content:
	948	+
938	938	Header, Query
939	939
940	940	Element Documentation:
941	941
942		-(% style="width:833.294px" %)
943		-|(% style="width:165px" %)**Name**|(% style="width:325px" %)**Type**|(% style="width:340px" %)**Documentation**
944		-|(% style="width:165px" %)Header|(% style="width:325px" %)BasicHeaderType|(% style="width:340px" %)
945		-|(% style="width:165px" %)Query|(% style="width:325px" %)qry: TransformationSchemeQueryType|(% style="width:340px" %)
	953	+|**Name**|**Type**|**Documentation**
	954	+|Header|BasicHeaderType|
	955	+|Query|qry: TransformationScheme QueryType|
946	946
947		-**VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] mappings scheme query message.
	957	+**VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a VTL mappings scheme query message.
948	948
949	949	Derivation:
950	950
951		-* //MessageType// (restriction)
952		-** VtlMappingSchemeQueryType
	961	+//MessageType// (restriction)
	962	+ VtlMappingSchemeQueryType
953	953
954	954	Content:
	965	+
955	955	Header, Query
956	956
957	957	Element Documentation:
958	958
959		-(% style="width:843.294px" %)
960		-|(% style="width:164px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:373px" %)**Documentation**
961		-|(% style="width:164px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:373px" %)
962		-|(% style="width:164px" %)Query|(% style="width:303px" %)qry: VtlMappingSchemeQueryType|(% style="width:373px" %)
	970	+|**Name**|**Type**|**Documentation**
	971	+|Header|BasicHeaderType|
	972	+|Query|qry: VtlMappingSchemeQuer yType|
963	963
964	964	**NamePersonalisationSchemeQueryType: **NamePersonalisationSchemeQueryType defines the structure of a name personalisation scheme query message.
965	965
966	966	Derivation:
967	967
968		-* //MessageType// (restriction)
969		-** NamePersonalisationSchemeQueryType
	978	+//MessageType// (restriction)
	979	+ NamePersonalisationSchemeQueryType
970	970
971	971	Content:
	982	+
972	972	Header, Query
973	973
974	974	Element Documentation:
975	975
976		-(% style="width:895.294px" %)
977		-|(% style="width:186px" %)**Name**|(% style="width:363px" %)**Type**|(% style="width:343px" %)**Documentation**
978		-|(% style="width:186px" %)Header|(% style="width:363px" %)BasicHeaderType|(% style="width:343px" %)
979		-|(% style="width:186px" %)Query|(% style="width:363px" %)qry: NamePersonalisationSchemeQueryType|(% style="width:343px" %)
	987	+|**Name**|**Type**|**Documentation**
	988	+|Header|BasicHeaderType|
	989	+|Query|qry: NamePersonalisationS chemeQueryType|
980	980
981	981	**RulesetSchemeQueryType: **RulesetSchemeQueryType defines the structure of a ruleset scheme query message.
982	982
983	983	Derivation:
984	984
985		-* //MessageType// (restriction)
986		-** RulesetSchemeQueryType
	995	+//MessageType// (restriction)
	996	+ RulesetSchemeQueryType
987	987
988	988	Content:
	999	+
989	989	Header, Query
990	990
991	991	Element Documentation:
992	992
993		-(% style="width:886.294px" %)
994		-|(% style="width:152px" %)**Name**|(% style="width:311px" %)**Type**|(% style="width:420px" %)**Documentation**
995		-|(% style="width:152px" %)Header|(% style="width:311px" %)BasicHeaderType|(% style="width:420px" %)
996		-|(% style="width:152px" %)Query|(% style="width:311px" %)qry: RulesetSchemeQueryType|(% style="width:420px" %)
	1004	+|**Name**|**Type**|**Documentation**
	1005	+|Header|BasicHeaderType|
	1006	+|Query|qry: RulesetSchemeQueryTy pe|
997	997
998	998	**UserDefinedOperatorSchemeQueryType: **UserDefinedOperatorSchemeQueryType defines the structure of a user defined operator scheme query message.
999	999
1000	1000	Derivation:
1001	1001
1002		-* //MessageType// (restriction)
1003		-** UserDefinedOperatorSchemeQueryType
	1012	+//MessageType// (restriction)
	1013	+ UserDefinedOperatorSchemeQueryType
1004	1004
1005	1005	Content:
	1016	+
1006	1006	Header, Query
1007	1007
1008	1008	Element Documentation:
1009	1009
1010		-(% style="width:866.294px" %)
1011		-|(% style="width:174px" %)**Name**|(% style="width:358px" %)**Type**|(% style="width:331px" %)**Documentation**
1012		-|(% style="width:174px" %)Header|(% style="width:358px" %)BasicHeaderType|(% style="width:331px" %)
1013		-|(% style="width:174px" %)Query|(% style="width:358px" %)qry: UserDefinedOperatorSchemeQueryType|(% style="width:331px" %)
	1021	+|**Name**|**Type**|**Documentation**
	1022	+|Header|BasicHeaderType|
	1023	+|Query|qry: UserDefinedOperatorS chemeQueryType|
1014	1014
1015	1015	**CustomTypeSchemeQueryType: **CustomTypeSchemeQueryType defines the structure of a custom type scheme query message.
1016	1016
1017	1017	Derivation:
1018	1018
1019		-* //MessageType// (restriction)
1020		-** CustomTypeSchemeQueryType
	1029	+//MessageType// (restriction)
	1030	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] CustomTypeSchemeQueryType
1021	1021
1022	1022	Content:
	1033	+
1023	1023	Header, Query
1024	1024
1025	1025	Element Documentation:
1026	1026
1027		-(% style="width:828.294px" %)
1028		-|(% style="width:200px" %)**Name**|(% style="width:308px" %)**Type**|(% style="width:317px" %)**Documentation**
1029		-|(% style="width:200px" %)Header|(% style="width:308px" %)BasicHeaderType|(% style="width:317px" %)
1030		-|(% style="width:200px" %)Query|(% style="width:308px" %)qry: CustomTypeSchemeQueryType|(% style="width:317px" %)
	1038	+|**Name**|**Type**|**Documentation**
	1039	+|Header|BasicHeaderType|
	1040	+|Query|qry: CustomTypeSchemeQuer yType|
1031	1031
1032	1032	**ErrorType: **ErrorType describes the structure of an error response.
1033	1033
1034	1034	Content:
	1045	+
1035	1035	ErrorMessage+
1036	1036
1037	1037	Element Documentation:
1038	1038
1039		-(% style="width:899.294px" %)
1040		-|**Name**|**Type**|(% style="width:546px" %)**Documentation**
1041		-|ErrorMessage|com: CodedStatusMessageTy pe|(% style="width:546px" %)ErrorMessage contains the error message. It can occur multiple times to communicate message for multiple errors, or to communicate the error message in parallel languages. If both messages for multiple errors and parallel language messages are used, then each error message should be given a [[code>>doc:sdmx:Glossary.Code.WebHome]] in order to distinguish message for unique errors.
	1050	+|**Name**|**Type**|**Documentation**
	1051	+|ErrorMessage|com: CodedStatusMessageTy pe|ErrorMessage contains the error message. It can occur multiple times to communicate message for multiple errors, or to communicate the error message in parallel languages. If both messages for multiple errors and parallel language messages are used, then each error message should be given a code in order to distinguish message for unique errors.
1042	1042
1043	1043	**//BaseHeaderType//: **BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this
1044	1044
1045	1045	Content:
	1056	+
1046	1046	ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure*, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
1047	1047
1048	1048	Element Documentation:
1049	1049
1050		-(% style="width:891.294px" %)
1051		-|**Name**|**Type**|(% style="width:552px" %)**Documentation**
1052		-|ID|com:IDType|(% style="width:552px" %)ID identifies an identification for the message, assigned by the sender.
1053		-|Test|xs:boolean|(% style="width:552px" %)Test indicates whether the message is for test purposes or not.
1054		-|Prepared|HeaderTimeType|(% style="width:552px" %)Prepared is the date the message was prepared.
1055		-|Sender|SenderType|(% style="width:552px" %)Sender is information about the party that is transmitting the message.
1056		-|Receiver|PartyType|(% style="width:552px" %)Receiver is information about the party that is the intended recipient of the message.
1057		-|com:Name|com:TextType|(% style="width:552px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1058		-|Structure|//com: PayloadStructureType//|(% style="width:552px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1059		-|DataProvider|com: DataProviderReferenceType|(% style="width:552px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1060		-|DataSetAction|com:ActionType|(% style="width:552px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1061		-|DataSetID|com:IDType|(% style="width:552px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1062		-|Extracted|xs:dateTime|(% style="width:552px" %)Extracted is a time-stamp from the system rendering the data.
1063		-|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1064		-|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1065		-|EmbargoDate|xs:dateTime|(% style="width:552px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.
1066		-|Source|com:TextType|(% style="width:552px" %)Source provides human-readable information about the source of the data.
	1061	+|**Name**|**Type**|**Documentation**
	1062	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1063	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1064	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1065	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1066	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1067	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1068	+|Structure|//com: PayloadStructureType//|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
	1069	+|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
	1070	+|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
	1071	+|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
	1072	+|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
	1073	+|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1074	+|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1075	+|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
	1076	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1067	1067
1068		-**StructureHeaderType: **StructureHeaderType defines the structure for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] messages.
	1078	+**StructureHeaderType: **StructureHeaderType defines the structure for structural metadata messages.
1069	1069
1070	1070	Derivation:
1071	1071
1072		-* //BaseHeaderType// (restriction)
1073		-** StructureHeaderType
	1082	+//BaseHeaderType// (restriction)
	1083	+ StructureHeaderType
1074	1074
1075	1075	Content:
	1086	+
1076	1076	ID, Test, Prepared, Sender, Receiver*, com:Name*, Source*
1077	1077
1078	1078	Element Documentation:
1079	1079
1080		-(% style="width:1099.29px" %)
1081		-|**Name**|(% style="width:224px" %)**Type**|(% style="width:663px" %)**Documentation**
1082		-|ID|(% style="width:224px" %)com:IDType|(% style="width:663px" %)ID identifies an identification for the message, assigned by the sender.
1083		-|Test|(% style="width:224px" %)xs:boolean|(% style="width:663px" %)Test indicates whether the message is for test purposes or not.
1084		-|Prepared|(% style="width:224px" %)HeaderTimeType|(% style="width:663px" %)Prepared is the date the message was prepared.
1085		-|Sender|(% style="width:224px" %)SenderType|(% style="width:663px" %)Sender is information about the party that is transmitting the message.
1086		-|Receiver|(% style="width:224px" %)PartyType|(% style="width:663px" %)Receiver is information about the party that is the intended recipient of the message.
1087		-|com:Name|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1088		-|Source|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Source provides human-readable information about the source of the data.
	1091	+|**Name**|**Type**|**Documentation**
	1092	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1093	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1094	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1095	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1096	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1097	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1098	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1089	1089
1090	1090	**GenericDataHeaderType: **GenericDataHeaderType defines the header structure for a generic data message.
1091	1091
1092	1092	Derivation:
1093	1093
1094		-* //BaseHeaderType// (restriction)
1095		-** GenericDataHeaderType
	1104	+//BaseHeaderType// (restriction)
	1105	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataHeaderType
1096	1096
1097	1097	Content:
	1108	+
1098	1098	ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
1099	1099
1100	1100	Element Documentation:
1101	1101
1102		-(% style="width:895.294px" %)
1103		-|**Name**|**Type**|(% style="width:556px" %)**Documentation**
1104		-|ID|com:IDType|(% style="width:556px" %)ID identifies an identification for the message, assigned by the sender.
1105		-|Test|xs:boolean|(% style="width:556px" %)Test indicates whether the message is for test purposes or not.
1106		-|Prepared|HeaderTimeType|(% style="width:556px" %)Prepared is the date the message was prepared.
1107		-|Sender|SenderType|(% style="width:556px" %)Sender is information about the party that is transmitting the message.
1108		-|Receiver|PartyType|(% style="width:556px" %)Receiver is information about the party that is the intended recipient of the message.
1109		-|com:Name|com:TextType|(% style="width:556px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1110		-|Structure|com: GenericDataStructureType|(% style="width:556px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1111		-|DataProvider|com: DataProviderReferenceType|(% style="width:556px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1112		-|DataSetAction|com:ActionType|(% style="width:556px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1113		-|DataSetID|com:IDType|(% style="width:556px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1114		-|Extracted|xs:dateTime|(% style="width:556px" %)Extracted is a time-stamp from the system rendering the data.
1115		-|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1116		-|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1117		-|EmbargoDate|xs:dateTime|(% style="width:556px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.
1118		-|Source|com:TextType|(% style="width:556px" %)Source provides human-readable information about the source of the data.
	1113	+|**Name**|**Type**|**Documentation**
	1114	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1115	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1116	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1117	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1118	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1119	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1120	+|Structure|com: GenericDataStructure Type|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
	1121	+|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
	1122	+|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
	1123	+|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
	1124	+|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
	1125	+|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1126	+|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1127	+|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
	1128	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1119	1119
1120	1120	**GenericTimeSeriesDataHeaderType: **GenericTimeSeriesDataHeaderType defines the header structure for a time series only generic data message.
1121	1121
1122	1122	Derivation:
1123	1123
1124		-* //BaseHeaderType// (restriction)
1125		-** GenericDataHeaderType (restriction)
1126		-*** GenericTimeSeriesDataHeaderType
	1134	+//BaseHeaderType// (restriction)
	1135	+ GenericDataHeaderType (restriction)
	1136	+ GenericTimeSeriesDataHeaderType
1127	1127
1128	1128	Content:
	1139	+
1129	1129	ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
1130	1130
1131	1131	Element Documentation:
1132	1132
1133		-(% style="width:926.294px" %)
1134		-|**Name**|**Type**|(% style="width:497px" %)**Documentation**
1135		-|ID|com:IDType|(% style="width:497px" %)ID identifies an identification for the message, assigned by the sender.
1136		-|Test|xs:boolean|(% style="width:497px" %)Test indicates whether the message is for test purposes or not.
1137		-|Prepared|HeaderTimeType|(% style="width:497px" %)Prepared is the date the message was prepared.
1138		-|Sender|SenderType|(% style="width:497px" %)Sender is information about the party that is transmitting the message.
1139		-|Receiver|PartyType|(% style="width:497px" %)Receiver is information about the party that is the intended recipient of the message.
1140		-|com:Name|com:TextType|(% style="width:497px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1141		-|Structure|com: GenericTimeSeriesDataStructureType|(% style="width:497px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1142		-|DataProvider|com: DataProviderReferenceType|(% style="width:497px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1143		-|DataSetAction|com:ActionType|(% style="width:497px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1144		-|DataSetID|com:IDType|(% style="width:497px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1145		-|Extracted|xs:dateTime|(% style="width:497px" %)Extracted is a time-stamp from the system rendering the data.
1146		-|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1147		-|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1148		-|EmbargoDate|xs:dateTime|(% style="width:497px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.
1149		-|Source|com:TextType|(% style="width:497px" %)Source provides human-readable information about the source of the data.
	1144	+|**Name**|**Type**|**Documentation**
	1145	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1146	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1147	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1148	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1149	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1150	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1151	+|Structure|com: GenericTimeSeriesDat aStructureType|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
	1152	+|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
	1153	+|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
	1154	+|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
	1155	+|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
	1156	+|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1157	+|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1158	+|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
	1159	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1150	1150
1151	1151	**StructureSpecificDataHeaderType: **StructureSpecificDataHeaderType defines the header structure for a structure specific data message.
1152	1152
1153	1153	Derivation:
1154	1154
1155		-* //BaseHeaderType// (restriction)
1156		-** StructureSpecificDataHeaderType
	1165	+//BaseHeaderType// (restriction)
	1166	+ StructureSpecificDataHeaderType
1157	1157
1158	1158	Content:
	1169	+
1159	1159	ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
1160	1160
1161	1161	Element Documentation:
1162	1162
1163		-(% style="width:930.294px" %)
1164		-|**Name**|**Type**|(% style="width:578px" %)**Documentation**
1165		-|ID|com:IDType|(% style="width:578px" %)ID identifies an identification for the message, assigned by the sender.
1166		-|Test|xs:boolean|(% style="width:578px" %)Test indicates whether the message is for test purposes or not.
1167		-|Prepared|HeaderTimeType|(% style="width:578px" %)Prepared is the date the message was prepared.
1168		-|Sender|SenderType|(% style="width:578px" %)Sender is information about the party that is transmitting the message.
1169		-|Receiver|PartyType|(% style="width:578px" %)Receiver is information about the party that is the intended recipient of the message.
1170		-|com:Name|com:TextType|(% style="width:578px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1171		-|Structure|com: StructureSpecificDataStructureType|(% style="width:578px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1172		-|DataProvider|com: DataProviderReferenceType|(% style="width:578px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1173		-|DataSetAction|com:ActionType|(% style="width:578px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1174		-|DataSetID|com:IDType|(% style="width:578px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1175		-|Extracted|xs:dateTime|(% style="width:578px" %)Extracted is a time-stamp from the system rendering the data.
1176		-|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1177		-|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1178		-|EmbargoDate|xs:dateTime|(% style="width:578px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.
1179		-|Source|com:TextType|(% style="width:578px" %)Source provides human-readable information about the source of the data.
	1174	+|**Name**|**Type**|**Documentation**
	1175	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1176	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1177	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1178	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1179	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1180	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1181	+|Structure|com: StructureSpecificDat aStructureType|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
	1182	+|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
	1183	+|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
	1184	+|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
	1185	+|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
	1186	+|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1187	+|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1188	+|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
	1189	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1180	1180
1181	1181	**StructureSpecificTimeSeriesDataHeaderType: **StructureSpecificTimeSeriesDataHeaderType defines the header structure for a time series only structure specific data message.
1182	1182
1183	1183	Derivation:
1184	1184
1185		-* //BaseHeaderType// (restriction)
1186		-** StructureSpecificDataHeaderType (restriction)
1187		-*** StructureSpecificTimeSeriesDataHeaderType
	1195	+//BaseHeaderType// (restriction)
	1196	+ StructureSpecificDataHeaderType (restriction)
	1197	+ StructureSpecificTimeSeriesDataHeaderType
1188	1188
1189	1189	Content:
	1200	+
1190	1190	ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
1191	1191
1192	1192	Element Documentation:
1193	1193
1194		-(% style="width:943.294px" %)
1195		-|**Name**|(% style="width:352px" %)**Type**|(% style="width:461px" %)**Documentation**
1196		-|ID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)ID identifies an identification for the message, assigned by the sender.
1197		-|Test|(% style="width:352px" %)xs:boolean|(% style="width:461px" %)Test indicates whether the message is for test purposes or not.
1198		-|Prepared|(% style="width:352px" %)HeaderTimeType|(% style="width:461px" %)Prepared is the date the message was prepared.
1199		-|Sender|(% style="width:352px" %)SenderType|(% style="width:461px" %)Sender is information about the party that is transmitting the message.
1200		-|Receiver|(% style="width:352px" %)PartyType|(% style="width:461px" %)Receiver is information about the party that is the intended recipient of the message.
1201		-|com:Name|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1202		-|Structure|(% style="width:352px" %)com: StructureSpecificDataTimeSeriesStructureType|(% style="width:461px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1203		-|DataProvider|(% style="width:352px" %)com: DataProviderReferenceType|(% style="width:461px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1204		-|DataSetAction|(% style="width:352px" %)com:ActionType|(% style="width:461px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1205		-|DataSetID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1206		-|Extracted|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)Extracted is a time-stamp from the system rendering the data.
1207		-|ReportingBegin|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1208		-|ReportingEnd|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1209		-|EmbargoDate|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.
1210		-|Source|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Source provides human-readable information about the source of the data.
	1205	+|**Name**|**Type**|**Documentation**
	1206	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1207	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1208	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1209	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1210	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1211	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1212	+|Structure|com: StructureSpecificDat aTimeSeriesStructure Type|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
	1213	+|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
	1214	+|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
	1215	+|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
	1216	+|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
	1217	+|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1218	+|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1219	+|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
	1220	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1211	1211
1212		-**GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]].
	1222	+**GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic reference metadata.
1213	1213
1214	1214	Derivation:
1215	1215
1216		-* //BaseHeaderType// (restriction)
1217		-** GenericMetadataHeaderType
	1226	+//BaseHeaderType// (restriction)
	1227	+ GenericMetadataHeaderType
1218	1218
1219	1219	Content:
	1230	+
1220	1220	ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, Source*
1221	1221
1222	1222	Element Documentation:
1223	1223
1224		-(% style="width:928.294px" %)
1225		-|**Name**|**Type**|(% style="width:554px" %)**Documentation**
1226		-|ID|com:IDType|(% style="width:554px" %)ID identifies an identification for the message, assigned by the sender.
1227		-|Test|xs:boolean|(% style="width:554px" %)Test indicates whether the message is for test purposes or not.
1228		-|Prepared|HeaderTimeType|(% style="width:554px" %)Prepared is the date the message was prepared.
1229		-|Sender|SenderType|(% style="width:554px" %)Sender is information about the party that is transmitting the message.
1230		-|Receiver|PartyType|(% style="width:554px" %)Receiver is information about the party that is the intended recipient of the message.
1231		-|com:Name|com:TextType|(% style="width:554px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1232		-|Structure|com: GenericMetadataStructureType|(% style="width:554px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1233		-|DataProvider|com: DataProviderReferenceType|(% style="width:554px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1234		-|DataSetAction|com:ActionType|(% style="width:554px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1235		-|DataSetID|com:IDType|(% style="width:554px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1236		-|Extracted|xs:dateTime|(% style="width:554px" %)Extracted is a time-stamp from the system rendering the data.
1237		-|Source|com:TextType|(% style="width:554px" %)Source provides human-readable information about the source of the data.
	1235	+|**Name**|**Type**|**Documentation**
	1236	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1237	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1238	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1239	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1240	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1241	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1242	+|Structure|com: GenericMetadataStruc tureType|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
	1243	+|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
	1244	+|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
	1245	+|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
	1246	+|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
	1247	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1238	1238
1239		-**StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] specific [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] messages.
	1249	+**StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for metadata structure definition specific reference metadata messages.
1240	1240
1241	1241	Derivation:
1242	1242
1243		-* //BaseHeaderType// (restriction)
1244		-** StructureSpecificMetadataHeaderType
	1253	+//BaseHeaderType// (restriction)
	1254	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType
1245	1245
1246	1246	Content:
	1257	+
1247	1247	ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, Source*
1248	1248
1249	1249	Element Documentation:
1250	1250
1251		-(% style="width:996.294px" %)
1252		-|**Name**|**Type**|(% style="width:557px" %)**Documentation**
1253		-|ID|com:IDType|(% style="width:557px" %)ID identifies an identification for the message, assigned by the sender.
1254		-|Test|xs:boolean|(% style="width:557px" %)Test indicates whether the message is for test purposes or not.
1255		-|Prepared|HeaderTimeType|(% style="width:557px" %)Prepared is the date the message was prepared.
1256		-|Sender|SenderType|(% style="width:557px" %)Sender is information about the party that is transmitting the message.
1257		-|Receiver|PartyType|(% style="width:557px" %)Receiver is information about the party that is the intended recipient of the message.
1258		-|com:Name|com:TextType|(% style="width:557px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1259		-|Structure|com: StructureSpecificMetadataStructureType|(% style="width:557px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1260		-|DataProvider|com: DataProviderReferenceType|(% style="width:557px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1261		-|DataSetAction|com:ActionType|(% style="width:557px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1262		-|DataSetID|com:IDType|(% style="width:557px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1263		-|Extracted|xs:dateTime|(% style="width:557px" %)Extracted is a time-stamp from the system rendering the data.
1264		-|Source|com:TextType|(% style="width:557px" %)Source provides human-readable information about the source of the data.
	1262	+|**Name**|**Type**|**Documentation**
	1263	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1264	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1265	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1266	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1267	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1268	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1269	+|Structure|com: StructureSpecificMet adataStructureType|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
	1270	+|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
	1271	+|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
	1272	+|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
	1273	+|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
	1274	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1265	1265
1266	1266	**BasicHeaderType: **BasicHeaderType defines the most basic header information used in simple message exchanges.
1267	1267
1268	1268	Derivation:
1269	1269
1270		-* //BaseHeaderType// (restriction)
1271		-** BasicHeaderType
	1280	+//BaseHeaderType// (restriction)
	1281	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType
1272	1272
1273	1273	Content:
	1284	+
1274	1274	ID, Test, Prepared, Sender, Receiver
1275	1275
1276	1276	Element Documentation:
1277	1277
1278		-(% style="width:903.294px" %)
1279		-|**Name**|(% style="width:236px" %)**Type**|(% style="width:457px" %)**Documentation**
1280		-|ID|(% style="width:236px" %)com:IDType|(% style="width:457px" %)ID identifies an identification for the message, assigned by the sender.
1281		-|Test|(% style="width:236px" %)xs:boolean|(% style="width:457px" %)Test indicates whether the message is for test purposes or not.
1282		-|Prepared|(% style="width:236px" %)HeaderTimeType|(% style="width:457px" %)Prepared is the date the message was prepared.
1283		-|Sender|(% style="width:236px" %)SenderType|(% style="width:457px" %)Sender is information about the party that is transmitting the message.
1284		-|Receiver|(% style="width:236px" %)PartyType|(% style="width:457px" %)Receiver is information about the party that is the intended recipient of the message.
	1289	+|**Name**|**Type**|**Documentation**
	1290	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1291	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1292	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1293	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1294	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1285	1285
1286	1286	**PartyType: **PartyType defines the information which is sent about various parties such as senders and receivers of messages.
1287	1287
...	...	@@ -1290,78 +1290,83 @@
1290	1290	id
1291	1291
1292	1292	Content:
1293		-com:Name*, (% style="color:#e74c3c" %)Contact(%%)*
1294	1294
1295		-[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Documentation:
	1304	+com:Name*, Contact*
1296	1296
1297		-(% style="width:888.294px" %)
1298		-|(% style="width:125px" %)**Name**|(% style="width:190px" %)**Type**|(% style="width:569px" %)**Documentation**
1299		-|(% style="width:125px" %)id|(% style="width:190px" %)com:IDType|(% style="width:569px" %)The id [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] holds the identification of the party.
	1306	+Attribute Documentation:
1300	1300
	1308	+|**Name**|**Type**|**Documentation**
	1309	+|id|com:IDType|The id attribute holds the identification of the party.
	1310	+
1301	1301	Element Documentation:
1302	1302
1303		-(% style="width:889.294px" %)
1304		-|(% style="width:134px" %)**Name**|(% style="width:183px" %)**Type**|(% style="width:568px" %)**Documentation**
1305		-|(% style="width:134px" %)com:Name|(% style="width:183px" %)com:TextType|(% style="width:568px" %)Name is a human-readable name of the party.
1306		-|(% style="width:134px" %)(% style="color:#e74c3c" %)Contact|(% style="width:183px" %)ContactType|(% style="width:568px" %)(% style="color:#e74c3c" %)Contact(%%) provides (% style="color:#e74c3c" %)contact(%%) information for the party in regard to the transmission of the message.
	1313	+|**Name**|**Type**|**Documentation**
	1314	+|com:Name|com:TextType|Name is a human-readable name of the party.
	1315	+|Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message.
1307	1307
1308	1308	**SenderType: **SenderType extends the basic party structure to add an optional time zone declaration.
1309	1309
1310	1310	Derivation:
1311	1311
1312		-* PartyType (extension)
1313		-** SenderType
	1321	+PartyType (extension)
	1322	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType
1314	1314
1315	1315	Attributes:
	1325	+
1316	1316	id
1317	1317
1318	1318	Content:
1319		-com:Name*, (% style="color:#e74c3c" %)Contact(%%)*, Timezone?
1320	1320
1321		-[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Documentation:
	1330	+com:Name*, Contact*, Timezone?
1322	1322
1323		-(% style="width:824.294px" %)
1324		-|(% style="width:177px" %)**Name**|(% style="width:241px" %)**Type**|(% style="width:403px" %)**Documentation**
1325		-|(% style="width:177px" %)id|(% style="width:241px" %)com:IDType|(% style="width:403px" %)The id [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] holds the identification of the party.
	1332	+Attribute Documentation:
1326	1326
	1334	+|**Name**|**Type**|**Documentation**
	1335	+|id|com:IDType|The id attribute holds the identification of the party.
	1336	+
1327	1327	Element Documentation:
1328	1328
1329		-(% style="width:1016.29px" %)
1330		-|**Name**|**Type**|(% style="width:738px" %)**Documentation**
1331		-|com:Name|com:TextType|(% style="width:738px" %)Name is a human-readable name of the party.
1332		-|(%%)(% style="color:#e74c3c" %)Contact|ContactType|(% style="width:738px" %)(% style="color:#e74c3c" %)Contact(%%) provides (% style="color:#e74c3c" %)contact(%%) information for the party in regard to the transmission of the message.
1333		-|Timezone|com:TimezoneType|(% style="width:738px" %)Timezone specifies the time zone of the sender, and if specified can be applied to all un-time zoned time values in the message. In the absence of this, any dates without time zone are implied to be in an indeterminate "local time".
	1339	+|**Name**|**Type**|**Documentation**
	1340	+|com:Name|com:TextType|Name is a human-readable name of the party.
	1341	+|Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message.
	1342	+|Timezone|com:TimezoneType|Timezone specifies the time zone of the sender, and if specified can be applied to all un-time zoned time values in the message. In the absence of this, any dates without time zone are implied to be in an indeterminate "local time".
1334	1334
1335		-**ContactType: **ContactType provides defines the (% style="color:#e74c3c" %)contact(%%) information about a party.
	1344	+**ContactType: **ContactType provides defines the contact information about a party.
1336	1336
1337	1337	Content:
	1347	+
1338	1338	com:Name*, Department*, Role*, (Telephone | Fax | X400 | URI | Email)*
1339	1339
1340	1340	Element Documentation:
1341	1341
1342		-(% style="width:1035.29px" %)
1343		-|**Name**|**Type**|(% style="width:623px" %)**Documentation**
1344		-|com:Name|com:TextType|(% style="width:623px" %)Name contains a human-readable name for the (% style="color:#e74c3c" %)contact(%%).
1345		-|Department|com:TextType|(% style="width:623px" %)Department is designation of the organisational structure by a linguistic expression, within which the (% style="color:#e74c3c" %)contact(%%) person works.
1346		-|Role|com:TextType|(% style="width:623px" %)Role is the responsibility of the (% style="color:#e74c3c" %)contact(%%) person with respect to the object for which this person is the (% style="color:#e74c3c" %)contact(%%).
1347		-|Telephone|xs:string|(% style="width:623px" %)Telephone holds the [[telephone number>>doc:sdmx:Glossary.Contact phone number.WebHome]] for the (% style="color:#e74c3c" %)contact(%%) person.
1348		-|Fax|xs:string|(% style="width:623px" %)Fax holds the fax number for the (% style="color:#e74c3c" %)contact(%%) person.
1349		-|X400|xs:string|(% style="width:623px" %)X400 holds the X.400 address for the (% style="color:#e74c3c" %)contact(%%) person.
1350		-|URI|xs:anyURI|(% style="width:623px" %)URI holds an information URL for the (% style="color:#e74c3c" %)contact(%%) person.
1351		-|Email|xs:string|(% style="width:623px" %)Email holds the email address for the (% style="color:#e74c3c" %)contact(%%) person.
	1352	+|**Name**|**Type**|**Documentation**
	1353	+|com:Name|com:TextType|Name contains a human-readable name for the contact.
	1354	+|Department|com:TextType|Department is designation of the organisational structure by a linguistic expression, within which the contact person works.
	1355	+|Role|com:TextType|Role is the responsibility of the contact person with respect to the object for which this person is the contact.
	1356	+|Telephone|xs:string|Telephone holds the telephone number for the contact person.
	1357	+|Fax|xs:string|Fax holds the fax number for the contact person.
	1358	+|X400|xs:string|X400 holds the X.400 address for the contact person.
	1359	+|URI|xs:anyURI|URI holds an information URL for the contact person.
	1360	+|Email|xs:string|Email holds the email address for the contact person.
1352	1352
1353		-=== 2.1.4 Simple Types ===
	1362	+1.
	1363	+11.
	1364	+111. Simple Types
1354	1354
1355	1355	**HeaderTimeType: **Provides a union type of xs:date and xs:dateTime for the header fields in the message.
1356	1356
1357	1357	Union of:
	1369	+
1358	1358	xs:dateTime, xs:date.
1359	1359
1360		-== 2.2 Message Footer Namespace ==
	1372	+1.
	1373	+11. Message Footer Namespace
1361	1361
1362	1362	**http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer**
1363	1363
1364		-=== 2.2.1 Summary ===
	1377	+1.
	1378	+11.
	1379	+111. Summary
1365	1365
1366	1366	Referenced Namespaces:
1367	1367
...	...	@@ -1370,45 +1370,52 @@
1370	1370	|http:~/~/www.w3.org/2001/XMLSchema|xs
1371	1371
1372	1372	Contents:
	1388	+
1373	1373	1 Global Element
1374	1374	2 Complex Types
1375	1375	1 Simple Type
1376	1376
1377		-=== 2.2.2 Global Elements ===
	1393	+1.
	1394	+11.
	1395	+111. Global Elements
1378	1378
1379	1379	**Footer (FooterType): **Footer is used to communicate information such as error and warnings after the payload of a message.
1380	1380
1381		-=== 2.2.3 Complex Types ===
	1399	+1.
	1400	+11.
	1401	+111. Complex Types
1382	1382
1383	1383	**FooterType: **FooterType describes the structure of a message footer. The footer is used to convey any error, information, or warning messages. This is to be used when the message has payload, but also needs to communicate additional information. If an error occurs and no payload is generated, an Error message should be returned.
1384	1384
1385	1385	Content:
	1406	+
1386	1386	Message+
1387	1387
1388	1388	Element Documentation:
1389	1389
1390		-(% style="width:1112.29px" %)
1391		-|**Name**|**Type**|(% style="width:782px" %)**Documentation**
1392		-|Message|FooterMessageType|(% style="width:782px" %)Message contains a single error, information, or warning message. A [[code>>doc:sdmx:Glossary.Code.WebHome]] is provided along with an optional severity. The text of the message can be expressed in multiple languages.
	1411	+|**Name**|**Type**|**Documentation**
	1412	+|Message|FooterMessageType|Message contains a single error, information, or warning message. A code is provided along with an optional severity. The text of the message can be expressed in multiple languages.
1393	1393
1394		-**FooterMessageType: **FooterMessageType defines the structure of a message that is contained in the footer of a message. It is a status message that have a severity [[code>>doc:sdmx:Glossary.Code.WebHome]] of Error, Information, or Warning added to it.
	1414	+**FooterMessageType: **FooterMessageType defines the structure of a message that is contained in the footer of a message. It is a status message that have a severity code of Error, Information, or Warning added to it.
1395	1395
1396	1396	Derivation:
1397	1397
1398		-* com:StatusMessageType (restriction)
1399		-** com:CodedStatusMessageType (extension)
1400		-*** FooterMessageType
	1418	+com:StatusMessageType (restriction)
	1419	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension)
	1420	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType
1401	1401
1402	1402	Attributes:
1403		-[[code>>doc:sdmx:Glossary.Code.WebHome]], severity?
1404	1404
	1424	+code, severity?
	1425	+
1405	1405	Content:
	1427	+
1406	1406	com:Text+
1407	1407
1408		-[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Documentation:
	1430	+Attribute Documentation:
1409	1409
1410	1410	|**Name**|**Type**|**Documentation**
1411		-|[[code>>doc:sdmx:Glossary.Code.WebHome]]|xs:string|The [[code>>doc:sdmx:Glossary.Code.WebHome]] [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] holds an optional [[code>>doc:sdmx:Glossary.Code.WebHome]] identifying the underlying error that generated the message. This should be used if parallel language descriptions of the error are supplied, to distinguish which of the multiple error messages are for the same underlying error.
	1433	+|code|xs:string|The code attribute holds an optional code identifying the underlying error that generated the message. This should be used if parallel language descriptions of the error are supplied, to distinguish which of the multiple error messages are for the same underlying error.
1412	1412	|severity|SeverityCodeType|
1413	1413
1414	1414	Element Documentation:
...	...	@@ -1416,7 +1416,9 @@
1416	1416	|**Name**|**Type**|**Documentation**
1417	1417	|com:Text|com:TextType|Text contains the text of the message, in parallel language values.
1418	1418
1419		-=== 2.2.4 Simple Types ===
	1441	+1.
	1442	+11.
	1443	+111. Simple Types
1420	1420
1421	1421	**SeverityCodeType:**
1422	1422
...	...	@@ -1427,4 +1427,19 @@
1427	1427	|**Value**|**Documentation**
1428	1428	|Error|Error indicates the status message coresponds to an error.
1429	1429	|Warning|Warning indicates that the status message corresponds to a warning.
1430		-|Information|Information indicates that the status message corresponds to an informational message.
	1454	+|Information|Information indicates that the status message corresponds to an informational message.
	1455	+
	1456	+
	1457	+
	1458	+
	1459	+
	1460	+
	1461	+
	1462	+
	1463	+
	1464	+
	1465	+
	1466	+
	1467	+
	1468	+
	1469	+