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
-
... ... @@ -177,8 +177,8 @@ 177 177 178 178 Derivation: 179 179 180 -//MessageType// (restriction) 181 - StructureType 180 +* //MessageType// (restriction) 181 +** StructureType 182 182 183 183 Content: 184 184 ... ... @@ -196,8 +196,8 @@ 196 196 197 197 Derivation: 198 198 199 -//MessageType// (restriction) 200 - GenericDataType 199 +* //MessageType// (restriction) 200 +** GenericDataType 201 201 202 202 Content: 203 203 ... ... @@ -347,9 +347,10 @@ 347 347 348 348 Content: 349 349 350 -* Header, SubmitRegistrationsRequest 351 -* Element Documentation: 350 +Header, SubmitRegistrationsRequest 352 352 352 +Element Documentation: 353 + 353 353 (% style="width:844.294px" %) 354 354 |**Name**|**Type**|(% style="width:377px" %)**Documentation** 355 355 |Header|BasicHeaderType|(% style="width:377px" %) ... ... @@ -365,9 +365,10 @@ 365 365 366 366 Content: 367 367 368 -* Header, SubmitRegistrationsResponse, ftr:Footer? 369 -* Element Documentation: 369 +Header, SubmitRegistrationsResponse, ftr:Footer? 370 370 371 +Element Documentation: 372 + 371 371 (% style="width:847.294px" %) 372 372 |**Name**|(% style="width:210px" %)**Type**|(% style="width:408px" %)**Documentation** 373 373 |Header|(% style="width:210px" %)BasicHeaderType|(% style="width:408px" %) ... ... @@ -384,9 +384,10 @@ 384 384 385 385 Content: 386 386 387 -* Header, QueryRegistrationRequest 388 -* Element Documentation: 389 +Header, QueryRegistrationRequest 389 389 391 +Element Documentation: 392 + 390 390 (% style="width:847.294px" %) 391 391 |**Name**|**Type**|(% style="width:397px" %)**Documentation** 392 392 |Header|BasicHeaderType|(% style="width:397px" %) ... ... @@ -441,9 +441,10 @@ 441 441 442 442 Content: 443 443 444 -* Header, SubmitStructureResponse, ftr:Footer? 445 -* Element Documentation: 447 +Header, SubmitStructureResponse, ftr:Footer? 446 446 449 +Element Documentation: 450 + 447 447 (% style="width:835.294px" %) 448 448 |**Name**|(% style="width:246px" %)**Type**|(% style="width:366px" %)**Documentation** 449 449 |Header|(% style="width:246px" %)BasicHeaderType|(% style="width:366px" %) ... ... @@ -460,9 +460,10 @@ 460 460 461 461 Content: 462 462 463 -* Header, SubmitSubscriptionsRequest 464 -* Element Documentation: 467 +Header, SubmitSubscriptionsRequest 465 465 469 +Element Documentation: 470 + 466 466 (% style="width:832.294px" %) 467 467 |**Name**|(% style="width:227px" %)**Type**|(% style="width:319px" %)**Documentation** 468 468 |Header|(% style="width:227px" %)BasicHeaderType|(% style="width:319px" %) ... ... @@ -478,9 +478,10 @@ 478 478 479 479 Content: 480 480 481 -* Header, SubmitSubscriptionsResponse, ftr:Footer? 482 -* Element Documentation: 486 +Header, SubmitSubscriptionsResponse, ftr:Footer? 483 483 488 +Element Documentation: 489 + 484 484 (% style="width:843.294px" %) 485 485 |**Name**|**Type**|(% style="width:362px" %)**Documentation** 486 486 |Header|BasicHeaderType|(% style="width:362px" %) ... ... @@ -497,9 +497,10 @@ 497 497 498 498 Content: 499 499 500 -* Header, QuerySubscriptionRequest 501 -* Element Documentation: 506 +Header, QuerySubscriptionRequest 502 502 508 +Element Documentation: 509 + 503 503 (% style="width:839.294px" %) 504 504 |(% style="width:230px" %)**Name**|(% style="width:254px" %)**Type**|(% style="width:352px" %)**Documentation** 505 505 |(% style="width:230px" %)Header|(% style="width:254px" %)BasicHeaderType|(% style="width:352px" %) ... ... @@ -515,9 +515,10 @@ 515 515 516 516 Content: 517 517 518 -* Header, QuerySubscriptionResponse, ftr:Footer? 519 -* Element Documentation: 525 +Header, QuerySubscriptionResponse, ftr:Footer? 520 520 527 +Element Documentation: 528 + 521 521 (% style="width:912.294px" %) 522 522 |**Name**|(% style="width:304px" %)**Type**|(% style="width:336px" %)**Documentation** 523 523 |Header|(% style="width:304px" %)BasicHeaderType|(% style="width:336px" %) ... ... @@ -534,9 +534,10 @@ 534 534 535 535 Content: 536 536 537 -* Header, NotifyRegistryEvent 538 -* Element Documentation: 545 +Header, NotifyRegistryEvent 539 539 547 +Element Documentation: 548 + 540 540 (% style="width:836.294px" %) 541 541 |**Name**|**Type**|(% style="width:473px" %)**Documentation** 542 542 |Header|BasicHeaderType|(% style="width:473px" %) ... ... @@ -551,9 +551,10 @@ 551 551 552 552 Content: 553 553 554 -* Header, Query 555 -* Element Documentation: 563 +Header, Query 556 556 565 +Element Documentation: 566 + 557 557 (% style="width:839.294px" %) 558 558 |(% style="width:244px" %)**Name**|(% style="width:262px" %)**Type**|(% style="width:330px" %)**Documentation** 559 559 |(% style="width:244px" %)Header|(% style="width:262px" %)BasicHeaderType|(% style="width:330px" %) ... ... @@ -569,9 +569,10 @@ 569 569 570 570 Content: 571 571 572 -* Header, Query 573 -* Element Documentation: 582 +Header, Query 574 574 584 +Element Documentation: 585 + 575 575 (% style="width:833.294px" %) 576 576 |(% style="width:213px" %)**Name**|(% style="width:243px" %)**Type**|(% style="width:374px" %)**Documentation** 577 577 |(% style="width:213px" %)Header|(% style="width:243px" %)BasicHeaderType|(% style="width:374px" %) ... ... @@ -588,9 +588,10 @@ 588 588 589 589 Content: 590 590 591 -* Header, Query 592 -* Element Documentation: 602 +Header, Query 593 593 604 +Element Documentation: 605 + 594 594 (% style="width:909.294px" %) 595 595 |(% style="width:221px" %)**Name**|(% style="width:305px" %)**Type**|(% style="width:380px" %)**Documentation** 596 596 |(% style="width:221px" %)Header|(% style="width:305px" %)BasicHeaderType|(% style="width:380px" %) ... ... @@ -606,9 +606,10 @@ 606 606 607 607 Content: 608 608 609 -* Header, Query 610 -* Element Documentation: 621 +Header, Query 611 611 623 +Element Documentation: 624 + 612 612 (% style="width:903.294px" %) 613 613 |(% style="width:189px" %)**Name**|(% style="width:259px" %)**Type**|(% style="width:452px" %)**Documentation** 614 614 |(% style="width:189px" %)Header|(% style="width:259px" %)BasicHeaderType|(% style="width:452px" %) ... ... @@ -623,9 +623,10 @@ 623 623 624 624 Content: 625 625 626 -* Header, Query 627 -* Element Documentation: 639 +Header, Query 628 628 641 +Element Documentation: 642 + 629 629 (% style="width:858.294px" %) 630 630 |(% style="width:138px" %)**Name**|(% style="width:246px" %)**Type**|(% style="width:471px" %)**Documentation** 631 631 |(% style="width:138px" %)Header|(% style="width:246px" %)BasicHeaderType|(% style="width:471px" %) ... ... @@ -640,9 +640,10 @@ 640 640 641 641 Content: 642 642 643 -* Header, Query 644 -* Element Documentation: 657 +Header, Query 645 645 659 +Element Documentation: 660 + 646 646 (% style="width:895.294px" %) 647 647 |(% style="width:185px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:413px" %)**Documentation** 648 648 |(% style="width:185px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:413px" %) ... ... @@ -657,9 +657,10 @@ 657 657 658 658 Content: 659 659 660 -* Header, Query 661 -* Element Documentation: 675 +Header, Query 662 662 677 +Element Documentation: 678 + 663 663 (% style="width:897.294px" %) 664 664 |(% style="width:166px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:447px" %)**Documentation** 665 665 |(% style="width:166px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:447px" %) ... ... @@ -674,9 +674,10 @@ 674 674 675 675 Content: 676 676 677 -* Header, Query 678 -* Element Documentation: 693 +Header, Query 679 679 695 +Element Documentation: 696 + 680 680 (% style="width:886.294px" %) 681 681 |(% style="width:223px" %)**Name**|(% style="width:255px" %)**Type**|(% style="width:405px" %)**Documentation** 682 682 |(% style="width:223px" %)Header|(% style="width:255px" %)BasicHeaderType|(% style="width:405px" %) ... ... @@ -691,9 +691,10 @@ 691 691 692 692 Content: 693 693 694 -* Header, Query 695 -* Element Documentation: 711 +Header, Query 696 696 713 +Element Documentation: 714 + 697 697 (% style="width:888.294px" %) 698 698 |(% style="width:176px" %)**Name**|(% style="width:260px" %)**Type**|(% style="width:449px" %)**Documentation** 699 699 |(% style="width:176px" %)Header|(% style="width:260px" %)BasicHeaderType|(% style="width:449px" %) ... ... @@ -708,9 +708,10 @@ 708 708 709 709 Content: 710 710 711 -* Header, Query 712 -* Element Documentation: 729 +Header, Query 713 713 731 +Element Documentation: 732 + 714 714 (% style="width:886.294px" %) 715 715 |(% style="width:199px" %)**Name**|(% style="width:296px" %)**Type**|(% style="width:388px" %)**Documentation** 716 716 |(% style="width:199px" %)Header|(% style="width:296px" %)BasicHeaderType|(% style="width:388px" %) ... ... @@ -725,9 +725,10 @@ 725 725 726 726 Content: 727 727 728 -* Header, Query 729 -* Element Documentation: 747 +Header, Query 730 730 749 +Element Documentation: 750 + 731 731 (% style="width:901.294px" %) 732 732 |(% style="width:202px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:393px" %)**Documentation** 733 733 |(% style="width:202px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:393px" %) ... ... @@ -742,9 +742,10 @@ 742 742 743 743 Content: 744 744 745 -* Header, Query 746 -* Element Documentation: 765 +Header, Query 747 747 767 +Element Documentation: 768 + 748 748 (% style="width:904.294px" %) 749 749 |(% style="width:226px" %)**Name**|(% style="width:275px" %)**Type**|(% style="width:400px" %)**Documentation** 750 750 |(% style="width:226px" %)Header|(% style="width:275px" %)BasicHeaderType|(% style="width:400px" %) ... ... @@ -759,9 +759,10 @@ 759 759 760 760 Content: 761 761 762 -* Header, Query 763 -* Element Documentation: 783 +Header, Query 764 764 785 +Element Documentation: 786 + 765 765 (% style="width:915.294px" %) 766 766 |(% style="width:196px" %)**Name**|(% style="width:347px" %)**Type**|(% style="width:369px" %)**Documentation** 767 767 |(% style="width:196px" %)Header|(% style="width:347px" %)BasicHeaderType|(% style="width:369px" %) ... ... @@ -776,9 +776,10 @@ 776 776 777 777 Content: 778 778 779 -* Header, Query 780 -* Element Documentation: 801 +Header, Query 781 781 803 +Element Documentation: 804 + 782 782 (% style="width:895.294px" %) 783 783 |(% style="width:222px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:331px" %)**Documentation** 784 784 |(% style="width:222px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:331px" %) ... ... @@ -1104,7 +1104,7 @@ 1104 1104 Derivation: 1105 1105 1106 1106 * //BaseHeaderType// (restriction) 1107 -* GenericDataHeaderType 1130 +** GenericDataHeaderType 1108 1108 1109 1109 Content: 1110 1110 ... ... @@ -1112,30 +1112,31 @@ 1112 1112 1113 1113 Element Documentation: 1114 1114 1115 -|**Name**|**Type**|**Documentation** 1116 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1117 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1118 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1119 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1120 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1121 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1122 -|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. 1123 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1124 -|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). 1125 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1126 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1127 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1128 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1129 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1130 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1138 +(% style="width:895.294px" %) 1139 +|**Name**|**Type**|(% style="width:556px" %)**Documentation** 1140 +|ID|com:IDType|(% style="width:556px" %)ID identifies an identification for the message, assigned by the sender. 1141 +|Test|xs:boolean|(% style="width:556px" %)Test indicates whether the message is for test purposes or not. 1142 +|Prepared|HeaderTimeType|(% style="width:556px" %)Prepared is the date the message was prepared. 1143 +|Sender|SenderType|(% style="width:556px" %)Sender is information about the party that is transmitting the message. 1144 +|Receiver|PartyType|(% style="width:556px" %)Receiver is information about the party that is the intended recipient of the message. 1145 +|com:Name|com:TextType|(% style="width:556px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1146 +|Structure|com: GenericDataStructureType|(% style="width:556px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1147 +|DataProvider|com: DataProviderReferenceType|(% style="width:556px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1148 +|DataSetAction|com:ActionType|(% style="width:556px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1149 +|DataSetID|com:IDType|(% style="width:556px" %)DataSetID provides an identifier for a contained data set. 1150 +|Extracted|xs:dateTime|(% style="width:556px" %)Extracted is a time-stamp from the system rendering the data. 1151 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data). 1152 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data). 1153 +|EmbargoDate|xs:dateTime|(% style="width:556px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1154 +|Source|com:TextType|(% style="width:556px" %)Source provides human-readable information about the source of the data. 1131 1131 1132 1132 **GenericTimeSeriesDataHeaderType: **GenericTimeSeriesDataHeaderType defines the header structure for a time series only generic data message. 1133 1133 1134 1134 Derivation: 1135 1135 1136 -//BaseHeaderType// (restriction) 1137 - GenericDataHeaderType (restriction)1138 - GenericTimeSeriesDataHeaderType1160 +* //BaseHeaderType// (restriction) 1161 +** GenericDataHeaderType (restriction) 1162 +*** GenericTimeSeriesDataHeaderType 1139 1139 1140 1140 Content: 1141 1141 ... ... @@ -1143,29 +1143,30 @@ 1143 1143 1144 1144 Element Documentation: 1145 1145 1146 -|**Name**|**Type**|**Documentation** 1147 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1148 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1149 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1150 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1151 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1152 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1153 -|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. 1154 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1155 -|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). 1156 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1157 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1158 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1159 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1160 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1161 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1170 +(% style="width:926.294px" %) 1171 +|**Name**|**Type**|(% style="width:497px" %)**Documentation** 1172 +|ID|com:IDType|(% style="width:497px" %)ID identifies an identification for the message, assigned by the sender. 1173 +|Test|xs:boolean|(% style="width:497px" %)Test indicates whether the message is for test purposes or not. 1174 +|Prepared|HeaderTimeType|(% style="width:497px" %)Prepared is the date the message was prepared. 1175 +|Sender|SenderType|(% style="width:497px" %)Sender is information about the party that is transmitting the message. 1176 +|Receiver|PartyType|(% style="width:497px" %)Receiver is information about the party that is the intended recipient of the message. 1177 +|com:Name|com:TextType|(% style="width:497px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1178 +|Structure|com: GenericTimeSeriesDataStructureType|(% style="width:497px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1179 +|DataProvider|com: DataProviderReferenceType|(% style="width:497px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1180 +|DataSetAction|com:ActionType|(% style="width:497px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1181 +|DataSetID|com:IDType|(% style="width:497px" %)DataSetID provides an identifier for a contained data set. 1182 +|Extracted|xs:dateTime|(% style="width:497px" %)Extracted is a time-stamp from the system rendering the data. 1183 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data). 1184 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data). 1185 +|EmbargoDate|xs:dateTime|(% style="width:497px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1186 +|Source|com:TextType|(% style="width:497px" %)Source provides human-readable information about the source of the data. 1162 1162 1163 1163 **StructureSpecificDataHeaderType: **StructureSpecificDataHeaderType defines the header structure for a structure specific data message. 1164 1164 1165 1165 Derivation: 1166 1166 1167 -//BaseHeaderType// (restriction) 1168 - StructureSpecificDataHeaderType1192 +* //BaseHeaderType// (restriction) 1193 +** StructureSpecificDataHeaderType 1169 1169 1170 1170 Content: 1171 1171 ... ... @@ -1173,30 +1173,31 @@ 1173 1173 1174 1174 Element Documentation: 1175 1175 1176 -|**Name**|**Type**|**Documentation** 1177 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1178 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1179 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1180 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1181 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1182 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1183 -|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. 1184 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1185 -|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). 1186 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1187 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1188 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1189 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1190 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1191 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1201 +(% style="width:930.294px" %) 1202 +|**Name**|**Type**|(% style="width:578px" %)**Documentation** 1203 +|ID|com:IDType|(% style="width:578px" %)ID identifies an identification for the message, assigned by the sender. 1204 +|Test|xs:boolean|(% style="width:578px" %)Test indicates whether the message is for test purposes or not. 1205 +|Prepared|HeaderTimeType|(% style="width:578px" %)Prepared is the date the message was prepared. 1206 +|Sender|SenderType|(% style="width:578px" %)Sender is information about the party that is transmitting the message. 1207 +|Receiver|PartyType|(% style="width:578px" %)Receiver is information about the party that is the intended recipient of the message. 1208 +|com:Name|com:TextType|(% style="width:578px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1209 +|Structure|com: StructureSpecificDataStructureType|(% style="width:578px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1210 +|DataProvider|com: DataProviderReferenceType|(% style="width:578px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1211 +|DataSetAction|com:ActionType|(% style="width:578px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1212 +|DataSetID|com:IDType|(% style="width:578px" %)DataSetID provides an identifier for a contained data set. 1213 +|Extracted|xs:dateTime|(% style="width:578px" %)Extracted is a time-stamp from the system rendering the data. 1214 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data). 1215 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data). 1216 +|EmbargoDate|xs:dateTime|(% style="width:578px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1217 +|Source|com:TextType|(% style="width:578px" %)Source provides human-readable information about the source of the data. 1192 1192 1193 1193 **StructureSpecificTimeSeriesDataHeaderType: **StructureSpecificTimeSeriesDataHeaderType defines the header structure for a time series only structure specific data message. 1194 1194 1195 1195 Derivation: 1196 1196 1197 -//BaseHeaderType// (restriction) 1198 - StructureSpecificDataHeaderType (restriction)1199 - StructureSpecificTimeSeriesDataHeaderType1223 +* //BaseHeaderType// (restriction) 1224 +** StructureSpecificDataHeaderType (restriction) 1225 +*** StructureSpecificTimeSeriesDataHeaderType 1200 1200 1201 1201 Content: 1202 1202 ... ... @@ -1204,29 +1204,30 @@ 1204 1204 1205 1205 Element Documentation: 1206 1206 1207 -|**Name**|**Type**|**Documentation** 1208 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1209 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1210 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1211 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1212 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1213 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1214 -|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. 1215 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1216 -|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). 1217 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1218 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1219 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1220 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1221 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1222 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1233 +(% style="width:943.294px" %) 1234 +|**Name**|(% style="width:352px" %)**Type**|(% style="width:461px" %)**Documentation** 1235 +|ID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)ID identifies an identification for the message, assigned by the sender. 1236 +|Test|(% style="width:352px" %)xs:boolean|(% style="width:461px" %)Test indicates whether the message is for test purposes or not. 1237 +|Prepared|(% style="width:352px" %)HeaderTimeType|(% style="width:461px" %)Prepared is the date the message was prepared. 1238 +|Sender|(% style="width:352px" %)SenderType|(% style="width:461px" %)Sender is information about the party that is transmitting the message. 1239 +|Receiver|(% style="width:352px" %)PartyType|(% style="width:461px" %)Receiver is information about the party that is the intended recipient of the message. 1240 +|com:Name|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1241 +|Structure|(% style="width:352px" %)com: StructureSpecificDataTimeSeriesStructureType|(% style="width:461px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1242 +|DataProvider|(% style="width:352px" %)com: DataProviderReferenceType|(% style="width:461px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1243 +|DataSetAction|(% style="width:352px" %)com:ActionType|(% style="width:461px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1244 +|DataSetID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)DataSetID provides an identifier for a contained data set. 1245 +|Extracted|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)Extracted is a time-stamp from the system rendering the data. 1246 +|ReportingBegin|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data). 1247 +|ReportingEnd|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data). 1248 +|EmbargoDate|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1249 +|Source|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Source provides human-readable information about the source of the data. 1223 1223 1224 1224 **GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic reference metadata. 1225 1225 1226 1226 Derivation: 1227 1227 1228 -//BaseHeaderType// (restriction) 1229 - GenericMetadataHeaderType1255 +* //BaseHeaderType// (restriction) 1256 +** GenericMetadataHeaderType 1230 1230 1231 1231 Content: 1232 1232 ... ... @@ -1234,26 +1234,27 @@ 1234 1234 1235 1235 Element Documentation: 1236 1236 1237 -|**Name**|**Type**|**Documentation** 1238 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1239 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1240 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1241 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1242 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1243 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1244 -|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. 1245 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1246 -|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). 1247 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1248 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1249 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1264 +(% style="width:928.294px" %) 1265 +|**Name**|**Type**|(% style="width:554px" %)**Documentation** 1266 +|ID|com:IDType|(% style="width:554px" %)ID identifies an identification for the message, assigned by the sender. 1267 +|Test|xs:boolean|(% style="width:554px" %)Test indicates whether the message is for test purposes or not. 1268 +|Prepared|HeaderTimeType|(% style="width:554px" %)Prepared is the date the message was prepared. 1269 +|Sender|SenderType|(% style="width:554px" %)Sender is information about the party that is transmitting the message. 1270 +|Receiver|PartyType|(% style="width:554px" %)Receiver is information about the party that is the intended recipient of the message. 1271 +|com:Name|com:TextType|(% style="width:554px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1272 +|Structure|com: GenericMetadataStructureType|(% style="width:554px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1273 +|DataProvider|com: DataProviderReferenceType|(% style="width:554px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1274 +|DataSetAction|com:ActionType|(% style="width:554px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1275 +|DataSetID|com:IDType|(% style="width:554px" %)DataSetID provides an identifier for a contained data set. 1276 +|Extracted|xs:dateTime|(% style="width:554px" %)Extracted is a time-stamp from the system rendering the data. 1277 +|Source|com:TextType|(% style="width:554px" %)Source provides human-readable information about the source of the data. 1250 1250 1251 1251 **StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for metadata structure definition specific reference metadata messages. 1252 1252 1253 1253 Derivation: 1254 1254 1255 -//BaseHeaderType// (restriction) 1256 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureSpecificMetadataHeaderType1283 +* //BaseHeaderType// (restriction) 1284 +** StructureSpecificMetadataHeaderType 1257 1257 1258 1258 Content: 1259 1259 ... ... @@ -1261,26 +1261,27 @@ 1261 1261 1262 1262 Element Documentation: 1263 1263 1264 -|**Name**|**Type**|**Documentation** 1265 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1266 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1267 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1268 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1269 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1270 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1271 -|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. 1272 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1273 -|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). 1274 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1275 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1276 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1292 +(% style="width:996.294px" %) 1293 +|**Name**|**Type**|(% style="width:557px" %)**Documentation** 1294 +|ID|com:IDType|(% style="width:557px" %)ID identifies an identification for the message, assigned by the sender. 1295 +|Test|xs:boolean|(% style="width:557px" %)Test indicates whether the message is for test purposes or not. 1296 +|Prepared|HeaderTimeType|(% style="width:557px" %)Prepared is the date the message was prepared. 1297 +|Sender|SenderType|(% style="width:557px" %)Sender is information about the party that is transmitting the message. 1298 +|Receiver|PartyType|(% style="width:557px" %)Receiver is information about the party that is the intended recipient of the message. 1299 +|com:Name|com:TextType|(% style="width:557px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1300 +|Structure|com: StructureSpecificMetadataStructureType|(% style="width:557px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1301 +|DataProvider|com: DataProviderReferenceType|(% style="width:557px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1302 +|DataSetAction|com:ActionType|(% style="width:557px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1303 +|DataSetID|com:IDType|(% style="width:557px" %)DataSetID provides an identifier for a contained data set. 1304 +|Extracted|xs:dateTime|(% style="width:557px" %)Extracted is a time-stamp from the system rendering the data. 1305 +|Source|com:TextType|(% style="width:557px" %)Source provides human-readable information about the source of the data. 1277 1277 1278 1278 **BasicHeaderType: **BasicHeaderType defines the most basic header information used in simple message exchanges. 1279 1279 1280 1280 Derivation: 1281 1281 1282 -//BaseHeaderType// (restriction) 1283 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]BasicHeaderType1311 +* //BaseHeaderType// (restriction) 1312 +** BasicHeaderType 1284 1284 1285 1285 Content: 1286 1286 ... ... @@ -1288,12 +1288,13 @@ 1288 1288 1289 1289 Element Documentation: 1290 1290 1291 -|**Name**|**Type**|**Documentation** 1292 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1293 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1294 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1295 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1296 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1320 +(% style="width:903.294px" %) 1321 +|**Name**|(% style="width:236px" %)**Type**|(% style="width:457px" %)**Documentation** 1322 +|ID|(% style="width:236px" %)com:IDType|(% style="width:457px" %)ID identifies an identification for the message, assigned by the sender. 1323 +|Test|(% style="width:236px" %)xs:boolean|(% style="width:457px" %)Test indicates whether the message is for test purposes or not. 1324 +|Prepared|(% style="width:236px" %)HeaderTimeType|(% style="width:457px" %)Prepared is the date the message was prepared. 1325 +|Sender|(% style="width:236px" %)SenderType|(% style="width:457px" %)Sender is information about the party that is transmitting the message. 1326 +|Receiver|(% style="width:236px" %)PartyType|(% style="width:457px" %)Receiver is information about the party that is the intended recipient of the message. 1297 1297 1298 1298 **PartyType: **PartyType defines the information which is sent about various parties such as senders and receivers of messages. 1299 1299 ... ... @@ -1307,21 +1307,23 @@ 1307 1307 1308 1308 Attribute Documentation: 1309 1309 1310 -|**Name**|**Type**|**Documentation** 1311 -|id|com:IDType|The id attribute holds the identification of the party. 1340 +(% style="width:739.294px" %) 1341 +|(% style="width:125px" %)**Name**|(% style="width:190px" %)**Type**|(% style="width:421px" %)**Documentation** 1342 +|(% style="width:125px" %)id|(% style="width:190px" %)com:IDType|(% style="width:421px" %)The id attribute holds the identification of the party. 1312 1312 1313 1313 Element Documentation: 1314 1314 1315 -|**Name**|**Type**|**Documentation** 1316 -|com:Name|com:TextType|Name is a human-readable name of the party. 1317 -|Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message. 1346 +(% style="width:751.294px" %) 1347 +|(% style="width:134px" %)**Name**|(% style="width:183px" %)**Type**|(% style="width:431px" %)**Documentation** 1348 +|(% style="width:134px" %)com:Name|(% style="width:183px" %)com:TextType|(% style="width:431px" %)Name is a human-readable name of the party. 1349 +|(% style="width:134px" %)Contact|(% style="width:183px" %)ContactType|(% style="width:431px" %)Contact provides contact information for the party in regard to the transmission of the message. 1318 1318 1319 1319 **SenderType: **SenderType extends the basic party structure to add an optional time zone declaration. 1320 1320 1321 1321 Derivation: 1322 1322 1323 -PartyType (extension) 1324 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SenderType1355 +* PartyType (extension) 1356 +** SenderType 1325 1325 1326 1326 Attributes: 1327 1327 ... ... @@ -1333,8 +1333,9 @@ 1333 1333 1334 1334 Attribute Documentation: 1335 1335 1336 -|**Name**|**Type**|**Documentation** 1337 -|id|com:IDType|The id attribute holds the identification of the party. 1368 +(% style="width:824.294px" %) 1369 +|(% style="width:177px" %)**Name**|(% style="width:241px" %)**Type**|(% style="width:403px" %)**Documentation** 1370 +|(% style="width:177px" %)id|(% style="width:241px" %)com:IDType|(% style="width:403px" %)The id attribute holds the identification of the party. 1338 1338 1339 1339 Element Documentation: 1340 1340 ... ... @@ -1361,8 +1361,8 @@ 1361 1361 |URI|xs:anyURI|URI holds an information URL for the contact person. 1362 1362 |Email|xs:string|Email holds the email address for the contact person. 1363 1363 1364 -1. 1365 -11. 1397 +1. 1398 +11. 1366 1366 111. Simple Types 1367 1367 1368 1368 **HeaderTimeType: **Provides a union type of xs:date and xs:dateTime for the header fields in the message. ... ... @@ -1371,13 +1371,13 @@ 1371 1371 1372 1372 xs:dateTime, xs:date. 1373 1373 1374 -1. 1407 +1. 1375 1375 11. Message Footer Namespace 1376 1376 1377 1377 **http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer** 1378 1378 1379 -1. 1380 -11. 1412 +1. 1413 +11. 1381 1381 111. Summary 1382 1382 1383 1383 Referenced Namespaces: ... ... @@ -1392,14 +1392,14 @@ 1392 1392 2 Complex Types 1393 1393 1 Simple Type 1394 1394 1395 -1. 1396 -11. 1428 +1. 1429 +11. 1397 1397 111. Global Elements 1398 1398 1399 1399 **Footer (FooterType): **Footer is used to communicate information such as error and warnings after the payload of a message. 1400 1400 1401 -1. 1402 -11. 1434 +1. 1435 +11. 1403 1403 111. Complex Types 1404 1404 1405 1405 **FooterType: **FooterType describes the structure of a message footer. The footer is used to convey any error, information, or warning messages. This is to be used when the message has payload, but also needs to communicate additional information. If an error occurs and no payload is generated, an Error message should be returned. ... ... @@ -1418,8 +1418,8 @@ 1418 1418 Derivation: 1419 1419 1420 1420 com:StatusMessageType (restriction) 1421 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension)1422 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType1454 +[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension) 1455 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType 1423 1423 1424 1424 Attributes: 1425 1425 ... ... @@ -1440,8 +1440,8 @@ 1440 1440 |**Name**|**Type**|**Documentation** 1441 1441 |com:Text|com:TextType|Text contains the text of the message, in parallel language values. 1442 1442 1443 -1. 1444 -11. 1476 +1. 1477 +11. 1445 1445 111. Simple Types 1446 1446 1447 1447 **SeverityCodeType:**