Changes for page Part I. Message Namespace

Summary

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

Details

Page properties

Content

...	...	@@ -6,7 +6,7 @@
6	6
7	7	The following problems with the specification dated April 2011 have been rectified as described below.
8	8
9		-**~1. Problem**
	9	+1. **Problem**
10	10
11	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
...	...	@@ -14,7 +14,7 @@
14	14
15	15	The documentation of the Structure element (line 40) has been updated to remove this reference.
16	16
17		-= 1. Introduction =
	17	+1. Introduction
18	18
19	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
...	...	@@ -28,28 +28,28 @@
28	28
29	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	30
31		-= 2. Schema Documentation =
	31	+1. Schema Documentation
	32	+11. Message Namespace
32	32
33		-== 2.1 Message Namespace ==
34		-
35	35	**http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message**
36	36
37		-=== 2.1.1 Summary ===
	36	+1.
	37	+11.
	38	+111. Summary
38	38
39	39	Referenced Namespaces:
40	40
41		-(% style="width:788.294px" %)
42		-|(% style="width:612px" %)**Namespace**|(% style="width:173px" %)**Prefix**
43		-|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common|(% style="width:173px" %)com
44		-|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/generic|(% style="width:173px" %)dat
45		-|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/structurespecific|(% style="width:173px" %)dsd
46		-|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer|(% style="width:173px" %)ftr
47		-|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/generic|(% style="width:173px" %)rep
48		-|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/structurespecific|(% style="width:173px" %)msd
49		-|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/query|(% style="width:173px" %)qry
50		-|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/registry|(% style="width:173px" %)ref
51		-|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/structure|(% style="width:173px" %)str
52		-|(% style="width:612px" %)http:~/~/www.w3.org/2001/XMLSchema|(% style="width:173px" %)xs
	42	+|**Namespace**|**Prefix**
	43	+|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common|com
	44	+|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/generic|dat
	45	+|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/structurespecific|dsd
	46	+|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer|ftr
	47	+|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/generic|rep
	48	+|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/structurespecific|msd
	49	+|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/query|qry
	50	+|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/registry|ref
	51	+|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/structure|str
	52	+|http:~/~/www.w3.org/2001/XMLSchema|xs
53	53
54	54	Contents:
55	55
...	...	@@ -57,7 +57,9 @@
57	57	62 Complex Types
58	58	1 Simple Type
59	59
60		-=== 2.1.2 Global Elements ===
	60	+1.
	61	+11.
	62	+111. Global Elements
61	61
62	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.
63	63
...	...	@@ -159,7 +159,9 @@
159	159
160	160	**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.
161	161
162		-=== 2.1.3 Complex Types ===
	164	+1.
	165	+11.
	166	+111. Complex Types
163	163
164	164	**//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.
165	165
...	...	@@ -178,7 +178,7 @@
178	178	Derivation:
179	179
180	180	//MessageType// (restriction)
181		- StructureType
	185	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureType
182	182
183	183	Content:
184	184
...	...	@@ -186,11 +186,10 @@
186	186
187	187	Element Documentation:
188	188
189		-(% style="width:856.294px" %)
190		-|**Name**|(% style="width:210px" %)**Type**|(% style="width:455px" %)**Documentation**
191		-|Header|(% style="width:210px" %)StructureHeaderType|(% style="width:455px" %)
192		-|Structures|(% style="width:210px" %)str:StructuresType|(% style="width:455px" %)
193		-|ftr:Footer|(% style="width:210px" %)ftr:FooterType|(% style="width:455px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
	193	+|**Name**|**Type**|**Documentation**
	194	+|Header|StructureHeaderType|
	195	+|Structures|str:StructuresType|
	196	+|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
194	194
195	195	**GenericDataType: **GenericDataType defines the contents of a generic data message.
196	196
...	...	@@ -197,7 +197,7 @@
197	197	Derivation:
198	198
199	199	//MessageType// (restriction)
200		- GenericDataType
	203	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataType
201	201
202	202	Content:
203	203
...	...	@@ -205,19 +205,18 @@
205	205
206	206	Element Documentation:
207	207
208		-(% style="width:847.294px" %)
209		-|**Name**|(% style="width:227px" %)**Type**|(% style="width:450px" %)**Documentation**
210		-|Header|(% style="width:227px" %)GenericDataHeaderTyp e|(% style="width:450px" %)
211		-|DataSet|(% style="width:227px" %)dat:DataSetType|(% style="width:450px" %)
212		-|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	+|**Name**|**Type**|**Documentation**
	212	+|Header|GenericDataHeaderTyp e|
	213	+|DataSet|dat:DataSetType|
	214	+|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
213	213
214	214	**GenericTimeSeriesDataType: **GenericTimeSeriesDataType defines the structure of the generic time series data message.
215	215
216	216	Derivation:
217	217
218		-* //MessageType// (restriction)
219		-** GenericDataType (restriction)
220		-*** GenericTimeSeriesDataType
	220	+//MessageType// (restriction)
	221	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataType (restriction)
	222	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericTimeSeriesDataType
221	221
222	222	Content:
223	223
...	...	@@ -225,18 +225,17 @@
225	225
226	226	Element Documentation:
227	227
228		-(% style="width:856.294px" %)
229		-|**Name**|(% style="width:239px" %)**Type**|(% style="width:458px" %)**Documentation**
230		-|Header|(% style="width:239px" %)GenericTimeSeriesDat aHeaderType|(% style="width:458px" %)
231		-|DataSet|(% style="width:239px" %)dat: TimeSeriesDataSetTyp e|(% style="width:458px" %)
232		-|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	+|**Name**|**Type**|**Documentation**
	231	+|Header|GenericTimeSeriesDat aHeaderType|
	232	+|DataSet|dat: TimeSeriesDataSetTyp e|
	233	+|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
233	233
234	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	235
236	236	Derivation:
237	237
238		-* //MessageType// (restriction)
239		-** StructureSpecificDataType
	239	+//MessageType// (restriction)
	240	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificDataType
240	240
241	241	Content:
242	242
...	...	@@ -244,19 +244,18 @@
244	244
245	245	Element Documentation:
246	246
247		-(% style="width:828.294px" %)
248		-|**Name**|(% style="width:247px" %)**Type**|(% style="width:420px" %)**Documentation**
249		-|Header|(% style="width:247px" %)StructureSpecificDat aHeaderType|(% style="width:420px" %)
250		-|DataSet|(% style="width:247px" %)//dsd:DataSetType//|(% style="width:420px" %)
251		-|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	+|**Name**|**Type**|**Documentation**
	249	+|Header|StructureSpecificDat aHeaderType|
	250	+|DataSet|//dsd:DataSetType//|
	251	+|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
252	252
253	253	**StructureSpecificTimeSeriesDataType: **StructureSpecificTimeSeriesDataType defines the structure of the structure specific time series data message.
254	254
255	255	Derivation:
256	256
257		-* //MessageType// (restriction)
258		-** StructureSpecificDataType (restriction)
259		-*** StructureSpecificTimeSeriesDataType
	257	+//MessageType// (restriction)
	258	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificDataType (restriction)
	259	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificTimeSeriesDataType
260	260
261	261	Content:
262	262
...	...	@@ -264,18 +264,17 @@
264	264
265	265	Element Documentation:
266	266
267		-(% style="width:839.294px" %)
268		-|**Name**|(% style="width:256px" %)**Type**|(% style="width:434px" %)**Documentation**
269		-|Header|(% style="width:256px" %)StructureSpecificTim eSeriesDataHeaderTyp e|(% style="width:434px" %)
270		-|DataSet|(% style="width:256px" %)//dsd: TimeSeriesDataSetTyp e//|(% style="width:434px" %)
271		-|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	+|**Name**|**Type**|**Documentation**
	268	+|Header|StructureSpecificTim eSeriesDataHeaderTyp e|
	269	+|DataSet|//dsd: TimeSeriesDataSetTyp e//|
	270	+|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
272	272
273	273	**GenericMetadataType: **GenericMetadataType defines the contents of a generic metadata message.
274	274
275	275	Derivation:
276	276
277		-* //MessageType// (restriction)
278		-** GenericMetadataType
	276	+//MessageType// (restriction)
	277	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericMetadataType
279	279
280	280	Content:
281	281
...	...	@@ -283,18 +283,17 @@
283	283
284	284	Element Documentation:
285	285
286		-(% style="width:836.294px" %)
287		-|(% style="width:181px" %)**Name**|(% style="width:225px" %)**Type**|(% style="width:427px" %)**Documentation**
288		-|(% style="width:181px" %)Header|(% style="width:225px" %)GenericMetadataHeade rType|(% style="width:427px" %)
289		-|(% style="width:181px" %)MetadataSet|(% style="width:225px" %)rep:MetadataSetType|(% style="width:427px" %)
290		-|(% 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	+|**Name**|**Type**|**Documentation**
	286	+|Header|GenericMetadataHeade rType|
	287	+|MetadataSet|rep:MetadataSetType|
	288	+|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
291	291
292	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.
293	293
294	294	Derivation:
295	295
296		-* //MessageType// (restriction)
297		-** StructureSpecificMetadataType
	294	+//MessageType// (restriction)
	295	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataType
298	298
299	299	Content:
300	300
...	...	@@ -302,18 +302,17 @@
302	302
303	303	Element Documentation:
304	304
305		-(% style="width:841.294px" %)
306		-|(% style="width:160px" %)**Name**|(% style="width:250px" %)**Type**|(% style="width:428px" %)**Documentation**
307		-|(% style="width:160px" %)Header|(% style="width:250px" %)StructureSpecificMet adataHeaderType|(% style="width:428px" %)
308		-|(% style="width:160px" %)MetadataSet|(% style="width:250px" %)//msd:MetadataSetType//|(% style="width:428px" %)
309		-|(% 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	+|**Name**|**Type**|**Documentation**
	304	+|Header|StructureSpecificMet adataHeaderType|
	305	+|MetadataSet|//msd:MetadataSetType//|
	306	+|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
310	310
311	311	**RegistryInterfaceType: **This is a type which describes a structure for holding all of the various dedicated registry interface message types.
312	312
313	313	Derivation:
314	314
315		-* //MessageType// (restriction)
316		-** RegistryInterfaceType
	312	+//MessageType// (restriction)
	313	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType
317	317
318	318	Content:
319	319
...	...	@@ -321,84 +321,83 @@
321	321
322	322	Element Documentation:
323	323
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.
	321	+|**Name**|**Type**|**Documentation**
	322	+|Header|BasicHeaderType|
	323	+|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.
	324	+|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.
	325	+|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.
	326	+|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.
	327	+|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.
	328	+|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.
	329	+|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.
	330	+|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.
	331	+|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
	332	+|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.
	333	+|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.
	334	+|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
339	339
340	340	**SubmitRegistrationsRequestType: **SubmitRegistrationsRequestType defines the structure of a registry submit registration requests document.
341	341
342	342	Derivation:
343	343
344		-* //MessageType// (restriction)
345		-** RegistryInterfaceType (restriction)
346		-*** SubmitRegistrationsRequestType
	340	+//MessageType// (restriction)
	341	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	342	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitRegistrationsRequestType
347	347
348	348	Content:
349	349
350		-* Header, SubmitRegistrationsRequest
351		-* Element Documentation:
	346	+Header, SubmitRegistrationsRequest
352	352
353		-(% style="width:844.294px" %)
354		-|**Name**|**Type**|(% style="width:377px" %)**Documentation**
355		-|Header|BasicHeaderType|(% style="width:377px" %)
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.
	348	+Element Documentation:
357	357
	350	+|**Name**|**Type**|**Documentation**
	351	+|Header|BasicHeaderType|
	352	+|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.
	353	+
358	358	**SubmitRegistrationsResponseType: **SubmitRegistrationsResponseType defines the structure of a registry submit registration response document.
359	359
360	360	Derivation:
361	361
362		-* //MessageType// (restriction)
363		-** RegistryInterfaceType (restriction)
364		-*** SubmitRegistrationsResponseType
	358	+//MessageType// (restriction)
	359	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	360	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitRegistrationsResponseType
365	365
366	366	Content:
367	367
368		-* Header, SubmitRegistrationsResponse, ftr:Footer?
369		-* Element Documentation:
	364	+Header, SubmitRegistrationsResponse, ftr:Footer?
370	370
371		-(% style="width:847.294px" %)
372		-|**Name**|(% style="width:210px" %)**Type**|(% style="width:408px" %)**Documentation**
373		-|Header|(% style="width:210px" %)BasicHeaderType|(% style="width:408px" %)
374		-|SubmitRegistrationsR esponse|(% style="width:210px" %)ref: SubmitRegistrationsR esponseType|(% style="width:408px" %)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.
375		-|ftr:Footer|(% style="width:210px" %)ftr:FooterType|(% style="width:408px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
	366	+Element Documentation:
376	376
	368	+|**Name**|**Type**|**Documentation**
	369	+|Header|BasicHeaderType|
	370	+|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.
	371	+|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
	372	+
377	377	**QueryRegistrationRequestType: **QueryRegistrationRequestType defines the structure of a registry query registration request document.
378	378
379	379	Derivation:
380	380
381		-* //MessageType// (restriction)
382		-** RegistryInterfaceType (restriction)
383		-*** QueryRegistrationRequestType
	377	+//MessageType// (restriction)
	378	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	379	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationRequestType
384	384
385	385	Content:
386	386
387		-* Header, QueryRegistrationRequest
388		-* Element Documentation:
	383	+Header, QueryRegistrationRequest
389	389
390		-(% style="width:847.294px" %)
391		-|**Name**|**Type**|(% style="width:397px" %)**Documentation**
392		-|Header|BasicHeaderType|(% style="width:397px" %)
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.
	385	+Element Documentation:
394	394
	387	+|**Name**|**Type**|**Documentation**
	388	+|Header|BasicHeaderType|
	389	+|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.
	390	+
395	395	**QueryRegistrationResponseType: **SubmitRegistrationRequestType defines the structure of a registry submit registration response document.
396	396
397	397	Derivation:
398	398
399		-* //MessageType// (restriction)
400		-** RegistryInterfaceType (restriction)
401		-*** QueryRegistrationResponseType
	395	+//MessageType// (restriction)
	396	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	397	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationResponseType
402	402
403	403	Content:
404	404
...	...	@@ -406,19 +406,18 @@
406	406
407	407	Element Documentation:
408	408
409		-(% style="width:856.294px" %)
410		-|**Name**|(% style="width:235px" %)**Type**|(% style="width:407px" %)**Documentation**
411		-|Header|(% style="width:235px" %)BasicHeaderType|(% style="width:407px" %)
412		-|QueryRegistrationRes ponse|(% style="width:235px" %)ref: QueryRegistrationRes ponseType|(% style="width:407px" %)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.
413		-|ftr:Footer|(% style="width:235px" %)ftr:FooterType|(% style="width:407px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
	405	+|**Name**|**Type**|**Documentation**
	406	+|Header|BasicHeaderType|
	407	+|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.
	408	+|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
414	414
415	415	**SubmitStructureRequestType: **SubmitStructureRequestType defines the structure of a registry submit structure request document.
416	416
417	417	Derivation:
418	418
419		-* //MessageType// (restriction)
420		-** RegistryInterfaceType (restriction)
421		-*** SubmitStructureRequestType
	414	+//MessageType// (restriction)
	415	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	416	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureRequestType
422	422
423	423	Content:
424	424
...	...	@@ -426,251 +426,250 @@
426	426
427	427	Element Documentation:
428	428
429		-(% style="width:870.294px" %)
430		-|**Name**|**Type**|(% style="width:453px" %)**Documentation**
431		-|Header|BasicHeaderType|(% style="width:453px" %)
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.
	424	+|**Name**|**Type**|**Documentation**
	425	+|Header|BasicHeaderType|
	426	+|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.
433	433
434	434	**SubmitStructureResponseType: **SubmitStructureResponseType defines the structure of a registry submit registration response document.
435	435
436	436	Derivation:
437	437
438		-* //MessageType// (restriction)
439		-** RegistryInterfaceType (restriction)
440		-*** SubmitStructureResponseType
	432	+//MessageType// (restriction)
	433	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	434	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureResponseType
441	441
442	442	Content:
443	443
444		-* Header, SubmitStructureResponse, ftr:Footer?
445		-* Element Documentation:
	438	+Header, SubmitStructureResponse, ftr:Footer?
446	446
447		-(% style="width:835.294px" %)
448		-|**Name**|(% style="width:246px" %)**Type**|(% style="width:366px" %)**Documentation**
449		-|Header|(% style="width:246px" %)BasicHeaderType|(% style="width:366px" %)
450		-|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.
451		-|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.
	440	+Element Documentation:
452	452
	442	+|**Name**|**Type**|**Documentation**
	443	+|Header|BasicHeaderType|
	444	+|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.
	445	+|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
	446	+
453	453	**SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit subscription request document.
454	454
455	455	Derivation:
456	456
457		-* //MessageType// (restriction)
458		-** RegistryInterfaceType (restriction)
459		-*** SubmitSubscriptionsRequestType
	451	+//MessageType// (restriction)
	452	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	453	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsRequestType
460	460
461	461	Content:
462	462
463		-* Header, SubmitSubscriptionsRequest
464		-* Element Documentation:
	457	+Header, SubmitSubscriptionsRequest
465	465
466		-(% style="width:832.294px" %)
467		-|**Name**|(% style="width:227px" %)**Type**|(% style="width:319px" %)**Documentation**
468		-|Header|(% style="width:227px" %)BasicHeaderType|(% style="width:319px" %)
469		-|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.
	459	+Element Documentation:
470	470
	461	+|**Name**|**Type**|**Documentation**
	462	+|Header|BasicHeaderType|
	463	+|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.
	464	+
471	471	**SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit subscription response document.
472	472
473	473	Derivation:
474	474
475		-* //MessageType// (restriction)
476		-** RegistryInterfaceType (restriction)
477		-*** SubmitSubscriptionsResponseType
	469	+//MessageType// (restriction)
	470	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	471	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsResponseType
478	478
479	479	Content:
480	480
481		-* Header, SubmitSubscriptionsResponse, ftr:Footer?
482		-* Element Documentation:
	475	+Header, SubmitSubscriptionsResponse, ftr:Footer?
483	483
484		-(% style="width:843.294px" %)
485		-|**Name**|**Type**|(% style="width:362px" %)**Documentation**
486		-|Header|BasicHeaderType|(% style="width:362px" %)
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.
488		-|ftr:Footer|ftr:FooterType|(% style="width:362px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
	477	+Element Documentation:
489	489
	479	+|**Name**|**Type**|**Documentation**
	480	+|Header|BasicHeaderType|
	481	+|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.
	482	+|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
	483	+
490	490	**QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query subscription request document.
491	491
492	492	Derivation:
493	493
494		-* //MessageType// (restriction)
495		-** RegistryInterfaceType (restriction)
496		-*** QuerySubscriptionRequestType
	488	+//MessageType// (restriction)
	489	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	490	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionRequestType
497	497
498	498	Content:
499	499
500		-* Header, QuerySubscriptionRequest
501		-* Element Documentation:
	494	+Header, QuerySubscriptionRequest
502	502
503		-(% style="width:839.294px" %)
504		-|(% style="width:230px" %)**Name**|(% style="width:254px" %)**Type**|(% style="width:352px" %)**Documentation**
505		-|(% style="width:230px" %)Header|(% style="width:254px" %)BasicHeaderType|(% style="width:352px" %)
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.
	496	+Element Documentation:
507	507
	498	+|**Name**|**Type**|**Documentation**
	499	+|Header|BasicHeaderType|
	500	+|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
	501	+
508	508	**QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query subscription response document.
509	509
510	510	Derivation:
511	511
512		-* //MessageType// (restriction)
513		-** RegistryInterfaceType (restriction)
514		-*** QuerySubscriptionResponseType
	506	+//MessageType// (restriction)
	507	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	508	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionResponseType
515	515
516	516	Content:
517	517
518		-* Header, QuerySubscriptionResponse, ftr:Footer?
519		-* Element Documentation:
	512	+Header, QuerySubscriptionResponse, ftr:Footer?
520	520
521		-(% style="width:912.294px" %)
522		-|**Name**|(% style="width:304px" %)**Type**|(% style="width:336px" %)**Documentation**
523		-|Header|(% style="width:304px" %)BasicHeaderType|(% style="width:336px" %)
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.
525		-|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.
	514	+Element Documentation:
526	526
	516	+|**Name**|**Type**|**Documentation**
	517	+|Header|BasicHeaderType|
	518	+|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.
	519	+|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
	520	+
527	527	**NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry notification document.
528	528
529	529	Derivation:
530	530
531		-* //MessageType// (restriction)
532		-** RegistryInterfaceType (restriction)
533		-*** NotifyRegistryEventType
	525	+//MessageType// (restriction)
	526	+ RegistryInterfaceType (restriction)
	527	+ NotifyRegistryEventType
534	534
535	535	Content:
536	536
537		-* Header, NotifyRegistryEvent
538		-* Element Documentation:
	531	+Header, NotifyRegistryEvent
539	539
540		-(% style="width:836.294px" %)
541		-|**Name**|**Type**|(% style="width:473px" %)**Documentation**
542		-|Header|BasicHeaderType|(% style="width:473px" %)
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.
	533	+Element Documentation:
544	544
	535	+|**Name**|**Type**|**Documentation**
	536	+|Header|BasicHeaderType|
	537	+|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.
	538	+
545	545	**DataQueryType: **DataQueryType defines the structure of a data query message.
546	546
547	547	Derivation:
548	548
549		-* //MessageType// (restriction)
550		-** DataQueryType
	543	+//MessageType// (restriction)
	544	+ DataQueryType
551	551
552	552	Content:
553	553
554		-* Header, Query
555		-* Element Documentation:
	548	+Header, Query
556	556
557		-(% style="width:839.294px" %)
558		-|(% style="width:244px" %)**Name**|(% style="width:262px" %)**Type**|(% style="width:330px" %)**Documentation**
559		-|(% style="width:244px" %)Header|(% style="width:262px" %)BasicHeaderType|(% style="width:330px" %)
560		-|(% style="width:244px" %)Query|(% style="width:262px" %)qry:DataQueryType|(% style="width:330px" %)
	550	+Element Documentation:
561	561
	552	+|**Name**|**Type**|**Documentation**
	553	+|Header|BasicHeaderType|
	554	+|Query|qry:DataQueryType|
	555	+
562	562	**GenericDataQueryType: **DataQueryType defines the structure of a generic data query message.
563	563
564	564	Derivation:
565	565
566		-* //MessageType// (restriction)
567		-** DataQueryType (restriction)
568		-*** GenericDataQueryType
	560	+//MessageType// (restriction)
	561	+ DataQueryType (restriction)
	562	+ GenericDataQueryType
569	569
570	570	Content:
571	571
572		-* Header, Query
573		-* Element Documentation:
	566	+Header, Query
574	574
575		-(% style="width:833.294px" %)
576		-|(% style="width:213px" %)**Name**|(% style="width:243px" %)**Type**|(% style="width:374px" %)**Documentation**
577		-|(% style="width:213px" %)Header|(% style="width:243px" %)BasicHeaderType|(% style="width:374px" %)
578		-|(% style="width:213px" %)Query|(% style="width:243px" %)qry: GenericDataQueryType|(% style="width:374px" %)
	568	+Element Documentation:
579	579
	570	+|**Name**|**Type**|**Documentation**
	571	+|Header|BasicHeaderType|
	572	+|Query|qry: GenericDataQueryType|
	573	+
580	580	**GenericTimeSeriesDataQueryType: **GenericTimeSeriesDataQueryType defines the structure of a time series generic data query message.
581	581
582	582	Derivation:
583	583
584		-* //MessageType// (restriction)
585		-** DataQueryType (restriction)
586		-*** GenericDataQueryType (restriction)
587		-**** GenericTimeSeriesDataQueryType
	578	+//MessageType// (restriction)
	579	+ DataQueryType (restriction)
	580	+ GenericDataQueryType (restriction)
	581	+ GenericTimeSeriesDataQueryType
588	588
589	589	Content:
590	590
591		-* Header, Query
592		-* Element Documentation:
	585	+Header, Query
593	593
594		-(% style="width:909.294px" %)
595		-|(% style="width:221px" %)**Name**|(% style="width:305px" %)**Type**|(% style="width:380px" %)**Documentation**
596		-|(% style="width:221px" %)Header|(% style="width:305px" %)BasicHeaderType|(% style="width:380px" %)
597		-|(% style="width:221px" %)Query|(% style="width:305px" %)qry: GenericTimeSeriesDat aQueryType|(% style="width:380px" %)
	587	+Element Documentation:
598	598
	589	+|**Name**|**Type**|**Documentation**
	590	+|Header|BasicHeaderType|
	591	+|Query|qry: GenericTimeSeriesDat aQueryType|
	592	+
599	599	**StructureSpecificTimeSeriesDataQueryType: **StructureSpecificTimeSeriesDataQueryType defines the structure of a time series generic data query message.
600	600
601	601	Derivation:
602	602
603		-* //MessageType// (restriction)
604		-** DataQueryType (restriction)
605		-*** StructureSpecificTimeSeriesDataQueryType
	597	+//MessageType// (restriction)
	598	+ DataQueryType (restriction)
	599	+ StructureSpecificTimeSeriesDataQueryType
606	606
607	607	Content:
608	608
609		-* Header, Query
610		-* Element Documentation:
	603	+Header, Query
611	611
612		-(% style="width:903.294px" %)
613		-|(% style="width:189px" %)**Name**|(% style="width:259px" %)**Type**|(% style="width:452px" %)**Documentation**
614		-|(% style="width:189px" %)Header|(% style="width:259px" %)BasicHeaderType|(% style="width:452px" %)
615		-|(% style="width:189px" %)Query|(% style="width:259px" %)qry: TimeSeriesDataQueryType|(% style="width:452px" %)
	605	+Element Documentation:
616	616
	607	+|**Name**|**Type**|**Documentation**
	608	+|Header|BasicHeaderType|
	609	+|Query|qry: TimeSeriesDataQueryT ype|
	610	+
617	617	**MetadataQueryType: **MetadataQueryType defines the structure of a reference metadata query message.
618	618
619	619	Derivation:
620	620
621		-* //MessageType// (restriction)
622		-** MetadataQueryType
	615	+//MessageType// (restriction)
	616	+ MetadataQueryType
623	623
624	624	Content:
625	625
626		-* Header, Query
627		-* Element Documentation:
	620	+Header, Query
628	628
629		-(% style="width:858.294px" %)
630		-|(% style="width:138px" %)**Name**|(% style="width:246px" %)**Type**|(% style="width:471px" %)**Documentation**
631		-|(% style="width:138px" %)Header|(% style="width:246px" %)BasicHeaderType|(% style="width:471px" %)
632		-|(% style="width:138px" %)Query|(% style="width:246px" %)qry: MetadataQueryType|(% style="width:471px" %)
	622	+Element Documentation:
633	633
	624	+|**Name**|**Type**|**Documentation**
	625	+|Header|BasicHeaderType|
	626	+|Query|qry: MetadataQueryType|
	627	+
634	634	**DataSchemaQueryType: **DataSchemaQueryType defines the structure of a data schema query message.
635	635
636	636	Derivation:
637	637
638		-* //MessageType// (restriction)
639		-** DataSchemaQueryType
	632	+//MessageType// (restriction)
	633	+ DataSchemaQueryType
640	640
641	641	Content:
642	642
643		-* Header, Query
644		-* Element Documentation:
	637	+Header, Query
645	645
646		-(% style="width:895.294px" %)
647		-|(% style="width:185px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:413px" %)**Documentation**
648		-|(% style="width:185px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:413px" %)
649		-|(% style="width:185px" %)Query|(% style="width:294px" %)qry: DataSchemaQueryType|(% style="width:413px" %)
	639	+Element Documentation:
650	650
	641	+|**Name**|**Type**|**Documentation**
	642	+|Header|BasicHeaderType|
	643	+|Query|qry: DataSchemaQueryType|
	644	+
651	651	**MetadataSchemaQueryType: **MetadataSchemaQueryType defines the structure of a metadata schema query message.
652	652
653	653	Derivation:
654	654
655		-* //MessageType// (restriction)
656		-** MetadataSchemaQueryType
	649	+//MessageType// (restriction)
	650	+ MetadataSchemaQueryType
657	657
658	658	Content:
659	659
660		-* Header, Query
661		-* Element Documentation:
	654	+Header, Query
662	662
663		-(% style="width:897.294px" %)
664		-|(% style="width:166px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:447px" %)**Documentation**
665		-|(% style="width:166px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:447px" %)
666		-|(% style="width:166px" %)Query|(% style="width:281px" %)qry: MetadataSchemaQueryType|(% style="width:447px" %)
	656	+Element Documentation:
667	667
	658	+|**Name**|**Type**|**Documentation**
	659	+|Header|BasicHeaderType|
	660	+|Query|qry: MetadataSchemaQueryT ype|
	661	+
668	668	**StructuresQueryType: **StructuresQueryType defines the structure of a structures query message.
669	669
670	670	Derivation:
671	671
672		-* //MessageType// (restriction)
673		-** StructuresQueryType
	666	+//MessageType// (restriction)
	667	+ StructuresQueryType
674	674
675	675	Content:
676	676
...	...	@@ -1027,7 +1027,7 @@
1027	1027	Derivation:
1028	1028
1029	1029	//MessageType// (restriction)
1030		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] CustomTypeSchemeQueryType
	1024	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] CustomTypeSchemeQueryType
1031	1031
1032	1032	Content:
1033	1033
...	...	@@ -1102,7 +1102,7 @@
1102	1102	Derivation:
1103	1103
1104	1104	//BaseHeaderType// (restriction)
1105		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataHeaderType
	1099	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataHeaderType
1106	1106
1107	1107	Content:
1108	1108
...	...	@@ -1251,7 +1251,7 @@
1251	1251	Derivation:
1252	1252
1253	1253	//BaseHeaderType// (restriction)
1254		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType
	1248	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType
1255	1255
1256	1256	Content:
1257	1257
...	...	@@ -1278,7 +1278,7 @@
1278	1278	Derivation:
1279	1279
1280	1280	//BaseHeaderType// (restriction)
1281		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType
	1275	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType
1282	1282
1283	1283	Content:
1284	1284
...	...	@@ -1319,7 +1319,7 @@
1319	1319	Derivation:
1320	1320
1321	1321	PartyType (extension)
1322		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType
	1316	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType
1323	1323
1324	1324	Attributes:
1325	1325
...	...	@@ -1416,8 +1416,8 @@
1416	1416	Derivation:
1417	1417
1418	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
	1413	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension)
	1414	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType
1421	1421
1422	1422	Attributes:
1423	1423