Changes for page Part I. Message Namespace

Summary

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

Details

Page properties

Content

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