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,9 +347,10 @@
347	347
348	348	Content:
349	349
350		-* Header, SubmitRegistrationsRequest
351		-* Element Documentation:
	350	+Header, SubmitRegistrationsRequest
352	352
	352	+Element Documentation:
	353	+
353	353	(% style="width:844.294px" %)
354	354	|**Name**|**Type**|(% style="width:377px" %)**Documentation**
355	355	|Header|BasicHeaderType|(% style="width:377px" %)
...	...	@@ -365,9 +365,10 @@
365	365
366	366	Content:
367	367
368		-* Header, SubmitRegistrationsResponse, ftr:Footer?
369		-* Element Documentation:
	369	+Header, SubmitRegistrationsResponse, ftr:Footer?
370	370
	371	+Element Documentation:
	372	+
371	371	(% style="width:847.294px" %)
372	372	|**Name**|(% style="width:210px" %)**Type**|(% style="width:408px" %)**Documentation**
373	373	|Header|(% style="width:210px" %)BasicHeaderType|(% style="width:408px" %)
...	...	@@ -384,9 +384,10 @@
384	384
385	385	Content:
386	386
387		-* Header, QueryRegistrationRequest
388		-* Element Documentation:
	389	+Header, QueryRegistrationRequest
389	389
	391	+Element Documentation:
	392	+
390	390	(% style="width:847.294px" %)
391	391	|**Name**|**Type**|(% style="width:397px" %)**Documentation**
392	392	|Header|BasicHeaderType|(% style="width:397px" %)
...	...	@@ -441,9 +441,10 @@
441	441
442	442	Content:
443	443
444		-* Header, SubmitStructureResponse, ftr:Footer?
445		-* Element Documentation:
	447	+Header, SubmitStructureResponse, ftr:Footer?
446	446
	449	+Element Documentation:
	450	+
447	447	(% style="width:835.294px" %)
448	448	|**Name**|(% style="width:246px" %)**Type**|(% style="width:366px" %)**Documentation**
449	449	|Header|(% style="width:246px" %)BasicHeaderType|(% style="width:366px" %)
...	...	@@ -460,9 +460,10 @@
460	460
461	461	Content:
462	462
463		-* Header, SubmitSubscriptionsRequest
464		-* Element Documentation:
	467	+Header, SubmitSubscriptionsRequest
465	465
	469	+Element Documentation:
	470	+
466	466	(% style="width:832.294px" %)
467	467	|**Name**|(% style="width:227px" %)**Type**|(% style="width:319px" %)**Documentation**
468	468	|Header|(% style="width:227px" %)BasicHeaderType|(% style="width:319px" %)
...	...	@@ -478,9 +478,10 @@
478	478
479	479	Content:
480	480
481		-* Header, SubmitSubscriptionsResponse, ftr:Footer?
482		-* Element Documentation:
	486	+Header, SubmitSubscriptionsResponse, ftr:Footer?
483	483
	488	+Element Documentation:
	489	+
484	484	(% style="width:843.294px" %)
485	485	|**Name**|**Type**|(% style="width:362px" %)**Documentation**
486	486	|Header|BasicHeaderType|(% style="width:362px" %)
...	...	@@ -497,9 +497,10 @@
497	497
498	498	Content:
499	499
500		-* Header, QuerySubscriptionRequest
501		-* Element Documentation:
	506	+Header, QuerySubscriptionRequest
502	502
	508	+Element Documentation:
	509	+
503	503	(% style="width:839.294px" %)
504	504	|(% style="width:230px" %)**Name**|(% style="width:254px" %)**Type**|(% style="width:352px" %)**Documentation**
505	505	|(% style="width:230px" %)Header|(% style="width:254px" %)BasicHeaderType|(% style="width:352px" %)
...	...	@@ -515,9 +515,10 @@
515	515
516	516	Content:
517	517
518		-* Header, QuerySubscriptionResponse, ftr:Footer?
519		-* Element Documentation:
	525	+Header, QuerySubscriptionResponse, ftr:Footer?
520	520
	527	+Element Documentation:
	528	+
521	521	(% style="width:912.294px" %)
522	522	|**Name**|(% style="width:304px" %)**Type**|(% style="width:336px" %)**Documentation**
523	523	|Header|(% style="width:304px" %)BasicHeaderType|(% style="width:336px" %)
...	...	@@ -534,9 +534,10 @@
534	534
535	535	Content:
536	536
537		-* Header, NotifyRegistryEvent
538		-* Element Documentation:
	545	+Header, NotifyRegistryEvent
539	539
	547	+Element Documentation:
	548	+
540	540	(% style="width:836.294px" %)
541	541	|**Name**|**Type**|(% style="width:473px" %)**Documentation**
542	542	|Header|BasicHeaderType|(% style="width:473px" %)
...	...	@@ -551,9 +551,10 @@
551	551
552	552	Content:
553	553
554		-* Header, Query
555		-* Element Documentation:
	563	+Header, Query
556	556
	565	+Element Documentation:
	566	+
557	557	(% style="width:839.294px" %)
558	558	|(% style="width:244px" %)**Name**|(% style="width:262px" %)**Type**|(% style="width:330px" %)**Documentation**
559	559	|(% style="width:244px" %)Header|(% style="width:262px" %)BasicHeaderType|(% style="width:330px" %)
...	...	@@ -569,9 +569,10 @@
569	569
570	570	Content:
571	571
572		-* Header, Query
573		-* Element Documentation:
	582	+Header, Query
574	574
	584	+Element Documentation:
	585	+
575	575	(% style="width:833.294px" %)
576	576	|(% style="width:213px" %)**Name**|(% style="width:243px" %)**Type**|(% style="width:374px" %)**Documentation**
577	577	|(% style="width:213px" %)Header|(% style="width:243px" %)BasicHeaderType|(% style="width:374px" %)
...	...	@@ -588,9 +588,10 @@
588	588
589	589	Content:
590	590
591		-* Header, Query
592		-* Element Documentation:
	602	+Header, Query
593	593
	604	+Element Documentation:
	605	+
594	594	(% style="width:909.294px" %)
595	595	|(% style="width:221px" %)**Name**|(% style="width:305px" %)**Type**|(% style="width:380px" %)**Documentation**
596	596	|(% style="width:221px" %)Header|(% style="width:305px" %)BasicHeaderType|(% style="width:380px" %)
...	...	@@ -606,9 +606,10 @@
606	606
607	607	Content:
608	608
609		-* Header, Query
610		-* Element Documentation:
	621	+Header, Query
611	611
	623	+Element Documentation:
	624	+
612	612	(% style="width:903.294px" %)
613	613	|(% style="width:189px" %)**Name**|(% style="width:259px" %)**Type**|(% style="width:452px" %)**Documentation**
614	614	|(% style="width:189px" %)Header|(% style="width:259px" %)BasicHeaderType|(% style="width:452px" %)
...	...	@@ -623,9 +623,10 @@
623	623
624	624	Content:
625	625
626		-* Header, Query
627		-* Element Documentation:
	639	+Header, Query
628	628
	641	+Element Documentation:
	642	+
629	629	(% style="width:858.294px" %)
630	630	|(% style="width:138px" %)**Name**|(% style="width:246px" %)**Type**|(% style="width:471px" %)**Documentation**
631	631	|(% style="width:138px" %)Header|(% style="width:246px" %)BasicHeaderType|(% style="width:471px" %)
...	...	@@ -640,9 +640,10 @@
640	640
641	641	Content:
642	642
643		-* Header, Query
644		-* Element Documentation:
	657	+Header, Query
645	645
	659	+Element Documentation:
	660	+
646	646	(% style="width:895.294px" %)
647	647	|(% style="width:185px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:413px" %)**Documentation**
648	648	|(% style="width:185px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:413px" %)
...	...	@@ -657,9 +657,10 @@
657	657
658	658	Content:
659	659
660		-* Header, Query
661		-* Element Documentation:
	675	+Header, Query
662	662
	677	+Element Documentation:
	678	+
663	663	(% style="width:897.294px" %)
664	664	|(% style="width:166px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:447px" %)**Documentation**
665	665	|(% style="width:166px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:447px" %)
...	...	@@ -674,9 +674,10 @@
674	674
675	675	Content:
676	676
677		-* Header, Query
678		-* Element Documentation:
	693	+Header, Query
679	679
	695	+Element Documentation:
	696	+
680	680	(% style="width:886.294px" %)
681	681	|(% style="width:223px" %)**Name**|(% style="width:255px" %)**Type**|(% style="width:405px" %)**Documentation**
682	682	|(% style="width:223px" %)Header|(% style="width:255px" %)BasicHeaderType|(% style="width:405px" %)
...	...	@@ -691,9 +691,10 @@
691	691
692	692	Content:
693	693
694		-* Header, Query
695		-* Element Documentation:
	711	+Header, Query
696	696
	713	+Element Documentation:
	714	+
697	697	(% style="width:888.294px" %)
698	698	|(% style="width:176px" %)**Name**|(% style="width:260px" %)**Type**|(% style="width:449px" %)**Documentation**
699	699	|(% style="width:176px" %)Header|(% style="width:260px" %)BasicHeaderType|(% style="width:449px" %)
...	...	@@ -708,9 +708,10 @@
708	708
709	709	Content:
710	710
711		-* Header, Query
712		-* Element Documentation:
	729	+Header, Query
713	713
	731	+Element Documentation:
	732	+
714	714	(% style="width:886.294px" %)
715	715	|(% style="width:199px" %)**Name**|(% style="width:296px" %)**Type**|(% style="width:388px" %)**Documentation**
716	716	|(% style="width:199px" %)Header|(% style="width:296px" %)BasicHeaderType|(% style="width:388px" %)
...	...	@@ -725,9 +725,10 @@
725	725
726	726	Content:
727	727
728		-* Header, Query
729		-* Element Documentation:
	747	+Header, Query
730	730
	749	+Element Documentation:
	750	+
731	731	(% style="width:901.294px" %)
732	732	|(% style="width:202px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:393px" %)**Documentation**
733	733	|(% style="width:202px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:393px" %)
...	...	@@ -742,9 +742,10 @@
742	742
743	743	Content:
744	744
745		-* Header, Query
746		-* Element Documentation:
	765	+Header, Query
747	747
	767	+Element Documentation:
	768	+
748	748	(% style="width:904.294px" %)
749	749	|(% style="width:226px" %)**Name**|(% style="width:275px" %)**Type**|(% style="width:400px" %)**Documentation**
750	750	|(% style="width:226px" %)Header|(% style="width:275px" %)BasicHeaderType|(% style="width:400px" %)
...	...	@@ -759,9 +759,10 @@
759	759
760	760	Content:
761	761
762		-* Header, Query
763		-* Element Documentation:
	783	+Header, Query
764	764
	785	+Element Documentation:
	786	+
765	765	(% style="width:915.294px" %)
766	766	|(% style="width:196px" %)**Name**|(% style="width:347px" %)**Type**|(% style="width:369px" %)**Documentation**
767	767	|(% style="width:196px" %)Header|(% style="width:347px" %)BasicHeaderType|(% style="width:369px" %)
...	...	@@ -776,9 +776,10 @@
776	776
777	777	Content:
778	778
779		-* Header, Query
780		-* Element Documentation:
	801	+Header, Query
781	781
	803	+Element Documentation:
	804	+
782	782	(% style="width:895.294px" %)
783	783	|(% style="width:222px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:331px" %)**Documentation**
784	784	|(% style="width:222px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:331px" %)
...	...	@@ -924,132 +924,132 @@
924	924
925	925	Derivation:
926	926
927		-//MessageType// (restriction)
928		- ConstraintQueryType
	950	+* //MessageType// (restriction)
	951	+** ConstraintQueryType
929	929
930	930	Content:
931	931
932		-Header, Query
	955	+* Header, Query
	956	+* Element Documentation:
933	933
934		-Element Documentation:
	958	+(% style="width:902.294px" %)
	959	+|(% style="width:167px" %)**Name**|(% style="width:287px" %)**Type**|(% style="width:445px" %)**Documentation**
	960	+|(% style="width:167px" %)Header|(% style="width:287px" %)BasicHeaderType|(% style="width:445px" %)
	961	+|(% style="width:167px" %)Query|(% style="width:287px" %)qry: ConstraintQueryType|(% style="width:445px" %)
935	935
936		-|**Name**|**Type**|**Documentation**
937		-|Header|BasicHeaderType|
938		-|Query|qry: ConstraintQueryType|
939		-
940	940	**TransformationSchemeQueryType: **TransformationSchemeQueryType defines the structure of a transformation scheme query message.
941	941
942	942	Derivation:
943	943
944		-//MessageType// (restriction)
945		- TransformationSchemeQueryType
	967	+* //MessageType// (restriction)
	968	+** TransformationSchemeQueryType
946	946
947	947	Content:
948	948
949		-Header, Query
	972	+* Header, Query
	973	+* Element Documentation:
950	950
951		-Element Documentation:
	975	+(% style="width:833.294px" %)
	976	+|(% style="width:165px" %)**Name**|(% style="width:325px" %)**Type**|(% style="width:340px" %)**Documentation**
	977	+|(% style="width:165px" %)Header|(% style="width:325px" %)BasicHeaderType|(% style="width:340px" %)
	978	+|(% style="width:165px" %)Query|(% style="width:325px" %)qry: TransformationSchemeQueryType|(% style="width:340px" %)
952	952
953		-|**Name**|**Type**|**Documentation**
954		-|Header|BasicHeaderType|
955		-|Query|qry: TransformationScheme QueryType|
956		-
957	957	**VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a VTL mappings scheme query message.
958	958
959	959	Derivation:
960	960
961		-//MessageType// (restriction)
962		- VtlMappingSchemeQueryType
	984	+* //MessageType// (restriction)
	985	+** VtlMappingSchemeQueryType
963	963
964	964	Content:
965	965
966		-Header, Query
	989	+* Header, Query
	990	+* Element Documentation:
967	967
968		-Element Documentation:
	992	+(% style="width:843.294px" %)
	993	+|(% style="width:164px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:373px" %)**Documentation**
	994	+|(% style="width:164px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:373px" %)
	995	+|(% style="width:164px" %)Query|(% style="width:303px" %)qry: VtlMappingSchemeQueryType|(% style="width:373px" %)
969	969
970		-|**Name**|**Type**|**Documentation**
971		-|Header|BasicHeaderType|
972		-|Query|qry: VtlMappingSchemeQuer yType|
973		-
974	974	**NamePersonalisationSchemeQueryType: **NamePersonalisationSchemeQueryType defines the structure of a name personalisation scheme query message.
975	975
976	976	Derivation:
977	977
978		-//MessageType// (restriction)
979		- NamePersonalisationSchemeQueryType
	1001	+* //MessageType// (restriction)
	1002	+** NamePersonalisationSchemeQueryType
980	980
981	981	Content:
982	982
983		-Header, Query
	1006	+* Header, Query
	1007	+* Element Documentation:
984	984
985		-Element Documentation:
	1009	+(% style="width:895.294px" %)
	1010	+|(% style="width:186px" %)**Name**|(% style="width:363px" %)**Type**|(% style="width:343px" %)**Documentation**
	1011	+|(% style="width:186px" %)Header|(% style="width:363px" %)BasicHeaderType|(% style="width:343px" %)
	1012	+|(% style="width:186px" %)Query|(% style="width:363px" %)qry: NamePersonalisationSchemeQueryType|(% style="width:343px" %)
986	986
987		-|**Name**|**Type**|**Documentation**
988		-|Header|BasicHeaderType|
989		-|Query|qry: NamePersonalisationS chemeQueryType|
990		-
991	991	**RulesetSchemeQueryType: **RulesetSchemeQueryType defines the structure of a ruleset scheme query message.
992	992
993	993	Derivation:
994	994
995		-//MessageType// (restriction)
996		- RulesetSchemeQueryType
	1018	+* //MessageType// (restriction)
	1019	+** RulesetSchemeQueryType
997	997
998	998	Content:
999	999
1000		-Header, Query
	1023	+* Header, Query
	1024	+* Element Documentation:
1001	1001
1002		-Element Documentation:
	1026	+(% style="width:886.294px" %)
	1027	+|(% style="width:152px" %)**Name**|(% style="width:311px" %)**Type**|(% style="width:420px" %)**Documentation**
	1028	+|(% style="width:152px" %)Header|(% style="width:311px" %)BasicHeaderType|(% style="width:420px" %)
	1029	+|(% style="width:152px" %)Query|(% style="width:311px" %)qry: RulesetSchemeQueryType|(% style="width:420px" %)
1003	1003
1004		-|**Name**|**Type**|**Documentation**
1005		-|Header|BasicHeaderType|
1006		-|Query|qry: RulesetSchemeQueryTy pe|
1007		-
1008	1008	**UserDefinedOperatorSchemeQueryType: **UserDefinedOperatorSchemeQueryType defines the structure of a user defined operator scheme query message.
1009	1009
1010	1010	Derivation:
1011	1011
1012		-//MessageType// (restriction)
1013		- UserDefinedOperatorSchemeQueryType
	1035	+* //MessageType// (restriction)
	1036	+** UserDefinedOperatorSchemeQueryType
1014	1014
1015	1015	Content:
1016	1016
1017		-Header, Query
	1040	+* Header, Query
	1041	+* Element Documentation:
1018	1018
1019		-Element Documentation:
	1043	+(% style="width:866.294px" %)
	1044	+|(% style="width:174px" %)**Name**|(% style="width:358px" %)**Type**|(% style="width:331px" %)**Documentation**
	1045	+|(% style="width:174px" %)Header|(% style="width:358px" %)BasicHeaderType|(% style="width:331px" %)
	1046	+|(% style="width:174px" %)Query|(% style="width:358px" %)qry: UserDefinedOperatorSchemeQueryType|(% style="width:331px" %)
1020	1020
1021		-|**Name**|**Type**|**Documentation**
1022		-|Header|BasicHeaderType|
1023		-|Query|qry: UserDefinedOperatorS chemeQueryType|
1024		-
1025	1025	**CustomTypeSchemeQueryType: **CustomTypeSchemeQueryType defines the structure of a custom type scheme query message.
1026	1026
1027	1027	Derivation:
1028	1028
1029		-//MessageType// (restriction)
1030		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] CustomTypeSchemeQueryType
	1052	+* //MessageType// (restriction)
	1053	+** CustomTypeSchemeQueryType
1031	1031
1032	1032	Content:
1033	1033
1034		-Header, Query
	1057	+* Header, Query
	1058	+* Element Documentation:
1035	1035
1036		-Element Documentation:
	1060	+(% style="width:828.294px" %)
	1061	+|(% style="width:200px" %)**Name**|(% style="width:308px" %)**Type**|(% style="width:317px" %)**Documentation**
	1062	+|(% style="width:200px" %)Header|(% style="width:308px" %)BasicHeaderType|(% style="width:317px" %)
	1063	+|(% style="width:200px" %)Query|(% style="width:308px" %)qry: CustomTypeSchemeQueryType|(% style="width:317px" %)
1037	1037
1038		-|**Name**|**Type**|**Documentation**
1039		-|Header|BasicHeaderType|
1040		-|Query|qry: CustomTypeSchemeQuer yType|
1041		-
1042	1042	**ErrorType: **ErrorType describes the structure of an error response.
1043	1043
1044	1044	Content:
1045	1045
1046		-ErrorMessage+
	1069	+* ErrorMessage+
	1070	+* Element Documentation:
1047	1047
1048		-Element Documentation:
	1072	+(% style="width:899.294px" %)
	1073	+|**Name**|**Type**|(% style="width:546px" %)**Documentation**
	1074	+|ErrorMessage|com: CodedStatusMessageTy pe|(% style="width:546px" %)ErrorMessage contains the error message. It can occur multiple times to communicate message for multiple errors, or to communicate the error message in parallel languages. If both messages for multiple errors and parallel language messages are used, then each error message should be given a code in order to distinguish message for unique errors.
1049	1049
1050		-|**Name**|**Type**|**Documentation**
1051		-|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.
1052		-
1053	1053	**//BaseHeaderType//: **BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this
1054	1054
1055	1055	Content:
...	...	@@ -1058,29 +1058,30 @@
1058	1058
1059	1059	Element Documentation:
1060	1060
1061		-|**Name**|**Type**|**Documentation**
1062		-|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1063		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1064		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1065		-|Sender|SenderType|Sender is information about the party that is transmitting the message.
1066		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1067		-|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1068		-|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.
1069		-|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1070		-|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).
1071		-|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1072		-|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1073		-|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1074		-|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1075		-|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1076		-|Source|com:TextType|Source provides human-readable information about the source of the data.
	1084	+(% style="width:891.294px" %)
	1085	+|**Name**|**Type**|(% style="width:552px" %)**Documentation**
	1086	+|ID|com:IDType|(% style="width:552px" %)ID identifies an identification for the message, assigned by the sender.
	1087	+|Test|xs:boolean|(% style="width:552px" %)Test indicates whether the message is for test purposes or not.
	1088	+|Prepared|HeaderTimeType|(% style="width:552px" %)Prepared is the date the message was prepared.
	1089	+|Sender|SenderType|(% style="width:552px" %)Sender is information about the party that is transmitting the message.
	1090	+|Receiver|PartyType|(% style="width:552px" %)Receiver is information about the party that is the intended recipient of the message.
	1091	+|com:Name|com:TextType|(% style="width:552px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1092	+|Structure|//com: PayloadStructureType//|(% style="width:552px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
	1093	+|DataProvider|com: DataProviderReferenceType|(% style="width:552px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
	1094	+|DataSetAction|com:ActionType|(% style="width:552px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
	1095	+|DataSetID|com:IDType|(% style="width:552px" %)DataSetID provides an identifier for a contained data set.
	1096	+|Extracted|xs:dateTime|(% style="width:552px" %)Extracted is a time-stamp from the system rendering the data.
	1097	+|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1098	+|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1099	+|EmbargoDate|xs:dateTime|(% style="width:552px" %)EmbargoDate holds a time period before which the data included in this message is not available.
	1100	+|Source|com:TextType|(% style="width:552px" %)Source provides human-readable information about the source of the data.
1077	1077
1078	1078	**StructureHeaderType: **StructureHeaderType defines the structure for structural metadata messages.
1079	1079
1080	1080	Derivation:
1081	1081
1082		-//BaseHeaderType// (restriction)
1083		- StructureHeaderType
	1106	+* //BaseHeaderType// (restriction)
	1107	+** StructureHeaderType
1084	1084
1085	1085	Content:
1086	1086
...	...	@@ -1088,21 +1088,22 @@
1088	1088
1089	1089	Element Documentation:
1090	1090
1091		-|**Name**|**Type**|**Documentation**
1092		-|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1093		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1094		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1095		-|Sender|SenderType|Sender is information about the party that is transmitting the message.
1096		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1097		-|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1098		-|Source|com:TextType|Source provides human-readable information about the source of the data.
	1115	+(% style="width:1099.29px" %)
	1116	+|**Name**|(% style="width:224px" %)**Type**|(% style="width:663px" %)**Documentation**
	1117	+|ID|(% style="width:224px" %)com:IDType|(% style="width:663px" %)ID identifies an identification for the message, assigned by the sender.
	1118	+|Test|(% style="width:224px" %)xs:boolean|(% style="width:663px" %)Test indicates whether the message is for test purposes or not.
	1119	+|Prepared|(% style="width:224px" %)HeaderTimeType|(% style="width:663px" %)Prepared is the date the message was prepared.
	1120	+|Sender|(% style="width:224px" %)SenderType|(% style="width:663px" %)Sender is information about the party that is transmitting the message.
	1121	+|Receiver|(% style="width:224px" %)PartyType|(% style="width:663px" %)Receiver is information about the party that is the intended recipient of the message.
	1122	+|com:Name|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1123	+|Source|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Source provides human-readable information about the source of the data.
1099	1099
1100	1100	**GenericDataHeaderType: **GenericDataHeaderType defines the header structure for a generic data message.
1101	1101
1102	1102	Derivation:
1103	1103
1104		-//BaseHeaderType// (restriction)
1105		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataHeaderType
	1129	+* //BaseHeaderType// (restriction)
	1130	+** GenericDataHeaderType
1106	1106
1107	1107	Content:
1108	1108
...	...	@@ -1110,30 +1110,31 @@
1110	1110
1111	1111	Element Documentation:
1112	1112
1113		-|**Name**|**Type**|**Documentation**
1114		-|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1115		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1116		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1117		-|Sender|SenderType|Sender is information about the party that is transmitting the message.
1118		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1119		-|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1120		-|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.
1121		-|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1122		-|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).
1123		-|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1124		-|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1125		-|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1126		-|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1127		-|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1128		-|Source|com:TextType|Source provides human-readable information about the source of the data.
	1138	+(% style="width:895.294px" %)
	1139	+|**Name**|**Type**|(% style="width:556px" %)**Documentation**
	1140	+|ID|com:IDType|(% style="width:556px" %)ID identifies an identification for the message, assigned by the sender.
	1141	+|Test|xs:boolean|(% style="width:556px" %)Test indicates whether the message is for test purposes or not.
	1142	+|Prepared|HeaderTimeType|(% style="width:556px" %)Prepared is the date the message was prepared.
	1143	+|Sender|SenderType|(% style="width:556px" %)Sender is information about the party that is transmitting the message.
	1144	+|Receiver|PartyType|(% style="width:556px" %)Receiver is information about the party that is the intended recipient of the message.
	1145	+|com:Name|com:TextType|(% style="width:556px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1146	+|Structure|com: GenericDataStructureType|(% style="width:556px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
	1147	+|DataProvider|com: DataProviderReferenceType|(% style="width:556px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
	1148	+|DataSetAction|com:ActionType|(% style="width:556px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
	1149	+|DataSetID|com:IDType|(% style="width:556px" %)DataSetID provides an identifier for a contained data set.
	1150	+|Extracted|xs:dateTime|(% style="width:556px" %)Extracted is a time-stamp from the system rendering the data.
	1151	+|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1152	+|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1153	+|EmbargoDate|xs:dateTime|(% style="width:556px" %)EmbargoDate holds a time period before which the data included in this message is not available.
	1154	+|Source|com:TextType|(% style="width:556px" %)Source provides human-readable information about the source of the data.
1129	1129
1130	1130	**GenericTimeSeriesDataHeaderType: **GenericTimeSeriesDataHeaderType defines the header structure for a time series only generic data message.
1131	1131
1132	1132	Derivation:
1133	1133
1134		-//BaseHeaderType// (restriction)
1135		- GenericDataHeaderType (restriction)
1136		- GenericTimeSeriesDataHeaderType
	1160	+* //BaseHeaderType// (restriction)
	1161	+** GenericDataHeaderType (restriction)
	1162	+*** GenericTimeSeriesDataHeaderType
1137	1137
1138	1138	Content:
1139	1139
...	...	@@ -1141,29 +1141,30 @@
1141	1141
1142	1142	Element Documentation:
1143	1143
1144		-|**Name**|**Type**|**Documentation**
1145		-|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1146		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1147		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1148		-|Sender|SenderType|Sender is information about the party that is transmitting the message.
1149		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1150		-|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1151		-|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.
1152		-|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1153		-|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).
1154		-|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1155		-|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1156		-|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1157		-|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1158		-|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1159		-|Source|com:TextType|Source provides human-readable information about the source of the data.
	1170	+(% style="width:926.294px" %)
	1171	+|**Name**|**Type**|(% style="width:497px" %)**Documentation**
	1172	+|ID|com:IDType|(% style="width:497px" %)ID identifies an identification for the message, assigned by the sender.
	1173	+|Test|xs:boolean|(% style="width:497px" %)Test indicates whether the message is for test purposes or not.
	1174	+|Prepared|HeaderTimeType|(% style="width:497px" %)Prepared is the date the message was prepared.
	1175	+|Sender|SenderType|(% style="width:497px" %)Sender is information about the party that is transmitting the message.
	1176	+|Receiver|PartyType|(% style="width:497px" %)Receiver is information about the party that is the intended recipient of the message.
	1177	+|com:Name|com:TextType|(% style="width:497px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1178	+|Structure|com: GenericTimeSeriesDataStructureType|(% style="width:497px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
	1179	+|DataProvider|com: DataProviderReferenceType|(% style="width:497px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
	1180	+|DataSetAction|com:ActionType|(% style="width:497px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
	1181	+|DataSetID|com:IDType|(% style="width:497px" %)DataSetID provides an identifier for a contained data set.
	1182	+|Extracted|xs:dateTime|(% style="width:497px" %)Extracted is a time-stamp from the system rendering the data.
	1183	+|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1184	+|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1185	+|EmbargoDate|xs:dateTime|(% style="width:497px" %)EmbargoDate holds a time period before which the data included in this message is not available.
	1186	+|Source|com:TextType|(% style="width:497px" %)Source provides human-readable information about the source of the data.
1160	1160
1161	1161	**StructureSpecificDataHeaderType: **StructureSpecificDataHeaderType defines the header structure for a structure specific data message.
1162	1162
1163	1163	Derivation:
1164	1164
1165		-//BaseHeaderType// (restriction)
1166		- StructureSpecificDataHeaderType
	1192	+* //BaseHeaderType// (restriction)
	1193	+** StructureSpecificDataHeaderType
1167	1167
1168	1168	Content:
1169	1169
...	...	@@ -1171,30 +1171,31 @@
1171	1171
1172	1172	Element Documentation:
1173	1173
1174		-|**Name**|**Type**|**Documentation**
1175		-|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1176		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1177		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1178		-|Sender|SenderType|Sender is information about the party that is transmitting the message.
1179		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1180		-|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1181		-|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.
1182		-|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1183		-|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).
1184		-|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1185		-|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1186		-|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1187		-|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1188		-|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1189		-|Source|com:TextType|Source provides human-readable information about the source of the data.
	1201	+(% style="width:930.294px" %)
	1202	+|**Name**|**Type**|(% style="width:578px" %)**Documentation**
	1203	+|ID|com:IDType|(% style="width:578px" %)ID identifies an identification for the message, assigned by the sender.
	1204	+|Test|xs:boolean|(% style="width:578px" %)Test indicates whether the message is for test purposes or not.
	1205	+|Prepared|HeaderTimeType|(% style="width:578px" %)Prepared is the date the message was prepared.
	1206	+|Sender|SenderType|(% style="width:578px" %)Sender is information about the party that is transmitting the message.
	1207	+|Receiver|PartyType|(% style="width:578px" %)Receiver is information about the party that is the intended recipient of the message.
	1208	+|com:Name|com:TextType|(% style="width:578px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1209	+|Structure|com: StructureSpecificDataStructureType|(% style="width:578px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
	1210	+|DataProvider|com: DataProviderReferenceType|(% style="width:578px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
	1211	+|DataSetAction|com:ActionType|(% style="width:578px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
	1212	+|DataSetID|com:IDType|(% style="width:578px" %)DataSetID provides an identifier for a contained data set.
	1213	+|Extracted|xs:dateTime|(% style="width:578px" %)Extracted is a time-stamp from the system rendering the data.
	1214	+|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1215	+|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1216	+|EmbargoDate|xs:dateTime|(% style="width:578px" %)EmbargoDate holds a time period before which the data included in this message is not available.
	1217	+|Source|com:TextType|(% style="width:578px" %)Source provides human-readable information about the source of the data.
1190	1190
1191	1191	**StructureSpecificTimeSeriesDataHeaderType: **StructureSpecificTimeSeriesDataHeaderType defines the header structure for a time series only structure specific data message.
1192	1192
1193	1193	Derivation:
1194	1194
1195		-//BaseHeaderType// (restriction)
1196		- StructureSpecificDataHeaderType (restriction)
1197		- StructureSpecificTimeSeriesDataHeaderType
	1223	+* //BaseHeaderType// (restriction)
	1224	+** StructureSpecificDataHeaderType (restriction)
	1225	+*** StructureSpecificTimeSeriesDataHeaderType
1198	1198
1199	1199	Content:
1200	1200
...	...	@@ -1202,29 +1202,30 @@
1202	1202
1203	1203	Element Documentation:
1204	1204
1205		-|**Name**|**Type**|**Documentation**
1206		-|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1207		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1208		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1209		-|Sender|SenderType|Sender is information about the party that is transmitting the message.
1210		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1211		-|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1212		-|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.
1213		-|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1214		-|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).
1215		-|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1216		-|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1217		-|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1218		-|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1219		-|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1220		-|Source|com:TextType|Source provides human-readable information about the source of the data.
	1233	+(% style="width:943.294px" %)
	1234	+|**Name**|(% style="width:352px" %)**Type**|(% style="width:461px" %)**Documentation**
	1235	+|ID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)ID identifies an identification for the message, assigned by the sender.
	1236	+|Test|(% style="width:352px" %)xs:boolean|(% style="width:461px" %)Test indicates whether the message is for test purposes or not.
	1237	+|Prepared|(% style="width:352px" %)HeaderTimeType|(% style="width:461px" %)Prepared is the date the message was prepared.
	1238	+|Sender|(% style="width:352px" %)SenderType|(% style="width:461px" %)Sender is information about the party that is transmitting the message.
	1239	+|Receiver|(% style="width:352px" %)PartyType|(% style="width:461px" %)Receiver is information about the party that is the intended recipient of the message.
	1240	+|com:Name|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1241	+|Structure|(% style="width:352px" %)com: StructureSpecificDataTimeSeriesStructureType|(% style="width:461px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
	1242	+|DataProvider|(% style="width:352px" %)com: DataProviderReferenceType|(% style="width:461px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
	1243	+|DataSetAction|(% style="width:352px" %)com:ActionType|(% style="width:461px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
	1244	+|DataSetID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)DataSetID provides an identifier for a contained data set.
	1245	+|Extracted|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)Extracted is a time-stamp from the system rendering the data.
	1246	+|ReportingBegin|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
	1247	+|ReportingEnd|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
	1248	+|EmbargoDate|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)EmbargoDate holds a time period before which the data included in this message is not available.
	1249	+|Source|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Source provides human-readable information about the source of the data.
1221	1221
1222	1222	**GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic reference metadata.
1223	1223
1224	1224	Derivation:
1225	1225
1226		-//BaseHeaderType// (restriction)
1227		- GenericMetadataHeaderType
	1255	+* //BaseHeaderType// (restriction)
	1256	+** GenericMetadataHeaderType
1228	1228
1229	1229	Content:
1230	1230
...	...	@@ -1232,26 +1232,27 @@
1232	1232
1233	1233	Element Documentation:
1234	1234
1235		-|**Name**|**Type**|**Documentation**
1236		-|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1237		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1238		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1239		-|Sender|SenderType|Sender is information about the party that is transmitting the message.
1240		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1241		-|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1242		-|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.
1243		-|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1244		-|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).
1245		-|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1246		-|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1247		-|Source|com:TextType|Source provides human-readable information about the source of the data.
	1264	+(% style="width:928.294px" %)
	1265	+|**Name**|**Type**|(% style="width:554px" %)**Documentation**
	1266	+|ID|com:IDType|(% style="width:554px" %)ID identifies an identification for the message, assigned by the sender.
	1267	+|Test|xs:boolean|(% style="width:554px" %)Test indicates whether the message is for test purposes or not.
	1268	+|Prepared|HeaderTimeType|(% style="width:554px" %)Prepared is the date the message was prepared.
	1269	+|Sender|SenderType|(% style="width:554px" %)Sender is information about the party that is transmitting the message.
	1270	+|Receiver|PartyType|(% style="width:554px" %)Receiver is information about the party that is the intended recipient of the message.
	1271	+|com:Name|com:TextType|(% style="width:554px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1272	+|Structure|com: GenericMetadataStructureType|(% style="width:554px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
	1273	+|DataProvider|com: DataProviderReferenceType|(% style="width:554px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
	1274	+|DataSetAction|com:ActionType|(% style="width:554px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
	1275	+|DataSetID|com:IDType|(% style="width:554px" %)DataSetID provides an identifier for a contained data set.
	1276	+|Extracted|xs:dateTime|(% style="width:554px" %)Extracted is a time-stamp from the system rendering the data.
	1277	+|Source|com:TextType|(% style="width:554px" %)Source provides human-readable information about the source of the data.
1248	1248
1249	1249	**StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for metadata structure definition specific reference metadata messages.
1250	1250
1251	1251	Derivation:
1252	1252
1253		-//BaseHeaderType// (restriction)
1254		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType
	1283	+* //BaseHeaderType// (restriction)
	1284	+** StructureSpecificMetadataHeaderType
1255	1255
1256	1256	Content:
1257	1257
...	...	@@ -1259,26 +1259,27 @@
1259	1259
1260	1260	Element Documentation:
1261	1261
1262		-|**Name**|**Type**|**Documentation**
1263		-|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1264		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1265		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1266		-|Sender|SenderType|Sender is information about the party that is transmitting the message.
1267		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1268		-|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1269		-|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.
1270		-|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1271		-|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).
1272		-|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1273		-|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1274		-|Source|com:TextType|Source provides human-readable information about the source of the data.
	1292	+(% style="width:996.294px" %)
	1293	+|**Name**|**Type**|(% style="width:557px" %)**Documentation**
	1294	+|ID|com:IDType|(% style="width:557px" %)ID identifies an identification for the message, assigned by the sender.
	1295	+|Test|xs:boolean|(% style="width:557px" %)Test indicates whether the message is for test purposes or not.
	1296	+|Prepared|HeaderTimeType|(% style="width:557px" %)Prepared is the date the message was prepared.
	1297	+|Sender|SenderType|(% style="width:557px" %)Sender is information about the party that is transmitting the message.
	1298	+|Receiver|PartyType|(% style="width:557px" %)Receiver is information about the party that is the intended recipient of the message.
	1299	+|com:Name|com:TextType|(% style="width:557px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
	1300	+|Structure|com: StructureSpecificMetadataStructureType|(% style="width:557px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
	1301	+|DataProvider|com: DataProviderReferenceType|(% style="width:557px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
	1302	+|DataSetAction|com:ActionType|(% style="width:557px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
	1303	+|DataSetID|com:IDType|(% style="width:557px" %)DataSetID provides an identifier for a contained data set.
	1304	+|Extracted|xs:dateTime|(% style="width:557px" %)Extracted is a time-stamp from the system rendering the data.
	1305	+|Source|com:TextType|(% style="width:557px" %)Source provides human-readable information about the source of the data.
1275	1275
1276	1276	**BasicHeaderType: **BasicHeaderType defines the most basic header information used in simple message exchanges.
1277	1277
1278	1278	Derivation:
1279	1279
1280		-//BaseHeaderType// (restriction)
1281		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType
	1311	+* //BaseHeaderType// (restriction)
	1312	+** BasicHeaderType
1282	1282
1283	1283	Content:
1284	1284
...	...	@@ -1286,12 +1286,13 @@
1286	1286
1287	1287	Element Documentation:
1288	1288
1289		-|**Name**|**Type**|**Documentation**
1290		-|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1291		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1292		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1293		-|Sender|SenderType|Sender is information about the party that is transmitting the message.
1294		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
	1320	+(% style="width:903.294px" %)
	1321	+|**Name**|(% style="width:236px" %)**Type**|(% style="width:457px" %)**Documentation**
	1322	+|ID|(% style="width:236px" %)com:IDType|(% style="width:457px" %)ID identifies an identification for the message, assigned by the sender.
	1323	+|Test|(% style="width:236px" %)xs:boolean|(% style="width:457px" %)Test indicates whether the message is for test purposes or not.
	1324	+|Prepared|(% style="width:236px" %)HeaderTimeType|(% style="width:457px" %)Prepared is the date the message was prepared.
	1325	+|Sender|(% style="width:236px" %)SenderType|(% style="width:457px" %)Sender is information about the party that is transmitting the message.
	1326	+|Receiver|(% style="width:236px" %)PartyType|(% style="width:457px" %)Receiver is information about the party that is the intended recipient of the message.
1295	1295
1296	1296	**PartyType: **PartyType defines the information which is sent about various parties such as senders and receivers of messages.
1297	1297
...	...	@@ -1305,21 +1305,23 @@
1305	1305
1306	1306	Attribute Documentation:
1307	1307
1308		-|**Name**|**Type**|**Documentation**
1309		-|id|com:IDType|The id attribute holds the identification of the party.
	1340	+(% style="width:739.294px" %)
	1341	+|(% style="width:125px" %)**Name**|(% style="width:190px" %)**Type**|(% style="width:421px" %)**Documentation**
	1342	+|(% style="width:125px" %)id|(% style="width:190px" %)com:IDType|(% style="width:421px" %)The id attribute holds the identification of the party.
1310	1310
1311	1311	Element Documentation:
1312	1312
1313		-|**Name**|**Type**|**Documentation**
1314		-|com:Name|com:TextType|Name is a human-readable name of the party.
1315		-|Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message.
	1346	+(% style="width:751.294px" %)
	1347	+|(% style="width:134px" %)**Name**|(% style="width:183px" %)**Type**|(% style="width:431px" %)**Documentation**
	1348	+|(% style="width:134px" %)com:Name|(% style="width:183px" %)com:TextType|(% style="width:431px" %)Name is a human-readable name of the party.
	1349	+|(% style="width:134px" %)Contact|(% style="width:183px" %)ContactType|(% style="width:431px" %)Contact provides contact information for the party in regard to the transmission of the message.
1316	1316
1317	1317	**SenderType: **SenderType extends the basic party structure to add an optional time zone declaration.
1318	1318
1319	1319	Derivation:
1320	1320
1321		-PartyType (extension)
1322		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType
	1355	+* PartyType (extension)
	1356	+** SenderType
1323	1323
1324	1324	Attributes:
1325	1325
...	...	@@ -1331,8 +1331,9 @@
1331	1331
1332	1332	Attribute Documentation:
1333	1333
1334		-|**Name**|**Type**|**Documentation**
1335		-|id|com:IDType|The id attribute holds the identification of the party.
	1368	+(% style="width:824.294px" %)
	1369	+|(% style="width:177px" %)**Name**|(% style="width:241px" %)**Type**|(% style="width:403px" %)**Documentation**
	1370	+|(% style="width:177px" %)id|(% style="width:241px" %)com:IDType|(% style="width:403px" %)The id attribute holds the identification of the party.
1336	1336
1337	1337	Element Documentation:
1338	1338
...	...	@@ -1359,8 +1359,8 @@
1359	1359	|URI|xs:anyURI|URI holds an information URL for the contact person.
1360	1360	|Email|xs:string|Email holds the email address for the contact person.
1361	1361
1362		-1.
1363		-11.
	1397	+1.
	1398	+11.
1364	1364	111. Simple Types
1365	1365
1366	1366	**HeaderTimeType: **Provides a union type of xs:date and xs:dateTime for the header fields in the message.
...	...	@@ -1369,13 +1369,13 @@
1369	1369
1370	1370	xs:dateTime, xs:date.
1371	1371
1372		-1.
	1407	+1.
1373	1373	11. Message Footer Namespace
1374	1374
1375	1375	**http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer**
1376	1376
1377		-1.
1378		-11.
	1412	+1.
	1413	+11.
1379	1379	111. Summary
1380	1380
1381	1381	Referenced Namespaces:
...	...	@@ -1390,14 +1390,14 @@
1390	1390	2 Complex Types
1391	1391	1 Simple Type
1392	1392
1393		-1.
1394		-11.
	1428	+1.
	1429	+11.
1395	1395	111. Global Elements
1396	1396
1397	1397	**Footer (FooterType): **Footer is used to communicate information such as error and warnings after the payload of a message.
1398	1398
1399		-1.
1400		-11.
	1434	+1.
	1435	+11.
1401	1401	111. Complex Types
1402	1402
1403	1403	**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.
...	...	@@ -1416,8 +1416,8 @@
1416	1416	Derivation:
1417	1417
1418	1418	com:StatusMessageType (restriction)
1419		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension)
1420		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType
	1454	+[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension)
	1455	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType
1421	1421
1422	1422	Attributes:
1423	1423
...	...	@@ -1438,8 +1438,8 @@
1438	1438	|**Name**|**Type**|**Documentation**
1439	1439	|com:Text|com:TextType|Text contains the text of the message, in parallel language values.
1440	1440
1441		-1.
1442		-11.
	1476	+1.
	1477	+11.
1443	1443	111. Simple Types
1444	1444
1445	1445	**SeverityCodeType:**