Changes for page Part I. Message Namespace
Last modified by Artur on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -805,251 +805,251 @@ 805 805 806 806 Derivation: 807 807 808 -//MessageType// (restriction) 809 - 808 +* //MessageType// (restriction) 809 +** HierarchicalCodelistQueryType 810 810 811 811 Content: 812 812 813 -Header, Query 813 +* Header, Query 814 +* Element Documentation: 814 814 815 -Element Documentation: 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" %) 816 816 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 - 825 +* //MessageType// (restriction) 826 +** OrganisationSchemeQueryType 827 827 828 828 Content: 829 829 830 -Header, Query 830 +* Header, Query 831 +* Element Documentation: 831 831 832 -Element Documentation: 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" %) 833 833 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 - 842 +* //MessageType// (restriction) 843 +** ReportingTaxonomyQueryType 844 844 845 845 Content: 846 846 847 -Header, Query 847 +* Header, Query 848 +* Element Documentation: 848 848 849 -Element Documentation: 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" %) 850 850 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 - 859 +* //MessageType// (restriction) 860 +** StructureSetQueryType 861 861 862 862 Content: 863 863 864 -Header, Query 864 +* Header, Query 865 +* Element Documentation: 865 865 866 -Element Documentation: 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" %) 867 867 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 - 876 +* //MessageType// (restriction) 877 +** ProcessQueryType 878 878 879 879 Content: 880 880 881 -Header, Query 881 +* Header, Query 882 +* Element Documentation: 882 882 883 -Element Documentation: 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" %) 884 884 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 - 893 +* //MessageType// (restriction) 894 +** CategorisationQueryType 895 895 896 896 Content: 897 897 898 -Header, Query 898 +* Header, Query 899 +* Element Documentation: 899 899 900 -Element Documentation: 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" %) 901 901 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 - 910 +* //MessageType// (restriction) 911 +** ProvisionAgreementQueryType 912 912 913 913 Content: 914 914 915 -Header, Query 915 +* Header, Query 916 +* Element Documentation: 916 916 917 -Element Documentation: 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" %) 918 918 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 - 927 +* //MessageType// (restriction) 928 +** ConstraintQueryType 929 929 930 930 Content: 931 931 932 -Header, Query 932 +* Header, Query 933 +* Element Documentation: 933 933 934 -Element Documentation: 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" %) 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 - 944 +* //MessageType// (restriction) 945 +** TransformationSchemeQueryType 946 946 947 947 Content: 948 948 949 -Header, Query 949 +* Header, Query 950 +* Element Documentation: 950 950 951 -Element Documentation: 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" %) 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 - 961 +* //MessageType// (restriction) 962 +** VtlMappingSchemeQueryType 963 963 964 964 Content: 965 965 966 -Header, Query 966 +* Header, Query 967 +* Element Documentation: 967 967 968 -Element Documentation: 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" %) 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 - 978 +* //MessageType// (restriction) 979 +** NamePersonalisationSchemeQueryType 980 980 981 981 Content: 982 982 983 -Header, Query 983 +* Header, Query 984 +* Element Documentation: 984 984 985 -Element Documentation: 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" %) 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 - 995 +* //MessageType// (restriction) 996 +** RulesetSchemeQueryType 997 997 998 998 Content: 999 999 1000 -Header, Query 1000 +* Header, Query 1001 +* Element Documentation: 1001 1001 1002 -Element Documentation: 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" %) 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 - 1012 +* //MessageType// (restriction) 1013 +** UserDefinedOperatorSchemeQueryType 1014 1014 1015 1015 Content: 1016 1016 1017 -Header, Query 1017 +* Header, Query 1018 +* Element Documentation: 1018 1018 1019 -Element Documentation: 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" %) 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="-"]]CustomTypeSchemeQueryType1029 +* //MessageType// (restriction) 1030 +** CustomTypeSchemeQueryType 1031 1031 1032 1032 Content: 1033 1033 1034 -Header, Query 1034 +* Header, Query 1035 +* Element Documentation: 1035 1035 1036 -Element Documentation: 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" %) 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+ 1046 +* ErrorMessage+ 1047 +* Element Documentation: 1047 1047 1048 -Element Documentation: 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. 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. 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. 1077 1077 1078 1078 **StructureHeaderType: **StructureHeaderType defines the structure for structural metadata messages. 1079 1079 1080 1080 Derivation: 1081 1081 1082 -//BaseHeaderType// (restriction) 1083 - 1083 +* //BaseHeaderType// (restriction) 1084 +** 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. 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. 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="-"]]GenericDataHeaderType1106 +* //BaseHeaderType// (restriction) 1107 +** 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. 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. 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 - 1136 - 1137 +* //BaseHeaderType// (restriction) 1138 +** GenericDataHeaderType (restriction) 1139 +*** 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. 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. 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 - 1169 +* //BaseHeaderType// (restriction) 1170 +** 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. 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. 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 - 1197 - 1200 +* //BaseHeaderType// (restriction) 1201 +** StructureSpecificDataHeaderType (restriction) 1202 +*** 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. 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. 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 - 1232 +* //BaseHeaderType// (restriction) 1233 +** 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. 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. 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="-"]]StructureSpecificMetadataHeaderType1260 +* //BaseHeaderType// (restriction) 1261 +** 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. 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. 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="-"]]BasicHeaderType1288 +* //BaseHeaderType// (restriction) 1289 +** 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. 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. 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. 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. 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. 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. 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="-"]]SenderType1332 +* PartyType (extension) 1333 +** 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. 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. 1336 1336 1337 1337 Element Documentation: 1338 1338