Changes for page Part I. Message Namespace

Summary

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

Details

Page properties

Content

...	...	@@ -674,382 +674,382 @@
674	674
675	675	Content:
676	676
677		-* Header, Query
678		-* Element Documentation:
	677	+Header, Query
679	679
680		-(% style="width:886.294px" %)
681		-|(% style="width:223px" %)**Name**|(% style="width:255px" %)**Type**|(% style="width:405px" %)**Documentation**
682		-|(% style="width:223px" %)Header|(% style="width:255px" %)BasicHeaderType|(% style="width:405px" %)
683		-|(% style="width:223px" %)Query|(% style="width:255px" %)qry: StructuresQueryType|(% style="width:405px" %)
	679	+Element Documentation:
684	684
	681	+|**Name**|**Type**|**Documentation**
	682	+|Header|BasicHeaderType|
	683	+|Query|qry: StructuresQueryType|
	684	+
685	685	**DataflowQueryType: **DataflowQueryType defines the structure of a dataflow query message.
686	686
687	687	Derivation:
688	688
689		-* //MessageType// (restriction)
690		-** DataflowQueryType
	689	+//MessageType// (restriction)
	690	+ DataflowQueryType
691	691
692	692	Content:
693	693
694		-* Header, Query
695		-* Element Documentation:
	694	+Header, Query
696	696
697		-(% style="width:888.294px" %)
698		-|(% style="width:176px" %)**Name**|(% style="width:260px" %)**Type**|(% style="width:449px" %)**Documentation**
699		-|(% style="width:176px" %)Header|(% style="width:260px" %)BasicHeaderType|(% style="width:449px" %)
700		-|(% style="width:176px" %)Query|(% style="width:260px" %)qry: DataflowQueryType|(% style="width:449px" %)
	696	+Element Documentation:
701	701
	698	+|**Name**|**Type**|**Documentation**
	699	+|Header|BasicHeaderType|
	700	+|Query|qry: DataflowQueryType|
	701	+
702	702	**MetadataflowQueryType: **MetadataflowQueryType defines the structure of a metadata flow query message.
703	703
704	704	Derivation:
705	705
706		-* //MessageType// (restriction)
707		-** MetadataflowQueryType
	706	+//MessageType// (restriction)
	707	+ MetadataflowQueryType
708	708
709	709	Content:
710	710
711		-* Header, Query
712		-* Element Documentation:
	711	+Header, Query
713	713
714		-(% style="width:886.294px" %)
715		-|(% style="width:199px" %)**Name**|(% style="width:296px" %)**Type**|(% style="width:388px" %)**Documentation**
716		-|(% style="width:199px" %)Header|(% style="width:296px" %)BasicHeaderType|(% style="width:388px" %)
717		-|(% style="width:199px" %)Query|(% style="width:296px" %)qry: MetadataflowQueryType|(% style="width:388px" %)
	713	+Element Documentation:
718	718
	715	+|**Name**|**Type**|**Documentation**
	716	+|Header|BasicHeaderType|
	717	+|Query|qry: MetadataflowQueryTyp e|
	718	+
719	719	**DataStructureQueryType: **KeyFamilyQueryType defines the structure of a data structure query message.
720	720
721	721	Derivation:
722	722
723		-* //MessageType// (restriction)
724		-** DataStructureQueryType
	723	+//MessageType// (restriction)
	724	+ DataStructureQueryType
725	725
726	726	Content:
727	727
728		-* Header, Query
729		-* Element Documentation:
	728	+Header, Query
730	730
731		-(% style="width:901.294px" %)
732		-|(% style="width:202px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:393px" %)**Documentation**
733		-|(% style="width:202px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:393px" %)
734		-|(% style="width:202px" %)Query|(% style="width:303px" %)qry: DataStructureQueryType|(% style="width:393px" %)
	730	+Element Documentation:
735	735
	732	+|**Name**|**Type**|**Documentation**
	733	+|Header|BasicHeaderType|
	734	+|Query|qry: DataStructureQueryTy pe|
	735	+
736	736	**MetadataStructureQueryType: **MetadataStructureQueryType defines the structure of a metadata structure query message.
737	737
738	738	Derivation:
739	739
740		-* //MessageType// (restriction)
741		-** MetadataStructureQueryType
	740	+//MessageType// (restriction)
	741	+ MetadataStructureQueryType
742	742
743	743	Content:
744	744
745		-* Header, Query
746		-* Element Documentation:
	745	+Header, Query
747	747
748		-(% style="width:904.294px" %)
749		-|(% style="width:226px" %)**Name**|(% style="width:275px" %)**Type**|(% style="width:400px" %)**Documentation**
750		-|(% style="width:226px" %)Header|(% style="width:275px" %)BasicHeaderType|(% style="width:400px" %)
751		-|(% style="width:226px" %)Query|(% style="width:275px" %)qry: MetadataStructureQueryType|(% style="width:400px" %)
	747	+Element Documentation:
752	752
	749	+|**Name**|**Type**|**Documentation**
	750	+|Header|BasicHeaderType|
	751	+|Query|qry: MetadataStructureQue ryType|
	752	+
753	753	**CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a category scheme query message.
754	754
755	755	Derivation:
756	756
757		-* //MessageType// (restriction)
758		-** CategorySchemeQueryType
	757	+//MessageType// (restriction)
	758	+ CategorySchemeQueryType
759	759
760	760	Content:
761	761
762		-* Header, Query
763		-* Element Documentation:
	762	+Header, Query
764	764
765		-(% style="width:915.294px" %)
766		-|(% style="width:196px" %)**Name**|(% style="width:347px" %)**Type**|(% style="width:369px" %)**Documentation**
767		-|(% style="width:196px" %)Header|(% style="width:347px" %)BasicHeaderType|(% style="width:369px" %)
768		-|(% style="width:196px" %)Query|(% style="width:347px" %)qry: CategorySchemeQueryType|(% style="width:369px" %)
	764	+Element Documentation:
769	769
	766	+|**Name**|**Type**|**Documentation**
	767	+|Header|BasicHeaderType|
	768	+|Query|qry: CategorySchemeQueryT ype|
	769	+
770	770	**ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a concept scheme query message.
771	771
772	772	Derivation:
773	773
774		-* //MessageType// (restriction)
775		-** ConceptSchemeQueryType
	774	+//MessageType// (restriction)
	775	+ ConceptSchemeQueryType
776	776
777	777	Content:
778	778
779		-* Header, Query
780		-* Element Documentation:
	779	+Header, Query
781	781
782		-(% style="width:895.294px" %)
783		-|(% style="width:222px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:331px" %)**Documentation**
784		-|(% style="width:222px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:331px" %)
785		-|(% style="width:222px" %)Query|(% style="width:339px" %)qry: ConceptSchemeQueryType|(% style="width:331px" %)
	781	+Element Documentation:
786	786
	783	+|**Name**|**Type**|**Documentation**
	784	+|Header|BasicHeaderType|
	785	+|Query|qry: ConceptSchemeQueryTy pe|
	786	+
787	787	**CodelistQueryType: **CodelistQueryType defines the structure of a codelist query message.
788	788
789	789	Derivation:
790	790
791		-* //MessageType// (restriction)
792		-** CodelistQueryType
	791	+//MessageType// (restriction)
	792	+ CodelistQueryType
793	793
794	794	Content:
795	795
796		-* Header, Query
797		-* Element Documentation:
	796	+Header, Query
798	798
799		-(% style="width:911.294px" %)
800		-|(% style="width:204px" %)**Name**|(% style="width:295px" %)**Type**|(% style="width:409px" %)**Documentation**
801		-|(% style="width:204px" %)Header|(% style="width:295px" %)BasicHeaderType|(% style="width:409px" %)
802		-|(% style="width:204px" %)Query|(% style="width:295px" %)qry:CodelistQueryType|(% style="width:409px" %)
	798	+Element Documentation:
803	803
	800	+|**Name**|**Type**|**Documentation**
	801	+|Header|BasicHeaderType|
	802	+|Query|qry: CodelistQueryType|
	803	+
804	804	**HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical codelist query message.
805	805
806	806	Derivation:
807	807
808		-* //MessageType// (restriction)
809		-** HierarchicalCodelistQueryType
	808	+//MessageType// (restriction)
	809	+ HierarchicalCodelistQueryType
810	810
811	811	Content:
812	812
813		-* Header, Query
814		-* Element Documentation:
	813	+Header, Query
815	815
816		-(% style="width:906.294px" %)
817		-|(% style="width:191px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:430px" %)**Documentation**
818		-|(% style="width:191px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:430px" %)
819		-|(% style="width:191px" %)Query|(% style="width:281px" %)qry: HierarchicalCodelist QueryType|(% style="width:430px" %)
	815	+Element Documentation:
820	820
	817	+|**Name**|**Type**|**Documentation**
	818	+|Header|BasicHeaderType|
	819	+|Query|qry: HierarchicalCodelist QueryType|
	820	+
821	821	**OrganisationSchemeQueryType: **OrganisationSchemeQueryType defines the structure of an organisation scheme query message.
822	822
823	823	Derivation:
824	824
825		-* //MessageType// (restriction)
826		-** OrganisationSchemeQueryType
	825	+//MessageType// (restriction)
	826	+ OrganisationSchemeQueryType
827	827
828	828	Content:
829	829
830		-* Header, Query
831		-* Element Documentation:
	830	+Header, Query
832	832
833		-(% style="width:891.294px" %)
834		-|(% style="width:174px" %)**Name**|(% style="width:292px" %)**Type**|(% style="width:422px" %)**Documentation**
835		-|(% style="width:174px" %)Header|(% style="width:292px" %)BasicHeaderType|(% style="width:422px" %)
836		-|(% style="width:174px" %)Query|(% style="width:292px" %)qry: OrganisationSchemeQueryType|(% style="width:422px" %)
	832	+Element Documentation:
837	837
	834	+|**Name**|**Type**|**Documentation**
	835	+|Header|BasicHeaderType|
	836	+|Query|qry: OrganisationSchemeQu eryType|
	837	+
838	838	**ReportingTaxonomyQueryType: **ReportingTaxonomyQueryType defines the structure of a reporting taxonomy query message.
839	839
840	840	Derivation:
841	841
842		-* //MessageType// (restriction)
843		-** ReportingTaxonomyQueryType
	842	+//MessageType// (restriction)
	843	+ ReportingTaxonomyQueryType
844	844
845	845	Content:
846	846
847		-* Header, Query
848		-* Element Documentation:
	847	+Header, Query
849	849
850		-(% style="width:916.294px" %)
851		-|(% style="width:162px" %)**Name**|(% style="width:318px" %)**Type**|(% style="width:434px" %)**Documentation**
852		-|(% style="width:162px" %)Header|(% style="width:318px" %)BasicHeaderType|(% style="width:434px" %)
853		-|(% style="width:162px" %)Query|(% style="width:318px" %)qry: ReportingTaxonomyQueryType|(% style="width:434px" %)
	849	+Element Documentation:
854	854
	851	+|**Name**|**Type**|**Documentation**
	852	+|Header|BasicHeaderType|
	853	+|Query|qry: ReportingTaxonomyQue ryType|
	854	+
855	855	**StructureSetQueryType: **StructureSetQueryType defines the structure of a structure set query message.
856	856
857	857	Derivation:
858	858
859		-* //MessageType// (restriction)
860		-** StructureSetQueryType
	859	+//MessageType// (restriction)
	860	+ StructureSetQueryType
861	861
862	862	Content:
863	863
864		-* Header, Query
865		-* Element Documentation:
	864	+Header, Query
866	866
867		-(% style="width:896.294px" %)
868		-|(% style="width:182px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:417px" %)**Documentation**
869		-|(% style="width:182px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:417px" %)
870		-|(% style="width:182px" %)Query|(% style="width:294px" %)qry: StructureSetQueryType|(% style="width:417px" %)
	866	+Element Documentation:
871	871
	868	+|**Name**|**Type**|**Documentation**
	869	+|Header|BasicHeaderType|
	870	+|Query|qry: StructureSetQueryTyp e|
	871	+
872	872	**ProcessQueryType: **CategorizationQueryType defines the structure of a categorization query message.
873	873
874	874	Derivation:
875	875
876		-* //MessageType// (restriction)
877		-** ProcessQueryType
	876	+//MessageType// (restriction)
	877	+ ProcessQueryType
878	878
879	879	Content:
880	880
881		-* Header, Query
882		-* Element Documentation:
	881	+Header, Query
883	883
884		-(% style="width:907.294px" %)
885		-|(% style="width:189px" %)**Name**|(% style="width:394px" %)**Type**|(% style="width:321px" %)**Documentation**
886		-|(% style="width:189px" %)Header|(% style="width:394px" %)BasicHeaderType|(% style="width:321px" %)
887		-|(% style="width:189px" %)Query|(% style="width:394px" %)qry:ProcessQueryType|(% style="width:321px" %)
	883	+Element Documentation:
888	888
	885	+|**Name**|**Type**|**Documentation**
	886	+|Header|BasicHeaderType|
	887	+|Query|qry:ProcessQueryType|
	888	+
889	889	**CategorisationQueryType: **CategorisationQueryType defines the structure of a categorisation query message.
890	890
891	891	Derivation:
892	892
893		-* //MessageType// (restriction)
894		-** CategorisationQueryType
	893	+//MessageType// (restriction)
	894	+ CategorisationQueryType
895	895
896	896	Content:
897	897
898		-* Header, Query
899		-* Element Documentation:
	898	+Header, Query
900	900
901		-(% style="width:897.294px" %)
902		-|(% style="width:230px" %)**Name**|(% style="width:300px" %)**Type**|(% style="width:363px" %)**Documentation**
903		-|(% style="width:230px" %)Header|(% style="width:300px" %)BasicHeaderType|(% style="width:363px" %)
904		-|(% style="width:230px" %)Query|(% style="width:300px" %)qry: CategorisationQueryType|(% style="width:363px" %)
	900	+Element Documentation:
905	905
	902	+|**Name**|**Type**|**Documentation**
	903	+|Header|BasicHeaderType|
	904	+|Query|qry: CategorisationQueryT ype|
	905	+
906	906	**ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a provision agreement query message.
907	907
908	908	Derivation:
909	909
910		-* //MessageType// (restriction)
911		-** ProvisionAgreementQueryType
	910	+//MessageType// (restriction)
	911	+ ProvisionAgreementQueryType
912	912
913	913	Content:
914	914
915		-* Header, Query
916		-* Element Documentation:
	915	+Header, Query
917	917
918		-(% style="width:902.294px" %)
919		-|(% style="width:142px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:418px" %)**Documentation**
920		-|(% style="width:142px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:418px" %)
921		-|(% style="width:142px" %)Query|(% style="width:339px" %)qry: ProvisionAgreementQueryType|(% style="width:418px" %)
	917	+Element Documentation:
922	922
	919	+|**Name**|**Type**|**Documentation**
	920	+|Header|BasicHeaderType|
	921	+|Query|qry: ProvisionAgreementQu eryType|
	922	+
923	923	**ConstraintQueryType: **ConstraintQueryType defines the structure of a constraint query message.
924	924
925	925	Derivation:
926	926
927		-* //MessageType// (restriction)
928		-** ConstraintQueryType
	927	+//MessageType// (restriction)
	928	+ ConstraintQueryType
929	929
930	930	Content:
931	931
932		-* Header, Query
933		-* Element Documentation:
	932	+Header, Query
934	934
935		-(% style="width:902.294px" %)
936		-|(% style="width:167px" %)**Name**|(% style="width:287px" %)**Type**|(% style="width:445px" %)**Documentation**
937		-|(% style="width:167px" %)Header|(% style="width:287px" %)BasicHeaderType|(% style="width:445px" %)
938		-|(% style="width:167px" %)Query|(% style="width:287px" %)qry: ConstraintQueryType|(% style="width:445px" %)
	934	+Element Documentation:
939	939
	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
	944	+//MessageType// (restriction)
	945	+ TransformationSchemeQueryType
946	946
947	947	Content:
948	948
949		-* Header, Query
950		-* Element Documentation:
	949	+Header, Query
951	951
952		-(% style="width:833.294px" %)
953		-|(% style="width:165px" %)**Name**|(% style="width:325px" %)**Type**|(% style="width:340px" %)**Documentation**
954		-|(% style="width:165px" %)Header|(% style="width:325px" %)BasicHeaderType|(% style="width:340px" %)
955		-|(% style="width:165px" %)Query|(% style="width:325px" %)qry: TransformationSchemeQueryType|(% style="width:340px" %)
	951	+Element Documentation:
956	956
	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
	961	+//MessageType// (restriction)
	962	+ VtlMappingSchemeQueryType
963	963
964	964	Content:
965	965
966		-* Header, Query
967		-* Element Documentation:
	966	+Header, Query
968	968
969		-(% style="width:843.294px" %)
970		-|(% style="width:164px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:373px" %)**Documentation**
971		-|(% style="width:164px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:373px" %)
972		-|(% style="width:164px" %)Query|(% style="width:303px" %)qry: VtlMappingSchemeQueryType|(% style="width:373px" %)
	968	+Element Documentation:
973	973
	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
	978	+//MessageType// (restriction)
	979	+ NamePersonalisationSchemeQueryType
980	980
981	981	Content:
982	982
983		-* Header, Query
984		-* Element Documentation:
	983	+Header, Query
985	985
986		-(% style="width:895.294px" %)
987		-|(% style="width:186px" %)**Name**|(% style="width:363px" %)**Type**|(% style="width:343px" %)**Documentation**
988		-|(% style="width:186px" %)Header|(% style="width:363px" %)BasicHeaderType|(% style="width:343px" %)
989		-|(% style="width:186px" %)Query|(% style="width:363px" %)qry: NamePersonalisationSchemeQueryType|(% style="width:343px" %)
	985	+Element Documentation:
990	990
	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
	995	+//MessageType// (restriction)
	996	+ RulesetSchemeQueryType
997	997
998	998	Content:
999	999
1000		-* Header, Query
1001		-* Element Documentation:
	1000	+Header, Query
1002	1002
1003		-(% style="width:886.294px" %)
1004		-|(% style="width:152px" %)**Name**|(% style="width:311px" %)**Type**|(% style="width:420px" %)**Documentation**
1005		-|(% style="width:152px" %)Header|(% style="width:311px" %)BasicHeaderType|(% style="width:420px" %)
1006		-|(% style="width:152px" %)Query|(% style="width:311px" %)qry: RulesetSchemeQueryType|(% style="width:420px" %)
	1002	+Element Documentation:
1007	1007
	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
	1012	+//MessageType// (restriction)
	1013	+ UserDefinedOperatorSchemeQueryType
1014	1014
1015	1015	Content:
1016	1016
1017		-* Header, Query
1018		-* Element Documentation:
	1017	+Header, Query
1019	1019
1020		-(% style="width:866.294px" %)
1021		-|(% style="width:174px" %)**Name**|(% style="width:358px" %)**Type**|(% style="width:331px" %)**Documentation**
1022		-|(% style="width:174px" %)Header|(% style="width:358px" %)BasicHeaderType|(% style="width:331px" %)
1023		-|(% style="width:174px" %)Query|(% style="width:358px" %)qry: UserDefinedOperatorSchemeQueryType|(% style="width:331px" %)
	1019	+Element Documentation:
1024	1024
	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		-** CustomTypeSchemeQueryType
	1029	+//MessageType// (restriction)
	1030	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] CustomTypeSchemeQueryType
1031	1031
1032	1032	Content:
1033	1033
1034		-* Header, Query
1035		-* Element Documentation:
	1034	+Header, Query
1036	1036
1037		-(% style="width:828.294px" %)
1038		-|(% style="width:200px" %)**Name**|(% style="width:308px" %)**Type**|(% style="width:317px" %)**Documentation**
1039		-|(% style="width:200px" %)Header|(% style="width:308px" %)BasicHeaderType|(% style="width:317px" %)
1040		-|(% style="width:200px" %)Query|(% style="width:308px" %)qry: CustomTypeSchemeQueryType|(% style="width:317px" %)
	1036	+Element Documentation:
1041	1041
	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+
1047		-* Element Documentation:
	1046	+ErrorMessage+
1048	1048
1049		-(% style="width:899.294px" %)
1050		-|**Name**|**Type**|(% style="width:546px" %)**Documentation**
1051		-|ErrorMessage|com: CodedStatusMessageTy pe|(% style="width:546px" %)ErrorMessage contains the error message. It can occur multiple times to communicate message for multiple errors, or to communicate the error message in parallel languages. If both messages for multiple errors and parallel language messages are used, then each error message should be given a code in order to distinguish message for unique errors.
	1048	+Element Documentation:
1052	1052
	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,30 +1058,29 @@
1058	1058
1059	1059	Element Documentation:
1060	1060
1061		-(% style="width:891.294px" %)
1062		-|**Name**|**Type**|(% style="width:552px" %)**Documentation**
1063		-|ID|com:IDType|(% style="width:552px" %)ID identifies an identification for the message, assigned by the sender.
1064		-|Test|xs:boolean|(% style="width:552px" %)Test indicates whether the message is for test purposes or not.
1065		-|Prepared|HeaderTimeType|(% style="width:552px" %)Prepared is the date the message was prepared.
1066		-|Sender|SenderType|(% style="width:552px" %)Sender is information about the party that is transmitting the message.
1067		-|Receiver|PartyType|(% style="width:552px" %)Receiver is information about the party that is the intended recipient of the message.
1068		-|com:Name|com:TextType|(% style="width:552px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1069		-|Structure|//com: PayloadStructureType//|(% style="width:552px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1070		-|DataProvider|com: DataProviderReferenceType|(% style="width:552px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1071		-|DataSetAction|com:ActionType|(% style="width:552px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1072		-|DataSetID|com:IDType|(% style="width:552px" %)DataSetID provides an identifier for a contained data set.
1073		-|Extracted|xs:dateTime|(% style="width:552px" %)Extracted is a time-stamp from the system rendering the data.
1074		-|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1075		-|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1076		-|EmbargoDate|xs:dateTime|(% style="width:552px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1077		-|Source|com:TextType|(% style="width:552px" %)Source provides human-readable information about the source of the data.
	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.
1078	1078
1079	1079	**StructureHeaderType: **StructureHeaderType defines the structure for structural metadata messages.
1080	1080
1081	1081	Derivation:
1082	1082
1083		-* //BaseHeaderType// (restriction)
1084		-** StructureHeaderType
	1082	+//BaseHeaderType// (restriction)
	1083	+ StructureHeaderType
1085	1085
1086	1086	Content:
1087	1087
...	...	@@ -1089,22 +1089,21 @@
1089	1089
1090	1090	Element Documentation:
1091	1091
1092		-(% style="width:1099.29px" %)
1093		-|**Name**|(% style="width:224px" %)**Type**|(% style="width:663px" %)**Documentation**
1094		-|ID|(% style="width:224px" %)com:IDType|(% style="width:663px" %)ID identifies an identification for the message, assigned by the sender.
1095		-|Test|(% style="width:224px" %)xs:boolean|(% style="width:663px" %)Test indicates whether the message is for test purposes or not.
1096		-|Prepared|(% style="width:224px" %)HeaderTimeType|(% style="width:663px" %)Prepared is the date the message was prepared.
1097		-|Sender|(% style="width:224px" %)SenderType|(% style="width:663px" %)Sender is information about the party that is transmitting the message.
1098		-|Receiver|(% style="width:224px" %)PartyType|(% style="width:663px" %)Receiver is information about the party that is the intended recipient of the message.
1099		-|com:Name|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1100		-|Source|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Source provides human-readable information about the source of the data.
	1091	+|**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.
1101	1101
1102	1102	**GenericDataHeaderType: **GenericDataHeaderType defines the header structure for a generic data message.
1103	1103
1104	1104	Derivation:
1105	1105
1106		-* //BaseHeaderType// (restriction)
1107		-** GenericDataHeaderType
	1104	+//BaseHeaderType// (restriction)
	1105	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataHeaderType
1108	1108
1109	1109	Content:
1110	1110
...	...	@@ -1112,31 +1112,30 @@
1112	1112
1113	1113	Element Documentation:
1114	1114
1115		-(% style="width:895.294px" %)
1116		-|**Name**|**Type**|(% style="width:556px" %)**Documentation**
1117		-|ID|com:IDType|(% style="width:556px" %)ID identifies an identification for the message, assigned by the sender.
1118		-|Test|xs:boolean|(% style="width:556px" %)Test indicates whether the message is for test purposes or not.
1119		-|Prepared|HeaderTimeType|(% style="width:556px" %)Prepared is the date the message was prepared.
1120		-|Sender|SenderType|(% style="width:556px" %)Sender is information about the party that is transmitting the message.
1121		-|Receiver|PartyType|(% style="width:556px" %)Receiver is information about the party that is the intended recipient of the message.
1122		-|com:Name|com:TextType|(% style="width:556px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1123		-|Structure|com: GenericDataStructureType|(% style="width:556px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1124		-|DataProvider|com: DataProviderReferenceType|(% style="width:556px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1125		-|DataSetAction|com:ActionType|(% style="width:556px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1126		-|DataSetID|com:IDType|(% style="width:556px" %)DataSetID provides an identifier for a contained data set.
1127		-|Extracted|xs:dateTime|(% style="width:556px" %)Extracted is a time-stamp from the system rendering the data.
1128		-|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1129		-|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1130		-|EmbargoDate|xs:dateTime|(% style="width:556px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1131		-|Source|com:TextType|(% style="width:556px" %)Source provides human-readable information about the source of the data.
	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.
1132	1132
1133	1133	**GenericTimeSeriesDataHeaderType: **GenericTimeSeriesDataHeaderType defines the header structure for a time series only generic data message.
1134	1134
1135	1135	Derivation:
1136	1136
1137		-* //BaseHeaderType// (restriction)
1138		-** GenericDataHeaderType (restriction)
1139		-*** GenericTimeSeriesDataHeaderType
	1134	+//BaseHeaderType// (restriction)
	1135	+ GenericDataHeaderType (restriction)
	1136	+ GenericTimeSeriesDataHeaderType
1140	1140
1141	1141	Content:
1142	1142
...	...	@@ -1144,30 +1144,29 @@
1144	1144
1145	1145	Element Documentation:
1146	1146
1147		-(% style="width:926.294px" %)
1148		-|**Name**|**Type**|(% style="width:497px" %)**Documentation**
1149		-|ID|com:IDType|(% style="width:497px" %)ID identifies an identification for the message, assigned by the sender.
1150		-|Test|xs:boolean|(% style="width:497px" %)Test indicates whether the message is for test purposes or not.
1151		-|Prepared|HeaderTimeType|(% style="width:497px" %)Prepared is the date the message was prepared.
1152		-|Sender|SenderType|(% style="width:497px" %)Sender is information about the party that is transmitting the message.
1153		-|Receiver|PartyType|(% style="width:497px" %)Receiver is information about the party that is the intended recipient of the message.
1154		-|com:Name|com:TextType|(% style="width:497px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1155		-|Structure|com: GenericTimeSeriesDataStructureType|(% style="width:497px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1156		-|DataProvider|com: DataProviderReferenceType|(% style="width:497px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1157		-|DataSetAction|com:ActionType|(% style="width:497px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1158		-|DataSetID|com:IDType|(% style="width:497px" %)DataSetID provides an identifier for a contained data set.
1159		-|Extracted|xs:dateTime|(% style="width:497px" %)Extracted is a time-stamp from the system rendering the data.
1160		-|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1161		-|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1162		-|EmbargoDate|xs:dateTime|(% style="width:497px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1163		-|Source|com:TextType|(% style="width:497px" %)Source provides human-readable information about the source of the data.
	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.
1164	1164
1165	1165	**StructureSpecificDataHeaderType: **StructureSpecificDataHeaderType defines the header structure for a structure specific data message.
1166	1166
1167	1167	Derivation:
1168	1168
1169		-* //BaseHeaderType// (restriction)
1170		-** StructureSpecificDataHeaderType
	1165	+//BaseHeaderType// (restriction)
	1166	+ StructureSpecificDataHeaderType
1171	1171
1172	1172	Content:
1173	1173
...	...	@@ -1175,31 +1175,30 @@
1175	1175
1176	1176	Element Documentation:
1177	1177
1178		-(% style="width:930.294px" %)
1179		-|**Name**|**Type**|(% style="width:578px" %)**Documentation**
1180		-|ID|com:IDType|(% style="width:578px" %)ID identifies an identification for the message, assigned by the sender.
1181		-|Test|xs:boolean|(% style="width:578px" %)Test indicates whether the message is for test purposes or not.
1182		-|Prepared|HeaderTimeType|(% style="width:578px" %)Prepared is the date the message was prepared.
1183		-|Sender|SenderType|(% style="width:578px" %)Sender is information about the party that is transmitting the message.
1184		-|Receiver|PartyType|(% style="width:578px" %)Receiver is information about the party that is the intended recipient of the message.
1185		-|com:Name|com:TextType|(% style="width:578px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1186		-|Structure|com: StructureSpecificDataStructureType|(% style="width:578px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1187		-|DataProvider|com: DataProviderReferenceType|(% style="width:578px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1188		-|DataSetAction|com:ActionType|(% style="width:578px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1189		-|DataSetID|com:IDType|(% style="width:578px" %)DataSetID provides an identifier for a contained data set.
1190		-|Extracted|xs:dateTime|(% style="width:578px" %)Extracted is a time-stamp from the system rendering the data.
1191		-|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1192		-|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1193		-|EmbargoDate|xs:dateTime|(% style="width:578px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1194		-|Source|com:TextType|(% style="width:578px" %)Source provides human-readable information about the source of the data.
	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.
1195	1195
1196	1196	**StructureSpecificTimeSeriesDataHeaderType: **StructureSpecificTimeSeriesDataHeaderType defines the header structure for a time series only structure specific data message.
1197	1197
1198	1198	Derivation:
1199	1199
1200		-* //BaseHeaderType// (restriction)
1201		-** StructureSpecificDataHeaderType (restriction)
1202		-*** StructureSpecificTimeSeriesDataHeaderType
	1195	+//BaseHeaderType// (restriction)
	1196	+ StructureSpecificDataHeaderType (restriction)
	1197	+ StructureSpecificTimeSeriesDataHeaderType
1203	1203
1204	1204	Content:
1205	1205
...	...	@@ -1207,30 +1207,29 @@
1207	1207
1208	1208	Element Documentation:
1209	1209
1210		-(% style="width:943.294px" %)
1211		-|**Name**|(% style="width:352px" %)**Type**|(% style="width:461px" %)**Documentation**
1212		-|ID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)ID identifies an identification for the message, assigned by the sender.
1213		-|Test|(% style="width:352px" %)xs:boolean|(% style="width:461px" %)Test indicates whether the message is for test purposes or not.
1214		-|Prepared|(% style="width:352px" %)HeaderTimeType|(% style="width:461px" %)Prepared is the date the message was prepared.
1215		-|Sender|(% style="width:352px" %)SenderType|(% style="width:461px" %)Sender is information about the party that is transmitting the message.
1216		-|Receiver|(% style="width:352px" %)PartyType|(% style="width:461px" %)Receiver is information about the party that is the intended recipient of the message.
1217		-|com:Name|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1218		-|Structure|(% style="width:352px" %)com: StructureSpecificDataTimeSeriesStructureType|(% style="width:461px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1219		-|DataProvider|(% style="width:352px" %)com: DataProviderReferenceType|(% style="width:461px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1220		-|DataSetAction|(% style="width:352px" %)com:ActionType|(% style="width:461px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1221		-|DataSetID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)DataSetID provides an identifier for a contained data set.
1222		-|Extracted|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)Extracted is a time-stamp from the system rendering the data.
1223		-|ReportingBegin|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1224		-|ReportingEnd|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1225		-|EmbargoDate|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1226		-|Source|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Source provides human-readable information about the source of the data.
	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.
1227	1227
1228	1228	**GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic reference metadata.
1229	1229
1230	1230	Derivation:
1231	1231
1232		-* //BaseHeaderType// (restriction)
1233		-** GenericMetadataHeaderType
	1226	+//BaseHeaderType// (restriction)
	1227	+ GenericMetadataHeaderType
1234	1234
1235	1235	Content:
1236	1236
...	...	@@ -1238,27 +1238,26 @@
1238	1238
1239	1239	Element Documentation:
1240	1240
1241		-(% style="width:928.294px" %)
1242		-|**Name**|**Type**|(% style="width:554px" %)**Documentation**
1243		-|ID|com:IDType|(% style="width:554px" %)ID identifies an identification for the message, assigned by the sender.
1244		-|Test|xs:boolean|(% style="width:554px" %)Test indicates whether the message is for test purposes or not.
1245		-|Prepared|HeaderTimeType|(% style="width:554px" %)Prepared is the date the message was prepared.
1246		-|Sender|SenderType|(% style="width:554px" %)Sender is information about the party that is transmitting the message.
1247		-|Receiver|PartyType|(% style="width:554px" %)Receiver is information about the party that is the intended recipient of the message.
1248		-|com:Name|com:TextType|(% style="width:554px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1249		-|Structure|com: GenericMetadataStructureType|(% style="width:554px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1250		-|DataProvider|com: DataProviderReferenceType|(% style="width:554px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1251		-|DataSetAction|com:ActionType|(% style="width:554px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1252		-|DataSetID|com:IDType|(% style="width:554px" %)DataSetID provides an identifier for a contained data set.
1253		-|Extracted|xs:dateTime|(% style="width:554px" %)Extracted is a time-stamp from the system rendering the data.
1254		-|Source|com:TextType|(% style="width:554px" %)Source provides human-readable information about the source of the data.
	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.
1255	1255
1256	1256	**StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for metadata structure definition specific reference metadata messages.
1257	1257
1258	1258	Derivation:
1259	1259
1260		-* //BaseHeaderType// (restriction)
1261		-** StructureSpecificMetadataHeaderType
	1253	+//BaseHeaderType// (restriction)
	1254	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType
1262	1262
1263	1263	Content:
1264	1264
...	...	@@ -1266,27 +1266,26 @@
1266	1266
1267	1267	Element Documentation:
1268	1268
1269		-(% style="width:996.294px" %)
1270		-|**Name**|**Type**|(% style="width:557px" %)**Documentation**
1271		-|ID|com:IDType|(% style="width:557px" %)ID identifies an identification for the message, assigned by the sender.
1272		-|Test|xs:boolean|(% style="width:557px" %)Test indicates whether the message is for test purposes or not.
1273		-|Prepared|HeaderTimeType|(% style="width:557px" %)Prepared is the date the message was prepared.
1274		-|Sender|SenderType|(% style="width:557px" %)Sender is information about the party that is transmitting the message.
1275		-|Receiver|PartyType|(% style="width:557px" %)Receiver is information about the party that is the intended recipient of the message.
1276		-|com:Name|com:TextType|(% style="width:557px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1277		-|Structure|com: StructureSpecificMetadataStructureType|(% style="width:557px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1278		-|DataProvider|com: DataProviderReferenceType|(% style="width:557px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1279		-|DataSetAction|com:ActionType|(% style="width:557px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1280		-|DataSetID|com:IDType|(% style="width:557px" %)DataSetID provides an identifier for a contained data set.
1281		-|Extracted|xs:dateTime|(% style="width:557px" %)Extracted is a time-stamp from the system rendering the data.
1282		-|Source|com:TextType|(% style="width:557px" %)Source provides human-readable information about the source of the data.
	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.
1283	1283
1284	1284	**BasicHeaderType: **BasicHeaderType defines the most basic header information used in simple message exchanges.
1285	1285
1286	1286	Derivation:
1287	1287
1288		-* //BaseHeaderType// (restriction)
1289		-** BasicHeaderType
	1280	+//BaseHeaderType// (restriction)
	1281	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType
1290	1290
1291	1291	Content:
1292	1292
...	...	@@ -1294,13 +1294,12 @@
1294	1294
1295	1295	Element Documentation:
1296	1296
1297		-(% style="width:903.294px" %)
1298		-|**Name**|(% style="width:236px" %)**Type**|(% style="width:457px" %)**Documentation**
1299		-|ID|(% style="width:236px" %)com:IDType|(% style="width:457px" %)ID identifies an identification for the message, assigned by the sender.
1300		-|Test|(% style="width:236px" %)xs:boolean|(% style="width:457px" %)Test indicates whether the message is for test purposes or not.
1301		-|Prepared|(% style="width:236px" %)HeaderTimeType|(% style="width:457px" %)Prepared is the date the message was prepared.
1302		-|Sender|(% style="width:236px" %)SenderType|(% style="width:457px" %)Sender is information about the party that is transmitting the message.
1303		-|Receiver|(% style="width:236px" %)PartyType|(% style="width:457px" %)Receiver is information about the party that is the intended recipient of the message.
	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.
1304	1304
1305	1305	**PartyType: **PartyType defines the information which is sent about various parties such as senders and receivers of messages.
1306	1306
...	...	@@ -1314,23 +1314,21 @@
1314	1314
1315	1315	Attribute Documentation:
1316	1316
1317		-(% style="width:739.294px" %)
1318		-|(% style="width:125px" %)**Name**|(% style="width:190px" %)**Type**|(% style="width:421px" %)**Documentation**
1319		-|(% style="width:125px" %)id|(% style="width:190px" %)com:IDType|(% style="width:421px" %)The id attribute holds the identification of the party.
	1308	+|**Name**|**Type**|**Documentation**
	1309	+|id|com:IDType|The id attribute holds the identification of the party.
1320	1320
1321	1321	Element Documentation:
1322	1322
1323		-(% style="width:751.294px" %)
1324		-|(% style="width:134px" %)**Name**|(% style="width:183px" %)**Type**|(% style="width:431px" %)**Documentation**
1325		-|(% style="width:134px" %)com:Name|(% style="width:183px" %)com:TextType|(% style="width:431px" %)Name is a human-readable name of the party.
1326		-|(% style="width:134px" %)Contact|(% style="width:183px" %)ContactType|(% style="width:431px" %)Contact provides contact information for the party in regard to the transmission of the message.
	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.
1327	1327
1328	1328	**SenderType: **SenderType extends the basic party structure to add an optional time zone declaration.
1329	1329
1330	1330	Derivation:
1331	1331
1332		-* PartyType (extension)
1333		-** SenderType
	1321	+PartyType (extension)
	1322	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType
1334	1334
1335	1335	Attributes:
1336	1336
...	...	@@ -1342,9 +1342,8 @@
1342	1342
1343	1343	Attribute Documentation:
1344	1344
1345		-(% style="width:824.294px" %)
1346		-|(% style="width:177px" %)**Name**|(% style="width:241px" %)**Type**|(% style="width:403px" %)**Documentation**
1347		-|(% style="width:177px" %)id|(% style="width:241px" %)com:IDType|(% style="width:403px" %)The id attribute holds the identification of the party.
	1334	+|**Name**|**Type**|**Documentation**
	1335	+|id|com:IDType|The id attribute holds the identification of the party.
1348	1348
1349	1349	Element Documentation:
1350	1350