Changes for page Part I. Message Namespace

Last modified by Artur on 2025/09/10 11:19

From version 3.26
edited by Helena
on 2025/06/23 17:29
Change comment: There is no comment for this version
To version 3.25
edited by Helena
on 2025/06/23 17:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1144,30 +1144,29 @@
1144 1144  
1145 1145  Element Documentation:
1146 1146  
1147 -(% style="width:926.294px" %)
1148 -|**Name**|**Type**|(% style="width:497px" %)**Documentation**
1149 -|ID|com:IDType|(% style="width:497px" %)ID identifies an identification for the message, assigned by the sender.
1150 -|Test|xs:boolean|(% style="width:497px" %)Test indicates whether the message is for test purposes or not.
1151 -|Prepared|HeaderTimeType|(% style="width:497px" %)Prepared is the date the message was prepared.
1152 -|Sender|SenderType|(% style="width:497px" %)Sender is information about the party that is transmitting the message.
1153 -|Receiver|PartyType|(% style="width:497px" %)Receiver is information about the party that is the intended recipient of the message.
1154 -|com:Name|com:TextType|(% style="width:497px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1155 -|Structure|com: GenericTimeSeriesDataStructureType|(% style="width:497px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1156 -|DataProvider|com: DataProviderReferenceType|(% style="width:497px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1157 -|DataSetAction|com:ActionType|(% style="width:497px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1158 -|DataSetID|com:IDType|(% style="width:497px" %)DataSetID provides an identifier for a contained data set.
1159 -|Extracted|xs:dateTime|(% style="width:497px" %)Extracted is a time-stamp from the system rendering the data.
1160 -|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1161 -|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1162 -|EmbargoDate|xs:dateTime|(% style="width:497px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1163 -|Source|com:TextType|(% style="width:497px" %)Source provides human-readable information about the source of the data.
1147 +|**Name**|**Type**|**Documentation**
1148 +|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1149 +|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1150 +|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1151 +|Sender|SenderType|Sender is information about the party that is transmitting the message.
1152 +|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1153 +|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1154 +|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.
1155 +|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1156 +|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).
1157 +|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1158 +|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1159 +|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1160 +|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1161 +|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1162 +|Source|com:TextType|Source provides human-readable information about the source of the data.
1164 1164  
1165 1165  **StructureSpecificDataHeaderType: **StructureSpecificDataHeaderType defines the header structure for a structure specific data message.
1166 1166  
1167 1167  Derivation:
1168 1168  
1169 -* //BaseHeaderType// (restriction)
1170 -** StructureSpecificDataHeaderType
1168 +//BaseHeaderType// (restriction)
1169 + StructureSpecificDataHeaderType
1171 1171  
1172 1172  Content:
1173 1173  
... ... @@ -1175,23 +1175,22 @@
1175 1175  
1176 1176  Element Documentation:
1177 1177  
1178 -(% style="width:930.294px" %)
1179 -|**Name**|**Type**|(% style="width:578px" %)**Documentation**
1180 -|ID|com:IDType|(% style="width:578px" %)ID identifies an identification for the message, assigned by the sender.
1181 -|Test|xs:boolean|(% style="width:578px" %)Test indicates whether the message is for test purposes or not.
1182 -|Prepared|HeaderTimeType|(% style="width:578px" %)Prepared is the date the message was prepared.
1183 -|Sender|SenderType|(% style="width:578px" %)Sender is information about the party that is transmitting the message.
1184 -|Receiver|PartyType|(% style="width:578px" %)Receiver is information about the party that is the intended recipient of the message.
1185 -|com:Name|com:TextType|(% style="width:578px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1186 -|Structure|com: StructureSpecificDataStructureType|(% style="width:578px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1187 -|DataProvider|com: DataProviderReferenceType|(% style="width:578px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1188 -|DataSetAction|com:ActionType|(% style="width:578px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1189 -|DataSetID|com:IDType|(% style="width:578px" %)DataSetID provides an identifier for a contained data set.
1190 -|Extracted|xs:dateTime|(% style="width:578px" %)Extracted is a time-stamp from the system rendering the data.
1191 -|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1192 -|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1193 -|EmbargoDate|xs:dateTime|(% style="width:578px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1194 -|Source|com:TextType|(% style="width:578px" %)Source provides human-readable information about the source of the data.
1177 +|**Name**|**Type**|**Documentation**
1178 +|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1179 +|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1180 +|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1181 +|Sender|SenderType|Sender is information about the party that is transmitting the message.
1182 +|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1183 +|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1184 +|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.
1185 +|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1186 +|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).
1187 +|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1188 +|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1189 +|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1190 +|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1191 +|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1192 +|Source|com:TextType|Source provides human-readable information about the source of the data.
1195 1195  
1196 1196  **StructureSpecificTimeSeriesDataHeaderType: **StructureSpecificTimeSeriesDataHeaderType defines the header structure for a time series only structure specific data message.
1197 1197