Changes for page Part I. Message Namespace

Summary

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

Details

Page properties

Content

...	...	@@ -159,9 +159,7 @@
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		-1.
163		-11.
164		-111. Complex Types
	162	+=== 2.1.3 Complex Types ===
165	165
166	166	**//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.
167	167
...	...	@@ -180,7 +180,7 @@
180	180	Derivation:
181	181
182	182	//MessageType// (restriction)
183		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureType
	181	+ StructureType
184	184
185	185	Content:
186	186
...	...	@@ -188,10 +188,11 @@
188	188
189	189	Element Documentation:
190	190
191		-|**Name**|**Type**|**Documentation**
192		-|Header|StructureHeaderType|
193		-|Structures|str:StructuresType|
194		-|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
	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.
195	195
196	196	**GenericDataType: **GenericDataType defines the contents of a generic data message.
197	197
...	...	@@ -198,7 +198,7 @@
198	198	Derivation:
199	199
200	200	//MessageType// (restriction)
201		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataType
	200	+ GenericDataType
202	202
203	203	Content:
204	204
...	...	@@ -206,18 +206,19 @@
206	206
207	207	Element Documentation:
208	208
209		-|**Name**|**Type**|**Documentation**
210		-|Header|GenericDataHeaderTyp e|
211		-|DataSet|dat:DataSetType|
212		-|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
	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.
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		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataType (restriction)
220		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericTimeSeriesDataType
	218	+* //MessageType// (restriction)
	219	+** GenericDataType (restriction)
	220	+*** GenericTimeSeriesDataType
221	221
222	222	Content:
223	223
...	...	@@ -225,17 +225,18 @@
225	225
226	226	Element Documentation:
227	227
228		-|**Name**|**Type**|**Documentation**
229		-|Header|GenericTimeSeriesDat aHeaderType|
230		-|DataSet|dat: TimeSeriesDataSetTyp e|
231		-|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
	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.
232	232
233	233	**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.
234	234
235	235	Derivation:
236	236
237		-//MessageType// (restriction)
238		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificDataType
	238	+* //MessageType// (restriction)
	239	+** StructureSpecificDataType
239	239
240	240	Content:
241	241
...	...	@@ -243,18 +243,19 @@
243	243
244	244	Element Documentation:
245	245
246		-|**Name**|**Type**|**Documentation**
247		-|Header|StructureSpecificDat aHeaderType|
248		-|DataSet|//dsd:DataSetType//|
249		-|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
	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.
250	250
251	251	**StructureSpecificTimeSeriesDataType: **StructureSpecificTimeSeriesDataType defines the structure of the structure specific time series data message.
252	252
253	253	Derivation:
254	254
255		-//MessageType// (restriction)
256		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificDataType (restriction)
257		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificTimeSeriesDataType
	257	+* //MessageType// (restriction)
	258	+** StructureSpecificDataType (restriction)
	259	+*** StructureSpecificTimeSeriesDataType
258	258
259	259	Content:
260	260
...	...	@@ -262,17 +262,18 @@
262	262
263	263	Element Documentation:
264	264
265		-|**Name**|**Type**|**Documentation**
266		-|Header|StructureSpecificTim eSeriesDataHeaderTyp e|
267		-|DataSet|//dsd: TimeSeriesDataSetTyp e//|
268		-|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
	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.
269	269
270	270	**GenericMetadataType: **GenericMetadataType defines the contents of a generic metadata message.
271	271
272	272	Derivation:
273	273
274		-//MessageType// (restriction)
275		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericMetadataType
	277	+* //MessageType// (restriction)
	278	+** GenericMetadataType
276	276
277	277	Content:
278	278
...	...	@@ -280,17 +280,18 @@
280	280
281	281	Element Documentation:
282	282
283		-|**Name**|**Type**|**Documentation**
284		-|Header|GenericMetadataHeade rType|
285		-|MetadataSet|rep:MetadataSetType|
286		-|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
	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.
287	287
288	288	**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.
289	289
290	290	Derivation:
291	291
292		-//MessageType// (restriction)
293		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataType
	296	+* //MessageType// (restriction)
	297	+** StructureSpecificMetadataType
294	294
295	295	Content:
296	296
...	...	@@ -298,17 +298,18 @@
298	298
299	299	Element Documentation:
300	300
301		-|**Name**|**Type**|**Documentation**
302		-|Header|StructureSpecificMet adataHeaderType|
303		-|MetadataSet|//msd:MetadataSetType//|
304		-|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
	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.
305	305
306	306	**RegistryInterfaceType: **This is a type which describes a structure for holding all of the various dedicated registry interface message types.
307	307
308	308	Derivation:
309	309
310		-//MessageType// (restriction)
311		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType
	315	+* //MessageType// (restriction)
	316	+** RegistryInterfaceType
312	312
313	313	Content:
314	314
...	...	@@ -316,83 +316,84 @@
316	316
317	317	Element Documentation:
318	318
319		-|**Name**|**Type**|**Documentation**
320		-|Header|BasicHeaderType|
321		-|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.
322		-|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.
323		-|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.
324		-|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.
325		-|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.
326		-|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.
327		-|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.
328		-|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.
329		-|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
330		-|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.
331		-|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.
332		-|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
	324	+(% style="width:903.294px" %)
	325	+|**Name**|**Type**|(% style="width:441px" %)**Documentation**
	326	+|Header|BasicHeaderType|(% style="width:441px" %)
	327	+|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:441px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
	328	+|SubmitRegistrationsR esponse|ref: SubmitRegistrationsR esponseType|(% style="width:441px" %)SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
	329	+|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:441px" %)QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys.
	330	+|QueryRegistrationRes ponse|ref: QueryRegistrationRes ponseType|(% style="width:441px" %)QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.
	331	+|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:441px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information.
	332	+|SubmitStructureRespo nse|ref: SubmitStructureRespo nseType|(% style="width:441px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
	333	+|SubmitSubscriptionsR equest|ref: SubmitSubscriptionsR equestType|(% style="width:441px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
	334	+|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:441px" %)SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID.
	335	+|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|(% style="width:441px" %)QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
	336	+|QuerySubscriptionRes ponse|ref: QuerySubscriptionRes ponseType|(% style="width:441px" %)QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent.
	337	+|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|(% style="width:441px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided.
	338	+|ftr:Footer|ftr:FooterType|(% style="width:441px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
333	333
334	334	**SubmitRegistrationsRequestType: **SubmitRegistrationsRequestType defines the structure of a registry submit registration requests document.
335	335
336	336	Derivation:
337	337
338		-//MessageType// (restriction)
339		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
340		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitRegistrationsRequestType
	344	+* //MessageType// (restriction)
	345	+** RegistryInterfaceType (restriction)
	346	+*** SubmitRegistrationsRequestType
341	341
342	342	Content:
343	343
344		-Header, SubmitRegistrationsRequest
	350	+* Header, SubmitRegistrationsRequest
	351	+* Element Documentation:
345	345
346		-Element Documentation:
	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.
347	347
348		-|**Name**|**Type**|**Documentation**
349		-|Header|BasicHeaderType|
350		-|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.
351		-
352	352	**SubmitRegistrationsResponseType: **SubmitRegistrationsResponseType defines the structure of a registry submit registration response document.
353	353
354	354	Derivation:
355	355
356		-//MessageType// (restriction)
357		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
358		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitRegistrationsResponseType
	362	+* //MessageType// (restriction)
	363	+** RegistryInterfaceType (restriction)
	364	+*** SubmitRegistrationsResponseType
359	359
360	360	Content:
361	361
362		-Header, SubmitRegistrationsResponse, ftr:Footer?
	368	+* Header, SubmitRegistrationsResponse, ftr:Footer?
	369	+* Element Documentation:
363	363
364		-Element Documentation:
	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.
365	365
366		-|**Name**|**Type**|**Documentation**
367		-|Header|BasicHeaderType|
368		-|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.
369		-|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
370		-
371	371	**QueryRegistrationRequestType: **QueryRegistrationRequestType defines the structure of a registry query registration request document.
372	372
373	373	Derivation:
374	374
375		-//MessageType// (restriction)
376		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
377		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationRequestType
	381	+* //MessageType// (restriction)
	382	+** RegistryInterfaceType (restriction)
	383	+*** QueryRegistrationRequestType
378	378
379	379	Content:
380	380
381		-Header, QueryRegistrationRequest
	387	+* Header, QueryRegistrationRequest
	388	+* Element Documentation:
382	382
383		-Element Documentation:
	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.
384	384
385		-|**Name**|**Type**|**Documentation**
386		-|Header|BasicHeaderType|
387		-|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.
388		-
389	389	**QueryRegistrationResponseType: **SubmitRegistrationRequestType defines the structure of a registry submit registration response document.
390	390
391	391	Derivation:
392	392
393		-//MessageType// (restriction)
394		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
395		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationResponseType
	399	+* //MessageType// (restriction)
	400	+** RegistryInterfaceType (restriction)
	401	+*** QueryRegistrationResponseType
396	396
397	397	Content:
398	398
...	...	@@ -400,18 +400,19 @@
400	400
401	401	Element Documentation:
402	402
403		-|**Name**|**Type**|**Documentation**
404		-|Header|BasicHeaderType|
405		-|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.
406		-|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
	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.
407	407
408	408	**SubmitStructureRequestType: **SubmitStructureRequestType defines the structure of a registry submit structure request document.
409	409
410	410	Derivation:
411	411
412		-//MessageType// (restriction)
413		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
414		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureRequestType
	419	+* //MessageType// (restriction)
	420	+** RegistryInterfaceType (restriction)
	421	+*** SubmitStructureRequestType
415	415
416	416	Content:
417	417
...	...	@@ -419,629 +419,630 @@
419	419
420	420	Element Documentation:
421	421
422		-|**Name**|**Type**|**Documentation**
423		-|Header|BasicHeaderType|
424		-|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.
	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.
425	425
426	426	**SubmitStructureResponseType: **SubmitStructureResponseType defines the structure of a registry submit registration response document.
427	427
428	428	Derivation:
429	429
430		-//MessageType// (restriction)
431		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
432		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureResponseType
	438	+* //MessageType// (restriction)
	439	+** RegistryInterfaceType (restriction)
	440	+*** SubmitStructureResponseType
433	433
434	434	Content:
435	435
436		-Header, SubmitStructureResponse, ftr:Footer?
	444	+* Header, SubmitStructureResponse, ftr:Footer?
	445	+* Element Documentation:
437	437
438		-Element Documentation:
	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.
439	439
440		-|**Name**|**Type**|**Documentation**
441		-|Header|BasicHeaderType|
442		-|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.
443		-|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
444		-
445	445	**SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit subscription request document.
446	446
447	447	Derivation:
448	448
449		-//MessageType// (restriction)
450		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
451		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsRequestType
	457	+* //MessageType// (restriction)
	458	+** RegistryInterfaceType (restriction)
	459	+*** SubmitSubscriptionsRequestType
452	452
453	453	Content:
454	454
455		-Header, SubmitSubscriptionsRequest
	463	+* Header, SubmitSubscriptionsRequest
	464	+* Element Documentation:
456	456
457		-Element Documentation:
	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.
458	458
459		-|**Name**|**Type**|**Documentation**
460		-|Header|BasicHeaderType|
461		-|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.
462		-
463	463	**SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit subscription response document.
464	464
465	465	Derivation:
466	466
467		-//MessageType// (restriction)
468		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
469		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsResponseType
	475	+* //MessageType// (restriction)
	476	+** RegistryInterfaceType (restriction)
	477	+*** SubmitSubscriptionsResponseType
470	470
471	471	Content:
472	472
473		-Header, SubmitSubscriptionsResponse, ftr:Footer?
	481	+* Header, SubmitSubscriptionsResponse, ftr:Footer?
	482	+* Element Documentation:
474	474
475		-Element Documentation:
	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.
476	476
477		-|**Name**|**Type**|**Documentation**
478		-|Header|BasicHeaderType|
479		-|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.
480		-|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
481		-
482	482	**QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query subscription request document.
483	483
484	484	Derivation:
485	485
486		-//MessageType// (restriction)
487		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
488		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionRequestType
	494	+* //MessageType// (restriction)
	495	+** RegistryInterfaceType (restriction)
	496	+*** QuerySubscriptionRequestType
489	489
490	490	Content:
491	491
492		-Header, QuerySubscriptionRequest
	500	+* Header, QuerySubscriptionRequest
	501	+* Element Documentation:
493	493
494		-Element Documentation:
	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.
495	495
496		-|**Name**|**Type**|**Documentation**
497		-|Header|BasicHeaderType|
498		-|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
499		-
500	500	**QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query subscription response document.
501	501
502	502	Derivation:
503	503
504		-//MessageType// (restriction)
505		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
506		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionResponseType
	512	+* //MessageType// (restriction)
	513	+** RegistryInterfaceType (restriction)
	514	+*** QuerySubscriptionResponseType
507	507
508	508	Content:
509	509
510		-Header, QuerySubscriptionResponse, ftr:Footer?
	518	+* Header, QuerySubscriptionResponse, ftr:Footer?
	519	+* Element Documentation:
511	511
512		-Element Documentation:
	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.
513	513
514		-|**Name**|**Type**|**Documentation**
515		-|Header|BasicHeaderType|
516		-|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.
517		-|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
518		-
519	519	**NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry notification document.
520	520
521	521	Derivation:
522	522
523		-//MessageType// (restriction)
524		- RegistryInterfaceType (restriction)
525		- NotifyRegistryEventType
	531	+* //MessageType// (restriction)
	532	+** RegistryInterfaceType (restriction)
	533	+*** NotifyRegistryEventType
526	526
527	527	Content:
528	528
529		-Header, NotifyRegistryEvent
	537	+* Header, NotifyRegistryEvent
	538	+* Element Documentation:
530	530
531		-Element Documentation:
	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.
532	532
533		-|**Name**|**Type**|**Documentation**
534		-|Header|BasicHeaderType|
535		-|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.
536		-
537	537	**DataQueryType: **DataQueryType defines the structure of a data query message.
538	538
539	539	Derivation:
540	540
541		-//MessageType// (restriction)
542		- DataQueryType
	549	+* //MessageType// (restriction)
	550	+** DataQueryType
543	543
544	544	Content:
545	545
546		-Header, Query
	554	+* Header, Query
	555	+* Element Documentation:
547	547
548		-Element Documentation:
	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" %)
549	549
550		-|**Name**|**Type**|**Documentation**
551		-|Header|BasicHeaderType|
552		-|Query|qry:DataQueryType|
553		-
554	554	**GenericDataQueryType: **DataQueryType defines the structure of a generic data query message.
555	555
556	556	Derivation:
557	557
558		-//MessageType// (restriction)
559		- DataQueryType (restriction)
560		- GenericDataQueryType
	566	+* //MessageType// (restriction)
	567	+** DataQueryType (restriction)
	568	+*** GenericDataQueryType
561	561
562	562	Content:
563	563
564		-Header, Query
	572	+* Header, Query
	573	+* Element Documentation:
565	565
566		-Element Documentation:
	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" %)
567	567
568		-|**Name**|**Type**|**Documentation**
569		-|Header|BasicHeaderType|
570		-|Query|qry: GenericDataQueryType|
571		-
572	572	**GenericTimeSeriesDataQueryType: **GenericTimeSeriesDataQueryType defines the structure of a time series generic data query message.
573	573
574	574	Derivation:
575	575
576		-//MessageType// (restriction)
577		- DataQueryType (restriction)
578		- GenericDataQueryType (restriction)
579		- GenericTimeSeriesDataQueryType
	584	+* //MessageType// (restriction)
	585	+** DataQueryType (restriction)
	586	+*** GenericDataQueryType (restriction)
	587	+**** GenericTimeSeriesDataQueryType
580	580
581	581	Content:
582	582
583		-Header, Query
	591	+* Header, Query
	592	+* Element Documentation:
584	584
585		-Element Documentation:
	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" %)
586	586
587		-|**Name**|**Type**|**Documentation**
588		-|Header|BasicHeaderType|
589		-|Query|qry: GenericTimeSeriesDat aQueryType|
590		-
591	591	**StructureSpecificTimeSeriesDataQueryType: **StructureSpecificTimeSeriesDataQueryType defines the structure of a time series generic data query message.
592	592
593	593	Derivation:
594	594
595		-//MessageType// (restriction)
596		- DataQueryType (restriction)
597		- StructureSpecificTimeSeriesDataQueryType
	603	+* //MessageType// (restriction)
	604	+** DataQueryType (restriction)
	605	+*** StructureSpecificTimeSeriesDataQueryType
598	598
599	599	Content:
600	600
601		-Header, Query
	609	+* Header, Query
	610	+* Element Documentation:
602	602
603		-Element Documentation:
	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" %)
604	604
605		-|**Name**|**Type**|**Documentation**
606		-|Header|BasicHeaderType|
607		-|Query|qry: TimeSeriesDataQueryT ype|
608		-
609	609	**MetadataQueryType: **MetadataQueryType defines the structure of a reference metadata query message.
610	610
611	611	Derivation:
612	612
613		-//MessageType// (restriction)
614		- MetadataQueryType
	621	+* //MessageType// (restriction)
	622	+** MetadataQueryType
615	615
616	616	Content:
617	617
618		-Header, Query
	626	+* Header, Query
	627	+* Element Documentation:
619	619
620		-Element Documentation:
	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" %)
621	621
622		-|**Name**|**Type**|**Documentation**
623		-|Header|BasicHeaderType|
624		-|Query|qry: MetadataQueryType|
625		-
626	626	**DataSchemaQueryType: **DataSchemaQueryType defines the structure of a data schema query message.
627	627
628	628	Derivation:
629	629
630		-//MessageType// (restriction)
631		- DataSchemaQueryType
	638	+* //MessageType// (restriction)
	639	+** DataSchemaQueryType
632	632
633	633	Content:
634	634
635		-Header, Query
	643	+* Header, Query
	644	+* Element Documentation:
636	636
637		-Element Documentation:
	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" %)
638	638
639		-|**Name**|**Type**|**Documentation**
640		-|Header|BasicHeaderType|
641		-|Query|qry: DataSchemaQueryType|
642		-
643	643	**MetadataSchemaQueryType: **MetadataSchemaQueryType defines the structure of a metadata schema query message.
644	644
645	645	Derivation:
646	646
647		-//MessageType// (restriction)
648		- MetadataSchemaQueryType
	655	+* //MessageType// (restriction)
	656	+** MetadataSchemaQueryType
649	649
650	650	Content:
651	651
652		-Header, Query
	660	+* Header, Query
	661	+* Element Documentation:
653	653
654		-Element Documentation:
	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" %)
655	655
656		-|**Name**|**Type**|**Documentation**
657		-|Header|BasicHeaderType|
658		-|Query|qry: MetadataSchemaQueryT ype|
659		-
660	660	**StructuresQueryType: **StructuresQueryType defines the structure of a structures query message.
661	661
662	662	Derivation:
663	663
664		-//MessageType// (restriction)
665		- StructuresQueryType
	672	+* //MessageType// (restriction)
	673	+** StructuresQueryType
666	666
667	667	Content:
668	668
669		-Header, Query
	677	+* Header, Query
	678	+* Element Documentation:
670	670
671		-Element Documentation:
	680	+(% style="width:886.294px" %)
	681	+|(% style="width:223px" %)**Name**|(% style="width:255px" %)**Type**|(% style="width:405px" %)**Documentation**
	682	+|(% style="width:223px" %)Header|(% style="width:255px" %)BasicHeaderType|(% style="width:405px" %)
	683	+|(% style="width:223px" %)Query|(% style="width:255px" %)qry: StructuresQueryType|(% style="width:405px" %)
672	672
673		-|**Name**|**Type**|**Documentation**
674		-|Header|BasicHeaderType|
675		-|Query|qry: StructuresQueryType|
676		-
677	677	**DataflowQueryType: **DataflowQueryType defines the structure of a dataflow query message.
678	678
679	679	Derivation:
680	680
681		-//MessageType// (restriction)
682		- DataflowQueryType
	689	+* //MessageType// (restriction)
	690	+** DataflowQueryType
683	683
684	684	Content:
685	685
686		-Header, Query
	694	+* Header, Query
	695	+* Element Documentation:
687	687
688		-Element Documentation:
	697	+(% style="width:888.294px" %)
	698	+|(% style="width:176px" %)**Name**|(% style="width:260px" %)**Type**|(% style="width:449px" %)**Documentation**
	699	+|(% style="width:176px" %)Header|(% style="width:260px" %)BasicHeaderType|(% style="width:449px" %)
	700	+|(% style="width:176px" %)Query|(% style="width:260px" %)qry: DataflowQueryType|(% style="width:449px" %)
689	689
690		-|**Name**|**Type**|**Documentation**
691		-|Header|BasicHeaderType|
692		-|Query|qry: DataflowQueryType|
693		-
694	694	**MetadataflowQueryType: **MetadataflowQueryType defines the structure of a metadata flow query message.
695	695
696	696	Derivation:
697	697
698		-//MessageType// (restriction)
699		- MetadataflowQueryType
	706	+* //MessageType// (restriction)
	707	+** MetadataflowQueryType
700	700
701	701	Content:
702	702
703		-Header, Query
	711	+* Header, Query
	712	+* Element Documentation:
704	704
705		-Element Documentation:
	714	+(% style="width:886.294px" %)
	715	+|(% style="width:199px" %)**Name**|(% style="width:296px" %)**Type**|(% style="width:388px" %)**Documentation**
	716	+|(% style="width:199px" %)Header|(% style="width:296px" %)BasicHeaderType|(% style="width:388px" %)
	717	+|(% style="width:199px" %)Query|(% style="width:296px" %)qry: MetadataflowQueryType|(% style="width:388px" %)
706	706
707		-|**Name**|**Type**|**Documentation**
708		-|Header|BasicHeaderType|
709		-|Query|qry: MetadataflowQueryTyp e|
710		-
711	711	**DataStructureQueryType: **KeyFamilyQueryType defines the structure of a data structure query message.
712	712
713	713	Derivation:
714	714
715		-//MessageType// (restriction)
716		- DataStructureQueryType
	723	+* //MessageType// (restriction)
	724	+** DataStructureQueryType
717	717
718	718	Content:
719	719
720		-Header, Query
	728	+* Header, Query
	729	+* Element Documentation:
721	721
722		-Element Documentation:
	731	+(% style="width:901.294px" %)
	732	+|(% style="width:202px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:393px" %)**Documentation**
	733	+|(% style="width:202px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:393px" %)
	734	+|(% style="width:202px" %)Query|(% style="width:303px" %)qry: DataStructureQueryType|(% style="width:393px" %)
723	723
724		-|**Name**|**Type**|**Documentation**
725		-|Header|BasicHeaderType|
726		-|Query|qry: DataStructureQueryTy pe|
727		-
728	728	**MetadataStructureQueryType: **MetadataStructureQueryType defines the structure of a metadata structure query message.
729	729
730	730	Derivation:
731	731
732		-//MessageType// (restriction)
733		- MetadataStructureQueryType
	740	+* //MessageType// (restriction)
	741	+** MetadataStructureQueryType
734	734
735	735	Content:
736	736
737		-Header, Query
	745	+* Header, Query
	746	+* Element Documentation:
738	738
739		-Element Documentation:
	748	+(% style="width:904.294px" %)
	749	+|(% style="width:226px" %)**Name**|(% style="width:275px" %)**Type**|(% style="width:400px" %)**Documentation**
	750	+|(% style="width:226px" %)Header|(% style="width:275px" %)BasicHeaderType|(% style="width:400px" %)
	751	+|(% style="width:226px" %)Query|(% style="width:275px" %)qry: MetadataStructureQueryType|(% style="width:400px" %)
740	740
741		-|**Name**|**Type**|**Documentation**
742		-|Header|BasicHeaderType|
743		-|Query|qry: MetadataStructureQue ryType|
744		-
745	745	**CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a category scheme query message.
746	746
747	747	Derivation:
748	748
749		-//MessageType// (restriction)
750		- CategorySchemeQueryType
	757	+* //MessageType// (restriction)
	758	+** CategorySchemeQueryType
751	751
752	752	Content:
753	753
754		-Header, Query
	762	+* Header, Query
	763	+* Element Documentation:
755	755
756		-Element Documentation:
	765	+(% style="width:915.294px" %)
	766	+|(% style="width:196px" %)**Name**|(% style="width:347px" %)**Type**|(% style="width:369px" %)**Documentation**
	767	+|(% style="width:196px" %)Header|(% style="width:347px" %)BasicHeaderType|(% style="width:369px" %)
	768	+|(% style="width:196px" %)Query|(% style="width:347px" %)qry: CategorySchemeQueryType|(% style="width:369px" %)
757	757
758		-|**Name**|**Type**|**Documentation**
759		-|Header|BasicHeaderType|
760		-|Query|qry: CategorySchemeQueryT ype|
761		-
762	762	**ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a concept scheme query message.
763	763
764	764	Derivation:
765	765
766		-//MessageType// (restriction)
767		- ConceptSchemeQueryType
	774	+* //MessageType// (restriction)
	775	+** ConceptSchemeQueryType
768	768
769	769	Content:
770	770
771		-Header, Query
	779	+* Header, Query
	780	+* Element Documentation:
772	772
773		-Element Documentation:
	782	+(% style="width:895.294px" %)
	783	+|(% style="width:222px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:331px" %)**Documentation**
	784	+|(% style="width:222px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:331px" %)
	785	+|(% style="width:222px" %)Query|(% style="width:339px" %)qry: ConceptSchemeQueryType|(% style="width:331px" %)
774	774
775		-|**Name**|**Type**|**Documentation**
776		-|Header|BasicHeaderType|
777		-|Query|qry: ConceptSchemeQueryTy pe|
778		-
779	779	**CodelistQueryType: **CodelistQueryType defines the structure of a codelist query message.
780	780
781	781	Derivation:
782	782
783		-//MessageType// (restriction)
784		- CodelistQueryType
	791	+* //MessageType// (restriction)
	792	+** CodelistQueryType
785	785
786	786	Content:
787	787
788		-Header, Query
	796	+* Header, Query
	797	+* Element Documentation:
789	789
790		-Element Documentation:
	799	+(% style="width:911.294px" %)
	800	+|(% style="width:204px" %)**Name**|(% style="width:295px" %)**Type**|(% style="width:409px" %)**Documentation**
	801	+|(% style="width:204px" %)Header|(% style="width:295px" %)BasicHeaderType|(% style="width:409px" %)
	802	+|(% style="width:204px" %)Query|(% style="width:295px" %)qry:CodelistQueryType|(% style="width:409px" %)
791	791
792		-|**Name**|**Type**|**Documentation**
793		-|Header|BasicHeaderType|
794		-|Query|qry: CodelistQueryType|
795		-
796	796	**HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical codelist query message.
797	797
798	798	Derivation:
799	799
800		-//MessageType// (restriction)
801		- HierarchicalCodelistQueryType
	808	+* //MessageType// (restriction)
	809	+** HierarchicalCodelistQueryType
802	802
803	803	Content:
804	804
805		-Header, Query
	813	+* Header, Query
	814	+* Element Documentation:
806	806
807		-Element Documentation:
	816	+(% style="width:906.294px" %)
	817	+|(% style="width:191px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:430px" %)**Documentation**
	818	+|(% style="width:191px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:430px" %)
	819	+|(% style="width:191px" %)Query|(% style="width:281px" %)qry: HierarchicalCodelist QueryType|(% style="width:430px" %)
808	808
809		-|**Name**|**Type**|**Documentation**
810		-|Header|BasicHeaderType|
811		-|Query|qry: HierarchicalCodelist QueryType|
812		-
813	813	**OrganisationSchemeQueryType: **OrganisationSchemeQueryType defines the structure of an organisation scheme query message.
814	814
815	815	Derivation:
816	816
817		-//MessageType// (restriction)
818		- OrganisationSchemeQueryType
	825	+* //MessageType// (restriction)
	826	+** OrganisationSchemeQueryType
819	819
820	820	Content:
821	821
822		-Header, Query
	830	+* Header, Query
	831	+* Element Documentation:
823	823
824		-Element Documentation:
	833	+(% style="width:891.294px" %)
	834	+|(% style="width:174px" %)**Name**|(% style="width:292px" %)**Type**|(% style="width:422px" %)**Documentation**
	835	+|(% style="width:174px" %)Header|(% style="width:292px" %)BasicHeaderType|(% style="width:422px" %)
	836	+|(% style="width:174px" %)Query|(% style="width:292px" %)qry: OrganisationSchemeQueryType|(% style="width:422px" %)
825	825
826		-|**Name**|**Type**|**Documentation**
827		-|Header|BasicHeaderType|
828		-|Query|qry: OrganisationSchemeQu eryType|
829		-
830	830	**ReportingTaxonomyQueryType: **ReportingTaxonomyQueryType defines the structure of a reporting taxonomy query message.
831	831
832	832	Derivation:
833	833
834		-//MessageType// (restriction)
835		- ReportingTaxonomyQueryType
	842	+* //MessageType// (restriction)
	843	+** ReportingTaxonomyQueryType
836	836
837	837	Content:
838	838
839		-Header, Query
	847	+* Header, Query
	848	+* Element Documentation:
840	840
841		-Element Documentation:
	850	+(% style="width:916.294px" %)
	851	+|(% style="width:162px" %)**Name**|(% style="width:318px" %)**Type**|(% style="width:434px" %)**Documentation**
	852	+|(% style="width:162px" %)Header|(% style="width:318px" %)BasicHeaderType|(% style="width:434px" %)
	853	+|(% style="width:162px" %)Query|(% style="width:318px" %)qry: ReportingTaxonomyQueryType|(% style="width:434px" %)
842	842
843		-|**Name**|**Type**|**Documentation**
844		-|Header|BasicHeaderType|
845		-|Query|qry: ReportingTaxonomyQue ryType|
846		-
847	847	**StructureSetQueryType: **StructureSetQueryType defines the structure of a structure set query message.
848	848
849	849	Derivation:
850	850
851		-//MessageType// (restriction)
852		- StructureSetQueryType
	859	+* //MessageType// (restriction)
	860	+** StructureSetQueryType
853	853
854	854	Content:
855	855
856		-Header, Query
	864	+* Header, Query
	865	+* Element Documentation:
857	857
858		-Element Documentation:
	867	+(% style="width:896.294px" %)
	868	+|(% style="width:182px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:417px" %)**Documentation**
	869	+|(% style="width:182px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:417px" %)
	870	+|(% style="width:182px" %)Query|(% style="width:294px" %)qry: StructureSetQueryType|(% style="width:417px" %)
859	859
860		-|**Name**|**Type**|**Documentation**
861		-|Header|BasicHeaderType|
862		-|Query|qry: StructureSetQueryTyp e|
863		-
864	864	**ProcessQueryType: **CategorizationQueryType defines the structure of a categorization query message.
865	865
866	866	Derivation:
867	867
868		-//MessageType// (restriction)
869		- ProcessQueryType
	876	+* //MessageType// (restriction)
	877	+** ProcessQueryType
870	870
871	871	Content:
872	872
873		-Header, Query
	881	+* Header, Query
	882	+* Element Documentation:
874	874
875		-Element Documentation:
	884	+(% style="width:907.294px" %)
	885	+|(% style="width:189px" %)**Name**|(% style="width:394px" %)**Type**|(% style="width:321px" %)**Documentation**
	886	+|(% style="width:189px" %)Header|(% style="width:394px" %)BasicHeaderType|(% style="width:321px" %)
	887	+|(% style="width:189px" %)Query|(% style="width:394px" %)qry:ProcessQueryType|(% style="width:321px" %)
876	876
877		-|**Name**|**Type**|**Documentation**
878		-|Header|BasicHeaderType|
879		-|Query|qry:ProcessQueryType|
880		-
881	881	**CategorisationQueryType: **CategorisationQueryType defines the structure of a categorisation query message.
882	882
883	883	Derivation:
884	884
885		-//MessageType// (restriction)
886		- CategorisationQueryType
	893	+* //MessageType// (restriction)
	894	+** CategorisationQueryType
887	887
888	888	Content:
889	889
890		-Header, Query
	898	+* Header, Query
	899	+* Element Documentation:
891	891
892		-Element Documentation:
	901	+(% style="width:897.294px" %)
	902	+|(% style="width:230px" %)**Name**|(% style="width:300px" %)**Type**|(% style="width:363px" %)**Documentation**
	903	+|(% style="width:230px" %)Header|(% style="width:300px" %)BasicHeaderType|(% style="width:363px" %)
	904	+|(% style="width:230px" %)Query|(% style="width:300px" %)qry: CategorisationQueryType|(% style="width:363px" %)
893	893
894		-|**Name**|**Type**|**Documentation**
895		-|Header|BasicHeaderType|
896		-|Query|qry: CategorisationQueryT ype|
897		-
898	898	**ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a provision agreement query message.
899	899
900	900	Derivation:
901	901
902		-//MessageType// (restriction)
903		- ProvisionAgreementQueryType
	910	+* //MessageType// (restriction)
	911	+** ProvisionAgreementQueryType
904	904
905	905	Content:
906	906
907		-Header, Query
	915	+* Header, Query
	916	+* Element Documentation:
908	908
909		-Element Documentation:
	918	+(% style="width:902.294px" %)
	919	+|(% style="width:142px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:418px" %)**Documentation**
	920	+|(% style="width:142px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:418px" %)
	921	+|(% style="width:142px" %)Query|(% style="width:339px" %)qry: ProvisionAgreementQueryType|(% style="width:418px" %)
910	910
911		-|**Name**|**Type**|**Documentation**
912		-|Header|BasicHeaderType|
913		-|Query|qry: ProvisionAgreementQu eryType|
914		-
915	915	**ConstraintQueryType: **ConstraintQueryType defines the structure of a constraint query message.
916	916
917	917	Derivation:
918	918
919		-//MessageType// (restriction)
920		- ConstraintQueryType
	927	+* //MessageType// (restriction)
	928	+** ConstraintQueryType
921	921
922	922	Content:
923	923
924		-Header, Query
	932	+* Header, Query
	933	+* Element Documentation:
925	925
926		-Element Documentation:
	935	+(% style="width:902.294px" %)
	936	+|(% style="width:167px" %)**Name**|(% style="width:287px" %)**Type**|(% style="width:445px" %)**Documentation**
	937	+|(% style="width:167px" %)Header|(% style="width:287px" %)BasicHeaderType|(% style="width:445px" %)
	938	+|(% style="width:167px" %)Query|(% style="width:287px" %)qry: ConstraintQueryType|(% style="width:445px" %)
927	927
928		-|**Name**|**Type**|**Documentation**
929		-|Header|BasicHeaderType|
930		-|Query|qry: ConstraintQueryType|
931		-
932	932	**TransformationSchemeQueryType: **TransformationSchemeQueryType defines the structure of a transformation scheme query message.
933	933
934	934	Derivation:
935	935
936		-//MessageType// (restriction)
937		- TransformationSchemeQueryType
	944	+* //MessageType// (restriction)
	945	+** TransformationSchemeQueryType
938	938
939	939	Content:
940	940
941		-Header, Query
	949	+* Header, Query
	950	+* Element Documentation:
942	942
943		-Element Documentation:
	952	+(% style="width:833.294px" %)
	953	+|(% style="width:165px" %)**Name**|(% style="width:325px" %)**Type**|(% style="width:340px" %)**Documentation**
	954	+|(% style="width:165px" %)Header|(% style="width:325px" %)BasicHeaderType|(% style="width:340px" %)
	955	+|(% style="width:165px" %)Query|(% style="width:325px" %)qry: TransformationSchemeQueryType|(% style="width:340px" %)
944	944
945		-|**Name**|**Type**|**Documentation**
946		-|Header|BasicHeaderType|
947		-|Query|qry: TransformationScheme QueryType|
948		-
949	949	**VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a VTL mappings scheme query message.
950	950
951	951	Derivation:
952	952
953		-//MessageType// (restriction)
954		- VtlMappingSchemeQueryType
	961	+* //MessageType// (restriction)
	962	+** VtlMappingSchemeQueryType
955	955
956	956	Content:
957	957
958		-Header, Query
	966	+* Header, Query
	967	+* Element Documentation:
959	959
960		-Element Documentation:
	969	+(% style="width:843.294px" %)
	970	+|(% style="width:164px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:373px" %)**Documentation**
	971	+|(% style="width:164px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:373px" %)
	972	+|(% style="width:164px" %)Query|(% style="width:303px" %)qry: VtlMappingSchemeQueryType|(% style="width:373px" %)
961	961
962		-|**Name**|**Type**|**Documentation**
963		-|Header|BasicHeaderType|
964		-|Query|qry: VtlMappingSchemeQuer yType|
965		-
966	966	**NamePersonalisationSchemeQueryType: **NamePersonalisationSchemeQueryType defines the structure of a name personalisation scheme query message.
967	967
968	968	Derivation:
969	969
970		-//MessageType// (restriction)
971		- NamePersonalisationSchemeQueryType
	978	+* //MessageType// (restriction)
	979	+** NamePersonalisationSchemeQueryType
972	972
973	973	Content:
974	974
975		-Header, Query
	983	+* Header, Query
	984	+* Element Documentation:
976	976
977		-Element Documentation:
	986	+(% style="width:895.294px" %)
	987	+|(% style="width:186px" %)**Name**|(% style="width:363px" %)**Type**|(% style="width:343px" %)**Documentation**
	988	+|(% style="width:186px" %)Header|(% style="width:363px" %)BasicHeaderType|(% style="width:343px" %)
	989	+|(% style="width:186px" %)Query|(% style="width:363px" %)qry: NamePersonalisationSchemeQueryType|(% style="width:343px" %)
978	978
979		-|**Name**|**Type**|**Documentation**
980		-|Header|BasicHeaderType|
981		-|Query|qry: NamePersonalisationS chemeQueryType|
982		-
983	983	**RulesetSchemeQueryType: **RulesetSchemeQueryType defines the structure of a ruleset scheme query message.
984	984
985	985	Derivation:
986	986
987		-//MessageType// (restriction)
988		- RulesetSchemeQueryType
	995	+* //MessageType// (restriction)
	996	+** RulesetSchemeQueryType
989	989
990	990	Content:
991	991
992		-Header, Query
	1000	+* Header, Query
	1001	+* Element Documentation:
993	993
994		-Element Documentation:
	1003	+(% style="width:886.294px" %)
	1004	+|(% style="width:152px" %)**Name**|(% style="width:311px" %)**Type**|(% style="width:420px" %)**Documentation**
	1005	+|(% style="width:152px" %)Header|(% style="width:311px" %)BasicHeaderType|(% style="width:420px" %)
	1006	+|(% style="width:152px" %)Query|(% style="width:311px" %)qry: RulesetSchemeQueryType|(% style="width:420px" %)
995	995
996		-|**Name**|**Type**|**Documentation**
997		-|Header|BasicHeaderType|
998		-|Query|qry: RulesetSchemeQueryTy pe|
999		-
1000	1000	**UserDefinedOperatorSchemeQueryType: **UserDefinedOperatorSchemeQueryType defines the structure of a user defined operator scheme query message.
1001	1001
1002	1002	Derivation:
1003	1003
1004		-//MessageType// (restriction)
1005		- UserDefinedOperatorSchemeQueryType
	1012	+* //MessageType// (restriction)
	1013	+** UserDefinedOperatorSchemeQueryType
1006	1006
1007	1007	Content:
1008	1008
1009		-Header, Query
	1017	+* Header, Query
	1018	+* Element Documentation:
1010	1010
1011		-Element Documentation:
	1020	+(% style="width:866.294px" %)
	1021	+|(% style="width:174px" %)**Name**|(% style="width:358px" %)**Type**|(% style="width:331px" %)**Documentation**
	1022	+|(% style="width:174px" %)Header|(% style="width:358px" %)BasicHeaderType|(% style="width:331px" %)
	1023	+|(% style="width:174px" %)Query|(% style="width:358px" %)qry: UserDefinedOperatorSchemeQueryType|(% style="width:331px" %)
1012	1012
1013		-|**Name**|**Type**|**Documentation**
1014		-|Header|BasicHeaderType|
1015		-|Query|qry: UserDefinedOperatorS chemeQueryType|
1016		-
1017	1017	**CustomTypeSchemeQueryType: **CustomTypeSchemeQueryType defines the structure of a custom type scheme query message.
1018	1018
1019	1019	Derivation:
1020	1020
1021		-//MessageType// (restriction)
1022		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] CustomTypeSchemeQueryType
	1029	+* //MessageType// (restriction)
	1030	+** CustomTypeSchemeQueryType
1023	1023
1024	1024	Content:
1025	1025
1026		-Header, Query
	1034	+* Header, Query
	1035	+* Element Documentation:
1027	1027
1028		-Element Documentation:
	1037	+(% style="width:828.294px" %)
	1038	+|(% style="width:200px" %)**Name**|(% style="width:308px" %)**Type**|(% style="width:317px" %)**Documentation**
	1039	+|(% style="width:200px" %)Header|(% style="width:308px" %)BasicHeaderType|(% style="width:317px" %)
	1040	+|(% style="width:200px" %)Query|(% style="width:308px" %)qry: CustomTypeSchemeQueryType|(% style="width:317px" %)
1029	1029
1030		-|**Name**|**Type**|**Documentation**
1031		-|Header|BasicHeaderType|
1032		-|Query|qry: CustomTypeSchemeQuer yType|
1033		-
1034	1034	**ErrorType: **ErrorType describes the structure of an error response.
1035	1035
1036	1036	Content:
1037	1037
1038		-ErrorMessage+
	1046	+* ErrorMessage+
	1047	+* Element Documentation:
1039	1039
1040		-Element Documentation:
	1049	+(% style="width:899.294px" %)
	1050	+|**Name**|**Type**|(% style="width:546px" %)**Documentation**
	1051	+|ErrorMessage|com: CodedStatusMessageTy pe|(% style="width:546px" %)ErrorMessage contains the error message. It can occur multiple times to communicate message for multiple errors, or to communicate the error message in parallel languages. If both messages for multiple errors and parallel language messages are used, then each error message should be given a code in order to distinguish message for unique errors.
1041	1041
1042		-|**Name**|**Type**|**Documentation**
1043		-|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.
1044		-
1045	1045	**//BaseHeaderType//: **BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this
1046	1046
1047	1047	Content:
...	...	@@ -1050,29 +1050,30 @@
1050	1050
1051	1051	Element Documentation:
1052	1052
1053		-|**Name**|**Type**|**Documentation**
1054		-|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1055		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1056		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1057		-|Sender|SenderType|Sender is information about the party that is transmitting the message.
1058		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1059		-|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1060		-|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.
1061		-|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1062		-|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).
1063		-|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1064		-|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1065		-|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1066		-|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1067		-|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1068		-|Source|com:TextType|Source provides human-readable information about the source of the data.
	1061	+(% style="width:891.294px" %)
	1062	+|**Name**|**Type**|(% style="width:552px" %)**Documentation**
	1063	+|ID|com:IDType|(% style="width:552px" %)ID identifies an identification for the message, assigned by the sender.
	1064	+|Test|xs:boolean|(% style="width:552px" %)Test indicates whether the message is for test purposes or not.
	1065	+|Prepared|HeaderTimeType|(% style="width:552px" %)Prepared is the date the message was prepared.
	1066	+|Sender|SenderType|(% style="width:552px" %)Sender is information about the party that is transmitting the message.
	1067	+|Receiver|PartyType|(% style="width:552px" %)Receiver is information about the party that is the intended recipient of the message.
	1068	+|com:Name|com:TextType|(% style="width:552px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1069	+|Structure|//com: PayloadStructureType//|(% style="width:552px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. 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.
	1070	+|DataProvider|com: DataProviderReferenceType|(% style="width:552px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
	1071	+|DataSetAction|com:ActionType|(% style="width:552px" %)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).
	1072	+|DataSetID|com:IDType|(% style="width:552px" %)DataSetID provides an identifier for a contained data set.
	1073	+|Extracted|xs:dateTime|(% style="width:552px" %)Extracted is a time-stamp from the system rendering the data.
	1074	+|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1075	+|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1076	+|EmbargoDate|xs:dateTime|(% style="width:552px" %)EmbargoDate holds a time period before which the data included in this message is not available.
	1077	+|Source|com:TextType|(% style="width:552px" %)Source provides human-readable information about the source of the data.
1069	1069
1070	1070	**StructureHeaderType: **StructureHeaderType defines the structure for structural metadata messages.
1071	1071
1072	1072	Derivation:
1073	1073
1074		-//BaseHeaderType// (restriction)
1075		- StructureHeaderType
	1083	+* //BaseHeaderType// (restriction)
	1084	+** StructureHeaderType
1076	1076
1077	1077	Content:
1078	1078
...	...	@@ -1080,21 +1080,22 @@
1080	1080
1081	1081	Element Documentation:
1082	1082
1083		-|**Name**|**Type**|**Documentation**
1084		-|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1085		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1086		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1087		-|Sender|SenderType|Sender is information about the party that is transmitting the message.
1088		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1089		-|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1090		-|Source|com:TextType|Source provides human-readable information about the source of the data.
	1092	+(% style="width:1099.29px" %)
	1093	+|**Name**|(% style="width:224px" %)**Type**|(% style="width:663px" %)**Documentation**
	1094	+|ID|(% style="width:224px" %)com:IDType|(% style="width:663px" %)ID identifies an identification for the message, assigned by the sender.
	1095	+|Test|(% style="width:224px" %)xs:boolean|(% style="width:663px" %)Test indicates whether the message is for test purposes or not.
	1096	+|Prepared|(% style="width:224px" %)HeaderTimeType|(% style="width:663px" %)Prepared is the date the message was prepared.
	1097	+|Sender|(% style="width:224px" %)SenderType|(% style="width:663px" %)Sender is information about the party that is transmitting the message.
	1098	+|Receiver|(% style="width:224px" %)PartyType|(% style="width:663px" %)Receiver is information about the party that is the intended recipient of the message.
	1099	+|com:Name|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1100	+|Source|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Source provides human-readable information about the source of the data.
1091	1091
1092	1092	**GenericDataHeaderType: **GenericDataHeaderType defines the header structure for a generic data message.
1093	1093
1094	1094	Derivation:
1095	1095
1096		-//BaseHeaderType// (restriction)
1097		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataHeaderType
	1106	+* //BaseHeaderType// (restriction)
	1107	+** GenericDataHeaderType
1098	1098
1099	1099	Content:
1100	1100
...	...	@@ -1102,30 +1102,31 @@
1102	1102
1103	1103	Element Documentation:
1104	1104
1105		-|**Name**|**Type**|**Documentation**
1106		-|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1107		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1108		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1109		-|Sender|SenderType|Sender is information about the party that is transmitting the message.
1110		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1111		-|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1112		-|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.
1113		-|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1114		-|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).
1115		-|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1116		-|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1117		-|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1118		-|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1119		-|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1120		-|Source|com:TextType|Source provides human-readable information about the source of the data.
	1115	+(% style="width:895.294px" %)
	1116	+|**Name**|**Type**|(% style="width:556px" %)**Documentation**
	1117	+|ID|com:IDType|(% style="width:556px" %)ID identifies an identification for the message, assigned by the sender.
	1118	+|Test|xs:boolean|(% style="width:556px" %)Test indicates whether the message is for test purposes or not.
	1119	+|Prepared|HeaderTimeType|(% style="width:556px" %)Prepared is the date the message was prepared.
	1120	+|Sender|SenderType|(% style="width:556px" %)Sender is information about the party that is transmitting the message.
	1121	+|Receiver|PartyType|(% style="width:556px" %)Receiver is information about the party that is the intended recipient of the message.
	1122	+|com:Name|com:TextType|(% style="width:556px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1123	+|Structure|com: GenericDataStructureType|(% style="width:556px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. 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.
	1124	+|DataProvider|com: DataProviderReferenceType|(% style="width:556px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
	1125	+|DataSetAction|com:ActionType|(% style="width:556px" %)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).
	1126	+|DataSetID|com:IDType|(% style="width:556px" %)DataSetID provides an identifier for a contained data set.
	1127	+|Extracted|xs:dateTime|(% style="width:556px" %)Extracted is a time-stamp from the system rendering the data.
	1128	+|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1129	+|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1130	+|EmbargoDate|xs:dateTime|(% style="width:556px" %)EmbargoDate holds a time period before which the data included in this message is not available.
	1131	+|Source|com:TextType|(% style="width:556px" %)Source provides human-readable information about the source of the data.
1121	1121
1122	1122	**GenericTimeSeriesDataHeaderType: **GenericTimeSeriesDataHeaderType defines the header structure for a time series only generic data message.
1123	1123
1124	1124	Derivation:
1125	1125
1126		-//BaseHeaderType// (restriction)
1127		- GenericDataHeaderType (restriction)
1128		- GenericTimeSeriesDataHeaderType
	1137	+* //BaseHeaderType// (restriction)
	1138	+** GenericDataHeaderType (restriction)
	1139	+*** GenericTimeSeriesDataHeaderType
1129	1129
1130	1130	Content:
1131	1131
...	...	@@ -1133,29 +1133,30 @@
1133	1133
1134	1134	Element Documentation:
1135	1135
1136		-|**Name**|**Type**|**Documentation**
1137		-|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1138		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1139		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1140		-|Sender|SenderType|Sender is information about the party that is transmitting the message.
1141		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1142		-|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1143		-|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.
1144		-|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1145		-|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).
1146		-|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1147		-|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1148		-|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1149		-|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1150		-|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1151		-|Source|com:TextType|Source provides human-readable information about the source of the data.
	1147	+(% style="width:926.294px" %)
	1148	+|**Name**|**Type**|(% style="width:497px" %)**Documentation**
	1149	+|ID|com:IDType|(% style="width:497px" %)ID identifies an identification for the message, assigned by the sender.
	1150	+|Test|xs:boolean|(% style="width:497px" %)Test indicates whether the message is for test purposes or not.
	1151	+|Prepared|HeaderTimeType|(% style="width:497px" %)Prepared is the date the message was prepared.
	1152	+|Sender|SenderType|(% style="width:497px" %)Sender is information about the party that is transmitting the message.
	1153	+|Receiver|PartyType|(% style="width:497px" %)Receiver is information about the party that is the intended recipient of the message.
	1154	+|com:Name|com:TextType|(% style="width:497px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1155	+|Structure|com: GenericTimeSeriesDataStructureType|(% style="width:497px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. 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.
	1156	+|DataProvider|com: DataProviderReferenceType|(% style="width:497px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
	1157	+|DataSetAction|com:ActionType|(% style="width:497px" %)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).
	1158	+|DataSetID|com:IDType|(% style="width:497px" %)DataSetID provides an identifier for a contained data set.
	1159	+|Extracted|xs:dateTime|(% style="width:497px" %)Extracted is a time-stamp from the system rendering the data.
	1160	+|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1161	+|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1162	+|EmbargoDate|xs:dateTime|(% style="width:497px" %)EmbargoDate holds a time period before which the data included in this message is not available.
	1163	+|Source|com:TextType|(% style="width:497px" %)Source provides human-readable information about the source of the data.
1152	1152
1153	1153	**StructureSpecificDataHeaderType: **StructureSpecificDataHeaderType defines the header structure for a structure specific data message.
1154	1154
1155	1155	Derivation:
1156	1156
1157		-//BaseHeaderType// (restriction)
1158		- StructureSpecificDataHeaderType
	1169	+* //BaseHeaderType// (restriction)
	1170	+** StructureSpecificDataHeaderType
1159	1159
1160	1160	Content:
1161	1161
...	...	@@ -1163,30 +1163,31 @@
1163	1163
1164	1164	Element Documentation:
1165	1165
1166		-|**Name**|**Type**|**Documentation**
1167		-|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1168		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1169		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1170		-|Sender|SenderType|Sender is information about the party that is transmitting the message.
1171		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1172		-|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1173		-|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.
1174		-|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1175		-|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).
1176		-|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1177		-|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1178		-|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1179		-|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1180		-|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1181		-|Source|com:TextType|Source provides human-readable information about the source of the data.
	1178	+(% style="width:930.294px" %)
	1179	+|**Name**|**Type**|(% style="width:578px" %)**Documentation**
	1180	+|ID|com:IDType|(% style="width:578px" %)ID identifies an identification for the message, assigned by the sender.
	1181	+|Test|xs:boolean|(% style="width:578px" %)Test indicates whether the message is for test purposes or not.
	1182	+|Prepared|HeaderTimeType|(% style="width:578px" %)Prepared is the date the message was prepared.
	1183	+|Sender|SenderType|(% style="width:578px" %)Sender is information about the party that is transmitting the message.
	1184	+|Receiver|PartyType|(% style="width:578px" %)Receiver is information about the party that is the intended recipient of the message.
	1185	+|com:Name|com:TextType|(% style="width:578px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1186	+|Structure|com: StructureSpecificDataStructureType|(% style="width:578px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. 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.
	1187	+|DataProvider|com: DataProviderReferenceType|(% style="width:578px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
	1188	+|DataSetAction|com:ActionType|(% style="width:578px" %)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).
	1189	+|DataSetID|com:IDType|(% style="width:578px" %)DataSetID provides an identifier for a contained data set.
	1190	+|Extracted|xs:dateTime|(% style="width:578px" %)Extracted is a time-stamp from the system rendering the data.
	1191	+|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1192	+|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1193	+|EmbargoDate|xs:dateTime|(% style="width:578px" %)EmbargoDate holds a time period before which the data included in this message is not available.
	1194	+|Source|com:TextType|(% style="width:578px" %)Source provides human-readable information about the source of the data.
1182	1182
1183	1183	**StructureSpecificTimeSeriesDataHeaderType: **StructureSpecificTimeSeriesDataHeaderType defines the header structure for a time series only structure specific data message.
1184	1184
1185	1185	Derivation:
1186	1186
1187		-//BaseHeaderType// (restriction)
1188		- StructureSpecificDataHeaderType (restriction)
1189		- StructureSpecificTimeSeriesDataHeaderType
	1200	+* //BaseHeaderType// (restriction)
	1201	+** StructureSpecificDataHeaderType (restriction)
	1202	+*** StructureSpecificTimeSeriesDataHeaderType
1190	1190
1191	1191	Content:
1192	1192
...	...	@@ -1194,29 +1194,30 @@
1194	1194
1195	1195	Element Documentation:
1196	1196
1197		-|**Name**|**Type**|**Documentation**
1198		-|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1199		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1200		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1201		-|Sender|SenderType|Sender is information about the party that is transmitting the message.
1202		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1203		-|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1204		-|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.
1205		-|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1206		-|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).
1207		-|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1208		-|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1209		-|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1210		-|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1211		-|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1212		-|Source|com:TextType|Source provides human-readable information about the source of the data.
	1210	+(% style="width:943.294px" %)
	1211	+|**Name**|(% style="width:352px" %)**Type**|(% style="width:461px" %)**Documentation**
	1212	+|ID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)ID identifies an identification for the message, assigned by the sender.
	1213	+|Test|(% style="width:352px" %)xs:boolean|(% style="width:461px" %)Test indicates whether the message is for test purposes or not.
	1214	+|Prepared|(% style="width:352px" %)HeaderTimeType|(% style="width:461px" %)Prepared is the date the message was prepared.
	1215	+|Sender|(% style="width:352px" %)SenderType|(% style="width:461px" %)Sender is information about the party that is transmitting the message.
	1216	+|Receiver|(% style="width:352px" %)PartyType|(% style="width:461px" %)Receiver is information about the party that is the intended recipient of the message.
	1217	+|com:Name|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1218	+|Structure|(% style="width:352px" %)com: StructureSpecificDataTimeSeriesStructureType|(% style="width:461px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. 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.
	1219	+|DataProvider|(% style="width:352px" %)com: DataProviderReferenceType|(% style="width:461px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
	1220	+|DataSetAction|(% style="width:352px" %)com:ActionType|(% style="width:461px" %)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).
	1221	+|DataSetID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)DataSetID provides an identifier for a contained data set.
	1222	+|Extracted|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)Extracted is a time-stamp from the system rendering the data.
	1223	+|ReportingBegin|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1224	+|ReportingEnd|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1225	+|EmbargoDate|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)EmbargoDate holds a time period before which the data included in this message is not available.
	1226	+|Source|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Source provides human-readable information about the source of the data.
1213	1213
1214	1214	**GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic reference metadata.
1215	1215
1216	1216	Derivation:
1217	1217
1218		-//BaseHeaderType// (restriction)
1219		- GenericMetadataHeaderType
	1232	+* //BaseHeaderType// (restriction)
	1233	+** GenericMetadataHeaderType
1220	1220
1221	1221	Content:
1222	1222
...	...	@@ -1224,26 +1224,27 @@
1224	1224
1225	1225	Element Documentation:
1226	1226
1227		-|**Name**|**Type**|**Documentation**
1228		-|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1229		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1230		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1231		-|Sender|SenderType|Sender is information about the party that is transmitting the message.
1232		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1233		-|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1234		-|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.
1235		-|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1236		-|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).
1237		-|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1238		-|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1239		-|Source|com:TextType|Source provides human-readable information about the source of the data.
	1241	+(% style="width:928.294px" %)
	1242	+|**Name**|**Type**|(% style="width:554px" %)**Documentation**
	1243	+|ID|com:IDType|(% style="width:554px" %)ID identifies an identification for the message, assigned by the sender.
	1244	+|Test|xs:boolean|(% style="width:554px" %)Test indicates whether the message is for test purposes or not.
	1245	+|Prepared|HeaderTimeType|(% style="width:554px" %)Prepared is the date the message was prepared.
	1246	+|Sender|SenderType|(% style="width:554px" %)Sender is information about the party that is transmitting the message.
	1247	+|Receiver|PartyType|(% style="width:554px" %)Receiver is information about the party that is the intended recipient of the message.
	1248	+|com:Name|com:TextType|(% style="width:554px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1249	+|Structure|com: GenericMetadataStructureType|(% style="width:554px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. 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.
	1250	+|DataProvider|com: DataProviderReferenceType|(% style="width:554px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
	1251	+|DataSetAction|com:ActionType|(% style="width:554px" %)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).
	1252	+|DataSetID|com:IDType|(% style="width:554px" %)DataSetID provides an identifier for a contained data set.
	1253	+|Extracted|xs:dateTime|(% style="width:554px" %)Extracted is a time-stamp from the system rendering the data.
	1254	+|Source|com:TextType|(% style="width:554px" %)Source provides human-readable information about the source of the data.
1240	1240
1241	1241	**StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for metadata structure definition specific reference metadata messages.
1242	1242
1243	1243	Derivation:
1244	1244
1245		-//BaseHeaderType// (restriction)
1246		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType
	1260	+* //BaseHeaderType// (restriction)
	1261	+** StructureSpecificMetadataHeaderType
1247	1247
1248	1248	Content:
1249	1249
...	...	@@ -1251,26 +1251,27 @@
1251	1251
1252	1252	Element Documentation:
1253	1253
1254		-|**Name**|**Type**|**Documentation**
1255		-|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1256		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1257		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1258		-|Sender|SenderType|Sender is information about the party that is transmitting the message.
1259		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1260		-|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1261		-|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.
1262		-|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1263		-|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).
1264		-|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1265		-|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1266		-|Source|com:TextType|Source provides human-readable information about the source of the data.
	1269	+(% style="width:996.294px" %)
	1270	+|**Name**|**Type**|(% style="width:557px" %)**Documentation**
	1271	+|ID|com:IDType|(% style="width:557px" %)ID identifies an identification for the message, assigned by the sender.
	1272	+|Test|xs:boolean|(% style="width:557px" %)Test indicates whether the message is for test purposes or not.
	1273	+|Prepared|HeaderTimeType|(% style="width:557px" %)Prepared is the date the message was prepared.
	1274	+|Sender|SenderType|(% style="width:557px" %)Sender is information about the party that is transmitting the message.
	1275	+|Receiver|PartyType|(% style="width:557px" %)Receiver is information about the party that is the intended recipient of the message.
	1276	+|com:Name|com:TextType|(% style="width:557px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1277	+|Structure|com: StructureSpecificMetadataStructureType|(% style="width:557px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. 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.
	1278	+|DataProvider|com: DataProviderReferenceType|(% style="width:557px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
	1279	+|DataSetAction|com:ActionType|(% style="width:557px" %)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).
	1280	+|DataSetID|com:IDType|(% style="width:557px" %)DataSetID provides an identifier for a contained data set.
	1281	+|Extracted|xs:dateTime|(% style="width:557px" %)Extracted is a time-stamp from the system rendering the data.
	1282	+|Source|com:TextType|(% style="width:557px" %)Source provides human-readable information about the source of the data.
1267	1267
1268	1268	**BasicHeaderType: **BasicHeaderType defines the most basic header information used in simple message exchanges.
1269	1269
1270	1270	Derivation:
1271	1271
1272		-//BaseHeaderType// (restriction)
1273		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType
	1288	+* //BaseHeaderType// (restriction)
	1289	+** BasicHeaderType
1274	1274
1275	1275	Content:
1276	1276
...	...	@@ -1278,12 +1278,13 @@
1278	1278
1279	1279	Element Documentation:
1280	1280
1281		-|**Name**|**Type**|**Documentation**
1282		-|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1283		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1284		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1285		-|Sender|SenderType|Sender is information about the party that is transmitting the message.
1286		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1297	+(% style="width:903.294px" %)
	1298	+|**Name**|(% style="width:236px" %)**Type**|(% style="width:457px" %)**Documentation**
	1299	+|ID|(% style="width:236px" %)com:IDType|(% style="width:457px" %)ID identifies an identification for the message, assigned by the sender.
	1300	+|Test|(% style="width:236px" %)xs:boolean|(% style="width:457px" %)Test indicates whether the message is for test purposes or not.
	1301	+|Prepared|(% style="width:236px" %)HeaderTimeType|(% style="width:457px" %)Prepared is the date the message was prepared.
	1302	+|Sender|(% style="width:236px" %)SenderType|(% style="width:457px" %)Sender is information about the party that is transmitting the message.
	1303	+|Receiver|(% style="width:236px" %)PartyType|(% style="width:457px" %)Receiver is information about the party that is the intended recipient of the message.
1287	1287
1288	1288	**PartyType: **PartyType defines the information which is sent about various parties such as senders and receivers of messages.
1289	1289
...	...	@@ -1297,21 +1297,23 @@
1297	1297
1298	1298	Attribute Documentation:
1299	1299
1300		-|**Name**|**Type**|**Documentation**
1301		-|id|com:IDType|The id attribute holds the identification of the party.
	1317	+(% style="width:739.294px" %)
	1318	+|(% style="width:125px" %)**Name**|(% style="width:190px" %)**Type**|(% style="width:421px" %)**Documentation**
	1319	+|(% style="width:125px" %)id|(% style="width:190px" %)com:IDType|(% style="width:421px" %)The id attribute holds the identification of the party.
1302	1302
1303	1303	Element Documentation:
1304	1304
1305		-|**Name**|**Type**|**Documentation**
1306		-|com:Name|com:TextType|Name is a human-readable name of the party.
1307		-|Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message.
	1323	+(% style="width:751.294px" %)
	1324	+|(% style="width:134px" %)**Name**|(% style="width:183px" %)**Type**|(% style="width:431px" %)**Documentation**
	1325	+|(% style="width:134px" %)com:Name|(% style="width:183px" %)com:TextType|(% style="width:431px" %)Name is a human-readable name of the party.
	1326	+|(% style="width:134px" %)Contact|(% style="width:183px" %)ContactType|(% style="width:431px" %)Contact provides contact information for the party in regard to the transmission of the message.
1308	1308
1309	1309	**SenderType: **SenderType extends the basic party structure to add an optional time zone declaration.
1310	1310
1311	1311	Derivation:
1312	1312
1313		-PartyType (extension)
1314		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType
	1332	+* PartyType (extension)
	1333	+** SenderType
1315	1315
1316	1316	Attributes:
1317	1317
...	...	@@ -1323,8 +1323,9 @@
1323	1323
1324	1324	Attribute Documentation:
1325	1325
1326		-|**Name**|**Type**|**Documentation**
1327		-|id|com:IDType|The id attribute holds the identification of the party.
	1345	+(% style="width:824.294px" %)
	1346	+|(% style="width:177px" %)**Name**|(% style="width:241px" %)**Type**|(% style="width:403px" %)**Documentation**
	1347	+|(% style="width:177px" %)id|(% style="width:241px" %)com:IDType|(% style="width:403px" %)The id attribute holds the identification of the party.
1328	1328
1329	1329	Element Documentation:
1330	1330
...	...	@@ -1351,8 +1351,8 @@
1351	1351	|URI|xs:anyURI|URI holds an information URL for the contact person.
1352	1352	|Email|xs:string|Email holds the email address for the contact person.
1353	1353
1354		-1.
1355		-11.
	1374	+1.
	1375	+11.
1356	1356	111. Simple Types
1357	1357
1358	1358	**HeaderTimeType: **Provides a union type of xs:date and xs:dateTime for the header fields in the message.
...	...	@@ -1361,13 +1361,13 @@
1361	1361
1362	1362	xs:dateTime, xs:date.
1363	1363
1364		-1.
	1384	+1.
1365	1365	11. Message Footer Namespace
1366	1366
1367	1367	**http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer**
1368	1368
1369		-1.
1370		-11.
	1389	+1.
	1390	+11.
1371	1371	111. Summary
1372	1372
1373	1373	Referenced Namespaces:
...	...	@@ -1382,14 +1382,14 @@
1382	1382	2 Complex Types
1383	1383	1 Simple Type
1384	1384
1385		-1.
1386		-11.
	1405	+1.
	1406	+11.
1387	1387	111. Global Elements
1388	1388
1389	1389	**Footer (FooterType): **Footer is used to communicate information such as error and warnings after the payload of a message.
1390	1390
1391		-1.
1392		-11.
	1411	+1.
	1412	+11.
1393	1393	111. Complex Types
1394	1394
1395	1395	**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.
...	...	@@ -1408,8 +1408,8 @@
1408	1408	Derivation:
1409	1409
1410	1410	com:StatusMessageType (restriction)
1411		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension)
1412		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType
	1431	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension)
	1432	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType
1413	1413
1414	1414	Attributes:
1415	1415
...	...	@@ -1430,8 +1430,8 @@
1430	1430	|**Name**|**Type**|**Documentation**
1431	1431	|com:Text|com:TextType|Text contains the text of the message, in parallel language values.
1432	1432
1433		-1.
1434		-11.
	1453	+1.
	1454	+11.
1435	1435	111. Simple Types
1436	1436
1437	1437	**SeverityCodeType:**