Wiki source code of Part I. Message

Version 2.3 by Helena on 2025/06/23 16:34

version	line-number	content
2.2	1	{{box title="Contents"}}
	2	{{toc/}}
	3	{{/box}}
	4
	5	Corrigendum
	6
	7	The following problems with the specification dated April 2011 have been rectified as described below.
	8
2.3	9	~1. Problem
2.2	10
	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
	13	Rectification
	14
	15	The documentation of the Structure element (line 40) has been updated to remove this reference.
	16
2.3	17	= 1. Introduction =
2.2	18
	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
	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
	23	In general, every message in SDMX follows common format of:
	24
	25	* Header
	26	* Payload (0..n)
	27	* Footer (0..1)
	28
	29	The header and payload elements exist in the message namespace, but the content of the payload is defined in the namespaces that are specific the functionality of the messages. Note that the header follows a common construct, which is then restricted according to the requirements of the message which is using it.
	30
2.3	31	= 2. Schema Documentation =
2.2	32
2.3	33	== 2.1 Message Namespace ==
	34
2.2	35	http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message
	36
2.3	37	=== 2.1.1 Summary ===
2.2	38
	39	Referenced Namespaces:
	40
	41	\|Namespace\|Prefix
	42	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common\|com
	43	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/generic\|dat
	44	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/structurespecific\|dsd
	45	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer\|ftr
	46	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/generic\|rep
	47	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/structurespecific\|msd
	48	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/query\|qry
	49	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/registry\|ref
	50	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/structure\|str
	51	\|http:~/~/www.w3.org/2001/XMLSchema\|xs
	52
	53	Contents:
	54
	55	50 Global Elements
	56	62 Complex Types
	57	1 Simple Type
	58
2.3	59	1.
	60	11.
2.2	61	111. Global Elements
	62
	63	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.
	64
	65	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).
	66
	67	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.
	68
	69	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.
	70
	71	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.
	72
	73	GenericMetadata (GenericMetadataType): GenericMetadata contains reported metadata in a format which supports any metadata structure definition.
	74
	75	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.
	76
	77	RegistryInterface (RegistryInterfaceType): RegistryInterface is used to conduct all interactions with the SDMX Registry Services.
	78
	79	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.
	80
	81	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.
	82
	83	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.
	84
	85	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.
	86
	87	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.
	88
	89	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.
	90
	91	SubmitSubscriptionsRequest (SubmitSubscriptionsRequestType): SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
	92
	93	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.
	94
	95	QuerySubscriptionRequest (QuerySubscriptionRequestType): QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
	96
	97	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.
	98
	99	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.
	100
	101	StructureSpecificDataQuery (DataQueryType): StructureSpecificDataQuery is used to query SDMX compliant databases or web services for structure specific data.
	102
	103	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.
	104
	105	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.
	106
	107	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.
	108
	109	GenericMetadataQuery (MetadataQueryType): GenericMetadataQuery is used to query SDMX compliant databases or web services for generic format reference metadata.
	110
	111	StructureSpecificMetadataQuery (MetadataQueryType): StructureSpecificMetadataQuery is used to query SDMX compliant databases or web services for metadata structure specific reference metadata.
	112
	113	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.
	114
	115	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.
	116
	117	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).
	118
	119	DataflowQuery (DataflowQueryType): DataflowQuery is used to query SDMX compliant databases or web services for dataflows.
	120
	121	MetadataflowQuery (MetadataflowQueryType): MetadataflowQuery is used to query SDMX compliant databases or web services for metadata flows.
	122
	123	DataStructureQuery (DataStructureQueryType): DataStructureQuery is used to query SDMX compliant databases or web services for data structures definitions.
	124
	125	MetadataStructureQuery (MetadataStructureQueryType): MetadataStructureQuery is used to query SDMX compliant databases or web services for metadata structure definitions.
	126
	127	CategorySchemeQuery (CategorySchemeQueryType): CategorySchemeQuery is used to query SDMX compliant databases or web services for category schemes.
	128
	129	ConceptSchemeQuery (ConceptSchemeQueryType): ConceptSchemeQuery is used to query SDMX compliant databases or web services for concept schemes.
	130
	131	CodelistQuery (CodelistQueryType): CodelistQuery is used to query SDMX compliant databases or web services for codelists.
	132
	133	HierarchicalCodelistQuery (HierarchicalCodelistQueryType): HierarchicalCodelistQuery is used to query SDMX compliant databases or web services for hierarchical codelists.
	134
	135	OrganisationSchemeQuery (OrganisationSchemeQueryType): OrganisationSchemeQuery is used to query SDMX compliant databases or web services for organisation schemes.
	136
	137	ReportingTaxonomyQuery (ReportingTaxonomyQueryType): ReportingTaxonomyQuery is used to query SDMX compliant databases or web services for reporting taxonomies.
	138
	139	StructureSetQuery (StructureSetQueryType): StructureSetQuery is used to query SDMX compliant databases or web services for structure sets.
	140
	141	ProcessQuery (ProcessQueryType): ProcessQuery is used to query SDMX compliant databases or web services for processes.
	142
	143	CategorisationQuery (CategorisationQueryType): CategorisationQuery is used to query SDMX compliant databases or web services for categorisations.
	144
	145	ProvisionAgreementQuery (ProvisionAgreementQueryType): ProvisionAgreementQuery is used to query SDMX compliant databases or web services for provision agreements.
	146
	147	ConstraintQuery (ConstraintQueryType): ConstraintQuery is used to query SDMX compliant databases or web services for constraints.
	148
	149	TransformationSchemeQuery (TransformationSchemeQueryType): TransformationSchemeQuery is used to query SDMX compliant databases or web services for transformation schemes.
	150
	151	VtlMappingSchemeQuery (VtlMappingSchemeQueryType): VtlMappingSchemeQuery is used to query SDMX compliant databases or web services for VTL mapping schemes.
	152
	153	NamePersonalisationSchemeQuery (NamePersonalisationSchemeQueryType): NamePersonalisationSchemeQuery is used to query SDMX compliant databases or web services for name personalisation schemes.
	154
	155	RulesetSchemeQuery (RulesetSchemeQueryType): RulesetSchemeQuery is used to query SDMX compliant databases or web services for ruleset schemes.
	156
	157	UserDefinedOperatorSchemeQuery (UserDefinedOperatorSchemeQueryType): UserDefinedOperatorSchemeQuery is used to query SDMX compliant databases or web services for user defined schemes.
	158
	159	CustomTypeSchemeQuery (CustomTypeSchemeQueryType): CustomTypeSchemeQuery is used to query SDMX compliant databases or web services for custom type schemes.
	160
	161	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.
	162
2.3	163	1.
	164	11.
2.2	165	111. Complex Types
	166
	167	//MessageType//: MessageType is an abstract type which is used by all of the messages, to allow inheritance of common features. Every message consists of a mandatory header, followed by optional payload (which may occur multiple times), and finally an optional footer section for conveying error, warning, and informational messages.
	168
	169	Content:
	170
	171	Header, {any element with namespace of http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message}*, ftr:Footer?
	172
	173	Element Documentation:
	174
	175	\|Name\|Type\|Documentation
	176	\|Header\|//BaseHeaderType//\|
	177	\|ftr:Footer\|ftr:FooterType\|Footer is used to communicate information such as error and warnings after the payload of a message.
	178
	179	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.
	180
	181	Derivation:
	182
	183	//MessageType// (restriction)
2.3	184	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] StructureType
2.2	185
	186	Content:
	187
	188	Header, Structures?, ftr:Footer?
	189
	190	Element Documentation:
	191
	192	\|Name\|Type\|Documentation
	193	\|Header\|StructureHeaderType\|
	194	\|Structures\|str:StructuresType\|
	195	\|ftr:Footer\|ftr:FooterType\|Footer is used to communicate information such as error and warnings after the payload of a message.
	196
	197	GenericDataType: GenericDataType defines the contents of a generic data message.
	198
	199	Derivation:
	200
	201	//MessageType// (restriction)
2.3	202	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] GenericDataType
2.2	203
	204	Content:
	205
	206	Header, DataSet*, ftr:Footer?
	207
	208	Element Documentation:
	209
	210	\|Name\|Type\|Documentation
	211	\|Header\|GenericDataHeaderTyp e\|
	212	\|DataSet\|dat:DataSetType\|
	213	\|ftr:Footer\|ftr:FooterType\|Footer is used to communicate information such as error and warnings after the payload of a message.
	214
	215	GenericTimeSeriesDataType: GenericTimeSeriesDataType defines the structure of the generic time series data message.
	216
	217	Derivation:
	218
	219	//MessageType// (restriction)
2.3	220	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] GenericDataType (restriction)
	221	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] GenericTimeSeriesDataType
2.2	222
	223	Content:
	224
	225	Header, DataSet*, ftr:Footer?
	226
	227	Element Documentation:
	228
	229	\|Name\|Type\|Documentation
	230	\|Header\|GenericTimeSeriesDat aHeaderType\|
	231	\|DataSet\|dat: TimeSeriesDataSetTyp e\|
	232	\|ftr:Footer\|ftr:FooterType\|Footer is used to communicate information such as error and warnings after the payload of a message.
	233
	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.
	235
	236	Derivation:
	237
	238	//MessageType// (restriction)
2.3	239	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] StructureSpecificDataType
2.2	240
	241	Content:
	242
	243	Header, DataSet*, ftr:Footer?
	244
	245	Element Documentation:
	246
	247	\|Name\|Type\|Documentation
	248	\|Header\|StructureSpecificDat aHeaderType\|
	249	\|DataSet\|//dsd:DataSetType//\|
	250	\|ftr:Footer\|ftr:FooterType\|Footer is used to communicate information such as error and warnings after the payload of a message.
	251
	252	StructureSpecificTimeSeriesDataType: StructureSpecificTimeSeriesDataType defines the structure of the structure specific time series data message.
	253
	254	Derivation:
	255
	256	//MessageType// (restriction)
2.3	257	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] StructureSpecificDataType (restriction)
	258	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] StructureSpecificTimeSeriesDataType
2.2	259
	260	Content:
	261
	262	Header, DataSet*, ftr:Footer?
	263
	264	Element Documentation:
	265
	266	\|Name\|Type\|Documentation
	267	\|Header\|StructureSpecificTim eSeriesDataHeaderTyp e\|
	268	\|DataSet\|//dsd: TimeSeriesDataSetTyp e//\|
	269	\|ftr:Footer\|ftr:FooterType\|Footer is used to communicate information such as error and warnings after the payload of a message.
	270
	271	GenericMetadataType: GenericMetadataType defines the contents of a generic metadata message.
	272
	273	Derivation:
	274
	275	//MessageType// (restriction)
2.3	276	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] GenericMetadataType
2.2	277
	278	Content:
	279
	280	Header, MetadataSet*, ftr:Footer?
	281
	282	Element Documentation:
	283
	284	\|Name\|Type\|Documentation
	285	\|Header\|GenericMetadataHeade rType\|
	286	\|MetadataSet\|rep:MetadataSetType\|
	287	\|ftr:Footer\|ftr:FooterType\|Footer is used to communicate information such as error and warnings after the payload of a message.
	288
	289	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.
	290
	291	Derivation:
	292
	293	//MessageType// (restriction)
2.3	294	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] StructureSpecificMetadataType
2.2	295
	296	Content:
	297
	298	Header, MetadataSet*, ftr:Footer?
	299
	300	Element Documentation:
	301
	302	\|Name\|Type\|Documentation
	303	\|Header\|StructureSpecificMet adataHeaderType\|
	304	\|MetadataSet\|//msd:MetadataSetType//\|
	305	\|ftr:Footer\|ftr:FooterType\|Footer is used to communicate information such as error and warnings after the payload of a message.
	306
	307	RegistryInterfaceType: This is a type which describes a structure for holding all of the various dedicated registry interface message types.
	308
	309	Derivation:
	310
	311	//MessageType// (restriction)
2.3	312	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] RegistryInterfaceType
2.2	313
	314	Content:
	315
	316	Header, (SubmitRegistrationsRequest \| SubmitRegistrationsResponse \| QueryRegistrationRequest \| QueryRegistrationResponse \| SubmitStructureRequest \| SubmitStructureResponse \| SubmitSubscriptionsRequest \| SubmitSubscriptionsResponse \| QuerySubscriptionRequest \| QuerySubscriptionResponse \| NotifyRegistryEvent)?, ftr:Footer?
	317
	318	Element Documentation:
	319
	320	\|Name\|Type\|Documentation
	321	\|Header\|BasicHeaderType\|
	322	\|SubmitRegistrationsR equest\|ref: SubmitRegistrationsR equestType\|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.
	323	\|SubmitRegistrationsR esponse\|ref: SubmitRegistrationsR esponseType\|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.
	324	\|QueryRegistrationReq uest\|ref: QueryRegistrationReq uestType\|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.
	325	\|QueryRegistrationRes ponse\|ref: QueryRegistrationRes ponseType\|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.
	326	\|SubmitStructureReque st\|ref: SubmitStructureReque stType\|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.
	327	\|SubmitStructureRespo nse\|ref: SubmitStructureRespo nseType\|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.
	328	\|SubmitSubscriptionsR equest\|ref: SubmitSubscriptionsR equestType\|SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
	329	\|SubmitSubscriptionsR esponse\|ref: SubmitSubscriptionsR esponseType\|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.
	330	\|QuerySubscriptionReq uest\|ref: QuerySubscriptionReq uestType\|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
	331	\|QuerySubscriptionRes ponse\|ref: QuerySubscriptionRes ponseType\|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.
	332	\|NotifyRegistryEvent\|ref: NotifyRegistryEventT ype\|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.
	333	\|ftr:Footer\|ftr:FooterType\|Footer is used to communicate information such as error and warnings after the payload of a message.
	334
	335	SubmitRegistrationsRequestType: SubmitRegistrationsRequestType defines the structure of a registry submit registration requests document.
	336
	337	Derivation:
	338
	339	//MessageType// (restriction)
2.3	340	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] RegistryInterfaceType (restriction)
	341	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] SubmitRegistrationsRequestType
2.2	342
	343	Content:
	344
	345	Header, SubmitRegistrationsRequest
	346
	347	Element Documentation:
	348
	349	\|Name\|Type\|Documentation
	350	\|Header\|BasicHeaderType\|
	351	\|SubmitRegistrationsR equest\|ref: SubmitRegistrationsR equestType\|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.
	352
	353	SubmitRegistrationsResponseType: SubmitRegistrationsResponseType defines the structure of a registry submit registration response document.
	354
	355	Derivation:
	356
	357	//MessageType// (restriction)
2.3	358	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] RegistryInterfaceType (restriction)
	359	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] SubmitRegistrationsResponseType
2.2	360
	361	Content:
	362
	363	Header, SubmitRegistrationsResponse, ftr:Footer?
	364
	365	Element Documentation:
	366
	367	\|Name\|Type\|Documentation
	368	\|Header\|BasicHeaderType\|
	369	\|SubmitRegistrationsR esponse\|ref: SubmitRegistrationsR esponseType\|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.
	370	\|ftr:Footer\|ftr:FooterType\|Footer is used to communicate information such as error and warnings after the payload of a message.
	371
	372	QueryRegistrationRequestType: QueryRegistrationRequestType defines the structure of a registry query registration request document.
	373
	374	Derivation:
	375
	376	//MessageType// (restriction)
2.3	377	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] RegistryInterfaceType (restriction)
	378	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] QueryRegistrationRequestType
2.2	379
	380	Content:
	381
	382	Header, QueryRegistrationRequest
	383
	384	Element Documentation:
	385
	386	\|Name\|Type\|Documentation
	387	\|Header\|BasicHeaderType\|
	388	\|QueryRegistrationReq uest\|ref: QueryRegistrationReq uestType\|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.
	389
	390	QueryRegistrationResponseType: SubmitRegistrationRequestType defines the structure of a registry submit registration response document.
	391
	392	Derivation:
	393
	394	//MessageType// (restriction)
2.3	395	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] RegistryInterfaceType (restriction)
	396	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] QueryRegistrationResponseType
2.2	397
	398	Content:
	399
	400	Header, QueryRegistrationResponse, ftr:Footer?
	401
	402	Element Documentation:
	403
	404	\|Name\|Type\|Documentation
	405	\|Header\|BasicHeaderType\|
	406	\|QueryRegistrationRes ponse\|ref: QueryRegistrationRes ponseType\|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.
	407	\|ftr:Footer\|ftr:FooterType\|Footer is used to communicate information such as error and warnings after the payload of a message.
	408
	409	SubmitStructureRequestType: SubmitStructureRequestType defines the structure of a registry submit structure request document.
	410
	411	Derivation:
	412
	413	//MessageType// (restriction)
2.3	414	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] RegistryInterfaceType (restriction)
	415	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] SubmitStructureRequestType
2.2	416
	417	Content:
	418
	419	Header, SubmitStructureRequest
	420
	421	Element Documentation:
	422
	423	\|Name\|Type\|Documentation
	424	\|Header\|BasicHeaderType\|
	425	\|SubmitStructureReque st\|ref: SubmitStructureReque stType\|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.
	426
	427	SubmitStructureResponseType: SubmitStructureResponseType defines the structure of a registry submit registration response document.
	428
	429	Derivation:
	430
	431	//MessageType// (restriction)
2.3	432	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] RegistryInterfaceType (restriction)
	433	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] SubmitStructureResponseType
2.2	434
	435	Content:
	436
	437	Header, SubmitStructureResponse, ftr:Footer?
	438
	439	Element Documentation:
	440
	441	\|Name\|Type\|Documentation
	442	\|Header\|BasicHeaderType\|
	443	\|SubmitStructureRespo nse\|ref: SubmitStructureRespo nseType\|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.
	444	\|ftr:Footer\|ftr:FooterType\|Footer is used to communicate information such as error and warnings after the payload of a message.
	445
	446	SubmitSubscriptionsRequestType: SubmitSubscriptionsRequestType defines the structure of a registry submit subscription request document.
	447
	448	Derivation:
	449
	450	//MessageType// (restriction)
2.3	451	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] RegistryInterfaceType (restriction)
	452	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] SubmitSubscriptionsRequestType
2.2	453
	454	Content:
	455
	456	Header, SubmitSubscriptionsRequest
	457
	458	Element Documentation:
	459
	460	\|Name\|Type\|Documentation
	461	\|Header\|BasicHeaderType\|
	462	\|SubmitSubscriptionsR equest\|ref: SubmitSubscriptionsR equestType\|SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
	463
	464	SubmitSubscriptionsResponseType: SubmitSubscriptionsResponseType defines the structure of a registry submit subscription response document.
	465
	466	Derivation:
	467
	468	//MessageType// (restriction)
2.3	469	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] RegistryInterfaceType (restriction)
	470	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] SubmitSubscriptionsResponseType
2.2	471
	472	Content:
	473
	474	Header, SubmitSubscriptionsResponse, ftr:Footer?
	475
	476	Element Documentation:
	477
	478	\|Name\|Type\|Documentation
	479	\|Header\|BasicHeaderType\|
	480	\|SubmitSubscriptionsR esponse\|ref: SubmitSubscriptionsR esponseType\|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.
	481	\|ftr:Footer\|ftr:FooterType\|Footer is used to communicate information such as error and warnings after the payload of a message.
	482
	483	QuerySubscriptionRequestType: QuerySubscriptionRequestType defines the structure of a registry query subscription request document.
	484
	485	Derivation:
	486
	487	//MessageType// (restriction)
2.3	488	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] RegistryInterfaceType (restriction)
	489	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] QuerySubscriptionRequestType
2.2	490
	491	Content:
	492
	493	Header, QuerySubscriptionRequest
	494
	495	Element Documentation:
	496
	497	\|Name\|Type\|Documentation
	498	\|Header\|BasicHeaderType\|
	499	\|QuerySubscriptionReq uest\|ref: QuerySubscriptionReq uestType\|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
	500
	501	QuerySubscriptionResponseType: QuerySubscriptionResponseType defines the structure of a registry query subscription response document.
	502
	503	Derivation:
	504
	505	//MessageType// (restriction)
2.3	506	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] RegistryInterfaceType (restriction)
	507	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] QuerySubscriptionResponseType
2.2	508
	509	Content:
	510
	511	Header, QuerySubscriptionResponse, ftr:Footer?
	512
	513	Element Documentation:
	514
	515	\|Name\|Type\|Documentation
	516	\|Header\|BasicHeaderType\|
	517	\|QuerySubscriptionRes ponse\|ref: QuerySubscriptionRes ponseType\|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.
	518	\|ftr:Footer\|ftr:FooterType\|Footer is used to communicate information such as error and warnings after the payload of a message.
	519
	520	NotifyRegistryEventType: NotifyRegistryEventType defines the structure of a registry notification document.
	521
	522	Derivation:
	523
	524	//MessageType// (restriction)
	525	RegistryInterfaceType (restriction)
	526	NotifyRegistryEventType
	527
	528	Content:
	529
	530	Header, NotifyRegistryEvent
	531
	532	Element Documentation:
	533
	534	\|Name\|Type\|Documentation
	535	\|Header\|BasicHeaderType\|
	536	\|NotifyRegistryEvent\|ref: NotifyRegistryEventT ype\|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.
	537
	538	DataQueryType: DataQueryType defines the structure of a data query message.
	539
	540	Derivation:
	541
	542	//MessageType// (restriction)
	543	DataQueryType
	544
	545	Content:
	546
	547	Header, Query
	548
	549	Element Documentation:
	550
	551	\|Name\|Type\|Documentation
	552	\|Header\|BasicHeaderType\|
	553	\|Query\|qry:DataQueryType\|
	554
	555	GenericDataQueryType: DataQueryType defines the structure of a generic data query message.
	556
	557	Derivation:
	558
	559	//MessageType// (restriction)
	560	DataQueryType (restriction)
	561	GenericDataQueryType
	562
	563	Content:
	564
	565	Header, Query
	566
	567	Element Documentation:
	568
	569	\|Name\|Type\|Documentation
	570	\|Header\|BasicHeaderType\|
	571	\|Query\|qry: GenericDataQueryType\|
	572
	573	GenericTimeSeriesDataQueryType: GenericTimeSeriesDataQueryType defines the structure of a time series generic data query message.
	574
	575	Derivation:
	576
	577	//MessageType// (restriction)
	578	DataQueryType (restriction)
	579	GenericDataQueryType (restriction)
	580	GenericTimeSeriesDataQueryType
	581
	582	Content:
	583
	584	Header, Query
	585
	586	Element Documentation:
	587
	588	\|Name\|Type\|Documentation
	589	\|Header\|BasicHeaderType\|
	590	\|Query\|qry: GenericTimeSeriesDat aQueryType\|
	591
	592	StructureSpecificTimeSeriesDataQueryType: StructureSpecificTimeSeriesDataQueryType defines the structure of a time series generic data query message.
	593
	594	Derivation:
	595
	596	//MessageType// (restriction)
	597	DataQueryType (restriction)
	598	StructureSpecificTimeSeriesDataQueryType
	599
	600	Content:
	601
	602	Header, Query
	603
	604	Element Documentation:
	605
	606	\|Name\|Type\|Documentation
	607	\|Header\|BasicHeaderType\|
	608	\|Query\|qry: TimeSeriesDataQueryT ype\|
	609
	610	MetadataQueryType: MetadataQueryType defines the structure of a reference metadata query message.
	611
	612	Derivation:
	613
	614	//MessageType// (restriction)
	615	MetadataQueryType
	616
	617	Content:
	618
	619	Header, Query
	620
	621	Element Documentation:
	622
	623	\|Name\|Type\|Documentation
	624	\|Header\|BasicHeaderType\|
	625	\|Query\|qry: MetadataQueryType\|
	626
	627	DataSchemaQueryType: DataSchemaQueryType defines the structure of a data schema query message.
	628
	629	Derivation:
	630
	631	//MessageType// (restriction)
	632	DataSchemaQueryType
	633
	634	Content:
	635
	636	Header, Query
	637
	638	Element Documentation:
	639
	640	\|Name\|Type\|Documentation
	641	\|Header\|BasicHeaderType\|
	642	\|Query\|qry: DataSchemaQueryType\|
	643
	644	MetadataSchemaQueryType: MetadataSchemaQueryType defines the structure of a metadata schema query message.
	645
	646	Derivation:
	647
	648	//MessageType// (restriction)
	649	MetadataSchemaQueryType
	650
	651	Content:
	652
	653	Header, Query
	654
	655	Element Documentation:
	656
	657	\|Name\|Type\|Documentation
	658	\|Header\|BasicHeaderType\|
	659	\|Query\|qry: MetadataSchemaQueryT ype\|
	660
	661	StructuresQueryType: StructuresQueryType defines the structure of a structures query message.
	662
	663	Derivation:
	664
	665	//MessageType// (restriction)
	666	StructuresQueryType
	667
	668	Content:
	669
	670	Header, Query
	671
	672	Element Documentation:
	673
	674	\|Name\|Type\|Documentation
	675	\|Header\|BasicHeaderType\|
	676	\|Query\|qry: StructuresQueryType\|
	677
	678	DataflowQueryType: DataflowQueryType defines the structure of a dataflow query message.
	679
	680	Derivation:
	681
	682	//MessageType// (restriction)
	683	DataflowQueryType
	684
	685	Content:
	686
	687	Header, Query
	688
	689	Element Documentation:
	690
	691	\|Name\|Type\|Documentation
	692	\|Header\|BasicHeaderType\|
	693	\|Query\|qry: DataflowQueryType\|
	694
	695	MetadataflowQueryType: MetadataflowQueryType defines the structure of a metadata flow query message.
	696
	697	Derivation:
	698
	699	//MessageType// (restriction)
	700	MetadataflowQueryType
	701
	702	Content:
	703
	704	Header, Query
	705
	706	Element Documentation:
	707
	708	\|Name\|Type\|Documentation
	709	\|Header\|BasicHeaderType\|
	710	\|Query\|qry: MetadataflowQueryTyp e\|
	711
	712	DataStructureQueryType: KeyFamilyQueryType defines the structure of a data structure query message.
	713
	714	Derivation:
	715
	716	//MessageType// (restriction)
	717	DataStructureQueryType
	718
	719	Content:
	720
	721	Header, Query
	722
	723	Element Documentation:
	724
	725	\|Name\|Type\|Documentation
	726	\|Header\|BasicHeaderType\|
	727	\|Query\|qry: DataStructureQueryTy pe\|
	728
	729	MetadataStructureQueryType: MetadataStructureQueryType defines the structure of a metadata structure query message.
	730
	731	Derivation:
	732
	733	//MessageType// (restriction)
	734	MetadataStructureQueryType
	735
	736	Content:
	737
	738	Header, Query
	739
	740	Element Documentation:
	741
	742	\|Name\|Type\|Documentation
	743	\|Header\|BasicHeaderType\|
	744	\|Query\|qry: MetadataStructureQue ryType\|
	745
	746	CategorySchemeQueryType: CategorySchemeQueryType defines the structure of a category scheme query message.
	747
	748	Derivation:
	749
	750	//MessageType// (restriction)
	751	CategorySchemeQueryType
	752
	753	Content:
	754
	755	Header, Query
	756
	757	Element Documentation:
	758
	759	\|Name\|Type\|Documentation
	760	\|Header\|BasicHeaderType\|
	761	\|Query\|qry: CategorySchemeQueryT ype\|
	762
	763	ConceptSchemeQueryType: ConceptSchemeQueryType defines the structure of a concept scheme query message.
	764
	765	Derivation:
	766
	767	//MessageType// (restriction)
	768	ConceptSchemeQueryType
	769
	770	Content:
	771
	772	Header, Query
	773
	774	Element Documentation:
	775
	776	\|Name\|Type\|Documentation
	777	\|Header\|BasicHeaderType\|
	778	\|Query\|qry: ConceptSchemeQueryTy pe\|
	779
	780	CodelistQueryType: CodelistQueryType defines the structure of a codelist query message.
	781
	782	Derivation:
	783
	784	//MessageType// (restriction)
	785	CodelistQueryType
	786
	787	Content:
	788
	789	Header, Query
	790
	791	Element Documentation:
	792
	793	\|Name\|Type\|Documentation
	794	\|Header\|BasicHeaderType\|
	795	\|Query\|qry: CodelistQueryType\|
	796
	797	HierarchicalCodelistQueryType: HierarchicalCodelistQueryType defines the structure of a hierarchical codelist query message.
	798
	799	Derivation:
	800
	801	//MessageType// (restriction)
	802	HierarchicalCodelistQueryType
	803
	804	Content:
	805
	806	Header, Query
	807
	808	Element Documentation:
	809
	810	\|Name\|Type\|Documentation
	811	\|Header\|BasicHeaderType\|
	812	\|Query\|qry: HierarchicalCodelist QueryType\|
	813
	814	OrganisationSchemeQueryType: OrganisationSchemeQueryType defines the structure of an organisation scheme query message.
	815
	816	Derivation:
	817
	818	//MessageType// (restriction)
	819	OrganisationSchemeQueryType
	820
	821	Content:
	822
	823	Header, Query
	824
	825	Element Documentation:
	826
	827	\|Name\|Type\|Documentation
	828	\|Header\|BasicHeaderType\|
	829	\|Query\|qry: OrganisationSchemeQu eryType\|
	830
	831	ReportingTaxonomyQueryType: ReportingTaxonomyQueryType defines the structure of a reporting taxonomy query message.
	832
	833	Derivation:
	834
	835	//MessageType// (restriction)
	836	ReportingTaxonomyQueryType
	837
	838	Content:
	839
	840	Header, Query
	841
	842	Element Documentation:
	843
	844	\|Name\|Type\|Documentation
	845	\|Header\|BasicHeaderType\|
	846	\|Query\|qry: ReportingTaxonomyQue ryType\|
	847
	848	StructureSetQueryType: StructureSetQueryType defines the structure of a structure set query message.
	849
	850	Derivation:
	851
	852	//MessageType// (restriction)
	853	StructureSetQueryType
	854
	855	Content:
	856
	857	Header, Query
	858
	859	Element Documentation:
	860
	861	\|Name\|Type\|Documentation
	862	\|Header\|BasicHeaderType\|
	863	\|Query\|qry: StructureSetQueryTyp e\|
	864
	865	ProcessQueryType: CategorizationQueryType defines the structure of a categorization query message.
	866
	867	Derivation:
	868
	869	//MessageType// (restriction)
	870	ProcessQueryType
	871
	872	Content:
	873
	874	Header, Query
	875
	876	Element Documentation:
	877
	878	\|Name\|Type\|Documentation
	879	\|Header\|BasicHeaderType\|
	880	\|Query\|qry:ProcessQueryType\|
	881
	882	CategorisationQueryType: CategorisationQueryType defines the structure of a categorisation query message.
	883
	884	Derivation:
	885
	886	//MessageType// (restriction)
	887	CategorisationQueryType
	888
	889	Content:
	890
	891	Header, Query
	892
	893	Element Documentation:
	894
	895	\|Name\|Type\|Documentation
	896	\|Header\|BasicHeaderType\|
	897	\|Query\|qry: CategorisationQueryT ype\|
	898
	899	ProvisionAgreementQueryType: ProvisionAgreementQueryType defines the structure of a provision agreement query message.
	900
	901	Derivation:
	902
	903	//MessageType// (restriction)
	904	ProvisionAgreementQueryType
	905
	906	Content:
	907
	908	Header, Query
	909
	910	Element Documentation:
	911
	912	\|Name\|Type\|Documentation
	913	\|Header\|BasicHeaderType\|
	914	\|Query\|qry: ProvisionAgreementQu eryType\|
	915
	916	ConstraintQueryType: ConstraintQueryType defines the structure of a constraint query message.
	917
	918	Derivation:
	919
	920	//MessageType// (restriction)
	921	ConstraintQueryType
	922
	923	Content:
	924
	925	Header, Query
	926
	927	Element Documentation:
	928
	929	\|Name\|Type\|Documentation
	930	\|Header\|BasicHeaderType\|
	931	\|Query\|qry: ConstraintQueryType\|
	932
	933	TransformationSchemeQueryType: TransformationSchemeQueryType defines the structure of a transformation scheme query message.
	934
	935	Derivation:
	936
	937	//MessageType// (restriction)
	938	TransformationSchemeQueryType
	939
	940	Content:
	941
	942	Header, Query
	943
	944	Element Documentation:
	945
	946	\|Name\|Type\|Documentation
	947	\|Header\|BasicHeaderType\|
	948	\|Query\|qry: TransformationScheme QueryType\|
	949
	950	VtlMappingSchemeQueryType: VtlMappingSchemeQueryType defines the structure of a VTL mappings scheme query message.
	951
	952	Derivation:
	953
	954	//MessageType// (restriction)
	955	VtlMappingSchemeQueryType
	956
	957	Content:
	958
	959	Header, Query
	960
	961	Element Documentation:
	962
	963	\|Name\|Type\|Documentation
	964	\|Header\|BasicHeaderType\|
	965	\|Query\|qry: VtlMappingSchemeQuer yType\|
	966
	967	NamePersonalisationSchemeQueryType: NamePersonalisationSchemeQueryType defines the structure of a name personalisation scheme query message.
	968
	969	Derivation:
	970
	971	//MessageType// (restriction)
	972	NamePersonalisationSchemeQueryType
	973
	974	Content:
	975
	976	Header, Query
	977
	978	Element Documentation:
	979
	980	\|Name\|Type\|Documentation
	981	\|Header\|BasicHeaderType\|
	982	\|Query\|qry: NamePersonalisationS chemeQueryType\|
	983
	984	RulesetSchemeQueryType: RulesetSchemeQueryType defines the structure of a ruleset scheme query message.
	985
	986	Derivation:
	987
	988	//MessageType// (restriction)
	989	RulesetSchemeQueryType
	990
	991	Content:
	992
	993	Header, Query
	994
	995	Element Documentation:
	996
	997	\|Name\|Type\|Documentation
	998	\|Header\|BasicHeaderType\|
	999	\|Query\|qry: RulesetSchemeQueryTy pe\|
	1000
	1001	UserDefinedOperatorSchemeQueryType: UserDefinedOperatorSchemeQueryType defines the structure of a user defined operator scheme query message.
	1002
	1003	Derivation:
	1004
	1005	//MessageType// (restriction)
	1006	UserDefinedOperatorSchemeQueryType
	1007
	1008	Content:
	1009
	1010	Header, Query
	1011
	1012	Element Documentation:
	1013
	1014	\|Name\|Type\|Documentation
	1015	\|Header\|BasicHeaderType\|
	1016	\|Query\|qry: UserDefinedOperatorS chemeQueryType\|
	1017
	1018	CustomTypeSchemeQueryType: CustomTypeSchemeQueryType defines the structure of a custom type scheme query message.
	1019
	1020	Derivation:
	1021
	1022	//MessageType// (restriction)
2.3	1023	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] CustomTypeSchemeQueryType
2.2	1024
	1025	Content:
	1026
	1027	Header, Query
	1028
	1029	Element Documentation:
	1030
	1031	\|Name\|Type\|Documentation
	1032	\|Header\|BasicHeaderType\|
	1033	\|Query\|qry: CustomTypeSchemeQuer yType\|
	1034
	1035	ErrorType: ErrorType describes the structure of an error response.
	1036
	1037	Content:
	1038
	1039	ErrorMessage+
	1040
	1041	Element Documentation:
	1042
	1043	\|Name\|Type\|Documentation
	1044	\|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.
	1045
	1046	//BaseHeaderType//: BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this
	1047
	1048	Content:
	1049
	1050	ID, Test, Prepared, Sender, Receiver, com:Name, Structure, DataProvider?, DataSetAction?, DataSetID, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
	1051
	1052	Element Documentation:
	1053
	1054	\|Name\|Type\|Documentation
	1055	\|ID\|com:IDType\|ID identifies an identification for the message, assigned by the sender.
	1056	\|Test\|xs:boolean\|Test indicates whether the message is for test purposes or not.
	1057	\|Prepared\|HeaderTimeType\|Prepared is the date the message was prepared.
	1058	\|Sender\|SenderType\|Sender is information about the party that is transmitting the message.
	1059	\|Receiver\|PartyType\|Receiver is information about the party that is the intended recipient of the message.
	1060	\|com:Name\|com:TextType\|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1061	\|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.
	1062	\|DataProvider\|com: DataProviderReferenc eType\|DataProvider identifies the provider of the data for a data/reference metadata message.
	1063	\|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).
	1064	\|DataSetID\|com:IDType\|DataSetID provides an identifier for a contained data set.
	1065	\|Extracted\|xs:dateTime\|Extracted is a time-stamp from the system rendering the data.
	1066	\|ReportingBegin\|com: ObservationalTimePer iodType\|ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1067	\|ReportingEnd\|com: ObservationalTimePer iodType\|ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1068	\|EmbargoDate\|xs:dateTime\|EmbargoDate holds a time period before which the data included in this message is not available.
	1069	\|Source\|com:TextType\|Source provides human-readable information about the source of the data.
	1070
	1071	StructureHeaderType: StructureHeaderType defines the structure for structural metadata messages.
	1072
	1073	Derivation:
	1074
	1075	//BaseHeaderType// (restriction)
	1076	StructureHeaderType
	1077
	1078	Content:
	1079
	1080	ID, Test, Prepared, Sender, Receiver, com:Name, Source*
	1081
	1082	Element Documentation:
	1083
	1084	\|Name\|Type\|Documentation
	1085	\|ID\|com:IDType\|ID identifies an identification for the message, assigned by the sender.
	1086	\|Test\|xs:boolean\|Test indicates whether the message is for test purposes or not.
	1087	\|Prepared\|HeaderTimeType\|Prepared is the date the message was prepared.
	1088	\|Sender\|SenderType\|Sender is information about the party that is transmitting the message.
	1089	\|Receiver\|PartyType\|Receiver is information about the party that is the intended recipient of the message.
	1090	\|com:Name\|com:TextType\|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1091	\|Source\|com:TextType\|Source provides human-readable information about the source of the data.
	1092
	1093	GenericDataHeaderType: GenericDataHeaderType defines the header structure for a generic data message.
	1094
	1095	Derivation:
	1096
	1097	//BaseHeaderType// (restriction)
2.3	1098	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] GenericDataHeaderType
2.2	1099
	1100	Content:
	1101
	1102	ID, Test, Prepared, Sender, Receiver, com:Name, Structure+, DataProvider?, DataSetAction?, DataSetID, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source
	1103
	1104	Element Documentation:
	1105
	1106	\|Name\|Type\|Documentation
	1107	\|ID\|com:IDType\|ID identifies an identification for the message, assigned by the sender.
	1108	\|Test\|xs:boolean\|Test indicates whether the message is for test purposes or not.
	1109	\|Prepared\|HeaderTimeType\|Prepared is the date the message was prepared.
	1110	\|Sender\|SenderType\|Sender is information about the party that is transmitting the message.
	1111	\|Receiver\|PartyType\|Receiver is information about the party that is the intended recipient of the message.
	1112	\|com:Name\|com:TextType\|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1113	\|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.
	1114	\|DataProvider\|com: DataProviderReferenc eType\|DataProvider identifies the provider of the data for a data/reference metadata message.
	1115	\|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).
	1116	\|DataSetID\|com:IDType\|DataSetID provides an identifier for a contained data set.
	1117	\|Extracted\|xs:dateTime\|Extracted is a time-stamp from the system rendering the data.
	1118	\|ReportingBegin\|com: ObservationalTimePer iodType\|ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1119	\|ReportingEnd\|com: ObservationalTimePer iodType\|ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1120	\|EmbargoDate\|xs:dateTime\|EmbargoDate holds a time period before which the data included in this message is not available.
	1121	\|Source\|com:TextType\|Source provides human-readable information about the source of the data.
	1122
	1123	GenericTimeSeriesDataHeaderType: GenericTimeSeriesDataHeaderType defines the header structure for a time series only generic data message.
	1124
	1125	Derivation:
	1126
	1127	//BaseHeaderType// (restriction)
	1128	GenericDataHeaderType (restriction)
	1129	GenericTimeSeriesDataHeaderType
	1130
	1131	Content:
	1132
	1133	ID, Test, Prepared, Sender, Receiver, com:Name, Structure, DataProvider?, DataSetAction?, DataSetID, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source
	1134
	1135	Element Documentation:
	1136
	1137	\|Name\|Type\|Documentation
	1138	\|ID\|com:IDType\|ID identifies an identification for the message, assigned by the sender.
	1139	\|Test\|xs:boolean\|Test indicates whether the message is for test purposes or not.
	1140	\|Prepared\|HeaderTimeType\|Prepared is the date the message was prepared.
	1141	\|Sender\|SenderType\|Sender is information about the party that is transmitting the message.
	1142	\|Receiver\|PartyType\|Receiver is information about the party that is the intended recipient of the message.
	1143	\|com:Name\|com:TextType\|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1144	\|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.
	1145	\|DataProvider\|com: DataProviderReferenc eType\|DataProvider identifies the provider of the data for a data/reference metadata message.
	1146	\|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).
	1147	\|DataSetID\|com:IDType\|DataSetID provides an identifier for a contained data set.
	1148	\|Extracted\|xs:dateTime\|Extracted is a time-stamp from the system rendering the data.
	1149	\|ReportingBegin\|com: ObservationalTimePer iodType\|ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1150	\|ReportingEnd\|com: ObservationalTimePer iodType\|ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1151	\|EmbargoDate\|xs:dateTime\|EmbargoDate holds a time period before which the data included in this message is not available.
	1152	\|Source\|com:TextType\|Source provides human-readable information about the source of the data.
	1153
	1154	StructureSpecificDataHeaderType: StructureSpecificDataHeaderType defines the header structure for a structure specific data message.
	1155
	1156	Derivation:
	1157
	1158	//BaseHeaderType// (restriction)
	1159	StructureSpecificDataHeaderType
	1160
	1161	Content:
	1162
	1163	ID, Test, Prepared, Sender, Receiver, com:Name, Structure+, DataProvider?, DataSetAction?, DataSetID, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source
	1164
	1165	Element Documentation:
	1166
	1167	\|Name\|Type\|Documentation
	1168	\|ID\|com:IDType\|ID identifies an identification for the message, assigned by the sender.
	1169	\|Test\|xs:boolean\|Test indicates whether the message is for test purposes or not.
	1170	\|Prepared\|HeaderTimeType\|Prepared is the date the message was prepared.
	1171	\|Sender\|SenderType\|Sender is information about the party that is transmitting the message.
	1172	\|Receiver\|PartyType\|Receiver is information about the party that is the intended recipient of the message.
	1173	\|com:Name\|com:TextType\|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1174	\|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.
	1175	\|DataProvider\|com: DataProviderReferenc eType\|DataProvider identifies the provider of the data for a data/reference metadata message.
	1176	\|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).
	1177	\|DataSetID\|com:IDType\|DataSetID provides an identifier for a contained data set.
	1178	\|Extracted\|xs:dateTime\|Extracted is a time-stamp from the system rendering the data.
	1179	\|ReportingBegin\|com: ObservationalTimePer iodType\|ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1180	\|ReportingEnd\|com: ObservationalTimePer iodType\|ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1181	\|EmbargoDate\|xs:dateTime\|EmbargoDate holds a time period before which the data included in this message is not available.
	1182	\|Source\|com:TextType\|Source provides human-readable information about the source of the data.
	1183
	1184	StructureSpecificTimeSeriesDataHeaderType: StructureSpecificTimeSeriesDataHeaderType defines the header structure for a time series only structure specific data message.
	1185
	1186	Derivation:
	1187
	1188	//BaseHeaderType// (restriction)
	1189	StructureSpecificDataHeaderType (restriction)
	1190	StructureSpecificTimeSeriesDataHeaderType
	1191
	1192	Content:
	1193
	1194	ID, Test, Prepared, Sender, Receiver, com:Name, Structure+, DataProvider?, DataSetAction?, DataSetID, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source
	1195
	1196	Element Documentation:
	1197
	1198	\|Name\|Type\|Documentation
	1199	\|ID\|com:IDType\|ID identifies an identification for the message, assigned by the sender.
	1200	\|Test\|xs:boolean\|Test indicates whether the message is for test purposes or not.
	1201	\|Prepared\|HeaderTimeType\|Prepared is the date the message was prepared.
	1202	\|Sender\|SenderType\|Sender is information about the party that is transmitting the message.
	1203	\|Receiver\|PartyType\|Receiver is information about the party that is the intended recipient of the message.
	1204	\|com:Name\|com:TextType\|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1205	\|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.
	1206	\|DataProvider\|com: DataProviderReferenc eType\|DataProvider identifies the provider of the data for a data/reference metadata message.
	1207	\|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).
	1208	\|DataSetID\|com:IDType\|DataSetID provides an identifier for a contained data set.
	1209	\|Extracted\|xs:dateTime\|Extracted is a time-stamp from the system rendering the data.
	1210	\|ReportingBegin\|com: ObservationalTimePer iodType\|ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1211	\|ReportingEnd\|com: ObservationalTimePer iodType\|ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1212	\|EmbargoDate\|xs:dateTime\|EmbargoDate holds a time period before which the data included in this message is not available.
	1213	\|Source\|com:TextType\|Source provides human-readable information about the source of the data.
	1214
	1215	GenericMetadataHeaderType: GenericMetadataHeaderType defines the header format for generic reference metadata.
	1216
	1217	Derivation:
	1218
	1219	//BaseHeaderType// (restriction)
	1220	GenericMetadataHeaderType
	1221
	1222	Content:
	1223
	1224	ID, Test, Prepared, Sender, Receiver, com:Name, Structure+, DataProvider?, DataSetAction?, DataSetID, Extracted?, Source
	1225
	1226	Element Documentation:
	1227
	1228	\|Name\|Type\|Documentation
	1229	\|ID\|com:IDType\|ID identifies an identification for the message, assigned by the sender.
	1230	\|Test\|xs:boolean\|Test indicates whether the message is for test purposes or not.
	1231	\|Prepared\|HeaderTimeType\|Prepared is the date the message was prepared.
	1232	\|Sender\|SenderType\|Sender is information about the party that is transmitting the message.
	1233	\|Receiver\|PartyType\|Receiver is information about the party that is the intended recipient of the message.
	1234	\|com:Name\|com:TextType\|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1235	\|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.
	1236	\|DataProvider\|com: DataProviderReferenc eType\|DataProvider identifies the provider of the data for a data/reference metadata message.
	1237	\|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).
	1238	\|DataSetID\|com:IDType\|DataSetID provides an identifier for a contained data set.
	1239	\|Extracted\|xs:dateTime\|Extracted is a time-stamp from the system rendering the data.
	1240	\|Source\|com:TextType\|Source provides human-readable information about the source of the data.
	1241
	1242	StructureSpecificMetadataHeaderType: StructureSpecificMetadataHeaderType defines the header format for metadata structure definition specific reference metadata messages.
	1243
	1244	Derivation:
	1245
	1246	//BaseHeaderType// (restriction)
2.3	1247	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] StructureSpecificMetadataHeaderType
2.2	1248
	1249	Content:
	1250
	1251	ID, Test, Prepared, Sender, Receiver, com:Name, Structure+, DataProvider?, DataSetAction?, DataSetID, Extracted?, Source
	1252
	1253	Element Documentation:
	1254
	1255	\|Name\|Type\|Documentation
	1256	\|ID\|com:IDType\|ID identifies an identification for the message, assigned by the sender.
	1257	\|Test\|xs:boolean\|Test indicates whether the message is for test purposes or not.
	1258	\|Prepared\|HeaderTimeType\|Prepared is the date the message was prepared.
	1259	\|Sender\|SenderType\|Sender is information about the party that is transmitting the message.
	1260	\|Receiver\|PartyType\|Receiver is information about the party that is the intended recipient of the message.
	1261	\|com:Name\|com:TextType\|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1262	\|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.
	1263	\|DataProvider\|com: DataProviderReferenc eType\|DataProvider identifies the provider of the data for a data/reference metadata message.
	1264	\|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).
	1265	\|DataSetID\|com:IDType\|DataSetID provides an identifier for a contained data set.
	1266	\|Extracted\|xs:dateTime\|Extracted is a time-stamp from the system rendering the data.
	1267	\|Source\|com:TextType\|Source provides human-readable information about the source of the data.
	1268
	1269	BasicHeaderType: BasicHeaderType defines the most basic header information used in simple message exchanges.
	1270
	1271	Derivation:
	1272
	1273	//BaseHeaderType// (restriction)
2.3	1274	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] BasicHeaderType
2.2	1275
	1276	Content:
	1277
	1278	ID, Test, Prepared, Sender, Receiver
	1279
	1280	Element Documentation:
	1281
	1282	\|Name\|Type\|Documentation
	1283	\|ID\|com:IDType\|ID identifies an identification for the message, assigned by the sender.
	1284	\|Test\|xs:boolean\|Test indicates whether the message is for test purposes or not.
	1285	\|Prepared\|HeaderTimeType\|Prepared is the date the message was prepared.
	1286	\|Sender\|SenderType\|Sender is information about the party that is transmitting the message.
	1287	\|Receiver\|PartyType\|Receiver is information about the party that is the intended recipient of the message.
	1288
	1289	PartyType: PartyType defines the information which is sent about various parties such as senders and receivers of messages.
	1290
	1291	Attributes:
	1292
	1293	id
	1294
	1295	Content:
	1296
	1297	com:Name, Contact
	1298
	1299	Attribute Documentation:
	1300
	1301	\|Name\|Type\|Documentation
	1302	\|id\|com:IDType\|The id attribute holds the identification of the party.
	1303
	1304	Element Documentation:
	1305
	1306	\|Name\|Type\|Documentation
	1307	\|com:Name\|com:TextType\|Name is a human-readable name of the party.
	1308	\|Contact\|ContactType\|Contact provides contact information for the party in regard to the transmission of the message.
	1309
	1310	SenderType: SenderType extends the basic party structure to add an optional time zone declaration.
	1311
	1312	Derivation:
	1313
	1314	PartyType (extension)
2.3	1315	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] SenderType
2.2	1316
	1317	Attributes:
	1318
	1319	id
	1320
	1321	Content:
	1322
	1323	com:Name, Contact, Timezone?
	1324
	1325	Attribute Documentation:
	1326
	1327	\|Name\|Type\|Documentation
	1328	\|id\|com:IDType\|The id attribute holds the identification of the party.
	1329
	1330	Element Documentation:
	1331
	1332	\|Name\|Type\|Documentation
	1333	\|com:Name\|com:TextType\|Name is a human-readable name of the party.
	1334	\|Contact\|ContactType\|Contact provides contact information for the party in regard to the transmission of the message.
	1335	\|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".
	1336
	1337	ContactType: ContactType provides defines the contact information about a party.
	1338
	1339	Content:
	1340
	1341	com:Name, Department, Role, (Telephone \| Fax \| X400 \| URI \| Email)
	1342
	1343	Element Documentation:
	1344
	1345	\|Name\|Type\|Documentation
	1346	\|com:Name\|com:TextType\|Name contains a human-readable name for the contact.
	1347	\|Department\|com:TextType\|Department is designation of the organisational structure by a linguistic expression, within which the contact person works.
	1348	\|Role\|com:TextType\|Role is the responsibility of the contact person with respect to the object for which this person is the contact.
	1349	\|Telephone\|xs:string\|Telephone holds the telephone number for the contact person.
	1350	\|Fax\|xs:string\|Fax holds the fax number for the contact person.
	1351	\|X400\|xs:string\|X400 holds the X.400 address for the contact person.
	1352	\|URI\|xs:anyURI\|URI holds an information URL for the contact person.
	1353	\|Email\|xs:string\|Email holds the email address for the contact person.
	1354
2.3	1355	1.
	1356	11.
2.2	1357	111. Simple Types
	1358
	1359	HeaderTimeType: Provides a union type of xs:date and xs:dateTime for the header fields in the message.
	1360
	1361	Union of:
	1362
	1363	xs:dateTime, xs:date.
	1364
2.3	1365	1.
2.2	1366	11. Message Footer Namespace
	1367
	1368	http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer
	1369
2.3	1370	1.
	1371	11.
2.2	1372	111. Summary
	1373
	1374	Referenced Namespaces:
	1375
	1376	\|Namespace\|Prefix
	1377	\|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common\|com
	1378	\|http:~/~/www.w3.org/2001/XMLSchema\|xs
	1379
	1380	Contents:
	1381
	1382	1 Global Element
	1383	2 Complex Types
	1384	1 Simple Type
	1385
2.3	1386	1.
	1387	11.
2.2	1388	111. Global Elements
	1389
	1390	Footer (FooterType): Footer is used to communicate information such as error and warnings after the payload of a message.
	1391
2.3	1392	1.
	1393	11.
2.2	1394	111. Complex Types
	1395
	1396	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.
	1397
	1398	Content:
	1399
	1400	Message+
	1401
	1402	Element Documentation:
	1403
	1404	\|Name\|Type\|Documentation
	1405	\|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.
	1406
	1407	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.
	1408
	1409	Derivation:
	1410
	1411	com:StatusMessageType (restriction)
2.3	1412	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] com:CodedStatusMessageType (extension)
	1413	[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif\|\|alt="-"]] FooterMessageType
2.2	1414
	1415	Attributes:
	1416
	1417	code, severity?
	1418
	1419	Content:
	1420
	1421	com:Text+
	1422
	1423	Attribute Documentation:
	1424
	1425	\|Name\|Type\|Documentation
	1426	\|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.
	1427	\|severity\|SeverityCodeType\|
	1428
	1429	Element Documentation:
	1430
	1431	\|Name\|Type\|Documentation
	1432	\|com:Text\|com:TextType\|Text contains the text of the message, in parallel language values.
	1433
2.3	1434	1.
	1435	11.
2.2	1436	111. Simple Types
	1437
	1438	SeverityCodeType:
	1439
	1440	Derived by restriction of xs:string .
	1441
	1442	Enumerations:
	1443
	1444	\|Value\|Documentation
	1445	\|Error\|Error indicates the status message coresponds to an error.
	1446	\|Warning\|Warning indicates that the status message corresponds to a warning.
	1447	\|Information\|Information indicates that the status message corresponds to an informational message.
	1448
	1449
	1450
	1451
	1452
	1453
	1454
	1455
	1456
	1457
	1458
	1459
	1460
	1461
	1462