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
-
... ... @@ -159,7 +159,9 @@ 159 159 160 160 **Error (ErrorType): **Error is used to communicate that an error has occurred when responding to a request in an non-registry environment. The content will be a collection of error messages. 161 161 162 -=== 2.1.3 Complex Types === 162 +1. 163 +11. 164 +111. Complex Types 163 163 164 164 **//MessageType//: **MessageType is an abstract type which is used by all of the messages, to allow inheritance of common features. Every message consists of a mandatory header, followed by optional payload (which may occur multiple times), and finally an optional footer section for conveying error, warning, and informational messages. 165 165 ... ... @@ -178,7 +178,7 @@ 178 178 Derivation: 179 179 180 180 //MessageType// (restriction) 181 - StructureType 183 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureType 182 182 183 183 Content: 184 184 ... ... @@ -186,11 +186,10 @@ 186 186 187 187 Element Documentation: 188 188 189 -(% style="width:856.294px" %) 190 -|**Name**|(% style="width:210px" %)**Type**|(% style="width:455px" %)**Documentation** 191 -|Header|(% style="width:210px" %)StructureHeaderType|(% style="width:455px" %) 192 -|Structures|(% style="width:210px" %)str:StructuresType|(% style="width:455px" %) 193 -|ftr:Footer|(% style="width:210px" %)ftr:FooterType|(% style="width:455px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 191 +|**Name**|**Type**|**Documentation** 192 +|Header|StructureHeaderType| 193 +|Structures|str:StructuresType| 194 +|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 194 194 195 195 **GenericDataType: **GenericDataType defines the contents of a generic data message. 196 196 ... ... @@ -197,7 +197,7 @@ 197 197 Derivation: 198 198 199 199 //MessageType// (restriction) 200 - GenericDataType 201 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataType 201 201 202 202 Content: 203 203 ... ... @@ -205,19 +205,18 @@ 205 205 206 206 Element Documentation: 207 207 208 -(% style="width:847.294px" %) 209 -|**Name**|(% style="width:227px" %)**Type**|(% style="width:450px" %)**Documentation** 210 -|Header|(% style="width:227px" %)GenericDataHeaderTyp e|(% style="width:450px" %) 211 -|DataSet|(% style="width:227px" %)dat:DataSetType|(% style="width:450px" %) 212 -|ftr:Footer|(% style="width:227px" %)ftr:FooterType|(% style="width:450px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 209 +|**Name**|**Type**|**Documentation** 210 +|Header|GenericDataHeaderTyp e| 211 +|DataSet|dat:DataSetType| 212 +|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 213 213 214 214 **GenericTimeSeriesDataType: **GenericTimeSeriesDataType defines the structure of the generic time series data message. 215 215 216 216 Derivation: 217 217 218 - *//MessageType// (restriction)219 - **GenericDataType (restriction)220 - ***GenericTimeSeriesDataType218 +//MessageType// (restriction) 219 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataType (restriction) 220 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericTimeSeriesDataType 221 221 222 222 Content: 223 223 ... ... @@ -225,18 +225,17 @@ 225 225 226 226 Element Documentation: 227 227 228 -(% style="width:856.294px" %) 229 -|**Name**|(% style="width:239px" %)**Type**|(% style="width:458px" %)**Documentation** 230 -|Header|(% style="width:239px" %)GenericTimeSeriesDat aHeaderType|(% style="width:458px" %) 231 -|DataSet|(% style="width:239px" %)dat: TimeSeriesDataSetTyp e|(% style="width:458px" %) 232 -|ftr:Footer|(% style="width:239px" %)ftr:FooterType|(% style="width:458px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 228 +|**Name**|**Type**|**Documentation** 229 +|Header|GenericTimeSeriesDat aHeaderType| 230 +|DataSet|dat: TimeSeriesDataSetTyp e| 231 +|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 233 233 234 234 **StructureSpecificDataType: **StructureSpecificDataType defines the structure of the structure specific data message. Note that the data set payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known. 235 235 236 236 Derivation: 237 237 238 - *//MessageType// (restriction)239 - **StructureSpecificDataType237 +//MessageType// (restriction) 238 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificDataType 240 240 241 241 Content: 242 242 ... ... @@ -244,19 +244,18 @@ 244 244 245 245 Element Documentation: 246 246 247 -(% style="width:828.294px" %) 248 -|**Name**|(% style="width:247px" %)**Type**|(% style="width:420px" %)**Documentation** 249 -|Header|(% style="width:247px" %)StructureSpecificDat aHeaderType|(% style="width:420px" %) 250 -|DataSet|(% style="width:247px" %)//dsd:DataSetType//|(% style="width:420px" %) 251 -|ftr:Footer|(% style="width:247px" %)ftr:FooterType|(% style="width:420px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 246 +|**Name**|**Type**|**Documentation** 247 +|Header|StructureSpecificDat aHeaderType| 248 +|DataSet|//dsd:DataSetType//| 249 +|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 252 252 253 253 **StructureSpecificTimeSeriesDataType: **StructureSpecificTimeSeriesDataType defines the structure of the structure specific time series data message. 254 254 255 255 Derivation: 256 256 257 - *//MessageType// (restriction)258 - **StructureSpecificDataType (restriction)259 - ***StructureSpecificTimeSeriesDataType255 +//MessageType// (restriction) 256 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificDataType (restriction) 257 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificTimeSeriesDataType 260 260 261 261 Content: 262 262 ... ... @@ -264,18 +264,17 @@ 264 264 265 265 Element Documentation: 266 266 267 -(% style="width:839.294px" %) 268 -|**Name**|(% style="width:256px" %)**Type**|(% style="width:434px" %)**Documentation** 269 -|Header|(% style="width:256px" %)StructureSpecificTim eSeriesDataHeaderTyp e|(% style="width:434px" %) 270 -|DataSet|(% style="width:256px" %)//dsd: TimeSeriesDataSetTyp e//|(% style="width:434px" %) 271 -|ftr:Footer|(% style="width:256px" %)ftr:FooterType|(% style="width:434px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 265 +|**Name**|**Type**|**Documentation** 266 +|Header|StructureSpecificTim eSeriesDataHeaderTyp e| 267 +|DataSet|//dsd: TimeSeriesDataSetTyp e//| 268 +|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 272 272 273 273 **GenericMetadataType: **GenericMetadataType defines the contents of a generic metadata message. 274 274 275 275 Derivation: 276 276 277 - *//MessageType// (restriction)278 - **GenericMetadataType274 +//MessageType// (restriction) 275 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericMetadataType 279 279 280 280 Content: 281 281 ... ... @@ -283,18 +283,17 @@ 283 283 284 284 Element Documentation: 285 285 286 -(% style="width:836.294px" %) 287 -|(% style="width:181px" %)**Name**|(% style="width:225px" %)**Type**|(% style="width:427px" %)**Documentation** 288 -|(% style="width:181px" %)Header|(% style="width:225px" %)GenericMetadataHeade rType|(% style="width:427px" %) 289 -|(% style="width:181px" %)MetadataSet|(% style="width:225px" %)rep:MetadataSetType|(% style="width:427px" %) 290 -|(% style="width:181px" %)ftr:Footer|(% style="width:225px" %)ftr:FooterType|(% style="width:427px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 283 +|**Name**|**Type**|**Documentation** 284 +|Header|GenericMetadataHeade rType| 285 +|MetadataSet|rep:MetadataSetType| 286 +|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 291 291 292 292 **StructureSpecificMetadataType: **StructureSpecificMetadataType defines the structure of a structure specific metadata message. Note that the metadata set payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known. 293 293 294 294 Derivation: 295 295 296 - *//MessageType// (restriction)297 - **StructureSpecificMetadataType292 +//MessageType// (restriction) 293 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataType 298 298 299 299 Content: 300 300 ... ... @@ -302,18 +302,17 @@ 302 302 303 303 Element Documentation: 304 304 305 -(% style="width:841.294px" %) 306 -|(% style="width:160px" %)**Name**|(% style="width:250px" %)**Type**|(% style="width:428px" %)**Documentation** 307 -|(% style="width:160px" %)Header|(% style="width:250px" %)StructureSpecificMet adataHeaderType|(% style="width:428px" %) 308 -|(% style="width:160px" %)MetadataSet|(% style="width:250px" %)//msd:MetadataSetType//|(% style="width:428px" %) 309 -|(% style="width:160px" %)ftr:Footer|(% style="width:250px" %)ftr:FooterType|(% style="width:428px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 301 +|**Name**|**Type**|**Documentation** 302 +|Header|StructureSpecificMet adataHeaderType| 303 +|MetadataSet|//msd:MetadataSetType//| 304 +|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 310 310 311 311 **RegistryInterfaceType: **This is a type which describes a structure for holding all of the various dedicated registry interface message types. 312 312 313 313 Derivation: 314 314 315 - *//MessageType// (restriction)316 - **RegistryInterfaceType310 +//MessageType// (restriction) 311 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType 317 317 318 318 Content: 319 319 ... ... @@ -321,84 +321,83 @@ 321 321 322 322 Element Documentation: 323 323 324 -(% style="width:903.294px" %) 325 -|**Name**|**Type**|(% style="width:441px" %)**Documentation** 326 -|Header|BasicHeaderType|(% style="width:441px" %) 327 -|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:441px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services. 328 -|SubmitRegistrationsR esponse|ref: SubmitRegistrationsR esponseType|(% style="width:441px" %)SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service. 329 -|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:441px" %)QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys. 330 -|QueryRegistrationRes ponse|ref: QueryRegistrationRes ponseType|(% style="width:441px" %)QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned. 331 -|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:441px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information. 332 -|SubmitStructureRespo nse|ref: SubmitStructureRespo nseType|(% style="width:441px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant. 333 -|SubmitSubscriptionsR equest|ref: SubmitSubscriptionsR equestType|(% style="width:441px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources. 334 -|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:441px" %)SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID. 335 -|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|(% style="width:441px" %)QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation. 336 -|QuerySubscriptionRes ponse|ref: QuerySubscriptionRes ponseType|(% style="width:441px" %)QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent. 337 -|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|(% style="width:441px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided. 338 -|ftr:Footer|ftr:FooterType|(% style="width:441px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 319 +|**Name**|**Type**|**Documentation** 320 +|Header|BasicHeaderType| 321 +|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services. 322 +|SubmitRegistrationsR esponse|ref: SubmitRegistrationsR esponseType|SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service. 323 +|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys. 324 +|QueryRegistrationRes ponse|ref: QueryRegistrationRes ponseType|QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned. 325 +|SubmitStructureReque st|ref: SubmitStructureReque stType|SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information. 326 +|SubmitStructureRespo nse|ref: SubmitStructureRespo nseType|SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant. 327 +|SubmitSubscriptionsR equest|ref: SubmitSubscriptionsR equestType|SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources. 328 +|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID. 329 +|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation. 330 +|QuerySubscriptionRes ponse|ref: QuerySubscriptionRes ponseType|QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent. 331 +|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided. 332 +|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 339 339 340 340 **SubmitRegistrationsRequestType: **SubmitRegistrationsRequestType defines the structure of a registry submit registration requests document. 341 341 342 342 Derivation: 343 343 344 - *//MessageType// (restriction)345 - **RegistryInterfaceType (restriction)346 - ***SubmitRegistrationsRequestType338 +//MessageType// (restriction) 339 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 340 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitRegistrationsRequestType 347 347 348 348 Content: 349 349 350 -* Header, SubmitRegistrationsRequest 351 -* Element Documentation: 344 +Header, SubmitRegistrationsRequest 352 352 353 -(% style="width:844.294px" %) 354 -|**Name**|**Type**|(% style="width:377px" %)**Documentation** 355 -|Header|BasicHeaderType|(% style="width:377px" %) 356 -|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:377px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services. 346 +Element Documentation: 357 357 348 +|**Name**|**Type**|**Documentation** 349 +|Header|BasicHeaderType| 350 +|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services. 351 + 358 358 **SubmitRegistrationsResponseType: **SubmitRegistrationsResponseType defines the structure of a registry submit registration response document. 359 359 360 360 Derivation: 361 361 362 - *//MessageType// (restriction)363 - **RegistryInterfaceType (restriction)364 - ***SubmitRegistrationsResponseType356 +//MessageType// (restriction) 357 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 358 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitRegistrationsResponseType 365 365 366 366 Content: 367 367 368 -* Header, SubmitRegistrationsResponse, ftr:Footer? 369 -* Element Documentation: 362 +Header, SubmitRegistrationsResponse, ftr:Footer? 370 370 371 -(% style="width:847.294px" %) 372 -|**Name**|(% style="width:210px" %)**Type**|(% style="width:408px" %)**Documentation** 373 -|Header|(% style="width:210px" %)BasicHeaderType|(% style="width:408px" %) 374 -|SubmitRegistrationsR esponse|(% style="width:210px" %)ref: SubmitRegistrationsR esponseType|(% style="width:408px" %)SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service. 375 -|ftr:Footer|(% style="width:210px" %)ftr:FooterType|(% style="width:408px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 364 +Element Documentation: 376 376 366 +|**Name**|**Type**|**Documentation** 367 +|Header|BasicHeaderType| 368 +|SubmitRegistrationsR esponse|ref: SubmitRegistrationsR esponseType|SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service. 369 +|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 370 + 377 377 **QueryRegistrationRequestType: **QueryRegistrationRequestType defines the structure of a registry query registration request document. 378 378 379 379 Derivation: 380 380 381 - *//MessageType// (restriction)382 - **RegistryInterfaceType (restriction)383 - ***QueryRegistrationRequestType375 +//MessageType// (restriction) 376 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 377 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationRequestType 384 384 385 385 Content: 386 386 387 -* Header, QueryRegistrationRequest 388 -* Element Documentation: 381 +Header, QueryRegistrationRequest 389 389 390 -(% style="width:847.294px" %) 391 -|**Name**|**Type**|(% style="width:397px" %)**Documentation** 392 -|Header|BasicHeaderType|(% style="width:397px" %) 393 -|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:397px" %)QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys. 383 +Element Documentation: 394 394 385 +|**Name**|**Type**|**Documentation** 386 +|Header|BasicHeaderType| 387 +|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys. 388 + 395 395 **QueryRegistrationResponseType: **SubmitRegistrationRequestType defines the structure of a registry submit registration response document. 396 396 397 397 Derivation: 398 398 399 - *//MessageType// (restriction)400 - **RegistryInterfaceType (restriction)401 - ***QueryRegistrationResponseType393 +//MessageType// (restriction) 394 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 395 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationResponseType 402 402 403 403 Content: 404 404 ... ... @@ -406,19 +406,18 @@ 406 406 407 407 Element Documentation: 408 408 409 -(% style="width:856.294px" %) 410 -|**Name**|(% style="width:235px" %)**Type**|(% style="width:407px" %)**Documentation** 411 -|Header|(% style="width:235px" %)BasicHeaderType|(% style="width:407px" %) 412 -|QueryRegistrationRes ponse|(% style="width:235px" %)ref: QueryRegistrationRes ponseType|(% style="width:407px" %)QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned. 413 -|ftr:Footer|(% style="width:235px" %)ftr:FooterType|(% style="width:407px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 403 +|**Name**|**Type**|**Documentation** 404 +|Header|BasicHeaderType| 405 +|QueryRegistrationRes ponse|ref: QueryRegistrationRes ponseType|QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned. 406 +|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 414 414 415 415 **SubmitStructureRequestType: **SubmitStructureRequestType defines the structure of a registry submit structure request document. 416 416 417 417 Derivation: 418 418 419 - *//MessageType// (restriction)420 - **RegistryInterfaceType (restriction)421 - ***SubmitStructureRequestType412 +//MessageType// (restriction) 413 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 414 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureRequestType 422 422 423 423 Content: 424 424 ... ... @@ -426,630 +426,629 @@ 426 426 427 427 Element Documentation: 428 428 429 -(% style="width:870.294px" %) 430 -|**Name**|**Type**|(% style="width:453px" %)**Documentation** 431 -|Header|BasicHeaderType|(% style="width:453px" %) 432 -|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:453px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information. 422 +|**Name**|**Type**|**Documentation** 423 +|Header|BasicHeaderType| 424 +|SubmitStructureReque st|ref: SubmitStructureReque stType|SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information. 433 433 434 434 **SubmitStructureResponseType: **SubmitStructureResponseType defines the structure of a registry submit registration response document. 435 435 436 436 Derivation: 437 437 438 - *//MessageType// (restriction)439 - **RegistryInterfaceType (restriction)440 - ***SubmitStructureResponseType430 +//MessageType// (restriction) 431 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 432 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureResponseType 441 441 442 442 Content: 443 443 444 -* Header, SubmitStructureResponse, ftr:Footer? 445 -* Element Documentation: 436 +Header, SubmitStructureResponse, ftr:Footer? 446 446 447 -(% style="width:835.294px" %) 448 -|**Name**|(% style="width:246px" %)**Type**|(% style="width:366px" %)**Documentation** 449 -|Header|(% style="width:246px" %)BasicHeaderType|(% style="width:366px" %) 450 -|SubmitStructureRespo nse|(% style="width:246px" %)ref: SubmitStructureRespo nseType|(% style="width:366px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant. 451 -|ftr:Footer|(% style="width:246px" %)ftr:FooterType|(% style="width:366px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 438 +Element Documentation: 452 452 440 +|**Name**|**Type**|**Documentation** 441 +|Header|BasicHeaderType| 442 +|SubmitStructureRespo nse|ref: SubmitStructureRespo nseType|SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant. 443 +|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 444 + 453 453 **SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit subscription request document. 454 454 455 455 Derivation: 456 456 457 - *//MessageType// (restriction)458 - **RegistryInterfaceType (restriction)459 - ***SubmitSubscriptionsRequestType449 +//MessageType// (restriction) 450 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 451 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsRequestType 460 460 461 461 Content: 462 462 463 -* Header, SubmitSubscriptionsRequest 464 -* Element Documentation: 455 +Header, SubmitSubscriptionsRequest 465 465 466 -(% style="width:832.294px" %) 467 -|**Name**|(% style="width:227px" %)**Type**|(% style="width:319px" %)**Documentation** 468 -|Header|(% style="width:227px" %)BasicHeaderType|(% style="width:319px" %) 469 -|SubmitSubscriptionsR equest|(% style="width:227px" %)ref: SubmitSubscriptionsR equestType|(% style="width:319px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources. 457 +Element Documentation: 470 470 459 +|**Name**|**Type**|**Documentation** 460 +|Header|BasicHeaderType| 461 +|SubmitSubscriptionsR equest|ref: SubmitSubscriptionsR equestType|SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources. 462 + 471 471 **SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit subscription response document. 472 472 473 473 Derivation: 474 474 475 - *//MessageType// (restriction)476 - **RegistryInterfaceType (restriction)477 - ***SubmitSubscriptionsResponseType467 +//MessageType// (restriction) 468 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 469 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsResponseType 478 478 479 479 Content: 480 480 481 -* Header, SubmitSubscriptionsResponse, ftr:Footer? 482 -* Element Documentation: 473 +Header, SubmitSubscriptionsResponse, ftr:Footer? 483 483 484 -(% style="width:843.294px" %) 485 -|**Name**|**Type**|(% style="width:362px" %)**Documentation** 486 -|Header|BasicHeaderType|(% style="width:362px" %) 487 -|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:362px" %)SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID. 488 -|ftr:Footer|ftr:FooterType|(% style="width:362px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 475 +Element Documentation: 489 489 477 +|**Name**|**Type**|**Documentation** 478 +|Header|BasicHeaderType| 479 +|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID. 480 +|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 481 + 490 490 **QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query subscription request document. 491 491 492 492 Derivation: 493 493 494 - *//MessageType// (restriction)495 - **RegistryInterfaceType (restriction)496 - ***QuerySubscriptionRequestType486 +//MessageType// (restriction) 487 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 488 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionRequestType 497 497 498 498 Content: 499 499 500 -* Header, QuerySubscriptionRequest 501 -* Element Documentation: 492 +Header, QuerySubscriptionRequest 502 502 503 -(% style="width:839.294px" %) 504 -|(% style="width:230px" %)**Name**|(% style="width:254px" %)**Type**|(% style="width:352px" %)**Documentation** 505 -|(% style="width:230px" %)Header|(% style="width:254px" %)BasicHeaderType|(% style="width:352px" %) 506 -|(% style="width:230px" %)QuerySubscriptionReq uest|(% style="width:254px" %)ref: QuerySubscriptionReq uestType|(% style="width:352px" %)QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation. 494 +Element Documentation: 507 507 496 +|**Name**|**Type**|**Documentation** 497 +|Header|BasicHeaderType| 498 +|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation. 499 + 508 508 **QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query subscription response document. 509 509 510 510 Derivation: 511 511 512 - *//MessageType// (restriction)513 - **RegistryInterfaceType (restriction)514 - ***QuerySubscriptionResponseType504 +//MessageType// (restriction) 505 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 506 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionResponseType 515 515 516 516 Content: 517 517 518 -* Header, QuerySubscriptionResponse, ftr:Footer? 519 -* Element Documentation: 510 +Header, QuerySubscriptionResponse, ftr:Footer? 520 520 521 -(% style="width:912.294px" %) 522 -|**Name**|(% style="width:304px" %)**Type**|(% style="width:336px" %)**Documentation** 523 -|Header|(% style="width:304px" %)BasicHeaderType|(% style="width:336px" %) 524 -|QuerySubscriptionRes ponse|(% style="width:304px" %)ref: QuerySubscriptionRes ponseType|(% style="width:336px" %)QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent. 525 -|ftr:Footer|(% style="width:304px" %)ftr:FooterType|(% style="width:336px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 512 +Element Documentation: 526 526 514 +|**Name**|**Type**|**Documentation** 515 +|Header|BasicHeaderType| 516 +|QuerySubscriptionRes ponse|ref: QuerySubscriptionRes ponseType|QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent. 517 +|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 518 + 527 527 **NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry notification document. 528 528 529 529 Derivation: 530 530 531 - *//MessageType// (restriction)532 - **RegistryInterfaceType (restriction)533 - ***NotifyRegistryEventType523 +//MessageType// (restriction) 524 + RegistryInterfaceType (restriction) 525 + NotifyRegistryEventType 534 534 535 535 Content: 536 536 537 -* Header, NotifyRegistryEvent 538 -* Element Documentation: 529 +Header, NotifyRegistryEvent 539 539 540 -(% style="width:836.294px" %) 541 -|**Name**|**Type**|(% style="width:473px" %)**Documentation** 542 -|Header|BasicHeaderType|(% style="width:473px" %) 543 -|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|(% style="width:473px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided. 531 +Element Documentation: 544 544 533 +|**Name**|**Type**|**Documentation** 534 +|Header|BasicHeaderType| 535 +|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided. 536 + 545 545 **DataQueryType: **DataQueryType defines the structure of a data query message. 546 546 547 547 Derivation: 548 548 549 - *//MessageType// (restriction)550 - **DataQueryType541 +//MessageType// (restriction) 542 + DataQueryType 551 551 552 552 Content: 553 553 554 -* Header, Query 555 -* Element Documentation: 546 +Header, Query 556 556 557 -(% style="width:839.294px" %) 558 -|(% style="width:244px" %)**Name**|(% style="width:262px" %)**Type**|(% style="width:330px" %)**Documentation** 559 -|(% style="width:244px" %)Header|(% style="width:262px" %)BasicHeaderType|(% style="width:330px" %) 560 -|(% style="width:244px" %)Query|(% style="width:262px" %)qry:DataQueryType|(% style="width:330px" %) 548 +Element Documentation: 561 561 550 +|**Name**|**Type**|**Documentation** 551 +|Header|BasicHeaderType| 552 +|Query|qry:DataQueryType| 553 + 562 562 **GenericDataQueryType: **DataQueryType defines the structure of a generic data query message. 563 563 564 564 Derivation: 565 565 566 - *//MessageType// (restriction)567 - **DataQueryType (restriction)568 - ***GenericDataQueryType558 +//MessageType// (restriction) 559 + DataQueryType (restriction) 560 + GenericDataQueryType 569 569 570 570 Content: 571 571 572 -* Header, Query 573 -* Element Documentation: 564 +Header, Query 574 574 575 -(% style="width:833.294px" %) 576 -|(% style="width:213px" %)**Name**|(% style="width:243px" %)**Type**|(% style="width:374px" %)**Documentation** 577 -|(% style="width:213px" %)Header|(% style="width:243px" %)BasicHeaderType|(% style="width:374px" %) 578 -|(% style="width:213px" %)Query|(% style="width:243px" %)qry: GenericDataQueryType|(% style="width:374px" %) 566 +Element Documentation: 579 579 568 +|**Name**|**Type**|**Documentation** 569 +|Header|BasicHeaderType| 570 +|Query|qry: GenericDataQueryType| 571 + 580 580 **GenericTimeSeriesDataQueryType: **GenericTimeSeriesDataQueryType defines the structure of a time series generic data query message. 581 581 582 582 Derivation: 583 583 584 - *//MessageType// (restriction)585 - **DataQueryType (restriction)586 - ***GenericDataQueryType (restriction)587 - ****GenericTimeSeriesDataQueryType576 +//MessageType// (restriction) 577 + DataQueryType (restriction) 578 + GenericDataQueryType (restriction) 579 + GenericTimeSeriesDataQueryType 588 588 589 589 Content: 590 590 591 -* Header, Query 592 -* Element Documentation: 583 +Header, Query 593 593 594 -(% style="width:909.294px" %) 595 -|(% style="width:221px" %)**Name**|(% style="width:305px" %)**Type**|(% style="width:380px" %)**Documentation** 596 -|(% style="width:221px" %)Header|(% style="width:305px" %)BasicHeaderType|(% style="width:380px" %) 597 -|(% style="width:221px" %)Query|(% style="width:305px" %)qry: GenericTimeSeriesDat aQueryType|(% style="width:380px" %) 585 +Element Documentation: 598 598 587 +|**Name**|**Type**|**Documentation** 588 +|Header|BasicHeaderType| 589 +|Query|qry: GenericTimeSeriesDat aQueryType| 590 + 599 599 **StructureSpecificTimeSeriesDataQueryType: **StructureSpecificTimeSeriesDataQueryType defines the structure of a time series generic data query message. 600 600 601 601 Derivation: 602 602 603 - *//MessageType// (restriction)604 - **DataQueryType (restriction)605 - ***StructureSpecificTimeSeriesDataQueryType595 +//MessageType// (restriction) 596 + DataQueryType (restriction) 597 + StructureSpecificTimeSeriesDataQueryType 606 606 607 607 Content: 608 608 609 -* Header, Query 610 -* Element Documentation: 601 +Header, Query 611 611 612 -(% style="width:903.294px" %) 613 -|(% style="width:189px" %)**Name**|(% style="width:259px" %)**Type**|(% style="width:452px" %)**Documentation** 614 -|(% style="width:189px" %)Header|(% style="width:259px" %)BasicHeaderType|(% style="width:452px" %) 615 -|(% style="width:189px" %)Query|(% style="width:259px" %)qry: TimeSeriesDataQueryType|(% style="width:452px" %) 603 +Element Documentation: 616 616 605 +|**Name**|**Type**|**Documentation** 606 +|Header|BasicHeaderType| 607 +|Query|qry: TimeSeriesDataQueryT ype| 608 + 617 617 **MetadataQueryType: **MetadataQueryType defines the structure of a reference metadata query message. 618 618 619 619 Derivation: 620 620 621 - *//MessageType// (restriction)622 - **MetadataQueryType613 +//MessageType// (restriction) 614 + MetadataQueryType 623 623 624 624 Content: 625 625 626 -* Header, Query 627 -* Element Documentation: 618 +Header, Query 628 628 629 -(% style="width:858.294px" %) 630 -|(% style="width:138px" %)**Name**|(% style="width:246px" %)**Type**|(% style="width:471px" %)**Documentation** 631 -|(% style="width:138px" %)Header|(% style="width:246px" %)BasicHeaderType|(% style="width:471px" %) 632 -|(% style="width:138px" %)Query|(% style="width:246px" %)qry: MetadataQueryType|(% style="width:471px" %) 620 +Element Documentation: 633 633 622 +|**Name**|**Type**|**Documentation** 623 +|Header|BasicHeaderType| 624 +|Query|qry: MetadataQueryType| 625 + 634 634 **DataSchemaQueryType: **DataSchemaQueryType defines the structure of a data schema query message. 635 635 636 636 Derivation: 637 637 638 - *//MessageType// (restriction)639 - **DataSchemaQueryType630 +//MessageType// (restriction) 631 + DataSchemaQueryType 640 640 641 641 Content: 642 642 643 -* Header, Query 644 -* Element Documentation: 635 +Header, Query 645 645 646 -(% style="width:895.294px" %) 647 -|(% style="width:185px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:413px" %)**Documentation** 648 -|(% style="width:185px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:413px" %) 649 -|(% style="width:185px" %)Query|(% style="width:294px" %)qry: DataSchemaQueryType|(% style="width:413px" %) 637 +Element Documentation: 650 650 639 +|**Name**|**Type**|**Documentation** 640 +|Header|BasicHeaderType| 641 +|Query|qry: DataSchemaQueryType| 642 + 651 651 **MetadataSchemaQueryType: **MetadataSchemaQueryType defines the structure of a metadata schema query message. 652 652 653 653 Derivation: 654 654 655 - *//MessageType// (restriction)656 - **MetadataSchemaQueryType647 +//MessageType// (restriction) 648 + MetadataSchemaQueryType 657 657 658 658 Content: 659 659 660 -* Header, Query 661 -* Element Documentation: 652 +Header, Query 662 662 663 -(% style="width:897.294px" %) 664 -|(% style="width:166px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:447px" %)**Documentation** 665 -|(% style="width:166px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:447px" %) 666 -|(% style="width:166px" %)Query|(% style="width:281px" %)qry: MetadataSchemaQueryType|(% style="width:447px" %) 654 +Element Documentation: 667 667 656 +|**Name**|**Type**|**Documentation** 657 +|Header|BasicHeaderType| 658 +|Query|qry: MetadataSchemaQueryT ype| 659 + 668 668 **StructuresQueryType: **StructuresQueryType defines the structure of a structures query message. 669 669 670 670 Derivation: 671 671 672 - *//MessageType// (restriction)673 - **StructuresQueryType664 +//MessageType// (restriction) 665 + StructuresQueryType 674 674 675 675 Content: 676 676 677 -* Header, Query 678 -* Element Documentation: 669 +Header, Query 679 679 680 -(% style="width:886.294px" %) 681 -|(% style="width:223px" %)**Name**|(% style="width:255px" %)**Type**|(% style="width:405px" %)**Documentation** 682 -|(% style="width:223px" %)Header|(% style="width:255px" %)BasicHeaderType|(% style="width:405px" %) 683 -|(% style="width:223px" %)Query|(% style="width:255px" %)qry: StructuresQueryType|(% style="width:405px" %) 671 +Element Documentation: 684 684 673 +|**Name**|**Type**|**Documentation** 674 +|Header|BasicHeaderType| 675 +|Query|qry: StructuresQueryType| 676 + 685 685 **DataflowQueryType: **DataflowQueryType defines the structure of a dataflow query message. 686 686 687 687 Derivation: 688 688 689 - *//MessageType// (restriction)690 - **DataflowQueryType681 +//MessageType// (restriction) 682 + DataflowQueryType 691 691 692 692 Content: 693 693 694 -* Header, Query 695 -* Element Documentation: 686 +Header, Query 696 696 697 -(% style="width:888.294px" %) 698 -|(% style="width:176px" %)**Name**|(% style="width:260px" %)**Type**|(% style="width:449px" %)**Documentation** 699 -|(% style="width:176px" %)Header|(% style="width:260px" %)BasicHeaderType|(% style="width:449px" %) 700 -|(% style="width:176px" %)Query|(% style="width:260px" %)qry: DataflowQueryType|(% style="width:449px" %) 688 +Element Documentation: 701 701 690 +|**Name**|**Type**|**Documentation** 691 +|Header|BasicHeaderType| 692 +|Query|qry: DataflowQueryType| 693 + 702 702 **MetadataflowQueryType: **MetadataflowQueryType defines the structure of a metadata flow query message. 703 703 704 704 Derivation: 705 705 706 - *//MessageType// (restriction)707 - **MetadataflowQueryType698 +//MessageType// (restriction) 699 + MetadataflowQueryType 708 708 709 709 Content: 710 710 711 -* Header, Query 712 -* Element Documentation: 703 +Header, Query 713 713 714 -(% style="width:886.294px" %) 715 -|(% style="width:199px" %)**Name**|(% style="width:296px" %)**Type**|(% style="width:388px" %)**Documentation** 716 -|(% style="width:199px" %)Header|(% style="width:296px" %)BasicHeaderType|(% style="width:388px" %) 717 -|(% style="width:199px" %)Query|(% style="width:296px" %)qry: MetadataflowQueryType|(% style="width:388px" %) 705 +Element Documentation: 718 718 707 +|**Name**|**Type**|**Documentation** 708 +|Header|BasicHeaderType| 709 +|Query|qry: MetadataflowQueryTyp e| 710 + 719 719 **DataStructureQueryType: **KeyFamilyQueryType defines the structure of a data structure query message. 720 720 721 721 Derivation: 722 722 723 - *//MessageType// (restriction)724 - **DataStructureQueryType715 +//MessageType// (restriction) 716 + DataStructureQueryType 725 725 726 726 Content: 727 727 728 -* Header, Query 729 -* Element Documentation: 720 +Header, Query 730 730 731 -(% style="width:901.294px" %) 732 -|(% style="width:202px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:393px" %)**Documentation** 733 -|(% style="width:202px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:393px" %) 734 -|(% style="width:202px" %)Query|(% style="width:303px" %)qry: DataStructureQueryType|(% style="width:393px" %) 722 +Element Documentation: 735 735 724 +|**Name**|**Type**|**Documentation** 725 +|Header|BasicHeaderType| 726 +|Query|qry: DataStructureQueryTy pe| 727 + 736 736 **MetadataStructureQueryType: **MetadataStructureQueryType defines the structure of a metadata structure query message. 737 737 738 738 Derivation: 739 739 740 - *//MessageType// (restriction)741 - **MetadataStructureQueryType732 +//MessageType// (restriction) 733 + MetadataStructureQueryType 742 742 743 743 Content: 744 744 745 -* Header, Query 746 -* Element Documentation: 737 +Header, Query 747 747 748 -(% style="width:904.294px" %) 749 -|(% style="width:226px" %)**Name**|(% style="width:275px" %)**Type**|(% style="width:400px" %)**Documentation** 750 -|(% style="width:226px" %)Header|(% style="width:275px" %)BasicHeaderType|(% style="width:400px" %) 751 -|(% style="width:226px" %)Query|(% style="width:275px" %)qry: MetadataStructureQueryType|(% style="width:400px" %) 739 +Element Documentation: 752 752 741 +|**Name**|**Type**|**Documentation** 742 +|Header|BasicHeaderType| 743 +|Query|qry: MetadataStructureQue ryType| 744 + 753 753 **CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a category scheme query message. 754 754 755 755 Derivation: 756 756 757 - *//MessageType// (restriction)758 - **CategorySchemeQueryType749 +//MessageType// (restriction) 750 + CategorySchemeQueryType 759 759 760 760 Content: 761 761 762 -* Header, Query 763 -* Element Documentation: 754 +Header, Query 764 764 765 -(% style="width:915.294px" %) 766 -|(% style="width:196px" %)**Name**|(% style="width:347px" %)**Type**|(% style="width:369px" %)**Documentation** 767 -|(% style="width:196px" %)Header|(% style="width:347px" %)BasicHeaderType|(% style="width:369px" %) 768 -|(% style="width:196px" %)Query|(% style="width:347px" %)qry: CategorySchemeQueryType|(% style="width:369px" %) 756 +Element Documentation: 769 769 758 +|**Name**|**Type**|**Documentation** 759 +|Header|BasicHeaderType| 760 +|Query|qry: CategorySchemeQueryT ype| 761 + 770 770 **ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a concept scheme query message. 771 771 772 772 Derivation: 773 773 774 - *//MessageType// (restriction)775 - **ConceptSchemeQueryType766 +//MessageType// (restriction) 767 + ConceptSchemeQueryType 776 776 777 777 Content: 778 778 779 -* Header, Query 780 -* Element Documentation: 771 +Header, Query 781 781 782 -(% style="width:895.294px" %) 783 -|(% style="width:222px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:331px" %)**Documentation** 784 -|(% style="width:222px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:331px" %) 785 -|(% style="width:222px" %)Query|(% style="width:339px" %)qry: ConceptSchemeQueryType|(% style="width:331px" %) 773 +Element Documentation: 786 786 775 +|**Name**|**Type**|**Documentation** 776 +|Header|BasicHeaderType| 777 +|Query|qry: ConceptSchemeQueryTy pe| 778 + 787 787 **CodelistQueryType: **CodelistQueryType defines the structure of a codelist query message. 788 788 789 789 Derivation: 790 790 791 - *//MessageType// (restriction)792 - **CodelistQueryType783 +//MessageType// (restriction) 784 + CodelistQueryType 793 793 794 794 Content: 795 795 796 -* Header, Query 797 -* Element Documentation: 788 +Header, Query 798 798 799 -(% style="width:911.294px" %) 800 -|(% style="width:204px" %)**Name**|(% style="width:295px" %)**Type**|(% style="width:409px" %)**Documentation** 801 -|(% style="width:204px" %)Header|(% style="width:295px" %)BasicHeaderType|(% style="width:409px" %) 802 -|(% style="width:204px" %)Query|(% style="width:295px" %)qry:CodelistQueryType|(% style="width:409px" %) 790 +Element Documentation: 803 803 792 +|**Name**|**Type**|**Documentation** 793 +|Header|BasicHeaderType| 794 +|Query|qry: CodelistQueryType| 795 + 804 804 **HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical codelist query message. 805 805 806 806 Derivation: 807 807 808 - *//MessageType// (restriction)809 - **HierarchicalCodelistQueryType800 +//MessageType// (restriction) 801 + HierarchicalCodelistQueryType 810 810 811 811 Content: 812 812 813 -* Header, Query 814 -* Element Documentation: 805 +Header, Query 815 815 816 -(% style="width:906.294px" %) 817 -|(% style="width:191px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:430px" %)**Documentation** 818 -|(% style="width:191px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:430px" %) 819 -|(% style="width:191px" %)Query|(% style="width:281px" %)qry: HierarchicalCodelist QueryType|(% style="width:430px" %) 807 +Element Documentation: 820 820 809 +|**Name**|**Type**|**Documentation** 810 +|Header|BasicHeaderType| 811 +|Query|qry: HierarchicalCodelist QueryType| 812 + 821 821 **OrganisationSchemeQueryType: **OrganisationSchemeQueryType defines the structure of an organisation scheme query message. 822 822 823 823 Derivation: 824 824 825 - *//MessageType// (restriction)826 - **OrganisationSchemeQueryType817 +//MessageType// (restriction) 818 + OrganisationSchemeQueryType 827 827 828 828 Content: 829 829 830 -* Header, Query 831 -* Element Documentation: 822 +Header, Query 832 832 833 -(% style="width:891.294px" %) 834 -|(% style="width:174px" %)**Name**|(% style="width:292px" %)**Type**|(% style="width:422px" %)**Documentation** 835 -|(% style="width:174px" %)Header|(% style="width:292px" %)BasicHeaderType|(% style="width:422px" %) 836 -|(% style="width:174px" %)Query|(% style="width:292px" %)qry: OrganisationSchemeQueryType|(% style="width:422px" %) 824 +Element Documentation: 837 837 826 +|**Name**|**Type**|**Documentation** 827 +|Header|BasicHeaderType| 828 +|Query|qry: OrganisationSchemeQu eryType| 829 + 838 838 **ReportingTaxonomyQueryType: **ReportingTaxonomyQueryType defines the structure of a reporting taxonomy query message. 839 839 840 840 Derivation: 841 841 842 - *//MessageType// (restriction)843 - **ReportingTaxonomyQueryType834 +//MessageType// (restriction) 835 + ReportingTaxonomyQueryType 844 844 845 845 Content: 846 846 847 -* Header, Query 848 -* Element Documentation: 839 +Header, Query 849 849 850 -(% style="width:916.294px" %) 851 -|(% style="width:162px" %)**Name**|(% style="width:318px" %)**Type**|(% style="width:434px" %)**Documentation** 852 -|(% style="width:162px" %)Header|(% style="width:318px" %)BasicHeaderType|(% style="width:434px" %) 853 -|(% style="width:162px" %)Query|(% style="width:318px" %)qry: ReportingTaxonomyQueryType|(% style="width:434px" %) 841 +Element Documentation: 854 854 843 +|**Name**|**Type**|**Documentation** 844 +|Header|BasicHeaderType| 845 +|Query|qry: ReportingTaxonomyQue ryType| 846 + 855 855 **StructureSetQueryType: **StructureSetQueryType defines the structure of a structure set query message. 856 856 857 857 Derivation: 858 858 859 - *//MessageType// (restriction)860 - **StructureSetQueryType851 +//MessageType// (restriction) 852 + StructureSetQueryType 861 861 862 862 Content: 863 863 864 -* Header, Query 865 -* Element Documentation: 856 +Header, Query 866 866 867 -(% style="width:896.294px" %) 868 -|(% style="width:182px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:417px" %)**Documentation** 869 -|(% style="width:182px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:417px" %) 870 -|(% style="width:182px" %)Query|(% style="width:294px" %)qry: StructureSetQueryType|(% style="width:417px" %) 858 +Element Documentation: 871 871 860 +|**Name**|**Type**|**Documentation** 861 +|Header|BasicHeaderType| 862 +|Query|qry: StructureSetQueryTyp e| 863 + 872 872 **ProcessQueryType: **CategorizationQueryType defines the structure of a categorization query message. 873 873 874 874 Derivation: 875 875 876 - *//MessageType// (restriction)877 - **ProcessQueryType868 +//MessageType// (restriction) 869 + ProcessQueryType 878 878 879 879 Content: 880 880 881 -* Header, Query 882 -* Element Documentation: 873 +Header, Query 883 883 884 -(% style="width:907.294px" %) 885 -|(% style="width:189px" %)**Name**|(% style="width:394px" %)**Type**|(% style="width:321px" %)**Documentation** 886 -|(% style="width:189px" %)Header|(% style="width:394px" %)BasicHeaderType|(% style="width:321px" %) 887 -|(% style="width:189px" %)Query|(% style="width:394px" %)qry:ProcessQueryType|(% style="width:321px" %) 875 +Element Documentation: 888 888 877 +|**Name**|**Type**|**Documentation** 878 +|Header|BasicHeaderType| 879 +|Query|qry:ProcessQueryType| 880 + 889 889 **CategorisationQueryType: **CategorisationQueryType defines the structure of a categorisation query message. 890 890 891 891 Derivation: 892 892 893 - *//MessageType// (restriction)894 - **CategorisationQueryType885 +//MessageType// (restriction) 886 + CategorisationQueryType 895 895 896 896 Content: 897 897 898 -* Header, Query 899 -* Element Documentation: 890 +Header, Query 900 900 901 -(% style="width:897.294px" %) 902 -|(% style="width:230px" %)**Name**|(% style="width:300px" %)**Type**|(% style="width:363px" %)**Documentation** 903 -|(% style="width:230px" %)Header|(% style="width:300px" %)BasicHeaderType|(% style="width:363px" %) 904 -|(% style="width:230px" %)Query|(% style="width:300px" %)qry: CategorisationQueryType|(% style="width:363px" %) 892 +Element Documentation: 905 905 894 +|**Name**|**Type**|**Documentation** 895 +|Header|BasicHeaderType| 896 +|Query|qry: CategorisationQueryT ype| 897 + 906 906 **ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a provision agreement query message. 907 907 908 908 Derivation: 909 909 910 - *//MessageType// (restriction)911 - **ProvisionAgreementQueryType902 +//MessageType// (restriction) 903 + ProvisionAgreementQueryType 912 912 913 913 Content: 914 914 915 -* Header, Query 916 -* Element Documentation: 907 +Header, Query 917 917 918 -(% style="width:902.294px" %) 919 -|(% style="width:142px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:418px" %)**Documentation** 920 -|(% style="width:142px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:418px" %) 921 -|(% style="width:142px" %)Query|(% style="width:339px" %)qry: ProvisionAgreementQueryType|(% style="width:418px" %) 909 +Element Documentation: 922 922 911 +|**Name**|**Type**|**Documentation** 912 +|Header|BasicHeaderType| 913 +|Query|qry: ProvisionAgreementQu eryType| 914 + 923 923 **ConstraintQueryType: **ConstraintQueryType defines the structure of a constraint query message. 924 924 925 925 Derivation: 926 926 927 - *//MessageType// (restriction)928 - **ConstraintQueryType919 +//MessageType// (restriction) 920 + ConstraintQueryType 929 929 930 930 Content: 931 931 932 -* Header, Query 933 -* Element Documentation: 924 +Header, Query 934 934 935 -(% style="width:902.294px" %) 936 -|(% style="width:167px" %)**Name**|(% style="width:287px" %)**Type**|(% style="width:445px" %)**Documentation** 937 -|(% style="width:167px" %)Header|(% style="width:287px" %)BasicHeaderType|(% style="width:445px" %) 938 -|(% style="width:167px" %)Query|(% style="width:287px" %)qry: ConstraintQueryType|(% style="width:445px" %) 926 +Element Documentation: 939 939 928 +|**Name**|**Type**|**Documentation** 929 +|Header|BasicHeaderType| 930 +|Query|qry: ConstraintQueryType| 931 + 940 940 **TransformationSchemeQueryType: **TransformationSchemeQueryType defines the structure of a transformation scheme query message. 941 941 942 942 Derivation: 943 943 944 - *//MessageType// (restriction)945 - **TransformationSchemeQueryType936 +//MessageType// (restriction) 937 + TransformationSchemeQueryType 946 946 947 947 Content: 948 948 949 -* Header, Query 950 -* Element Documentation: 941 +Header, Query 951 951 952 -(% style="width:833.294px" %) 953 -|(% style="width:165px" %)**Name**|(% style="width:325px" %)**Type**|(% style="width:340px" %)**Documentation** 954 -|(% style="width:165px" %)Header|(% style="width:325px" %)BasicHeaderType|(% style="width:340px" %) 955 -|(% style="width:165px" %)Query|(% style="width:325px" %)qry: TransformationSchemeQueryType|(% style="width:340px" %) 943 +Element Documentation: 956 956 945 +|**Name**|**Type**|**Documentation** 946 +|Header|BasicHeaderType| 947 +|Query|qry: TransformationScheme QueryType| 948 + 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 - **VtlMappingSchemeQueryType953 +//MessageType// (restriction) 954 + VtlMappingSchemeQueryType 963 963 964 964 Content: 965 965 966 -* Header, Query 967 -* Element Documentation: 958 +Header, Query 968 968 969 -(% style="width:843.294px" %) 970 -|(% style="width:164px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:373px" %)**Documentation** 971 -|(% style="width:164px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:373px" %) 972 -|(% style="width:164px" %)Query|(% style="width:303px" %)qry: VtlMappingSchemeQueryType|(% style="width:373px" %) 960 +Element Documentation: 973 973 962 +|**Name**|**Type**|**Documentation** 963 +|Header|BasicHeaderType| 964 +|Query|qry: VtlMappingSchemeQuer yType| 965 + 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 - **NamePersonalisationSchemeQueryType970 +//MessageType// (restriction) 971 + NamePersonalisationSchemeQueryType 980 980 981 981 Content: 982 982 983 -* Header, Query 984 -* Element Documentation: 975 +Header, Query 985 985 986 -(% style="width:895.294px" %) 987 -|(% style="width:186px" %)**Name**|(% style="width:363px" %)**Type**|(% style="width:343px" %)**Documentation** 988 -|(% style="width:186px" %)Header|(% style="width:363px" %)BasicHeaderType|(% style="width:343px" %) 989 -|(% style="width:186px" %)Query|(% style="width:363px" %)qry: NamePersonalisationSchemeQueryType|(% style="width:343px" %) 977 +Element Documentation: 990 990 979 +|**Name**|**Type**|**Documentation** 980 +|Header|BasicHeaderType| 981 +|Query|qry: NamePersonalisationS chemeQueryType| 982 + 991 991 **RulesetSchemeQueryType: **RulesetSchemeQueryType defines the structure of a ruleset scheme query message. 992 992 993 993 Derivation: 994 994 995 - *//MessageType// (restriction)996 - **RulesetSchemeQueryType987 +//MessageType// (restriction) 988 + RulesetSchemeQueryType 997 997 998 998 Content: 999 999 1000 -* Header, Query 1001 -* Element Documentation: 992 +Header, Query 1002 1002 1003 -(% style="width:886.294px" %) 1004 -|(% style="width:152px" %)**Name**|(% style="width:311px" %)**Type**|(% style="width:420px" %)**Documentation** 1005 -|(% style="width:152px" %)Header|(% style="width:311px" %)BasicHeaderType|(% style="width:420px" %) 1006 -|(% style="width:152px" %)Query|(% style="width:311px" %)qry: RulesetSchemeQueryType|(% style="width:420px" %) 994 +Element Documentation: 1007 1007 996 +|**Name**|**Type**|**Documentation** 997 +|Header|BasicHeaderType| 998 +|Query|qry: RulesetSchemeQueryTy pe| 999 + 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 - **UserDefinedOperatorSchemeQueryType1004 +//MessageType// (restriction) 1005 + UserDefinedOperatorSchemeQueryType 1014 1014 1015 1015 Content: 1016 1016 1017 -* Header, Query 1018 -* Element Documentation: 1009 +Header, Query 1019 1019 1020 -(% style="width:866.294px" %) 1021 -|(% style="width:174px" %)**Name**|(% style="width:358px" %)**Type**|(% style="width:331px" %)**Documentation** 1022 -|(% style="width:174px" %)Header|(% style="width:358px" %)BasicHeaderType|(% style="width:331px" %) 1023 -|(% style="width:174px" %)Query|(% style="width:358px" %)qry: UserDefinedOperatorSchemeQueryType|(% style="width:331px" %) 1011 +Element Documentation: 1024 1024 1013 +|**Name**|**Type**|**Documentation** 1014 +|Header|BasicHeaderType| 1015 +|Query|qry: UserDefinedOperatorS chemeQueryType| 1016 + 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 - **CustomTypeSchemeQueryType1021 +//MessageType// (restriction) 1022 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] CustomTypeSchemeQueryType 1031 1031 1032 1032 Content: 1033 1033 1034 -* Header, Query 1035 -* Element Documentation: 1026 +Header, Query 1036 1036 1037 -(% style="width:828.294px" %) 1038 -|(% style="width:200px" %)**Name**|(% style="width:308px" %)**Type**|(% style="width:317px" %)**Documentation** 1039 -|(% style="width:200px" %)Header|(% style="width:308px" %)BasicHeaderType|(% style="width:317px" %) 1040 -|(% style="width:200px" %)Query|(% style="width:308px" %)qry: CustomTypeSchemeQueryType|(% style="width:317px" %) 1028 +Element Documentation: 1041 1041 1030 +|**Name**|**Type**|**Documentation** 1031 +|Header|BasicHeaderType| 1032 +|Query|qry: CustomTypeSchemeQuer yType| 1033 + 1042 1042 **ErrorType: **ErrorType describes the structure of an error response. 1043 1043 1044 1044 Content: 1045 1045 1046 -* ErrorMessage+ 1047 -* Element Documentation: 1038 +ErrorMessage+ 1048 1048 1049 -(% style="width:899.294px" %) 1050 -|**Name**|**Type**|(% style="width:546px" %)**Documentation** 1051 -|ErrorMessage|com: CodedStatusMessageTy pe|(% style="width:546px" %)ErrorMessage contains the error message. It can occur multiple times to communicate message for multiple errors, or to communicate the error message in parallel languages. If both messages for multiple errors and parallel language messages are used, then each error message should be given a code in order to distinguish message for unique errors. 1040 +Element Documentation: 1052 1052 1042 +|**Name**|**Type**|**Documentation** 1043 +|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. 1044 + 1053 1053 **//BaseHeaderType//: **BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this 1054 1054 1055 1055 Content: ... ... @@ -1058,30 +1058,29 @@ 1058 1058 1059 1059 Element Documentation: 1060 1060 1061 -(% style="width:891.294px" %) 1062 -|**Name**|**Type**|(% style="width:552px" %)**Documentation** 1063 -|ID|com:IDType|(% style="width:552px" %)ID identifies an identification for the message, assigned by the sender. 1064 -|Test|xs:boolean|(% style="width:552px" %)Test indicates whether the message is for test purposes or not. 1065 -|Prepared|HeaderTimeType|(% style="width:552px" %)Prepared is the date the message was prepared. 1066 -|Sender|SenderType|(% style="width:552px" %)Sender is information about the party that is transmitting the message. 1067 -|Receiver|PartyType|(% style="width:552px" %)Receiver is information about the party that is the intended recipient of the message. 1068 -|com:Name|com:TextType|(% style="width:552px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1069 -|Structure|//com: PayloadStructureType//|(% style="width:552px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1070 -|DataProvider|com: DataProviderReferenceType|(% style="width:552px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1071 -|DataSetAction|com:ActionType|(% style="width:552px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1072 -|DataSetID|com:IDType|(% style="width:552px" %)DataSetID provides an identifier for a contained data set. 1073 -|Extracted|xs:dateTime|(% style="width:552px" %)Extracted is a time-stamp from the system rendering the data. 1074 -|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data). 1075 -|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data). 1076 -|EmbargoDate|xs:dateTime|(% style="width:552px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1077 -|Source|com:TextType|(% style="width:552px" %)Source provides human-readable information about the source of the data. 1053 +|**Name**|**Type**|**Documentation** 1054 +|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1055 +|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1056 +|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1057 +|Sender|SenderType|Sender is information about the party that is transmitting the message. 1058 +|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1059 +|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1060 +|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. 1061 +|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1062 +|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). 1063 +|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1064 +|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1065 +|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1066 +|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1067 +|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1068 +|Source|com:TextType|Source provides human-readable information about the source of the data. 1078 1078 1079 1079 **StructureHeaderType: **StructureHeaderType defines the structure for structural metadata messages. 1080 1080 1081 1081 Derivation: 1082 1082 1083 - *//BaseHeaderType// (restriction)1084 - **StructureHeaderType1074 +//BaseHeaderType// (restriction) 1075 + StructureHeaderType 1085 1085 1086 1086 Content: 1087 1087 ... ... @@ -1089,22 +1089,21 @@ 1089 1089 1090 1090 Element Documentation: 1091 1091 1092 -(% style="width:1099.29px" %) 1093 -|**Name**|(% style="width:224px" %)**Type**|(% style="width:663px" %)**Documentation** 1094 -|ID|(% style="width:224px" %)com:IDType|(% style="width:663px" %)ID identifies an identification for the message, assigned by the sender. 1095 -|Test|(% style="width:224px" %)xs:boolean|(% style="width:663px" %)Test indicates whether the message is for test purposes or not. 1096 -|Prepared|(% style="width:224px" %)HeaderTimeType|(% style="width:663px" %)Prepared is the date the message was prepared. 1097 -|Sender|(% style="width:224px" %)SenderType|(% style="width:663px" %)Sender is information about the party that is transmitting the message. 1098 -|Receiver|(% style="width:224px" %)PartyType|(% style="width:663px" %)Receiver is information about the party that is the intended recipient of the message. 1099 -|com:Name|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1100 -|Source|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Source provides human-readable information about the source of the data. 1083 +|**Name**|**Type**|**Documentation** 1084 +|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1085 +|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1086 +|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1087 +|Sender|SenderType|Sender is information about the party that is transmitting the message. 1088 +|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1089 +|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1090 +|Source|com:TextType|Source provides human-readable information about the source of the data. 1101 1101 1102 1102 **GenericDataHeaderType: **GenericDataHeaderType defines the header structure for a generic data message. 1103 1103 1104 1104 Derivation: 1105 1105 1106 - *//BaseHeaderType// (restriction)1107 - **GenericDataHeaderType1096 +//BaseHeaderType// (restriction) 1097 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataHeaderType 1108 1108 1109 1109 Content: 1110 1110 ... ... @@ -1112,31 +1112,30 @@ 1112 1112 1113 1113 Element Documentation: 1114 1114 1115 -(% style="width:895.294px" %) 1116 -|**Name**|**Type**|(% style="width:556px" %)**Documentation** 1117 -|ID|com:IDType|(% style="width:556px" %)ID identifies an identification for the message, assigned by the sender. 1118 -|Test|xs:boolean|(% style="width:556px" %)Test indicates whether the message is for test purposes or not. 1119 -|Prepared|HeaderTimeType|(% style="width:556px" %)Prepared is the date the message was prepared. 1120 -|Sender|SenderType|(% style="width:556px" %)Sender is information about the party that is transmitting the message. 1121 -|Receiver|PartyType|(% style="width:556px" %)Receiver is information about the party that is the intended recipient of the message. 1122 -|com:Name|com:TextType|(% style="width:556px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1123 -|Structure|com: GenericDataStructureType|(% style="width:556px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1124 -|DataProvider|com: DataProviderReferenceType|(% style="width:556px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1125 -|DataSetAction|com:ActionType|(% style="width:556px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1126 -|DataSetID|com:IDType|(% style="width:556px" %)DataSetID provides an identifier for a contained data set. 1127 -|Extracted|xs:dateTime|(% style="width:556px" %)Extracted is a time-stamp from the system rendering the data. 1128 -|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data). 1129 -|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data). 1130 -|EmbargoDate|xs:dateTime|(% style="width:556px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1131 -|Source|com:TextType|(% style="width:556px" %)Source provides human-readable information about the source of the data. 1105 +|**Name**|**Type**|**Documentation** 1106 +|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1107 +|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1108 +|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1109 +|Sender|SenderType|Sender is information about the party that is transmitting the message. 1110 +|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1111 +|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1112 +|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. 1113 +|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1114 +|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). 1115 +|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1116 +|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1117 +|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1118 +|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1119 +|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1120 +|Source|com:TextType|Source provides human-readable information about the source of the data. 1132 1132 1133 1133 **GenericTimeSeriesDataHeaderType: **GenericTimeSeriesDataHeaderType defines the header structure for a time series only generic data message. 1134 1134 1135 1135 Derivation: 1136 1136 1137 - *//BaseHeaderType// (restriction)1138 - **GenericDataHeaderType (restriction)1139 - ***GenericTimeSeriesDataHeaderType1126 +//BaseHeaderType// (restriction) 1127 + GenericDataHeaderType (restriction) 1128 + GenericTimeSeriesDataHeaderType 1140 1140 1141 1141 Content: 1142 1142 ... ... @@ -1144,30 +1144,29 @@ 1144 1144 1145 1145 Element Documentation: 1146 1146 1147 -(% style="width:926.294px" %) 1148 -|**Name**|**Type**|(% style="width:497px" %)**Documentation** 1149 -|ID|com:IDType|(% style="width:497px" %)ID identifies an identification for the message, assigned by the sender. 1150 -|Test|xs:boolean|(% style="width:497px" %)Test indicates whether the message is for test purposes or not. 1151 -|Prepared|HeaderTimeType|(% style="width:497px" %)Prepared is the date the message was prepared. 1152 -|Sender|SenderType|(% style="width:497px" %)Sender is information about the party that is transmitting the message. 1153 -|Receiver|PartyType|(% style="width:497px" %)Receiver is information about the party that is the intended recipient of the message. 1154 -|com:Name|com:TextType|(% style="width:497px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1155 -|Structure|com: GenericTimeSeriesDataStructureType|(% style="width:497px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1156 -|DataProvider|com: DataProviderReferenceType|(% style="width:497px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1157 -|DataSetAction|com:ActionType|(% style="width:497px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1158 -|DataSetID|com:IDType|(% style="width:497px" %)DataSetID provides an identifier for a contained data set. 1159 -|Extracted|xs:dateTime|(% style="width:497px" %)Extracted is a time-stamp from the system rendering the data. 1160 -|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data). 1161 -|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data). 1162 -|EmbargoDate|xs:dateTime|(% style="width:497px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1163 -|Source|com:TextType|(% style="width:497px" %)Source provides human-readable information about the source of the data. 1136 +|**Name**|**Type**|**Documentation** 1137 +|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1138 +|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1139 +|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1140 +|Sender|SenderType|Sender is information about the party that is transmitting the message. 1141 +|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1142 +|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1143 +|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. 1144 +|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1145 +|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). 1146 +|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1147 +|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1148 +|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1149 +|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1150 +|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1151 +|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 - **StructureSpecificDataHeaderType1157 +//BaseHeaderType// (restriction) 1158 + StructureSpecificDataHeaderType 1171 1171 1172 1172 Content: 1173 1173 ... ... @@ -1175,31 +1175,30 @@ 1175 1175 1176 1176 Element Documentation: 1177 1177 1178 -(% style="width:930.294px" %) 1179 -|**Name**|**Type**|(% style="width:578px" %)**Documentation** 1180 -|ID|com:IDType|(% style="width:578px" %)ID identifies an identification for the message, assigned by the sender. 1181 -|Test|xs:boolean|(% style="width:578px" %)Test indicates whether the message is for test purposes or not. 1182 -|Prepared|HeaderTimeType|(% style="width:578px" %)Prepared is the date the message was prepared. 1183 -|Sender|SenderType|(% style="width:578px" %)Sender is information about the party that is transmitting the message. 1184 -|Receiver|PartyType|(% style="width:578px" %)Receiver is information about the party that is the intended recipient of the message. 1185 -|com:Name|com:TextType|(% style="width:578px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1186 -|Structure|com: StructureSpecificDataStructureType|(% style="width:578px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1187 -|DataProvider|com: DataProviderReferenceType|(% style="width:578px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1188 -|DataSetAction|com:ActionType|(% style="width:578px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1189 -|DataSetID|com:IDType|(% style="width:578px" %)DataSetID provides an identifier for a contained data set. 1190 -|Extracted|xs:dateTime|(% style="width:578px" %)Extracted is a time-stamp from the system rendering the data. 1191 -|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data). 1192 -|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data). 1193 -|EmbargoDate|xs:dateTime|(% style="width:578px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1194 -|Source|com:TextType|(% style="width:578px" %)Source provides human-readable information about the source of the data. 1166 +|**Name**|**Type**|**Documentation** 1167 +|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1168 +|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1169 +|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1170 +|Sender|SenderType|Sender is information about the party that is transmitting the message. 1171 +|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1172 +|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1173 +|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. 1174 +|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1175 +|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). 1176 +|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1177 +|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1178 +|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1179 +|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1180 +|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1181 +|Source|com:TextType|Source provides human-readable information about the source of the data. 1195 1195 1196 1196 **StructureSpecificTimeSeriesDataHeaderType: **StructureSpecificTimeSeriesDataHeaderType defines the header structure for a time series only structure specific data message. 1197 1197 1198 1198 Derivation: 1199 1199 1200 - *//BaseHeaderType// (restriction)1201 - **StructureSpecificDataHeaderType (restriction)1202 - ***StructureSpecificTimeSeriesDataHeaderType1187 +//BaseHeaderType// (restriction) 1188 + StructureSpecificDataHeaderType (restriction) 1189 + StructureSpecificTimeSeriesDataHeaderType 1203 1203 1204 1204 Content: 1205 1205 ... ... @@ -1207,30 +1207,29 @@ 1207 1207 1208 1208 Element Documentation: 1209 1209 1210 -(% style="width:943.294px" %) 1211 -|**Name**|(% style="width:352px" %)**Type**|(% style="width:461px" %)**Documentation** 1212 -|ID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)ID identifies an identification for the message, assigned by the sender. 1213 -|Test|(% style="width:352px" %)xs:boolean|(% style="width:461px" %)Test indicates whether the message is for test purposes or not. 1214 -|Prepared|(% style="width:352px" %)HeaderTimeType|(% style="width:461px" %)Prepared is the date the message was prepared. 1215 -|Sender|(% style="width:352px" %)SenderType|(% style="width:461px" %)Sender is information about the party that is transmitting the message. 1216 -|Receiver|(% style="width:352px" %)PartyType|(% style="width:461px" %)Receiver is information about the party that is the intended recipient of the message. 1217 -|com:Name|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1218 -|Structure|(% style="width:352px" %)com: StructureSpecificDataTimeSeriesStructureType|(% style="width:461px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1219 -|DataProvider|(% style="width:352px" %)com: DataProviderReferenceType|(% style="width:461px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1220 -|DataSetAction|(% style="width:352px" %)com:ActionType|(% style="width:461px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1221 -|DataSetID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)DataSetID provides an identifier for a contained data set. 1222 -|Extracted|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)Extracted is a time-stamp from the system rendering the data. 1223 -|ReportingBegin|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data). 1224 -|ReportingEnd|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data). 1225 -|EmbargoDate|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1226 -|Source|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Source provides human-readable information about the source of the data. 1197 +|**Name**|**Type**|**Documentation** 1198 +|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1199 +|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1200 +|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1201 +|Sender|SenderType|Sender is information about the party that is transmitting the message. 1202 +|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1203 +|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1204 +|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. 1205 +|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1206 +|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). 1207 +|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1208 +|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1209 +|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1210 +|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1211 +|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1212 +|Source|com:TextType|Source provides human-readable information about the source of the data. 1227 1227 1228 1228 **GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic reference metadata. 1229 1229 1230 1230 Derivation: 1231 1231 1232 - *//BaseHeaderType// (restriction)1233 - **GenericMetadataHeaderType1218 +//BaseHeaderType// (restriction) 1219 + GenericMetadataHeaderType 1234 1234 1235 1235 Content: 1236 1236 ... ... @@ -1238,27 +1238,26 @@ 1238 1238 1239 1239 Element Documentation: 1240 1240 1241 -(% style="width:928.294px" %) 1242 -|**Name**|**Type**|(% style="width:554px" %)**Documentation** 1243 -|ID|com:IDType|(% style="width:554px" %)ID identifies an identification for the message, assigned by the sender. 1244 -|Test|xs:boolean|(% style="width:554px" %)Test indicates whether the message is for test purposes or not. 1245 -|Prepared|HeaderTimeType|(% style="width:554px" %)Prepared is the date the message was prepared. 1246 -|Sender|SenderType|(% style="width:554px" %)Sender is information about the party that is transmitting the message. 1247 -|Receiver|PartyType|(% style="width:554px" %)Receiver is information about the party that is the intended recipient of the message. 1248 -|com:Name|com:TextType|(% style="width:554px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1249 -|Structure|com: GenericMetadataStructureType|(% style="width:554px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1250 -|DataProvider|com: DataProviderReferenceType|(% style="width:554px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1251 -|DataSetAction|com:ActionType|(% style="width:554px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1252 -|DataSetID|com:IDType|(% style="width:554px" %)DataSetID provides an identifier for a contained data set. 1253 -|Extracted|xs:dateTime|(% style="width:554px" %)Extracted is a time-stamp from the system rendering the data. 1254 -|Source|com:TextType|(% style="width:554px" %)Source provides human-readable information about the source of the data. 1227 +|**Name**|**Type**|**Documentation** 1228 +|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1229 +|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1230 +|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1231 +|Sender|SenderType|Sender is information about the party that is transmitting the message. 1232 +|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1233 +|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1234 +|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. 1235 +|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1236 +|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). 1237 +|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1238 +|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1239 +|Source|com:TextType|Source provides human-readable information about the source of the data. 1255 1255 1256 1256 **StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for metadata structure definition specific reference metadata messages. 1257 1257 1258 1258 Derivation: 1259 1259 1260 - *//BaseHeaderType// (restriction)1261 - **StructureSpecificMetadataHeaderType1245 +//BaseHeaderType// (restriction) 1246 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType 1262 1262 1263 1263 Content: 1264 1264 ... ... @@ -1266,27 +1266,26 @@ 1266 1266 1267 1267 Element Documentation: 1268 1268 1269 -(% style="width:996.294px" %) 1270 -|**Name**|**Type**|(% style="width:557px" %)**Documentation** 1271 -|ID|com:IDType|(% style="width:557px" %)ID identifies an identification for the message, assigned by the sender. 1272 -|Test|xs:boolean|(% style="width:557px" %)Test indicates whether the message is for test purposes or not. 1273 -|Prepared|HeaderTimeType|(% style="width:557px" %)Prepared is the date the message was prepared. 1274 -|Sender|SenderType|(% style="width:557px" %)Sender is information about the party that is transmitting the message. 1275 -|Receiver|PartyType|(% style="width:557px" %)Receiver is information about the party that is the intended recipient of the message. 1276 -|com:Name|com:TextType|(% style="width:557px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1277 -|Structure|com: StructureSpecificMetadataStructureType|(% style="width:557px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1278 -|DataProvider|com: DataProviderReferenceType|(% style="width:557px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1279 -|DataSetAction|com:ActionType|(% style="width:557px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1280 -|DataSetID|com:IDType|(% style="width:557px" %)DataSetID provides an identifier for a contained data set. 1281 -|Extracted|xs:dateTime|(% style="width:557px" %)Extracted is a time-stamp from the system rendering the data. 1282 -|Source|com:TextType|(% style="width:557px" %)Source provides human-readable information about the source of the data. 1254 +|**Name**|**Type**|**Documentation** 1255 +|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1256 +|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1257 +|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1258 +|Sender|SenderType|Sender is information about the party that is transmitting the message. 1259 +|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1260 +|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1261 +|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. 1262 +|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1263 +|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). 1264 +|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1265 +|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1266 +|Source|com:TextType|Source provides human-readable information about the source of the data. 1283 1283 1284 1284 **BasicHeaderType: **BasicHeaderType defines the most basic header information used in simple message exchanges. 1285 1285 1286 1286 Derivation: 1287 1287 1288 - *//BaseHeaderType// (restriction)1289 - **BasicHeaderType1272 +//BaseHeaderType// (restriction) 1273 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType 1290 1290 1291 1291 Content: 1292 1292 ... ... @@ -1327,7 +1327,7 @@ 1327 1327 Derivation: 1328 1328 1329 1329 PartyType (extension) 1330 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType 1314 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType 1331 1331 1332 1332 Attributes: 1333 1333 ... ... @@ -1367,8 +1367,8 @@ 1367 1367 |URI|xs:anyURI|URI holds an information URL for the contact person. 1368 1368 |Email|xs:string|Email holds the email address for the contact person. 1369 1369 1370 -1. 1371 -11. 1354 +1. 1355 +11. 1372 1372 111. Simple Types 1373 1373 1374 1374 **HeaderTimeType: **Provides a union type of xs:date and xs:dateTime for the header fields in the message. ... ... @@ -1377,13 +1377,13 @@ 1377 1377 1378 1378 xs:dateTime, xs:date. 1379 1379 1380 -1. 1364 +1. 1381 1381 11. Message Footer Namespace 1382 1382 1383 1383 **http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer** 1384 1384 1385 -1. 1386 -11. 1369 +1. 1370 +11. 1387 1387 111. Summary 1388 1388 1389 1389 Referenced Namespaces: ... ... @@ -1398,14 +1398,14 @@ 1398 1398 2 Complex Types 1399 1399 1 Simple Type 1400 1400 1401 -1. 1402 -11. 1385 +1. 1386 +11. 1403 1403 111. Global Elements 1404 1404 1405 1405 **Footer (FooterType): **Footer is used to communicate information such as error and warnings after the payload of a message. 1406 1406 1407 -1. 1408 -11. 1391 +1. 1392 +11. 1409 1409 111. Complex Types 1410 1410 1411 1411 **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. ... ... @@ -1424,8 +1424,8 @@ 1424 1424 Derivation: 1425 1425 1426 1426 com:StatusMessageType (restriction) 1427 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension) 1428 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType 1411 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension) 1412 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType 1429 1429 1430 1430 Attributes: 1431 1431 ... ... @@ -1446,8 +1446,8 @@ 1446 1446 |**Name**|**Type**|**Documentation** 1447 1447 |com:Text|com:TextType|Text contains the text of the message, in parallel language values. 1448 1448 1449 -1. 1450 -11. 1433 +1. 1434 +11. 1451 1451 111. Simple Types 1452 1452 1453 1453 **SeverityCodeType:**