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		-** StructureType
	180	+//MessageType// (restriction)
	181	+ StructureType
182	182
183	183	Content:
184	184
...	...	@@ -196,8 +196,8 @@
196	196
197	197	Derivation:
198	198
199		-* //MessageType// (restriction)
200		-** GenericDataType
	199	+//MessageType// (restriction)
	200	+ GenericDataType
201	201
202	202	Content:
203	203
...	...	@@ -351,18 +351,17 @@
351	351
352	352	Element Documentation:
353	353
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.
	354	+|**Name**|**Type**|**Documentation**
	355	+|Header|BasicHeaderType|
	356	+|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.
358	358
359	359	**SubmitRegistrationsResponseType: **SubmitRegistrationsResponseType defines the structure of a registry submit registration response document.
360	360
361	361	Derivation:
362	362
363		-* //MessageType// (restriction)
364		-** RegistryInterfaceType (restriction)
365		-*** SubmitRegistrationsResponseType
	362	+//MessageType// (restriction)
	363	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	364	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitRegistrationsResponseType
366	366
367	367	Content:
368	368
...	...	@@ -370,19 +370,18 @@
370	370
371	371	Element Documentation:
372	372
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.
	372	+|**Name**|**Type**|**Documentation**
	373	+|Header|BasicHeaderType|
	374	+|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.
	375	+|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
378	378
379	379	**QueryRegistrationRequestType: **QueryRegistrationRequestType defines the structure of a registry query registration request document.
380	380
381	381	Derivation:
382	382
383		-* //MessageType// (restriction)
384		-** RegistryInterfaceType (restriction)
385		-*** QueryRegistrationRequestType
	381	+//MessageType// (restriction)
	382	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	383	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationRequestType
386	386
387	387	Content:
388	388
...	...	@@ -390,18 +390,17 @@
390	390
391	391	Element Documentation:
392	392
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.
	391	+|**Name**|**Type**|**Documentation**
	392	+|Header|BasicHeaderType|
	393	+|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.
397	397
398	398	**QueryRegistrationResponseType: **SubmitRegistrationRequestType defines the structure of a registry submit registration response document.
399	399
400	400	Derivation:
401	401
402		-* //MessageType// (restriction)
403		-** RegistryInterfaceType (restriction)
404		-*** QueryRegistrationResponseType
	399	+//MessageType// (restriction)
	400	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	401	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationResponseType
405	405
406	406	Content:
407	407
...	...	@@ -409,19 +409,18 @@
409	409
410	410	Element Documentation:
411	411
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.
	409	+|**Name**|**Type**|**Documentation**
	410	+|Header|BasicHeaderType|
	411	+|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.
	412	+|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
417	417
418	418	**SubmitStructureRequestType: **SubmitStructureRequestType defines the structure of a registry submit structure request document.
419	419
420	420	Derivation:
421	421
422		-* //MessageType// (restriction)
423		-** RegistryInterfaceType (restriction)
424		-*** SubmitStructureRequestType
	418	+//MessageType// (restriction)
	419	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	420	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureRequestType
425	425
426	426	Content:
427	427
...	...	@@ -429,18 +429,17 @@
429	429
430	430	Element Documentation:
431	431
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.
	428	+|**Name**|**Type**|**Documentation**
	429	+|Header|BasicHeaderType|
	430	+|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.
436	436
437	437	**SubmitStructureResponseType: **SubmitStructureResponseType defines the structure of a registry submit registration response document.
438	438
439	439	Derivation:
440	440
441		-* //MessageType// (restriction)
442		-** RegistryInterfaceType (restriction)
443		-*** SubmitStructureResponseType
	436	+//MessageType// (restriction)
	437	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	438	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureResponseType
444	444
445	445	Content:
446	446
...	...	@@ -448,19 +448,18 @@
448	448
449	449	Element Documentation:
450	450
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.
	446	+|**Name**|**Type**|**Documentation**
	447	+|Header|BasicHeaderType|
	448	+|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.
	449	+|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
456	456
457	457	**SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit subscription request document.
458	458
459	459	Derivation:
460	460
461		-* //MessageType// (restriction)
462		-** RegistryInterfaceType (restriction)
463		-*** SubmitSubscriptionsRequestType
	455	+//MessageType// (restriction)
	456	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	457	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsRequestType
464	464
465	465	Content:
466	466
...	...	@@ -468,18 +468,17 @@
468	468
469	469	Element Documentation:
470	470
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.
	465	+|**Name**|**Type**|**Documentation**
	466	+|Header|BasicHeaderType|
	467	+|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.
475	475
476	476	**SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit subscription response document.
477	477
478	478	Derivation:
479	479
480		-* //MessageType// (restriction)
481		-** RegistryInterfaceType (restriction)
482		-*** SubmitSubscriptionsResponseType
	473	+//MessageType// (restriction)
	474	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	475	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsResponseType
483	483
484	484	Content:
485	485
...	...	@@ -487,19 +487,18 @@
487	487
488	488	Element Documentation:
489	489
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.
	483	+|**Name**|**Type**|**Documentation**
	484	+|Header|BasicHeaderType|
	485	+|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.
	486	+|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
495	495
496	496	**QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query subscription request document.
497	497
498	498	Derivation:
499	499
500		-* //MessageType// (restriction)
501		-** RegistryInterfaceType (restriction)
502		-*** QuerySubscriptionRequestType
	492	+//MessageType// (restriction)
	493	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	494	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionRequestType
503	503
504	504	Content:
505	505
...	...	@@ -507,18 +507,17 @@
507	507
508	508	Element Documentation:
509	509
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.
	502	+|**Name**|**Type**|**Documentation**
	503	+|Header|BasicHeaderType|
	504	+|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
514	514
515	515	**QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query subscription response document.
516	516
517	517	Derivation:
518	518
519		-* //MessageType// (restriction)
520		-** RegistryInterfaceType (restriction)
521		-*** QuerySubscriptionResponseType
	510	+//MessageType// (restriction)
	511	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	512	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionResponseType
522	522
523	523	Content:
524	524
...	...	@@ -526,19 +526,18 @@
526	526
527	527	Element Documentation:
528	528
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.
	520	+|**Name**|**Type**|**Documentation**
	521	+|Header|BasicHeaderType|
	522	+|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.
	523	+|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
534	534
535	535	**NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry notification document.
536	536
537	537	Derivation:
538	538
539		-* //MessageType// (restriction)
540		-** RegistryInterfaceType (restriction)
541		-*** NotifyRegistryEventType
	529	+//MessageType// (restriction)
	530	+ RegistryInterfaceType (restriction)
	531	+ NotifyRegistryEventType
542	542
543	543	Content:
544	544
...	...	@@ -546,17 +546,16 @@
546	546
547	547	Element Documentation:
548	548
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.
	539	+|**Name**|**Type**|**Documentation**
	540	+|Header|BasicHeaderType|
	541	+|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.
553	553
554	554	**DataQueryType: **DataQueryType defines the structure of a data query message.
555	555
556	556	Derivation:
557	557
558		-* //MessageType// (restriction)
559		-** DataQueryType
	547	+//MessageType// (restriction)
	548	+ DataQueryType
560	560
561	561	Content:
562	562
...	...	@@ -564,18 +564,17 @@
564	564
565	565	Element Documentation:
566	566
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" %)
	556	+|**Name**|**Type**|**Documentation**
	557	+|Header|BasicHeaderType|
	558	+|Query|qry:DataQueryType|
571	571
572	572	**GenericDataQueryType: **DataQueryType defines the structure of a generic data query message.
573	573
574	574	Derivation:
575	575
576		-* //MessageType// (restriction)
577		-** DataQueryType (restriction)
578		-*** GenericDataQueryType
	564	+//MessageType// (restriction)
	565	+ DataQueryType (restriction)
	566	+ GenericDataQueryType
579	579
580	580	Content:
581	581
...	...	@@ -583,19 +583,18 @@
583	583
584	584	Element Documentation:
585	585
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" %)
	574	+|**Name**|**Type**|**Documentation**
	575	+|Header|BasicHeaderType|
	576	+|Query|qry: GenericDataQueryType|
590	590
591	591	**GenericTimeSeriesDataQueryType: **GenericTimeSeriesDataQueryType defines the structure of a time series generic data query message.
592	592
593	593	Derivation:
594	594
595		-* //MessageType// (restriction)
596		-** DataQueryType (restriction)
597		-*** GenericDataQueryType (restriction)
598		-**** GenericTimeSeriesDataQueryType
	582	+//MessageType// (restriction)
	583	+ DataQueryType (restriction)
	584	+ GenericDataQueryType (restriction)
	585	+ GenericTimeSeriesDataQueryType
599	599
600	600	Content:
601	601
...	...	@@ -603,18 +603,17 @@
603	603
604	604	Element Documentation:
605	605
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" %)
	593	+|**Name**|**Type**|**Documentation**
	594	+|Header|BasicHeaderType|
	595	+|Query|qry: GenericTimeSeriesDat aQueryType|
610	610
611	611	**StructureSpecificTimeSeriesDataQueryType: **StructureSpecificTimeSeriesDataQueryType defines the structure of a time series generic data query message.
612	612
613	613	Derivation:
614	614
615		-* //MessageType// (restriction)
616		-** DataQueryType (restriction)
617		-*** StructureSpecificTimeSeriesDataQueryType
	601	+//MessageType// (restriction)
	602	+ DataQueryType (restriction)
	603	+ StructureSpecificTimeSeriesDataQueryType
618	618
619	619	Content:
620	620
...	...	@@ -622,17 +622,16 @@
622	622
623	623	Element Documentation:
624	624
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" %)
	611	+|**Name**|**Type**|**Documentation**
	612	+|Header|BasicHeaderType|
	613	+|Query|qry: TimeSeriesDataQueryT ype|
629	629
630	630	**MetadataQueryType: **MetadataQueryType defines the structure of a reference metadata query message.
631	631
632	632	Derivation:
633	633
634		-* //MessageType// (restriction)
635		-** MetadataQueryType
	619	+//MessageType// (restriction)
	620	+ MetadataQueryType
636	636
637	637	Content:
638	638
...	...	@@ -640,17 +640,16 @@
640	640
641	641	Element Documentation:
642	642
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" %)
	628	+|**Name**|**Type**|**Documentation**
	629	+|Header|BasicHeaderType|
	630	+|Query|qry: MetadataQueryType|
647	647
648	648	**DataSchemaQueryType: **DataSchemaQueryType defines the structure of a data schema query message.
649	649
650	650	Derivation:
651	651
652		-* //MessageType// (restriction)
653		-** DataSchemaQueryType
	636	+//MessageType// (restriction)
	637	+ DataSchemaQueryType
654	654
655	655	Content:
656	656
...	...	@@ -658,17 +658,16 @@
658	658
659	659	Element Documentation:
660	660
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" %)
	645	+|**Name**|**Type**|**Documentation**
	646	+|Header|BasicHeaderType|
	647	+|Query|qry: DataSchemaQueryType|
665	665
666	666	**MetadataSchemaQueryType: **MetadataSchemaQueryType defines the structure of a metadata schema query message.
667	667
668	668	Derivation:
669	669
670		-* //MessageType// (restriction)
671		-** MetadataSchemaQueryType
	653	+//MessageType// (restriction)
	654	+ MetadataSchemaQueryType
672	672
673	673	Content:
674	674
...	...	@@ -676,17 +676,16 @@
676	676
677	677	Element Documentation:
678	678
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" %)
	662	+|**Name**|**Type**|**Documentation**
	663	+|Header|BasicHeaderType|
	664	+|Query|qry: MetadataSchemaQueryT ype|
683	683
684	684	**StructuresQueryType: **StructuresQueryType defines the structure of a structures query message.
685	685
686	686	Derivation:
687	687
688		-* //MessageType// (restriction)
689		-** StructuresQueryType
	670	+//MessageType// (restriction)
	671	+ StructuresQueryType
690	690
691	691	Content:
692	692
...	...	@@ -694,17 +694,16 @@
694	694
695	695	Element Documentation:
696	696
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" %)
	679	+|**Name**|**Type**|**Documentation**
	680	+|Header|BasicHeaderType|
	681	+|Query|qry: StructuresQueryType|
701	701
702	702	**DataflowQueryType: **DataflowQueryType defines the structure of a dataflow query message.
703	703
704	704	Derivation:
705	705
706		-* //MessageType// (restriction)
707		-** DataflowQueryType
	687	+//MessageType// (restriction)
	688	+ DataflowQueryType
708	708
709	709	Content:
710	710
...	...	@@ -712,17 +712,16 @@
712	712
713	713	Element Documentation:
714	714
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" %)
	696	+|**Name**|**Type**|**Documentation**
	697	+|Header|BasicHeaderType|
	698	+|Query|qry: DataflowQueryType|
719	719
720	720	**MetadataflowQueryType: **MetadataflowQueryType defines the structure of a metadata flow query message.
721	721
722	722	Derivation:
723	723
724		-* //MessageType// (restriction)
725		-** MetadataflowQueryType
	704	+//MessageType// (restriction)
	705	+ MetadataflowQueryType
726	726
727	727	Content:
728	728
...	...	@@ -730,17 +730,16 @@
730	730
731	731	Element Documentation:
732	732
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" %)
	713	+|**Name**|**Type**|**Documentation**
	714	+|Header|BasicHeaderType|
	715	+|Query|qry: MetadataflowQueryTyp e|
737	737
738	738	**DataStructureQueryType: **KeyFamilyQueryType defines the structure of a data structure query message.
739	739
740	740	Derivation:
741	741
742		-* //MessageType// (restriction)
743		-** DataStructureQueryType
	721	+//MessageType// (restriction)
	722	+ DataStructureQueryType
744	744
745	745	Content:
746	746
...	...	@@ -748,17 +748,16 @@
748	748
749	749	Element Documentation:
750	750
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" %)
	730	+|**Name**|**Type**|**Documentation**
	731	+|Header|BasicHeaderType|
	732	+|Query|qry: DataStructureQueryTy pe|
755	755
756	756	**MetadataStructureQueryType: **MetadataStructureQueryType defines the structure of a metadata structure query message.
757	757
758	758	Derivation:
759	759
760		-* //MessageType// (restriction)
761		-** MetadataStructureQueryType
	738	+//MessageType// (restriction)
	739	+ MetadataStructureQueryType
762	762
763	763	Content:
764	764
...	...	@@ -766,17 +766,16 @@
766	766
767	767	Element Documentation:
768	768
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" %)
	747	+|**Name**|**Type**|**Documentation**
	748	+|Header|BasicHeaderType|
	749	+|Query|qry: MetadataStructureQue ryType|
773	773
774	774	**CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a category scheme query message.
775	775
776	776	Derivation:
777	777
778		-* //MessageType// (restriction)
779		-** CategorySchemeQueryType
	755	+//MessageType// (restriction)
	756	+ CategorySchemeQueryType
780	780
781	781	Content:
782	782
...	...	@@ -784,17 +784,16 @@
784	784
785	785	Element Documentation:
786	786
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" %)
	764	+|**Name**|**Type**|**Documentation**
	765	+|Header|BasicHeaderType|
	766	+|Query|qry: CategorySchemeQueryT ype|
791	791
792	792	**ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a concept scheme query message.
793	793
794	794	Derivation:
795	795
796		-* //MessageType// (restriction)
797		-** ConceptSchemeQueryType
	772	+//MessageType// (restriction)
	773	+ ConceptSchemeQueryType
798	798
799	799	Content:
800	800
...	...	@@ -802,277 +802,276 @@
802	802
803	803	Element Documentation:
804	804
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" %)
	781	+|**Name**|**Type**|**Documentation**
	782	+|Header|BasicHeaderType|
	783	+|Query|qry: ConceptSchemeQueryTy pe|
809	809
810	810	**CodelistQueryType: **CodelistQueryType defines the structure of a codelist query message.
811	811
812	812	Derivation:
813	813
814		-* //MessageType// (restriction)
815		-** CodelistQueryType
	789	+//MessageType// (restriction)
	790	+ CodelistQueryType
816	816
817	817	Content:
818	818
819		-* Header, Query
820		-* Element Documentation:
	794	+Header, Query
821	821
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" %)
	796	+Element Documentation:
826	826
	798	+|**Name**|**Type**|**Documentation**
	799	+|Header|BasicHeaderType|
	800	+|Query|qry: CodelistQueryType|
	801	+
827	827	**HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical codelist query message.
828	828
829	829	Derivation:
830	830
831		-* //MessageType// (restriction)
832		-** HierarchicalCodelistQueryType
	806	+//MessageType// (restriction)
	807	+ HierarchicalCodelistQueryType
833	833
834	834	Content:
835	835
836		-* Header, Query
837		-* Element Documentation:
	811	+Header, Query
838	838
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" %)
	813	+Element Documentation:
843	843
	815	+|**Name**|**Type**|**Documentation**
	816	+|Header|BasicHeaderType|
	817	+|Query|qry: HierarchicalCodelist QueryType|
	818	+
844	844	**OrganisationSchemeQueryType: **OrganisationSchemeQueryType defines the structure of an organisation scheme query message.
845	845
846	846	Derivation:
847	847
848		-* //MessageType// (restriction)
849		-** OrganisationSchemeQueryType
	823	+//MessageType// (restriction)
	824	+ OrganisationSchemeQueryType
850	850
851	851	Content:
852	852
853		-* Header, Query
854		-* Element Documentation:
	828	+Header, Query
855	855
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" %)
	830	+Element Documentation:
860	860
	832	+|**Name**|**Type**|**Documentation**
	833	+|Header|BasicHeaderType|
	834	+|Query|qry: OrganisationSchemeQu eryType|
	835	+
861	861	**ReportingTaxonomyQueryType: **ReportingTaxonomyQueryType defines the structure of a reporting taxonomy query message.
862	862
863	863	Derivation:
864	864
865		-* //MessageType// (restriction)
866		-** ReportingTaxonomyQueryType
	840	+//MessageType// (restriction)
	841	+ ReportingTaxonomyQueryType
867	867
868	868	Content:
869	869
870		-* Header, Query
871		-* Element Documentation:
	845	+Header, Query
872	872
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" %)
	847	+Element Documentation:
877	877
	849	+|**Name**|**Type**|**Documentation**
	850	+|Header|BasicHeaderType|
	851	+|Query|qry: ReportingTaxonomyQue ryType|
	852	+
878	878	**StructureSetQueryType: **StructureSetQueryType defines the structure of a structure set query message.
879	879
880	880	Derivation:
881	881
882		-* //MessageType// (restriction)
883		-** StructureSetQueryType
	857	+//MessageType// (restriction)
	858	+ StructureSetQueryType
884	884
885	885	Content:
886	886
887		-* Header, Query
888		-* Element Documentation:
	862	+Header, Query
889	889
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" %)
	864	+Element Documentation:
894	894
	866	+|**Name**|**Type**|**Documentation**
	867	+|Header|BasicHeaderType|
	868	+|Query|qry: StructureSetQueryTyp e|
	869	+
895	895	**ProcessQueryType: **CategorizationQueryType defines the structure of a categorization query message.
896	896
897	897	Derivation:
898	898
899		-* //MessageType// (restriction)
900		-** ProcessQueryType
	874	+//MessageType// (restriction)
	875	+ ProcessQueryType
901	901
902	902	Content:
903	903
904		-* Header, Query
905		-* Element Documentation:
	879	+Header, Query
906	906
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" %)
	881	+Element Documentation:
911	911
	883	+|**Name**|**Type**|**Documentation**
	884	+|Header|BasicHeaderType|
	885	+|Query|qry:ProcessQueryType|
	886	+
912	912	**CategorisationQueryType: **CategorisationQueryType defines the structure of a categorisation query message.
913	913
914	914	Derivation:
915	915
916		-* //MessageType// (restriction)
917		-** CategorisationQueryType
	891	+//MessageType// (restriction)
	892	+ CategorisationQueryType
918	918
919	919	Content:
920	920
921		-* Header, Query
922		-* Element Documentation:
	896	+Header, Query
923	923
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" %)
	898	+Element Documentation:
928	928
	900	+|**Name**|**Type**|**Documentation**
	901	+|Header|BasicHeaderType|
	902	+|Query|qry: CategorisationQueryT ype|
	903	+
929	929	**ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a provision agreement query message.
930	930
931	931	Derivation:
932	932
933		-* //MessageType// (restriction)
934		-** ProvisionAgreementQueryType
	908	+//MessageType// (restriction)
	909	+ ProvisionAgreementQueryType
935	935
936	936	Content:
937	937
938		-* Header, Query
939		-* Element Documentation:
	913	+Header, Query
940	940
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" %)
	915	+Element Documentation:
945	945
	917	+|**Name**|**Type**|**Documentation**
	918	+|Header|BasicHeaderType|
	919	+|Query|qry: ProvisionAgreementQu eryType|
	920	+
946	946	**ConstraintQueryType: **ConstraintQueryType defines the structure of a constraint query message.
947	947
948	948	Derivation:
949	949
950		-* //MessageType// (restriction)
951		-** ConstraintQueryType
	925	+//MessageType// (restriction)
	926	+ ConstraintQueryType
952	952
953	953	Content:
954	954
955		-* Header, Query
956		-* Element Documentation:
	930	+Header, Query
957	957
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" %)
	932	+Element Documentation:
962	962
	934	+|**Name**|**Type**|**Documentation**
	935	+|Header|BasicHeaderType|
	936	+|Query|qry: ConstraintQueryType|
	937	+
963	963	**TransformationSchemeQueryType: **TransformationSchemeQueryType defines the structure of a transformation scheme query message.
964	964
965	965	Derivation:
966	966
967		-* //MessageType// (restriction)
968		-** TransformationSchemeQueryType
	942	+//MessageType// (restriction)
	943	+ TransformationSchemeQueryType
969	969
970	970	Content:
971	971
972		-* Header, Query
973		-* Element Documentation:
	947	+Header, Query
974	974
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" %)
	949	+Element Documentation:
979	979
	951	+|**Name**|**Type**|**Documentation**
	952	+|Header|BasicHeaderType|
	953	+|Query|qry: TransformationScheme QueryType|
	954	+
980	980	**VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a VTL mappings scheme query message.
981	981
982	982	Derivation:
983	983
984		-* //MessageType// (restriction)
985		-** VtlMappingSchemeQueryType
	959	+//MessageType// (restriction)
	960	+ VtlMappingSchemeQueryType
986	986
987	987	Content:
988	988
989		-* Header, Query
990		-* Element Documentation:
	964	+Header, Query
991	991
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" %)
	966	+Element Documentation:
996	996
	968	+|**Name**|**Type**|**Documentation**
	969	+|Header|BasicHeaderType|
	970	+|Query|qry: VtlMappingSchemeQuer yType|
	971	+
997	997	**NamePersonalisationSchemeQueryType: **NamePersonalisationSchemeQueryType defines the structure of a name personalisation scheme query message.
998	998
999	999	Derivation:
1000	1000
1001		-* //MessageType// (restriction)
1002		-** NamePersonalisationSchemeQueryType
	976	+//MessageType// (restriction)
	977	+ NamePersonalisationSchemeQueryType
1003	1003
1004	1004	Content:
1005	1005
1006		-* Header, Query
1007		-* Element Documentation:
	981	+Header, Query
1008	1008
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" %)
	983	+Element Documentation:
1013	1013
	985	+|**Name**|**Type**|**Documentation**
	986	+|Header|BasicHeaderType|
	987	+|Query|qry: NamePersonalisationS chemeQueryType|
	988	+
1014	1014	**RulesetSchemeQueryType: **RulesetSchemeQueryType defines the structure of a ruleset scheme query message.
1015	1015
1016	1016	Derivation:
1017	1017
1018		-* //MessageType// (restriction)
1019		-** RulesetSchemeQueryType
	993	+//MessageType// (restriction)
	994	+ RulesetSchemeQueryType
1020	1020
1021	1021	Content:
1022	1022
1023		-* Header, Query
1024		-* Element Documentation:
	998	+Header, Query
1025	1025
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" %)
	1000	+Element Documentation:
1030	1030
	1002	+|**Name**|**Type**|**Documentation**
	1003	+|Header|BasicHeaderType|
	1004	+|Query|qry: RulesetSchemeQueryTy pe|
	1005	+
1031	1031	**UserDefinedOperatorSchemeQueryType: **UserDefinedOperatorSchemeQueryType defines the structure of a user defined operator scheme query message.
1032	1032
1033	1033	Derivation:
1034	1034
1035		-* //MessageType// (restriction)
1036		-** UserDefinedOperatorSchemeQueryType
	1010	+//MessageType// (restriction)
	1011	+ UserDefinedOperatorSchemeQueryType
1037	1037
1038	1038	Content:
1039	1039
1040		-* Header, Query
1041		-* Element Documentation:
	1015	+Header, Query
1042	1042
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" %)
	1017	+Element Documentation:
1047	1047
	1019	+|**Name**|**Type**|**Documentation**
	1020	+|Header|BasicHeaderType|
	1021	+|Query|qry: UserDefinedOperatorS chemeQueryType|
	1022	+
1048	1048	**CustomTypeSchemeQueryType: **CustomTypeSchemeQueryType defines the structure of a custom type scheme query message.
1049	1049
1050	1050	Derivation:
1051	1051
1052		-* //MessageType// (restriction)
1053		-** CustomTypeSchemeQueryType
	1027	+//MessageType// (restriction)
	1028	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] CustomTypeSchemeQueryType
1054	1054
1055	1055	Content:
1056	1056
1057		-* Header, Query
1058		-* Element Documentation:
	1032	+Header, Query
1059	1059
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" %)
	1034	+Element Documentation:
1064	1064
	1036	+|**Name**|**Type**|**Documentation**
	1037	+|Header|BasicHeaderType|
	1038	+|Query|qry: CustomTypeSchemeQuer yType|
	1039	+
1065	1065	**ErrorType: **ErrorType describes the structure of an error response.
1066	1066
1067	1067	Content:
1068	1068
1069		-* ErrorMessage+
1070		-* Element Documentation:
	1044	+ErrorMessage+
1071	1071
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.
	1046	+Element Documentation:
1075	1075
	1048	+|**Name**|**Type**|**Documentation**
	1049	+|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.
	1050	+
1076	1076	**//BaseHeaderType//: **BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this
1077	1077
1078	1078	Content:
...	...	@@ -1081,30 +1081,29 @@
1081	1081
1082	1082	Element Documentation:
1083	1083
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.
	1059	+|**Name**|**Type**|**Documentation**
	1060	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1061	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1062	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1063	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1064	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1065	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1066	+|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.
	1067	+|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
	1068	+|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).
	1069	+|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
	1070	+|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
	1071	+|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1072	+|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1073	+|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
	1074	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1101	1101
1102	1102	**StructureHeaderType: **StructureHeaderType defines the structure for structural metadata messages.
1103	1103
1104	1104	Derivation:
1105	1105
1106		-* //BaseHeaderType// (restriction)
1107		-** StructureHeaderType
	1080	+//BaseHeaderType// (restriction)
	1081	+ StructureHeaderType
1108	1108
1109	1109	Content:
1110	1110
...	...	@@ -1112,22 +1112,21 @@
1112	1112
1113	1113	Element Documentation:
1114	1114
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	+|**Name**|**Type**|**Documentation**
	1090	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1091	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1092	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1093	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1094	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1095	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1096	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1124	1124
1125	1125	**GenericDataHeaderType: **GenericDataHeaderType defines the header structure for a generic data message.
1126	1126
1127	1127	Derivation:
1128	1128
1129		-* //BaseHeaderType// (restriction)
1130		-** GenericDataHeaderType
	1102	+//BaseHeaderType// (restriction)
	1103	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataHeaderType
1131	1131
1132	1132	Content:
1133	1133
...	...	@@ -1135,31 +1135,30 @@
1135	1135
1136	1136	Element Documentation:
1137	1137
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.
	1111	+|**Name**|**Type**|**Documentation**
	1112	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1113	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1114	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1115	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1116	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1117	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1118	+|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.
	1119	+|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
	1120	+|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).
	1121	+|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
	1122	+|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
	1123	+|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1124	+|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1125	+|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
	1126	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1155	1155
1156	1156	**GenericTimeSeriesDataHeaderType: **GenericTimeSeriesDataHeaderType defines the header structure for a time series only generic data message.
1157	1157
1158	1158	Derivation:
1159	1159
1160		-* //BaseHeaderType// (restriction)
1161		-** GenericDataHeaderType (restriction)
1162		-*** GenericTimeSeriesDataHeaderType
	1132	+//BaseHeaderType// (restriction)
	1133	+ GenericDataHeaderType (restriction)
	1134	+ GenericTimeSeriesDataHeaderType
1163	1163
1164	1164	Content:
1165	1165
...	...	@@ -1167,30 +1167,29 @@
1167	1167
1168	1168	Element Documentation:
1169	1169
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.
	1142	+|**Name**|**Type**|**Documentation**
	1143	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1144	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1145	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1146	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1147	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1148	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1149	+|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.
	1150	+|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
	1151	+|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).
	1152	+|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
	1153	+|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
	1154	+|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1155	+|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1156	+|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
	1157	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1187	1187
1188	1188	**StructureSpecificDataHeaderType: **StructureSpecificDataHeaderType defines the header structure for a structure specific data message.
1189	1189
1190	1190	Derivation:
1191	1191
1192		-* //BaseHeaderType// (restriction)
1193		-** StructureSpecificDataHeaderType
	1163	+//BaseHeaderType// (restriction)
	1164	+ StructureSpecificDataHeaderType
1194	1194
1195	1195	Content:
1196	1196
...	...	@@ -1198,31 +1198,30 @@
1198	1198
1199	1199	Element Documentation:
1200	1200
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.
	1172	+|**Name**|**Type**|**Documentation**
	1173	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1174	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1175	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1176	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1177	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1178	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1179	+|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.
	1180	+|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
	1181	+|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).
	1182	+|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
	1183	+|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
	1184	+|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1185	+|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1186	+|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
	1187	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1218	1218
1219	1219	**StructureSpecificTimeSeriesDataHeaderType: **StructureSpecificTimeSeriesDataHeaderType defines the header structure for a time series only structure specific data message.
1220	1220
1221	1221	Derivation:
1222	1222
1223		-* //BaseHeaderType// (restriction)
1224		-** StructureSpecificDataHeaderType (restriction)
1225		-*** StructureSpecificTimeSeriesDataHeaderType
	1193	+//BaseHeaderType// (restriction)
	1194	+ StructureSpecificDataHeaderType (restriction)
	1195	+ StructureSpecificTimeSeriesDataHeaderType
1226	1226
1227	1227	Content:
1228	1228
...	...	@@ -1230,30 +1230,29 @@
1230	1230
1231	1231	Element Documentation:
1232	1232
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.
	1203	+|**Name**|**Type**|**Documentation**
	1204	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1205	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1206	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1207	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1208	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1209	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1210	+|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.
	1211	+|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
	1212	+|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).
	1213	+|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
	1214	+|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
	1215	+|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1216	+|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1217	+|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
	1218	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1250	1250
1251	1251	**GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic reference metadata.
1252	1252
1253	1253	Derivation:
1254	1254
1255		-* //BaseHeaderType// (restriction)
1256		-** GenericMetadataHeaderType
	1224	+//BaseHeaderType// (restriction)
	1225	+ GenericMetadataHeaderType
1257	1257
1258	1258	Content:
1259	1259
...	...	@@ -1261,27 +1261,26 @@
1261	1261
1262	1262	Element Documentation:
1263	1263
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.
	1233	+|**Name**|**Type**|**Documentation**
	1234	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1235	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1236	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1237	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1238	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1239	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1240	+|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.
	1241	+|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
	1242	+|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).
	1243	+|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
	1244	+|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
	1245	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1278	1278
1279	1279	**StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for metadata structure definition specific reference metadata messages.
1280	1280
1281	1281	Derivation:
1282	1282
1283		-* //BaseHeaderType// (restriction)
1284		-** StructureSpecificMetadataHeaderType
	1251	+//BaseHeaderType// (restriction)
	1252	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType
1285	1285
1286	1286	Content:
1287	1287
...	...	@@ -1289,27 +1289,26 @@
1289	1289
1290	1290	Element Documentation:
1291	1291
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.
	1260	+|**Name**|**Type**|**Documentation**
	1261	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1262	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1263	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1264	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1265	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1266	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1267	+|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.
	1268	+|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
	1269	+|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).
	1270	+|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
	1271	+|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
	1272	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1306	1306
1307	1307	**BasicHeaderType: **BasicHeaderType defines the most basic header information used in simple message exchanges.
1308	1308
1309	1309	Derivation:
1310	1310
1311		-* //BaseHeaderType// (restriction)
1312		-** BasicHeaderType
	1278	+//BaseHeaderType// (restriction)
	1279	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType
1313	1313
1314	1314	Content:
1315	1315
...	...	@@ -1317,13 +1317,12 @@
1317	1317
1318	1318	Element Documentation:
1319	1319
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.
	1287	+|**Name**|**Type**|**Documentation**
	1288	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1289	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1290	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1291	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1292	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1327	1327
1328	1328	**PartyType: **PartyType defines the information which is sent about various parties such as senders and receivers of messages.
1329	1329
...	...	@@ -1337,23 +1337,21 @@
1337	1337
1338	1338	Attribute Documentation:
1339	1339
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.
	1306	+|**Name**|**Type**|**Documentation**
	1307	+|id|com:IDType|The id attribute holds the identification of the party.
1343	1343
1344	1344	Element Documentation:
1345	1345
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.
	1311	+|**Name**|**Type**|**Documentation**
	1312	+|com:Name|com:TextType|Name is a human-readable name of the party.
	1313	+|Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message.
1350	1350
1351	1351	**SenderType: **SenderType extends the basic party structure to add an optional time zone declaration.
1352	1352
1353	1353	Derivation:
1354	1354
1355		-* PartyType (extension)
1356		-** SenderType
	1319	+PartyType (extension)
	1320	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType
1357	1357
1358	1358	Attributes:
1359	1359
...	...	@@ -1365,9 +1365,8 @@
1365	1365
1366	1366	Attribute Documentation:
1367	1367
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.
	1332	+|**Name**|**Type**|**Documentation**
	1333	+|id|com:IDType|The id attribute holds the identification of the party.
1371	1371
1372	1372	Element Documentation:
1373	1373
...	...	@@ -1394,8 +1394,8 @@
1394	1394	|URI|xs:anyURI|URI holds an information URL for the contact person.
1395	1395	|Email|xs:string|Email holds the email address for the contact person.
1396	1396
1397		-1.
1398		-11.
	1360	+1.
	1361	+11.
1399	1399	111. Simple Types
1400	1400
1401	1401	**HeaderTimeType: **Provides a union type of xs:date and xs:dateTime for the header fields in the message.
...	...	@@ -1404,13 +1404,13 @@
1404	1404
1405	1405	xs:dateTime, xs:date.
1406	1406
1407		-1.
	1370	+1.
1408	1408	11. Message Footer Namespace
1409	1409
1410	1410	**http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer**
1411	1411
1412		-1.
1413		-11.
	1375	+1.
	1376	+11.
1414	1414	111. Summary
1415	1415
1416	1416	Referenced Namespaces:
...	...	@@ -1425,14 +1425,14 @@
1425	1425	2 Complex Types
1426	1426	1 Simple Type
1427	1427
1428		-1.
1429		-11.
	1391	+1.
	1392	+11.
1430	1430	111. Global Elements
1431	1431
1432	1432	**Footer (FooterType): **Footer is used to communicate information such as error and warnings after the payload of a message.
1433	1433
1434		-1.
1435		-11.
	1397	+1.
	1398	+11.
1436	1436	111. Complex Types
1437	1437
1438	1438	**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.
...	...	@@ -1451,8 +1451,8 @@
1451	1451	Derivation:
1452	1452
1453	1453	com:StatusMessageType (restriction)
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
	1417	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension)
	1418	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType
1456	1456
1457	1457	Attributes:
1458	1458
...	...	@@ -1473,8 +1473,8 @@
1473	1473	|**Name**|**Type**|**Documentation**
1474	1474	|com:Text|com:TextType|Text contains the text of the message, in parallel language values.
1475	1475
1476		-1.
1477		-11.
	1439	+1.
	1440	+11.
1478	1478	111. Simple Types
1479	1479
1480	1480	**SeverityCodeType:**