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
...	...	@@ -347,10 +347,9 @@
347	347
348	348	Content:
349	349
350		-Header, SubmitRegistrationsRequest
	350	+* Header, SubmitRegistrationsRequest
	351	+* Element Documentation:
351	351
352		-Element Documentation:
353		-
354	354	(% style="width:844.294px" %)
355	355	|**Name**|**Type**|(% style="width:377px" %)**Documentation**
356	356	|Header|BasicHeaderType|(% style="width:377px" %)
...	...	@@ -366,23 +366,21 @@
366	366
367	367	Content:
368	368
369		-Header, SubmitRegistrationsResponse, ftr:Footer?
	368	+* Header, SubmitRegistrationsResponse, ftr:Footer?
	369	+* Element Documentation:
370	370
371		-Element Documentation:
	371	+|**Name**|**Type**|**Documentation**
	372	+|Header|BasicHeaderType|
	373	+|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.
	374	+|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
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.
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
	380	+//MessageType// (restriction)
	381	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	382	+ [[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.
	390	+|**Name**|**Type**|**Documentation**
	391	+|Header|BasicHeaderType|
	392	+|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
	398	+//MessageType// (restriction)
	399	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	400	+ [[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.
	408	+|**Name**|**Type**|**Documentation**
	409	+|Header|BasicHeaderType|
	410	+|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.
	411	+|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
	417	+//MessageType// (restriction)
	418	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	419	+ [[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.
	427	+|**Name**|**Type**|**Documentation**
	428	+|Header|BasicHeaderType|
	429	+|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
	435	+//MessageType// (restriction)
	436	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	437	+ [[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.
	445	+|**Name**|**Type**|**Documentation**
	446	+|Header|BasicHeaderType|
	447	+|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.
	448	+|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
	454	+//MessageType// (restriction)
	455	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	456	+ [[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.
	464	+|**Name**|**Type**|**Documentation**
	465	+|Header|BasicHeaderType|
	466	+|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
	472	+//MessageType// (restriction)
	473	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	474	+ [[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.
	482	+|**Name**|**Type**|**Documentation**
	483	+|Header|BasicHeaderType|
	484	+|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.
	485	+|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
	491	+//MessageType// (restriction)
	492	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	493	+ [[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.
	501	+|**Name**|**Type**|**Documentation**
	502	+|Header|BasicHeaderType|
	503	+|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
	509	+//MessageType// (restriction)
	510	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
	511	+ [[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.
	519	+|**Name**|**Type**|**Documentation**
	520	+|Header|BasicHeaderType|
	521	+|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.
	522	+|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
	528	+//MessageType// (restriction)
	529	+ RegistryInterfaceType (restriction)
	530	+ 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.
	538	+|**Name**|**Type**|**Documentation**
	539	+|Header|BasicHeaderType|
	540	+|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
	546	+//MessageType// (restriction)
	547	+ 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" %)
	555	+|**Name**|**Type**|**Documentation**
	556	+|Header|BasicHeaderType|
	557	+|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
	563	+//MessageType// (restriction)
	564	+ DataQueryType (restriction)
	565	+ 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" %)
	573	+|**Name**|**Type**|**Documentation**
	574	+|Header|BasicHeaderType|
	575	+|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
	581	+//MessageType// (restriction)
	582	+ DataQueryType (restriction)
	583	+ GenericDataQueryType (restriction)
	584	+ 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" %)
	592	+|**Name**|**Type**|**Documentation**
	593	+|Header|BasicHeaderType|
	594	+|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
	600	+//MessageType// (restriction)
	601	+ DataQueryType (restriction)
	602	+ 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" %)
	610	+|**Name**|**Type**|**Documentation**
	611	+|Header|BasicHeaderType|
	612	+|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
	618	+//MessageType// (restriction)
	619	+ 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" %)
	627	+|**Name**|**Type**|**Documentation**
	628	+|Header|BasicHeaderType|
	629	+|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
	635	+//MessageType// (restriction)
	636	+ 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" %)
	644	+|**Name**|**Type**|**Documentation**
	645	+|Header|BasicHeaderType|
	646	+|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
	652	+//MessageType// (restriction)
	653	+ 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" %)
	661	+|**Name**|**Type**|**Documentation**
	662	+|Header|BasicHeaderType|
	663	+|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
	669	+//MessageType// (restriction)
	670	+ 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" %)
	678	+|**Name**|**Type**|**Documentation**
	679	+|Header|BasicHeaderType|
	680	+|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
	686	+//MessageType// (restriction)
	687	+ 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" %)
	695	+|**Name**|**Type**|**Documentation**
	696	+|Header|BasicHeaderType|
	697	+|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
	703	+//MessageType// (restriction)
	704	+ 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" %)
	712	+|**Name**|**Type**|**Documentation**
	713	+|Header|BasicHeaderType|
	714	+|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
	720	+//MessageType// (restriction)
	721	+ 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" %)
	729	+|**Name**|**Type**|**Documentation**
	730	+|Header|BasicHeaderType|
	731	+|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
	737	+//MessageType// (restriction)
	738	+ 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" %)
	746	+|**Name**|**Type**|**Documentation**
	747	+|Header|BasicHeaderType|
	748	+|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
	754	+//MessageType// (restriction)
	755	+ 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" %)
	763	+|**Name**|**Type**|**Documentation**
	764	+|Header|BasicHeaderType|
	765	+|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
	771	+//MessageType// (restriction)
	772	+ ConceptSchemeQueryType
798	798
799	799	Content:
800	800
...	...	@@ -802,17 +802,16 @@
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" %)
	780	+|**Name**|**Type**|**Documentation**
	781	+|Header|BasicHeaderType|
	782	+|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
	788	+//MessageType// (restriction)
	789	+ CodelistQueryType
816	816
817	817	Content:
818	818
...	...	@@ -820,17 +820,16 @@
820	820
821	821	Element Documentation:
822	822
823		-(% style="width:911.294px" %)
824		-|(% style="width:204px" %)**Name**|(% style="width:295px" %)**Type**|(% style="width:409px" %)**Documentation**
825		-|(% style="width:204px" %)Header|(% style="width:295px" %)BasicHeaderType|(% style="width:409px" %)
826		-|(% style="width:204px" %)Query|(% style="width:295px" %)qry:CodelistQueryType|(% style="width:409px" %)
	797	+|**Name**|**Type**|**Documentation**
	798	+|Header|BasicHeaderType|
	799	+|Query|qry: CodelistQueryType|
827	827
828	828	**HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical codelist query message.
829	829
830	830	Derivation:
831	831
832		-* //MessageType// (restriction)
833		-** HierarchicalCodelistQueryType
	805	+//MessageType// (restriction)
	806	+ HierarchicalCodelistQueryType
834	834
835	835	Content:
836	836
...	...	@@ -838,17 +838,16 @@
838	838
839	839	Element Documentation:
840	840
841		-(% style="width:906.294px" %)
842		-|(% style="width:191px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:430px" %)**Documentation**
843		-|(% style="width:191px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:430px" %)
844		-|(% style="width:191px" %)Query|(% style="width:281px" %)qry: HierarchicalCodelist QueryType|(% style="width:430px" %)
	814	+|**Name**|**Type**|**Documentation**
	815	+|Header|BasicHeaderType|
	816	+|Query|qry: HierarchicalCodelist QueryType|
845	845
846	846	**OrganisationSchemeQueryType: **OrganisationSchemeQueryType defines the structure of an organisation scheme query message.
847	847
848	848	Derivation:
849	849
850		-* //MessageType// (restriction)
851		-** OrganisationSchemeQueryType
	822	+//MessageType// (restriction)
	823	+ OrganisationSchemeQueryType
852	852
853	853	Content:
854	854
...	...	@@ -856,17 +856,16 @@
856	856
857	857	Element Documentation:
858	858
859		-(% style="width:891.294px" %)
860		-|(% style="width:174px" %)**Name**|(% style="width:292px" %)**Type**|(% style="width:422px" %)**Documentation**
861		-|(% style="width:174px" %)Header|(% style="width:292px" %)BasicHeaderType|(% style="width:422px" %)
862		-|(% style="width:174px" %)Query|(% style="width:292px" %)qry: OrganisationSchemeQueryType|(% style="width:422px" %)
	831	+|**Name**|**Type**|**Documentation**
	832	+|Header|BasicHeaderType|
	833	+|Query|qry: OrganisationSchemeQu eryType|
863	863
864	864	**ReportingTaxonomyQueryType: **ReportingTaxonomyQueryType defines the structure of a reporting taxonomy query message.
865	865
866	866	Derivation:
867	867
868		-* //MessageType// (restriction)
869		-** ReportingTaxonomyQueryType
	839	+//MessageType// (restriction)
	840	+ ReportingTaxonomyQueryType
870	870
871	871	Content:
872	872
...	...	@@ -874,17 +874,16 @@
874	874
875	875	Element Documentation:
876	876
877		-(% style="width:916.294px" %)
878		-|(% style="width:162px" %)**Name**|(% style="width:318px" %)**Type**|(% style="width:434px" %)**Documentation**
879		-|(% style="width:162px" %)Header|(% style="width:318px" %)BasicHeaderType|(% style="width:434px" %)
880		-|(% style="width:162px" %)Query|(% style="width:318px" %)qry: ReportingTaxonomyQueryType|(% style="width:434px" %)
	848	+|**Name**|**Type**|**Documentation**
	849	+|Header|BasicHeaderType|
	850	+|Query|qry: ReportingTaxonomyQue ryType|
881	881
882	882	**StructureSetQueryType: **StructureSetQueryType defines the structure of a structure set query message.
883	883
884	884	Derivation:
885	885
886		-* //MessageType// (restriction)
887		-** StructureSetQueryType
	856	+//MessageType// (restriction)
	857	+ StructureSetQueryType
888	888
889	889	Content:
890	890
...	...	@@ -892,17 +892,16 @@
892	892
893	893	Element Documentation:
894	894
895		-(% style="width:896.294px" %)
896		-|(% style="width:182px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:417px" %)**Documentation**
897		-|(% style="width:182px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:417px" %)
898		-|(% style="width:182px" %)Query|(% style="width:294px" %)qry: StructureSetQueryType|(% style="width:417px" %)
	865	+|**Name**|**Type**|**Documentation**
	866	+|Header|BasicHeaderType|
	867	+|Query|qry: StructureSetQueryTyp e|
899	899
900	900	**ProcessQueryType: **CategorizationQueryType defines the structure of a categorization query message.
901	901
902	902	Derivation:
903	903
904		-* //MessageType// (restriction)
905		-** ProcessQueryType
	873	+//MessageType// (restriction)
	874	+ ProcessQueryType
906	906
907	907	Content:
908	908
...	...	@@ -910,17 +910,16 @@
910	910
911	911	Element Documentation:
912	912
913		-(% style="width:907.294px" %)
914		-|(% style="width:189px" %)**Name**|(% style="width:394px" %)**Type**|(% style="width:321px" %)**Documentation**
915		-|(% style="width:189px" %)Header|(% style="width:394px" %)BasicHeaderType|(% style="width:321px" %)
916		-|(% style="width:189px" %)Query|(% style="width:394px" %)qry:ProcessQueryType|(% style="width:321px" %)
	882	+|**Name**|**Type**|**Documentation**
	883	+|Header|BasicHeaderType|
	884	+|Query|qry:ProcessQueryType|
917	917
918	918	**CategorisationQueryType: **CategorisationQueryType defines the structure of a categorisation query message.
919	919
920	920	Derivation:
921	921
922		-* //MessageType// (restriction)
923		-** CategorisationQueryType
	890	+//MessageType// (restriction)
	891	+ CategorisationQueryType
924	924
925	925	Content:
926	926
...	...	@@ -928,17 +928,16 @@
928	928
929	929	Element Documentation:
930	930
931		-(% style="width:897.294px" %)
932		-|(% style="width:230px" %)**Name**|(% style="width:300px" %)**Type**|(% style="width:363px" %)**Documentation**
933		-|(% style="width:230px" %)Header|(% style="width:300px" %)BasicHeaderType|(% style="width:363px" %)
934		-|(% style="width:230px" %)Query|(% style="width:300px" %)qry: CategorisationQueryType|(% style="width:363px" %)
	899	+|**Name**|**Type**|**Documentation**
	900	+|Header|BasicHeaderType|
	901	+|Query|qry: CategorisationQueryT ype|
935	935
936	936	**ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a provision agreement query message.
937	937
938	938	Derivation:
939	939
940		-* //MessageType// (restriction)
941		-** ProvisionAgreementQueryType
	907	+//MessageType// (restriction)
	908	+ ProvisionAgreementQueryType
942	942
943	943	Content:
944	944
...	...	@@ -946,17 +946,16 @@
946	946
947	947	Element Documentation:
948	948
949		-(% style="width:902.294px" %)
950		-|(% style="width:142px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:418px" %)**Documentation**
951		-|(% style="width:142px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:418px" %)
952		-|(% style="width:142px" %)Query|(% style="width:339px" %)qry: ProvisionAgreementQueryType|(% style="width:418px" %)
	916	+|**Name**|**Type**|**Documentation**
	917	+|Header|BasicHeaderType|
	918	+|Query|qry: ProvisionAgreementQu eryType|
953	953
954	954	**ConstraintQueryType: **ConstraintQueryType defines the structure of a constraint query message.
955	955
956	956	Derivation:
957	957
958		-* //MessageType// (restriction)
959		-** ConstraintQueryType
	924	+//MessageType// (restriction)
	925	+ ConstraintQueryType
960	960
961	961	Content:
962	962
...	...	@@ -964,17 +964,16 @@
964	964
965	965	Element Documentation:
966	966
967		-(% style="width:902.294px" %)
968		-|(% style="width:167px" %)**Name**|(% style="width:287px" %)**Type**|(% style="width:445px" %)**Documentation**
969		-|(% style="width:167px" %)Header|(% style="width:287px" %)BasicHeaderType|(% style="width:445px" %)
970		-|(% style="width:167px" %)Query|(% style="width:287px" %)qry: ConstraintQueryType|(% style="width:445px" %)
	933	+|**Name**|**Type**|**Documentation**
	934	+|Header|BasicHeaderType|
	935	+|Query|qry: ConstraintQueryType|
971	971
972	972	**TransformationSchemeQueryType: **TransformationSchemeQueryType defines the structure of a transformation scheme query message.
973	973
974	974	Derivation:
975	975
976		-* //MessageType// (restriction)
977		-** TransformationSchemeQueryType
	941	+//MessageType// (restriction)
	942	+ TransformationSchemeQueryType
978	978
979	979	Content:
980	980
...	...	@@ -982,17 +982,16 @@
982	982
983	983	Element Documentation:
984	984
985		-(% style="width:833.294px" %)
986		-|(% style="width:165px" %)**Name**|(% style="width:325px" %)**Type**|(% style="width:340px" %)**Documentation**
987		-|(% style="width:165px" %)Header|(% style="width:325px" %)BasicHeaderType|(% style="width:340px" %)
988		-|(% style="width:165px" %)Query|(% style="width:325px" %)qry: TransformationSchemeQueryType|(% style="width:340px" %)
	950	+|**Name**|**Type**|**Documentation**
	951	+|Header|BasicHeaderType|
	952	+|Query|qry: TransformationScheme QueryType|
989	989
990	990	**VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a VTL mappings scheme query message.
991	991
992	992	Derivation:
993	993
994		-* //MessageType// (restriction)
995		-** VtlMappingSchemeQueryType
	958	+//MessageType// (restriction)
	959	+ VtlMappingSchemeQueryType
996	996
997	997	Content:
998	998
...	...	@@ -1000,17 +1000,16 @@
1000	1000
1001	1001	Element Documentation:
1002	1002
1003		-(% style="width:843.294px" %)
1004		-|(% style="width:164px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:373px" %)**Documentation**
1005		-|(% style="width:164px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:373px" %)
1006		-|(% style="width:164px" %)Query|(% style="width:303px" %)qry: VtlMappingSchemeQueryType|(% style="width:373px" %)
	967	+|**Name**|**Type**|**Documentation**
	968	+|Header|BasicHeaderType|
	969	+|Query|qry: VtlMappingSchemeQuer yType|
1007	1007
1008	1008	**NamePersonalisationSchemeQueryType: **NamePersonalisationSchemeQueryType defines the structure of a name personalisation scheme query message.
1009	1009
1010	1010	Derivation:
1011	1011
1012		-* //MessageType// (restriction)
1013		-** NamePersonalisationSchemeQueryType
	975	+//MessageType// (restriction)
	976	+ NamePersonalisationSchemeQueryType
1014	1014
1015	1015	Content:
1016	1016
...	...	@@ -1018,17 +1018,16 @@
1018	1018
1019	1019	Element Documentation:
1020	1020
1021		-(% style="width:895.294px" %)
1022		-|(% style="width:186px" %)**Name**|(% style="width:363px" %)**Type**|(% style="width:343px" %)**Documentation**
1023		-|(% style="width:186px" %)Header|(% style="width:363px" %)BasicHeaderType|(% style="width:343px" %)
1024		-|(% style="width:186px" %)Query|(% style="width:363px" %)qry: NamePersonalisationSchemeQueryType|(% style="width:343px" %)
	984	+|**Name**|**Type**|**Documentation**
	985	+|Header|BasicHeaderType|
	986	+|Query|qry: NamePersonalisationS chemeQueryType|
1025	1025
1026	1026	**RulesetSchemeQueryType: **RulesetSchemeQueryType defines the structure of a ruleset scheme query message.
1027	1027
1028	1028	Derivation:
1029	1029
1030		-* //MessageType// (restriction)
1031		-** RulesetSchemeQueryType
	992	+//MessageType// (restriction)
	993	+ RulesetSchemeQueryType
1032	1032
1033	1033	Content:
1034	1034
...	...	@@ -1036,17 +1036,16 @@
1036	1036
1037	1037	Element Documentation:
1038	1038
1039		-(% style="width:886.294px" %)
1040		-|(% style="width:152px" %)**Name**|(% style="width:311px" %)**Type**|(% style="width:420px" %)**Documentation**
1041		-|(% style="width:152px" %)Header|(% style="width:311px" %)BasicHeaderType|(% style="width:420px" %)
1042		-|(% style="width:152px" %)Query|(% style="width:311px" %)qry: RulesetSchemeQueryType|(% style="width:420px" %)
	1001	+|**Name**|**Type**|**Documentation**
	1002	+|Header|BasicHeaderType|
	1003	+|Query|qry: RulesetSchemeQueryTy pe|
1043	1043
1044	1044	**UserDefinedOperatorSchemeQueryType: **UserDefinedOperatorSchemeQueryType defines the structure of a user defined operator scheme query message.
1045	1045
1046	1046	Derivation:
1047	1047
1048		-* //MessageType// (restriction)
1049		-** UserDefinedOperatorSchemeQueryType
	1009	+//MessageType// (restriction)
	1010	+ UserDefinedOperatorSchemeQueryType
1050	1050
1051	1051	Content:
1052	1052
...	...	@@ -1054,17 +1054,16 @@
1054	1054
1055	1055	Element Documentation:
1056	1056
1057		-(% style="width:866.294px" %)
1058		-|(% style="width:174px" %)**Name**|(% style="width:358px" %)**Type**|(% style="width:331px" %)**Documentation**
1059		-|(% style="width:174px" %)Header|(% style="width:358px" %)BasicHeaderType|(% style="width:331px" %)
1060		-|(% style="width:174px" %)Query|(% style="width:358px" %)qry: UserDefinedOperatorSchemeQueryType|(% style="width:331px" %)
	1018	+|**Name**|**Type**|**Documentation**
	1019	+|Header|BasicHeaderType|
	1020	+|Query|qry: UserDefinedOperatorS chemeQueryType|
1061	1061
1062	1062	**CustomTypeSchemeQueryType: **CustomTypeSchemeQueryType defines the structure of a custom type scheme query message.
1063	1063
1064	1064	Derivation:
1065	1065
1066		-* //MessageType// (restriction)
1067		-** CustomTypeSchemeQueryType
	1026	+//MessageType// (restriction)
	1027	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] CustomTypeSchemeQueryType
1068	1068
1069	1069	Content:
1070	1070
...	...	@@ -1072,10 +1072,9 @@
1072	1072
1073	1073	Element Documentation:
1074	1074
1075		-(% style="width:828.294px" %)
1076		-|(% style="width:200px" %)**Name**|(% style="width:308px" %)**Type**|(% style="width:317px" %)**Documentation**
1077		-|(% style="width:200px" %)Header|(% style="width:308px" %)BasicHeaderType|(% style="width:317px" %)
1078		-|(% style="width:200px" %)Query|(% style="width:308px" %)qry: CustomTypeSchemeQueryType|(% style="width:317px" %)
	1035	+|**Name**|**Type**|**Documentation**
	1036	+|Header|BasicHeaderType|
	1037	+|Query|qry: CustomTypeSchemeQuer yType|
1079	1079
1080	1080	**ErrorType: **ErrorType describes the structure of an error response.
1081	1081
...	...	@@ -1085,9 +1085,8 @@
1085	1085
1086	1086	Element Documentation:
1087	1087
1088		-(% style="width:899.294px" %)
1089		-|**Name**|**Type**|(% style="width:546px" %)**Documentation**
1090		-|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.
	1047	+|**Name**|**Type**|**Documentation**
	1048	+|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.
1091	1091
1092	1092	**//BaseHeaderType//: **BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this
1093	1093
...	...	@@ -1097,30 +1097,29 @@
1097	1097
1098	1098	Element Documentation:
1099	1099
1100		-(% style="width:891.294px" %)
1101		-|**Name**|**Type**|(% style="width:552px" %)**Documentation**
1102		-|ID|com:IDType|(% style="width:552px" %)ID identifies an identification for the message, assigned by the sender.
1103		-|Test|xs:boolean|(% style="width:552px" %)Test indicates whether the message is for test purposes or not.
1104		-|Prepared|HeaderTimeType|(% style="width:552px" %)Prepared is the date the message was prepared.
1105		-|Sender|SenderType|(% style="width:552px" %)Sender is information about the party that is transmitting the message.
1106		-|Receiver|PartyType|(% style="width:552px" %)Receiver is information about the party that is the intended recipient of the message.
1107		-|com:Name|com:TextType|(% style="width:552px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1108		-|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.
1109		-|DataProvider|com: DataProviderReferenceType|(% style="width:552px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1110		-|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).
1111		-|DataSetID|com:IDType|(% style="width:552px" %)DataSetID provides an identifier for a contained data set.
1112		-|Extracted|xs:dateTime|(% style="width:552px" %)Extracted is a time-stamp from the system rendering the data.
1113		-|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1114		-|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1115		-|EmbargoDate|xs:dateTime|(% style="width:552px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1116		-|Source|com:TextType|(% style="width:552px" %)Source provides human-readable information about the source of the data.
	1058	+|**Name**|**Type**|**Documentation**
	1059	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1060	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1061	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1062	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1063	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1064	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1065	+|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.
	1066	+|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
	1067	+|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).
	1068	+|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
	1069	+|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
	1070	+|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1071	+|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1072	+|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
	1073	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1117	1117
1118	1118	**StructureHeaderType: **StructureHeaderType defines the structure for structural metadata messages.
1119	1119
1120	1120	Derivation:
1121	1121
1122		-* //BaseHeaderType// (restriction)
1123		-** StructureHeaderType
	1079	+//BaseHeaderType// (restriction)
	1080	+ StructureHeaderType
1124	1124
1125	1125	Content:
1126	1126
...	...	@@ -1128,22 +1128,21 @@
1128	1128
1129	1129	Element Documentation:
1130	1130
1131		-(% style="width:1099.29px" %)
1132		-|**Name**|(% style="width:224px" %)**Type**|(% style="width:663px" %)**Documentation**
1133		-|ID|(% style="width:224px" %)com:IDType|(% style="width:663px" %)ID identifies an identification for the message, assigned by the sender.
1134		-|Test|(% style="width:224px" %)xs:boolean|(% style="width:663px" %)Test indicates whether the message is for test purposes or not.
1135		-|Prepared|(% style="width:224px" %)HeaderTimeType|(% style="width:663px" %)Prepared is the date the message was prepared.
1136		-|Sender|(% style="width:224px" %)SenderType|(% style="width:663px" %)Sender is information about the party that is transmitting the message.
1137		-|Receiver|(% style="width:224px" %)PartyType|(% style="width:663px" %)Receiver is information about the party that is the intended recipient of the message.
1138		-|com:Name|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1139		-|Source|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Source provides human-readable information about the source of the data.
	1088	+|**Name**|**Type**|**Documentation**
	1089	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1090	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1091	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1092	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1093	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1094	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1095	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1140	1140
1141	1141	**GenericDataHeaderType: **GenericDataHeaderType defines the header structure for a generic data message.
1142	1142
1143	1143	Derivation:
1144	1144
1145		-* //BaseHeaderType// (restriction)
1146		-** GenericDataHeaderType
	1101	+//BaseHeaderType// (restriction)
	1102	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataHeaderType
1147	1147
1148	1148	Content:
1149	1149
...	...	@@ -1151,31 +1151,30 @@
1151	1151
1152	1152	Element Documentation:
1153	1153
1154		-(% style="width:895.294px" %)
1155		-|**Name**|**Type**|(% style="width:556px" %)**Documentation**
1156		-|ID|com:IDType|(% style="width:556px" %)ID identifies an identification for the message, assigned by the sender.
1157		-|Test|xs:boolean|(% style="width:556px" %)Test indicates whether the message is for test purposes or not.
1158		-|Prepared|HeaderTimeType|(% style="width:556px" %)Prepared is the date the message was prepared.
1159		-|Sender|SenderType|(% style="width:556px" %)Sender is information about the party that is transmitting the message.
1160		-|Receiver|PartyType|(% style="width:556px" %)Receiver is information about the party that is the intended recipient of the message.
1161		-|com:Name|com:TextType|(% style="width:556px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1162		-|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.
1163		-|DataProvider|com: DataProviderReferenceType|(% style="width:556px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1164		-|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).
1165		-|DataSetID|com:IDType|(% style="width:556px" %)DataSetID provides an identifier for a contained data set.
1166		-|Extracted|xs:dateTime|(% style="width:556px" %)Extracted is a time-stamp from the system rendering the data.
1167		-|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1168		-|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1169		-|EmbargoDate|xs:dateTime|(% style="width:556px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1170		-|Source|com:TextType|(% style="width:556px" %)Source provides human-readable information about the source of the data.
	1110	+|**Name**|**Type**|**Documentation**
	1111	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1112	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1113	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1114	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1115	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1116	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1117	+|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.
	1118	+|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
	1119	+|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).
	1120	+|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
	1121	+|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
	1122	+|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1123	+|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1124	+|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
	1125	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1171	1171
1172	1172	**GenericTimeSeriesDataHeaderType: **GenericTimeSeriesDataHeaderType defines the header structure for a time series only generic data message.
1173	1173
1174	1174	Derivation:
1175	1175
1176		-* //BaseHeaderType// (restriction)
1177		-** GenericDataHeaderType (restriction)
1178		-*** GenericTimeSeriesDataHeaderType
	1131	+//BaseHeaderType// (restriction)
	1132	+ GenericDataHeaderType (restriction)
	1133	+ GenericTimeSeriesDataHeaderType
1179	1179
1180	1180	Content:
1181	1181
...	...	@@ -1183,30 +1183,29 @@
1183	1183
1184	1184	Element Documentation:
1185	1185
1186		-(% style="width:926.294px" %)
1187		-|**Name**|**Type**|(% style="width:497px" %)**Documentation**
1188		-|ID|com:IDType|(% style="width:497px" %)ID identifies an identification for the message, assigned by the sender.
1189		-|Test|xs:boolean|(% style="width:497px" %)Test indicates whether the message is for test purposes or not.
1190		-|Prepared|HeaderTimeType|(% style="width:497px" %)Prepared is the date the message was prepared.
1191		-|Sender|SenderType|(% style="width:497px" %)Sender is information about the party that is transmitting the message.
1192		-|Receiver|PartyType|(% style="width:497px" %)Receiver is information about the party that is the intended recipient of the message.
1193		-|com:Name|com:TextType|(% style="width:497px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1194		-|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.
1195		-|DataProvider|com: DataProviderReferenceType|(% style="width:497px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1196		-|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).
1197		-|DataSetID|com:IDType|(% style="width:497px" %)DataSetID provides an identifier for a contained data set.
1198		-|Extracted|xs:dateTime|(% style="width:497px" %)Extracted is a time-stamp from the system rendering the data.
1199		-|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1200		-|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1201		-|EmbargoDate|xs:dateTime|(% style="width:497px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1202		-|Source|com:TextType|(% style="width:497px" %)Source provides human-readable information about the source of the data.
	1141	+|**Name**|**Type**|**Documentation**
	1142	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1143	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1144	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1145	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1146	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1147	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1148	+|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.
	1149	+|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
	1150	+|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).
	1151	+|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
	1152	+|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
	1153	+|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1154	+|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1155	+|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
	1156	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1203	1203
1204	1204	**StructureSpecificDataHeaderType: **StructureSpecificDataHeaderType defines the header structure for a structure specific data message.
1205	1205
1206	1206	Derivation:
1207	1207
1208		-* //BaseHeaderType// (restriction)
1209		-** StructureSpecificDataHeaderType
	1162	+//BaseHeaderType// (restriction)
	1163	+ StructureSpecificDataHeaderType
1210	1210
1211	1211	Content:
1212	1212
...	...	@@ -1214,31 +1214,30 @@
1214	1214
1215	1215	Element Documentation:
1216	1216
1217		-(% style="width:930.294px" %)
1218		-|**Name**|**Type**|(% style="width:578px" %)**Documentation**
1219		-|ID|com:IDType|(% style="width:578px" %)ID identifies an identification for the message, assigned by the sender.
1220		-|Test|xs:boolean|(% style="width:578px" %)Test indicates whether the message is for test purposes or not.
1221		-|Prepared|HeaderTimeType|(% style="width:578px" %)Prepared is the date the message was prepared.
1222		-|Sender|SenderType|(% style="width:578px" %)Sender is information about the party that is transmitting the message.
1223		-|Receiver|PartyType|(% style="width:578px" %)Receiver is information about the party that is the intended recipient of the message.
1224		-|com:Name|com:TextType|(% style="width:578px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1225		-|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.
1226		-|DataProvider|com: DataProviderReferenceType|(% style="width:578px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1227		-|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).
1228		-|DataSetID|com:IDType|(% style="width:578px" %)DataSetID provides an identifier for a contained data set.
1229		-|Extracted|xs:dateTime|(% style="width:578px" %)Extracted is a time-stamp from the system rendering the data.
1230		-|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1231		-|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1232		-|EmbargoDate|xs:dateTime|(% style="width:578px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1233		-|Source|com:TextType|(% style="width:578px" %)Source provides human-readable information about the source of the data.
	1171	+|**Name**|**Type**|**Documentation**
	1172	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1173	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1174	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1175	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1176	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1177	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1178	+|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.
	1179	+|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
	1180	+|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).
	1181	+|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
	1182	+|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
	1183	+|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1184	+|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1185	+|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
	1186	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1234	1234
1235	1235	**StructureSpecificTimeSeriesDataHeaderType: **StructureSpecificTimeSeriesDataHeaderType defines the header structure for a time series only structure specific data message.
1236	1236
1237	1237	Derivation:
1238	1238
1239		-* //BaseHeaderType// (restriction)
1240		-** StructureSpecificDataHeaderType (restriction)
1241		-*** StructureSpecificTimeSeriesDataHeaderType
	1192	+//BaseHeaderType// (restriction)
	1193	+ StructureSpecificDataHeaderType (restriction)
	1194	+ StructureSpecificTimeSeriesDataHeaderType
1242	1242
1243	1243	Content:
1244	1244
...	...	@@ -1246,30 +1246,29 @@
1246	1246
1247	1247	Element Documentation:
1248	1248
1249		-(% style="width:943.294px" %)
1250		-|**Name**|(% style="width:352px" %)**Type**|(% style="width:461px" %)**Documentation**
1251		-|ID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)ID identifies an identification for the message, assigned by the sender.
1252		-|Test|(% style="width:352px" %)xs:boolean|(% style="width:461px" %)Test indicates whether the message is for test purposes or not.
1253		-|Prepared|(% style="width:352px" %)HeaderTimeType|(% style="width:461px" %)Prepared is the date the message was prepared.
1254		-|Sender|(% style="width:352px" %)SenderType|(% style="width:461px" %)Sender is information about the party that is transmitting the message.
1255		-|Receiver|(% style="width:352px" %)PartyType|(% style="width:461px" %)Receiver is information about the party that is the intended recipient of the message.
1256		-|com:Name|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1257		-|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.
1258		-|DataProvider|(% style="width:352px" %)com: DataProviderReferenceType|(% style="width:461px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1259		-|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).
1260		-|DataSetID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)DataSetID provides an identifier for a contained data set.
1261		-|Extracted|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)Extracted is a time-stamp from the system rendering the data.
1262		-|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).
1263		-|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).
1264		-|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.
1265		-|Source|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Source provides human-readable information about the source of the data.
	1202	+|**Name**|**Type**|**Documentation**
	1203	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1204	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1205	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1206	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1207	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1208	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1209	+|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.
	1210	+|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
	1211	+|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).
	1212	+|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
	1213	+|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
	1214	+|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1215	+|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1216	+|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
	1217	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1266	1266
1267	1267	**GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic reference metadata.
1268	1268
1269	1269	Derivation:
1270	1270
1271		-* //BaseHeaderType// (restriction)
1272		-** GenericMetadataHeaderType
	1223	+//BaseHeaderType// (restriction)
	1224	+ GenericMetadataHeaderType
1273	1273
1274	1274	Content:
1275	1275
...	...	@@ -1277,27 +1277,26 @@
1277	1277
1278	1278	Element Documentation:
1279	1279
1280		-(% style="width:928.294px" %)
1281		-|**Name**|**Type**|(% style="width:554px" %)**Documentation**
1282		-|ID|com:IDType|(% style="width:554px" %)ID identifies an identification for the message, assigned by the sender.
1283		-|Test|xs:boolean|(% style="width:554px" %)Test indicates whether the message is for test purposes or not.
1284		-|Prepared|HeaderTimeType|(% style="width:554px" %)Prepared is the date the message was prepared.
1285		-|Sender|SenderType|(% style="width:554px" %)Sender is information about the party that is transmitting the message.
1286		-|Receiver|PartyType|(% style="width:554px" %)Receiver is information about the party that is the intended recipient of the message.
1287		-|com:Name|com:TextType|(% style="width:554px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1288		-|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.
1289		-|DataProvider|com: DataProviderReferenceType|(% style="width:554px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1290		-|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).
1291		-|DataSetID|com:IDType|(% style="width:554px" %)DataSetID provides an identifier for a contained data set.
1292		-|Extracted|xs:dateTime|(% style="width:554px" %)Extracted is a time-stamp from the system rendering the data.
1293		-|Source|com:TextType|(% style="width:554px" %)Source provides human-readable information about the source of the data.
	1232	+|**Name**|**Type**|**Documentation**
	1233	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1234	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1235	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1236	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1237	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1238	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1239	+|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.
	1240	+|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
	1241	+|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).
	1242	+|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
	1243	+|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
	1244	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1294	1294
1295	1295	**StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for metadata structure definition specific reference metadata messages.
1296	1296
1297	1297	Derivation:
1298	1298
1299		-* //BaseHeaderType// (restriction)
1300		-** StructureSpecificMetadataHeaderType
	1250	+//BaseHeaderType// (restriction)
	1251	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType
1301	1301
1302	1302	Content:
1303	1303
...	...	@@ -1305,27 +1305,26 @@
1305	1305
1306	1306	Element Documentation:
1307	1307
1308		-(% style="width:996.294px" %)
1309		-|**Name**|**Type**|(% style="width:557px" %)**Documentation**
1310		-|ID|com:IDType|(% style="width:557px" %)ID identifies an identification for the message, assigned by the sender.
1311		-|Test|xs:boolean|(% style="width:557px" %)Test indicates whether the message is for test purposes or not.
1312		-|Prepared|HeaderTimeType|(% style="width:557px" %)Prepared is the date the message was prepared.
1313		-|Sender|SenderType|(% style="width:557px" %)Sender is information about the party that is transmitting the message.
1314		-|Receiver|PartyType|(% style="width:557px" %)Receiver is information about the party that is the intended recipient of the message.
1315		-|com:Name|com:TextType|(% style="width:557px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1316		-|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.
1317		-|DataProvider|com: DataProviderReferenceType|(% style="width:557px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1318		-|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).
1319		-|DataSetID|com:IDType|(% style="width:557px" %)DataSetID provides an identifier for a contained data set.
1320		-|Extracted|xs:dateTime|(% style="width:557px" %)Extracted is a time-stamp from the system rendering the data.
1321		-|Source|com:TextType|(% style="width:557px" %)Source provides human-readable information about the source of the data.
	1259	+|**Name**|**Type**|**Documentation**
	1260	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1261	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1262	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1263	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1264	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1265	+|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1266	+|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.
	1267	+|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
	1268	+|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).
	1269	+|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
	1270	+|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
	1271	+|Source|com:TextType|Source provides human-readable information about the source of the data.
1322	1322
1323	1323	**BasicHeaderType: **BasicHeaderType defines the most basic header information used in simple message exchanges.
1324	1324
1325	1325	Derivation:
1326	1326
1327		-* //BaseHeaderType// (restriction)
1328		-** BasicHeaderType
	1277	+//BaseHeaderType// (restriction)
	1278	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType
1329	1329
1330	1330	Content:
1331	1331
...	...	@@ -1333,13 +1333,12 @@
1333	1333
1334	1334	Element Documentation:
1335	1335
1336		-(% style="width:903.294px" %)
1337		-|**Name**|(% style="width:236px" %)**Type**|(% style="width:457px" %)**Documentation**
1338		-|ID|(% style="width:236px" %)com:IDType|(% style="width:457px" %)ID identifies an identification for the message, assigned by the sender.
1339		-|Test|(% style="width:236px" %)xs:boolean|(% style="width:457px" %)Test indicates whether the message is for test purposes or not.
1340		-|Prepared|(% style="width:236px" %)HeaderTimeType|(% style="width:457px" %)Prepared is the date the message was prepared.
1341		-|Sender|(% style="width:236px" %)SenderType|(% style="width:457px" %)Sender is information about the party that is transmitting the message.
1342		-|Receiver|(% style="width:236px" %)PartyType|(% style="width:457px" %)Receiver is information about the party that is the intended recipient of the message.
	1286	+|**Name**|**Type**|**Documentation**
	1287	+|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
	1288	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	1289	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	1290	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	1291	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1343	1343
1344	1344	**PartyType: **PartyType defines the information which is sent about various parties such as senders and receivers of messages.
1345	1345
...	...	@@ -1353,23 +1353,21 @@
1353	1353
1354	1354	Attribute Documentation:
1355	1355
1356		-(% style="width:739.294px" %)
1357		-|(% style="width:125px" %)**Name**|(% style="width:190px" %)**Type**|(% style="width:421px" %)**Documentation**
1358		-|(% style="width:125px" %)id|(% style="width:190px" %)com:IDType|(% style="width:421px" %)The id attribute holds the identification of the party.
	1305	+|**Name**|**Type**|**Documentation**
	1306	+|id|com:IDType|The id attribute holds the identification of the party.
1359	1359
1360	1360	Element Documentation:
1361	1361
1362		-(% style="width:751.294px" %)
1363		-|(% style="width:134px" %)**Name**|(% style="width:183px" %)**Type**|(% style="width:431px" %)**Documentation**
1364		-|(% style="width:134px" %)com:Name|(% style="width:183px" %)com:TextType|(% style="width:431px" %)Name is a human-readable name of the party.
1365		-|(% 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.
	1310	+|**Name**|**Type**|**Documentation**
	1311	+|com:Name|com:TextType|Name is a human-readable name of the party.
	1312	+|Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message.
1366	1366
1367	1367	**SenderType: **SenderType extends the basic party structure to add an optional time zone declaration.
1368	1368
1369	1369	Derivation:
1370	1370
1371		-* PartyType (extension)
1372		-** SenderType
	1318	+PartyType (extension)
	1319	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType
1373	1373
1374	1374	Attributes:
1375	1375
...	...	@@ -1381,9 +1381,8 @@
1381	1381
1382	1382	Attribute Documentation:
1383	1383
1384		-(% style="width:824.294px" %)
1385		-|(% style="width:177px" %)**Name**|(% style="width:241px" %)**Type**|(% style="width:403px" %)**Documentation**
1386		-|(% style="width:177px" %)id|(% style="width:241px" %)com:IDType|(% style="width:403px" %)The id attribute holds the identification of the party.
	1331	+|**Name**|**Type**|**Documentation**
	1332	+|id|com:IDType|The id attribute holds the identification of the party.
1387	1387
1388	1388	Element Documentation:
1389	1389
...	...	@@ -1410,7 +1410,9 @@
1410	1410	|URI|xs:anyURI|URI holds an information URL for the contact person.
1411	1411	|Email|xs:string|Email holds the email address for the contact person.
1412	1412
1413		-=== 2.1.4 Simple Types ===
	1359	+1.
	1360	+11.
	1361	+111. Simple Types
1414	1414
1415	1415	**HeaderTimeType: **Provides a union type of xs:date and xs:dateTime for the header fields in the message.
1416	1416
...	...	@@ -1418,11 +1418,14 @@
1418	1418
1419	1419	xs:dateTime, xs:date.
1420	1420
1421		-== 2.2 Message Footer Namespace ==
	1369	+1.
	1370	+11. Message Footer Namespace
1422	1422
1423	1423	**http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer**
1424	1424
1425		-=== 2.2.1 Summary ===
	1374	+1.
	1375	+11.
	1376	+111. Summary
1426	1426
1427	1427	Referenced Namespaces:
1428	1428
...	...	@@ -1436,11 +1436,15 @@
1436	1436	2 Complex Types
1437	1437	1 Simple Type
1438	1438
1439		-=== 2.2.2 Global Elements ===
	1390	+1.
	1391	+11.
	1392	+111. Global Elements
1440	1440
1441	1441	**Footer (FooterType): **Footer is used to communicate information such as error and warnings after the payload of a message.
1442	1442
1443		-=== 2.2.3 Complex Types ===
	1396	+1.
	1397	+11.
	1398	+111. Complex Types
1444	1444
1445	1445	**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.
1446	1446
...	...	@@ -1458,8 +1458,8 @@
1458	1458	Derivation:
1459	1459
1460	1460	com:StatusMessageType (restriction)
1461		-[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension)
1462		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType
	1416	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension)
	1417	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType
1463	1463
1464	1464	Attributes:
1465	1465
...	...	@@ -1480,7 +1480,9 @@
1480	1480	|**Name**|**Type**|**Documentation**
1481	1481	|com:Text|com:TextType|Text contains the text of the message, in parallel language values.
1482	1482
1483		-=== 2.2.4 Simple Types ===
	1438	+1.
	1439	+11.
	1440	+111. Simple Types
1484	1484
1485	1485	**SeverityCodeType:**
1486	1486
...	...	@@ -1491,4 +1491,19 @@
1491	1491	|**Value**|**Documentation**
1492	1492	|Error|Error indicates the status message coresponds to an error.
1493	1493	|Warning|Warning indicates that the status message corresponds to a warning.
1494		-|Information|Information indicates that the status message corresponds to an informational message.
	1451	+|Information|Information indicates that the status message corresponds to an informational message.
	1452	+
	1453	+
	1454	+
	1455	+
	1456	+
	1457	+
	1458	+
	1459	+
	1460	+
	1461	+
	1462	+
	1463	+
	1464	+
	1465	+
	1466	+