Changes for page Part I. Message Namespace
Last modified by Artur on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -177,8 +177,8 @@ 177 177 178 178 Derivation: 179 179 180 -//MessageType// (restriction) 181 - StructureType 180 +* //MessageType// (restriction) 181 +** StructureType 182 182 183 183 Content: 184 184 ... ... @@ -196,8 +196,8 @@ 196 196 197 197 Derivation: 198 198 199 -//MessageType// (restriction) 200 - GenericDataType 199 +* //MessageType// (restriction) 200 +** GenericDataType 201 201 202 202 Content: 203 203 ... ... @@ -274,8 +274,8 @@ 274 274 275 275 Derivation: 276 276 277 -//MessageType// (restriction) 278 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]GenericMetadataType277 +* //MessageType// (restriction) 278 +** GenericMetadataType 279 279 280 280 Content: 281 281 ... ... @@ -283,17 +283,18 @@ 283 283 284 284 Element Documentation: 285 285 286 -|**Name**|**Type**|**Documentation** 287 -|Header|GenericMetadataHeade rType| 288 -|MetadataSet|rep:MetadataSetType| 289 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 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. 290 290 291 291 **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. 292 292 293 293 Derivation: 294 294 295 -//MessageType// (restriction) 296 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureSpecificMetadataType296 +* //MessageType// (restriction) 297 +** StructureSpecificMetadataType 297 297 298 298 Content: 299 299 ... ... @@ -301,17 +301,18 @@ 301 301 302 302 Element Documentation: 303 303 304 -|**Name**|**Type**|**Documentation** 305 -|Header|StructureSpecificMet adataHeaderType| 306 -|MetadataSet|//msd:MetadataSetType//| 307 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 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. 308 308 309 309 **RegistryInterfaceType: **This is a type which describes a structure for holding all of the various dedicated registry interface message types. 310 310 311 311 Derivation: 312 312 313 -//MessageType// (restriction) 314 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType315 +* //MessageType// (restriction) 316 +** RegistryInterfaceType 315 315 316 316 Content: 317 317 ... ... @@ -319,28 +319,29 @@ 319 319 320 320 Element Documentation: 321 321 322 -|**Name**|**Type**|**Documentation** 323 -|Header|BasicHeaderType| 324 -|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. 325 -|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. 326 -|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. 327 -|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. 328 -|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. 329 -|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. 330 -|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. 331 -|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. 332 -|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation. 333 -|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. 334 -|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. 335 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 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. 336 336 337 337 **SubmitRegistrationsRequestType: **SubmitRegistrationsRequestType defines the structure of a registry submit registration requests document. 338 338 339 339 Derivation: 340 340 341 -//MessageType// (restriction) 342 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)343 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitRegistrationsRequestType344 +* //MessageType// (restriction) 345 +** RegistryInterfaceType (restriction) 346 +*** SubmitRegistrationsRequestType 344 344 345 345 Content: 346 346 ... ... @@ -348,17 +348,18 @@ 348 348 349 349 Element Documentation: 350 350 351 -|**Name**|**Type**|**Documentation** 352 -|Header|BasicHeaderType| 353 -|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. 354 +(% style="width:844.294px" %) 355 +|**Name**|**Type**|(% style="width:377px" %)**Documentation** 356 +|Header|BasicHeaderType|(% style="width:377px" %) 357 +|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. 354 354 355 355 **SubmitRegistrationsResponseType: **SubmitRegistrationsResponseType defines the structure of a registry submit registration response document. 356 356 357 357 Derivation: 358 358 359 -//MessageType// (restriction) 360 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)361 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitRegistrationsResponseType363 +* //MessageType// (restriction) 364 +** RegistryInterfaceType (restriction) 365 +*** SubmitRegistrationsResponseType 362 362 363 363 Content: 364 364 ... ... @@ -366,18 +366,19 @@ 366 366 367 367 Element Documentation: 368 368 369 -|**Name**|**Type**|**Documentation** 370 -|Header|BasicHeaderType| 371 -|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. 372 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 373 +(% style="width:847.294px" %) 374 +|**Name**|(% style="width:210px" %)**Type**|(% style="width:408px" %)**Documentation** 375 +|Header|(% style="width:210px" %)BasicHeaderType|(% style="width:408px" %) 376 +|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. 377 +|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. 373 373 374 374 **QueryRegistrationRequestType: **QueryRegistrationRequestType defines the structure of a registry query registration request document. 375 375 376 376 Derivation: 377 377 378 -//MessageType// (restriction) 379 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)380 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]QueryRegistrationRequestType383 +* //MessageType// (restriction) 384 +** RegistryInterfaceType (restriction) 385 +*** QueryRegistrationRequestType 381 381 382 382 Content: 383 383 ... ... @@ -385,17 +385,18 @@ 385 385 386 386 Element Documentation: 387 387 388 -|**Name**|**Type**|**Documentation** 389 -|Header|BasicHeaderType| 390 -|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. 393 +(% style="width:847.294px" %) 394 +|**Name**|**Type**|(% style="width:397px" %)**Documentation** 395 +|Header|BasicHeaderType|(% style="width:397px" %) 396 +|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. 391 391 392 392 **QueryRegistrationResponseType: **SubmitRegistrationRequestType defines the structure of a registry submit registration response document. 393 393 394 394 Derivation: 395 395 396 -//MessageType// (restriction) 397 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)398 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]QueryRegistrationResponseType402 +* //MessageType// (restriction) 403 +** RegistryInterfaceType (restriction) 404 +*** QueryRegistrationResponseType 399 399 400 400 Content: 401 401 ... ... @@ -403,18 +403,19 @@ 403 403 404 404 Element Documentation: 405 405 406 -|**Name**|**Type**|**Documentation** 407 -|Header|BasicHeaderType| 408 -|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. 409 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 412 +(% style="width:856.294px" %) 413 +|**Name**|(% style="width:235px" %)**Type**|(% style="width:407px" %)**Documentation** 414 +|Header|(% style="width:235px" %)BasicHeaderType|(% style="width:407px" %) 415 +|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. 416 +|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. 410 410 411 411 **SubmitStructureRequestType: **SubmitStructureRequestType defines the structure of a registry submit structure request document. 412 412 413 413 Derivation: 414 414 415 -//MessageType// (restriction) 416 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)417 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitStructureRequestType422 +* //MessageType// (restriction) 423 +** RegistryInterfaceType (restriction) 424 +*** SubmitStructureRequestType 418 418 419 419 Content: 420 420 ... ... @@ -422,17 +422,18 @@ 422 422 423 423 Element Documentation: 424 424 425 -|**Name**|**Type**|**Documentation** 426 -|Header|BasicHeaderType| 427 -|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. 432 +(% style="width:870.294px" %) 433 +|**Name**|**Type**|(% style="width:453px" %)**Documentation** 434 +|Header|BasicHeaderType|(% style="width:453px" %) 435 +|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. 428 428 429 429 **SubmitStructureResponseType: **SubmitStructureResponseType defines the structure of a registry submit registration response document. 430 430 431 431 Derivation: 432 432 433 -//MessageType// (restriction) 434 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)435 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitStructureResponseType441 +* //MessageType// (restriction) 442 +** RegistryInterfaceType (restriction) 443 +*** SubmitStructureResponseType 436 436 437 437 Content: 438 438 ... ... @@ -440,18 +440,19 @@ 440 440 441 441 Element Documentation: 442 442 443 -|**Name**|**Type**|**Documentation** 444 -|Header|BasicHeaderType| 445 -|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. 446 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 451 +(% style="width:835.294px" %) 452 +|**Name**|(% style="width:246px" %)**Type**|(% style="width:366px" %)**Documentation** 453 +|Header|(% style="width:246px" %)BasicHeaderType|(% style="width:366px" %) 454 +|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. 455 +|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. 447 447 448 448 **SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit subscription request document. 449 449 450 450 Derivation: 451 451 452 -//MessageType// (restriction) 453 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)454 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitSubscriptionsRequestType461 +* //MessageType// (restriction) 462 +** RegistryInterfaceType (restriction) 463 +*** SubmitSubscriptionsRequestType 455 455 456 456 Content: 457 457 ... ... @@ -459,17 +459,18 @@ 459 459 460 460 Element Documentation: 461 461 462 -|**Name**|**Type**|**Documentation** 463 -|Header|BasicHeaderType| 464 -|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. 471 +(% style="width:832.294px" %) 472 +|**Name**|(% style="width:227px" %)**Type**|(% style="width:319px" %)**Documentation** 473 +|Header|(% style="width:227px" %)BasicHeaderType|(% style="width:319px" %) 474 +|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. 465 465 466 466 **SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit subscription response document. 467 467 468 468 Derivation: 469 469 470 -//MessageType// (restriction) 471 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)472 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitSubscriptionsResponseType480 +* //MessageType// (restriction) 481 +** RegistryInterfaceType (restriction) 482 +*** SubmitSubscriptionsResponseType 473 473 474 474 Content: 475 475 ... ... @@ -477,18 +477,19 @@ 477 477 478 478 Element Documentation: 479 479 480 -|**Name**|**Type**|**Documentation** 481 -|Header|BasicHeaderType| 482 -|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. 483 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 490 +(% style="width:843.294px" %) 491 +|**Name**|**Type**|(% style="width:362px" %)**Documentation** 492 +|Header|BasicHeaderType|(% style="width:362px" %) 493 +|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. 494 +|ftr:Footer|ftr:FooterType|(% style="width:362px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 484 484 485 485 **QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query subscription request document. 486 486 487 487 Derivation: 488 488 489 -//MessageType// (restriction) 490 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)491 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]QuerySubscriptionRequestType500 +* //MessageType// (restriction) 501 +** RegistryInterfaceType (restriction) 502 +*** QuerySubscriptionRequestType 492 492 493 493 Content: 494 494 ... ... @@ -496,17 +496,18 @@ 496 496 497 497 Element Documentation: 498 498 499 -|**Name**|**Type**|**Documentation** 500 -|Header|BasicHeaderType| 501 -|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation. 510 +(% style="width:839.294px" %) 511 +|(% style="width:230px" %)**Name**|(% style="width:254px" %)**Type**|(% style="width:352px" %)**Documentation** 512 +|(% style="width:230px" %)Header|(% style="width:254px" %)BasicHeaderType|(% style="width:352px" %) 513 +|(% 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. 502 502 503 503 **QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query subscription response document. 504 504 505 505 Derivation: 506 506 507 -//MessageType// (restriction) 508 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)509 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]QuerySubscriptionResponseType519 +* //MessageType// (restriction) 520 +** RegistryInterfaceType (restriction) 521 +*** QuerySubscriptionResponseType 510 510 511 511 Content: 512 512 ... ... @@ -514,18 +514,19 @@ 514 514 515 515 Element Documentation: 516 516 517 -|**Name**|**Type**|**Documentation** 518 -|Header|BasicHeaderType| 519 -|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. 520 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 529 +(% style="width:912.294px" %) 530 +|**Name**|(% style="width:304px" %)**Type**|(% style="width:336px" %)**Documentation** 531 +|Header|(% style="width:304px" %)BasicHeaderType|(% style="width:336px" %) 532 +|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. 533 +|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. 521 521 522 522 **NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry notification document. 523 523 524 524 Derivation: 525 525 526 -//MessageType// (restriction) 527 - 528 - 539 +* //MessageType// (restriction) 540 +** RegistryInterfaceType (restriction) 541 +*** NotifyRegistryEventType 529 529 530 530 Content: 531 531 ... ... @@ -533,16 +533,17 @@ 533 533 534 534 Element Documentation: 535 535 536 -|**Name**|**Type**|**Documentation** 537 -|Header|BasicHeaderType| 538 -|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. 549 +(% style="width:836.294px" %) 550 +|**Name**|**Type**|(% style="width:473px" %)**Documentation** 551 +|Header|BasicHeaderType|(% style="width:473px" %) 552 +|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. 539 539 540 540 **DataQueryType: **DataQueryType defines the structure of a data query message. 541 541 542 542 Derivation: 543 543 544 -//MessageType// (restriction) 545 - 558 +* //MessageType// (restriction) 559 +** DataQueryType 546 546 547 547 Content: 548 548 ... ... @@ -550,17 +550,18 @@ 550 550 551 551 Element Documentation: 552 552 553 -|**Name**|**Type**|**Documentation** 554 -|Header|BasicHeaderType| 555 -|Query|qry:DataQueryType| 567 +(% style="width:839.294px" %) 568 +|(% style="width:244px" %)**Name**|(% style="width:262px" %)**Type**|(% style="width:330px" %)**Documentation** 569 +|(% style="width:244px" %)Header|(% style="width:262px" %)BasicHeaderType|(% style="width:330px" %) 570 +|(% style="width:244px" %)Query|(% style="width:262px" %)qry:DataQueryType|(% style="width:330px" %) 556 556 557 557 **GenericDataQueryType: **DataQueryType defines the structure of a generic data query message. 558 558 559 559 Derivation: 560 560 561 -//MessageType// (restriction) 562 - 563 - 576 +* //MessageType// (restriction) 577 +** DataQueryType (restriction) 578 +*** GenericDataQueryType 564 564 565 565 Content: 566 566 ... ... @@ -568,18 +568,19 @@ 568 568 569 569 Element Documentation: 570 570 571 -|**Name**|**Type**|**Documentation** 572 -|Header|BasicHeaderType| 573 -|Query|qry: GenericDataQueryType| 586 +(% style="width:833.294px" %) 587 +|(% style="width:213px" %)**Name**|(% style="width:243px" %)**Type**|(% style="width:374px" %)**Documentation** 588 +|(% style="width:213px" %)Header|(% style="width:243px" %)BasicHeaderType|(% style="width:374px" %) 589 +|(% style="width:213px" %)Query|(% style="width:243px" %)qry: GenericDataQueryType|(% style="width:374px" %) 574 574 575 575 **GenericTimeSeriesDataQueryType: **GenericTimeSeriesDataQueryType defines the structure of a time series generic data query message. 576 576 577 577 Derivation: 578 578 579 -//MessageType// (restriction) 580 - 581 - 582 - 595 +* //MessageType// (restriction) 596 +** DataQueryType (restriction) 597 +*** GenericDataQueryType (restriction) 598 +**** GenericTimeSeriesDataQueryType 583 583 584 584 Content: 585 585 ... ... @@ -587,17 +587,18 @@ 587 587 588 588 Element Documentation: 589 589 590 -|**Name**|**Type**|**Documentation** 591 -|Header|BasicHeaderType| 592 -|Query|qry: GenericTimeSeriesDat aQueryType| 606 +(% style="width:909.294px" %) 607 +|(% style="width:221px" %)**Name**|(% style="width:305px" %)**Type**|(% style="width:380px" %)**Documentation** 608 +|(% style="width:221px" %)Header|(% style="width:305px" %)BasicHeaderType|(% style="width:380px" %) 609 +|(% style="width:221px" %)Query|(% style="width:305px" %)qry: GenericTimeSeriesDat aQueryType|(% style="width:380px" %) 593 593 594 594 **StructureSpecificTimeSeriesDataQueryType: **StructureSpecificTimeSeriesDataQueryType defines the structure of a time series generic data query message. 595 595 596 596 Derivation: 597 597 598 -//MessageType// (restriction) 599 - 600 - 615 +* //MessageType// (restriction) 616 +** DataQueryType (restriction) 617 +*** StructureSpecificTimeSeriesDataQueryType 601 601 602 602 Content: 603 603 ... ... @@ -605,16 +605,17 @@ 605 605 606 606 Element Documentation: 607 607 608 -|**Name**|**Type**|**Documentation** 609 -|Header|BasicHeaderType| 610 -|Query|qry: TimeSeriesDataQueryT ype| 625 +(% style="width:903.294px" %) 626 +|(% style="width:189px" %)**Name**|(% style="width:259px" %)**Type**|(% style="width:452px" %)**Documentation** 627 +|(% style="width:189px" %)Header|(% style="width:259px" %)BasicHeaderType|(% style="width:452px" %) 628 +|(% style="width:189px" %)Query|(% style="width:259px" %)qry: TimeSeriesDataQueryType|(% style="width:452px" %) 611 611 612 612 **MetadataQueryType: **MetadataQueryType defines the structure of a reference metadata query message. 613 613 614 614 Derivation: 615 615 616 -//MessageType// (restriction) 617 - 634 +* //MessageType// (restriction) 635 +** MetadataQueryType 618 618 619 619 Content: 620 620 ... ... @@ -622,16 +622,17 @@ 622 622 623 623 Element Documentation: 624 624 625 -|**Name**|**Type**|**Documentation** 626 -|Header|BasicHeaderType| 627 -|Query|qry: MetadataQueryType| 643 +(% style="width:858.294px" %) 644 +|(% style="width:138px" %)**Name**|(% style="width:246px" %)**Type**|(% style="width:471px" %)**Documentation** 645 +|(% style="width:138px" %)Header|(% style="width:246px" %)BasicHeaderType|(% style="width:471px" %) 646 +|(% style="width:138px" %)Query|(% style="width:246px" %)qry: MetadataQueryType|(% style="width:471px" %) 628 628 629 629 **DataSchemaQueryType: **DataSchemaQueryType defines the structure of a data schema query message. 630 630 631 631 Derivation: 632 632 633 -//MessageType// (restriction) 634 - 652 +* //MessageType// (restriction) 653 +** DataSchemaQueryType 635 635 636 636 Content: 637 637 ... ... @@ -639,16 +639,17 @@ 639 639 640 640 Element Documentation: 641 641 642 -|**Name**|**Type**|**Documentation** 643 -|Header|BasicHeaderType| 644 -|Query|qry: DataSchemaQueryType| 661 +(% style="width:895.294px" %) 662 +|(% style="width:185px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:413px" %)**Documentation** 663 +|(% style="width:185px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:413px" %) 664 +|(% style="width:185px" %)Query|(% style="width:294px" %)qry: DataSchemaQueryType|(% style="width:413px" %) 645 645 646 646 **MetadataSchemaQueryType: **MetadataSchemaQueryType defines the structure of a metadata schema query message. 647 647 648 648 Derivation: 649 649 650 -//MessageType// (restriction) 651 - 670 +* //MessageType// (restriction) 671 +** MetadataSchemaQueryType 652 652 653 653 Content: 654 654 ... ... @@ -656,16 +656,17 @@ 656 656 657 657 Element Documentation: 658 658 659 -|**Name**|**Type**|**Documentation** 660 -|Header|BasicHeaderType| 661 -|Query|qry: MetadataSchemaQueryT ype| 679 +(% style="width:897.294px" %) 680 +|(% style="width:166px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:447px" %)**Documentation** 681 +|(% style="width:166px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:447px" %) 682 +|(% style="width:166px" %)Query|(% style="width:281px" %)qry: MetadataSchemaQueryType|(% style="width:447px" %) 662 662 663 663 **StructuresQueryType: **StructuresQueryType defines the structure of a structures query message. 664 664 665 665 Derivation: 666 666 667 -//MessageType// (restriction) 668 - 688 +* //MessageType// (restriction) 689 +** StructuresQueryType 669 669 670 670 Content: 671 671 ... ... @@ -673,16 +673,17 @@ 673 673 674 674 Element Documentation: 675 675 676 -|**Name**|**Type**|**Documentation** 677 -|Header|BasicHeaderType| 678 -|Query|qry: StructuresQueryType| 697 +(% style="width:886.294px" %) 698 +|(% style="width:223px" %)**Name**|(% style="width:255px" %)**Type**|(% style="width:405px" %)**Documentation** 699 +|(% style="width:223px" %)Header|(% style="width:255px" %)BasicHeaderType|(% style="width:405px" %) 700 +|(% style="width:223px" %)Query|(% style="width:255px" %)qry: StructuresQueryType|(% style="width:405px" %) 679 679 680 680 **DataflowQueryType: **DataflowQueryType defines the structure of a dataflow query message. 681 681 682 682 Derivation: 683 683 684 -//MessageType// (restriction) 685 - 706 +* //MessageType// (restriction) 707 +** DataflowQueryType 686 686 687 687 Content: 688 688 ... ... @@ -690,16 +690,17 @@ 690 690 691 691 Element Documentation: 692 692 693 -|**Name**|**Type**|**Documentation** 694 -|Header|BasicHeaderType| 695 -|Query|qry: DataflowQueryType| 715 +(% style="width:888.294px" %) 716 +|(% style="width:176px" %)**Name**|(% style="width:260px" %)**Type**|(% style="width:449px" %)**Documentation** 717 +|(% style="width:176px" %)Header|(% style="width:260px" %)BasicHeaderType|(% style="width:449px" %) 718 +|(% style="width:176px" %)Query|(% style="width:260px" %)qry: DataflowQueryType|(% style="width:449px" %) 696 696 697 697 **MetadataflowQueryType: **MetadataflowQueryType defines the structure of a metadata flow query message. 698 698 699 699 Derivation: 700 700 701 -//MessageType// (restriction) 702 - 724 +* //MessageType// (restriction) 725 +** MetadataflowQueryType 703 703 704 704 Content: 705 705 ... ... @@ -707,16 +707,17 @@ 707 707 708 708 Element Documentation: 709 709 710 -|**Name**|**Type**|**Documentation** 711 -|Header|BasicHeaderType| 712 -|Query|qry: MetadataflowQueryTyp e| 733 +(% style="width:886.294px" %) 734 +|(% style="width:199px" %)**Name**|(% style="width:296px" %)**Type**|(% style="width:388px" %)**Documentation** 735 +|(% style="width:199px" %)Header|(% style="width:296px" %)BasicHeaderType|(% style="width:388px" %) 736 +|(% style="width:199px" %)Query|(% style="width:296px" %)qry: MetadataflowQueryType|(% style="width:388px" %) 713 713 714 714 **DataStructureQueryType: **KeyFamilyQueryType defines the structure of a data structure query message. 715 715 716 716 Derivation: 717 717 718 -//MessageType// (restriction) 719 - 742 +* //MessageType// (restriction) 743 +** DataStructureQueryType 720 720 721 721 Content: 722 722 ... ... @@ -724,16 +724,17 @@ 724 724 725 725 Element Documentation: 726 726 727 -|**Name**|**Type**|**Documentation** 728 -|Header|BasicHeaderType| 729 -|Query|qry: DataStructureQueryTy pe| 751 +(% style="width:901.294px" %) 752 +|(% style="width:202px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:393px" %)**Documentation** 753 +|(% style="width:202px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:393px" %) 754 +|(% style="width:202px" %)Query|(% style="width:303px" %)qry: DataStructureQueryType|(% style="width:393px" %) 730 730 731 731 **MetadataStructureQueryType: **MetadataStructureQueryType defines the structure of a metadata structure query message. 732 732 733 733 Derivation: 734 734 735 -//MessageType// (restriction) 736 - 760 +* //MessageType// (restriction) 761 +** MetadataStructureQueryType 737 737 738 738 Content: 739 739 ... ... @@ -741,16 +741,17 @@ 741 741 742 742 Element Documentation: 743 743 744 -|**Name**|**Type**|**Documentation** 745 -|Header|BasicHeaderType| 746 -|Query|qry: MetadataStructureQue ryType| 769 +(% style="width:904.294px" %) 770 +|(% style="width:226px" %)**Name**|(% style="width:275px" %)**Type**|(% style="width:400px" %)**Documentation** 771 +|(% style="width:226px" %)Header|(% style="width:275px" %)BasicHeaderType|(% style="width:400px" %) 772 +|(% style="width:226px" %)Query|(% style="width:275px" %)qry: MetadataStructureQueryType|(% style="width:400px" %) 747 747 748 748 **CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a category scheme query message. 749 749 750 750 Derivation: 751 751 752 -//MessageType// (restriction) 753 - 778 +* //MessageType// (restriction) 779 +** CategorySchemeQueryType 754 754 755 755 Content: 756 756 ... ... @@ -758,16 +758,17 @@ 758 758 759 759 Element Documentation: 760 760 761 -|**Name**|**Type**|**Documentation** 762 -|Header|BasicHeaderType| 763 -|Query|qry: CategorySchemeQueryT ype| 787 +(% style="width:915.294px" %) 788 +|(% style="width:196px" %)**Name**|(% style="width:347px" %)**Type**|(% style="width:369px" %)**Documentation** 789 +|(% style="width:196px" %)Header|(% style="width:347px" %)BasicHeaderType|(% style="width:369px" %) 790 +|(% style="width:196px" %)Query|(% style="width:347px" %)qry: CategorySchemeQueryType|(% style="width:369px" %) 764 764 765 765 **ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a concept scheme query message. 766 766 767 767 Derivation: 768 768 769 -//MessageType// (restriction) 770 - 796 +* //MessageType// (restriction) 797 +** ConceptSchemeQueryType 771 771 772 772 Content: 773 773 ... ... @@ -775,16 +775,17 @@ 775 775 776 776 Element Documentation: 777 777 778 -|**Name**|**Type**|**Documentation** 779 -|Header|BasicHeaderType| 780 -|Query|qry: ConceptSchemeQueryTy pe| 805 +(% style="width:895.294px" %) 806 +|(% style="width:222px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:331px" %)**Documentation** 807 +|(% style="width:222px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:331px" %) 808 +|(% style="width:222px" %)Query|(% style="width:339px" %)qry: ConceptSchemeQueryType|(% style="width:331px" %) 781 781 782 782 **CodelistQueryType: **CodelistQueryType defines the structure of a codelist query message. 783 783 784 784 Derivation: 785 785 786 -//MessageType// (restriction) 787 - 814 +* //MessageType// (restriction) 815 +** CodelistQueryType 788 788 789 789 Content: 790 790 ... ... @@ -792,16 +792,17 @@ 792 792 793 793 Element Documentation: 794 794 795 -|**Name**|**Type**|**Documentation** 796 -|Header|BasicHeaderType| 797 -|Query|qry: CodelistQueryType| 823 +(% style="width:911.294px" %) 824 +|(% style="width:204px" %)**Name**|(% style="width:295px" %)**Type**|(% style="width:409px" %)**Documentation** 825 +|(% style="width:204px" %)Header|(% style="width:295px" %)BasicHeaderType|(% style="width:409px" %) 826 +|(% style="width:204px" %)Query|(% style="width:295px" %)qry:CodelistQueryType|(% style="width:409px" %) 798 798 799 799 **HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical codelist query message. 800 800 801 801 Derivation: 802 802 803 -//MessageType// (restriction) 804 - 832 +* //MessageType// (restriction) 833 +** HierarchicalCodelistQueryType 805 805 806 806 Content: 807 807 ... ... @@ -809,16 +809,17 @@ 809 809 810 810 Element Documentation: 811 811 812 -|**Name**|**Type**|**Documentation** 813 -|Header|BasicHeaderType| 814 -|Query|qry: HierarchicalCodelist QueryType| 841 +(% style="width:906.294px" %) 842 +|(% style="width:191px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:430px" %)**Documentation** 843 +|(% style="width:191px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:430px" %) 844 +|(% style="width:191px" %)Query|(% style="width:281px" %)qry: HierarchicalCodelist QueryType|(% style="width:430px" %) 815 815 816 816 **OrganisationSchemeQueryType: **OrganisationSchemeQueryType defines the structure of an organisation scheme query message. 817 817 818 818 Derivation: 819 819 820 -//MessageType// (restriction) 821 - 850 +* //MessageType// (restriction) 851 +** OrganisationSchemeQueryType 822 822 823 823 Content: 824 824 ... ... @@ -826,16 +826,17 @@ 826 826 827 827 Element Documentation: 828 828 829 -|**Name**|**Type**|**Documentation** 830 -|Header|BasicHeaderType| 831 -|Query|qry: OrganisationSchemeQu eryType| 859 +(% style="width:891.294px" %) 860 +|(% style="width:174px" %)**Name**|(% style="width:292px" %)**Type**|(% style="width:422px" %)**Documentation** 861 +|(% style="width:174px" %)Header|(% style="width:292px" %)BasicHeaderType|(% style="width:422px" %) 862 +|(% style="width:174px" %)Query|(% style="width:292px" %)qry: OrganisationSchemeQueryType|(% style="width:422px" %) 832 832 833 833 **ReportingTaxonomyQueryType: **ReportingTaxonomyQueryType defines the structure of a reporting taxonomy query message. 834 834 835 835 Derivation: 836 836 837 -//MessageType// (restriction) 838 - 868 +* //MessageType// (restriction) 869 +** ReportingTaxonomyQueryType 839 839 840 840 Content: 841 841 ... ... @@ -843,16 +843,17 @@ 843 843 844 844 Element Documentation: 845 845 846 -|**Name**|**Type**|**Documentation** 847 -|Header|BasicHeaderType| 848 -|Query|qry: ReportingTaxonomyQue ryType| 877 +(% style="width:916.294px" %) 878 +|(% style="width:162px" %)**Name**|(% style="width:318px" %)**Type**|(% style="width:434px" %)**Documentation** 879 +|(% style="width:162px" %)Header|(% style="width:318px" %)BasicHeaderType|(% style="width:434px" %) 880 +|(% style="width:162px" %)Query|(% style="width:318px" %)qry: ReportingTaxonomyQueryType|(% style="width:434px" %) 849 849 850 850 **StructureSetQueryType: **StructureSetQueryType defines the structure of a structure set query message. 851 851 852 852 Derivation: 853 853 854 -//MessageType// (restriction) 855 - 886 +* //MessageType// (restriction) 887 +** StructureSetQueryType 856 856 857 857 Content: 858 858 ... ... @@ -860,16 +860,17 @@ 860 860 861 861 Element Documentation: 862 862 863 -|**Name**|**Type**|**Documentation** 864 -|Header|BasicHeaderType| 865 -|Query|qry: StructureSetQueryTyp e| 895 +(% style="width:896.294px" %) 896 +|(% style="width:182px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:417px" %)**Documentation** 897 +|(% style="width:182px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:417px" %) 898 +|(% style="width:182px" %)Query|(% style="width:294px" %)qry: StructureSetQueryType|(% style="width:417px" %) 866 866 867 867 **ProcessQueryType: **CategorizationQueryType defines the structure of a categorization query message. 868 868 869 869 Derivation: 870 870 871 -//MessageType// (restriction) 872 - 904 +* //MessageType// (restriction) 905 +** ProcessQueryType 873 873 874 874 Content: 875 875 ... ... @@ -877,16 +877,17 @@ 877 877 878 878 Element Documentation: 879 879 880 -|**Name**|**Type**|**Documentation** 881 -|Header|BasicHeaderType| 882 -|Query|qry:ProcessQueryType| 913 +(% style="width:907.294px" %) 914 +|(% style="width:189px" %)**Name**|(% style="width:394px" %)**Type**|(% style="width:321px" %)**Documentation** 915 +|(% style="width:189px" %)Header|(% style="width:394px" %)BasicHeaderType|(% style="width:321px" %) 916 +|(% style="width:189px" %)Query|(% style="width:394px" %)qry:ProcessQueryType|(% style="width:321px" %) 883 883 884 884 **CategorisationQueryType: **CategorisationQueryType defines the structure of a categorisation query message. 885 885 886 886 Derivation: 887 887 888 -//MessageType// (restriction) 889 - 922 +* //MessageType// (restriction) 923 +** CategorisationQueryType 890 890 891 891 Content: 892 892 ... ... @@ -894,16 +894,17 @@ 894 894 895 895 Element Documentation: 896 896 897 -|**Name**|**Type**|**Documentation** 898 -|Header|BasicHeaderType| 899 -|Query|qry: CategorisationQueryT ype| 931 +(% style="width:897.294px" %) 932 +|(% style="width:230px" %)**Name**|(% style="width:300px" %)**Type**|(% style="width:363px" %)**Documentation** 933 +|(% style="width:230px" %)Header|(% style="width:300px" %)BasicHeaderType|(% style="width:363px" %) 934 +|(% style="width:230px" %)Query|(% style="width:300px" %)qry: CategorisationQueryType|(% style="width:363px" %) 900 900 901 901 **ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a provision agreement query message. 902 902 903 903 Derivation: 904 904 905 -//MessageType// (restriction) 906 - 940 +* //MessageType// (restriction) 941 +** ProvisionAgreementQueryType 907 907 908 908 Content: 909 909 ... ... @@ -911,16 +911,17 @@ 911 911 912 912 Element Documentation: 913 913 914 -|**Name**|**Type**|**Documentation** 915 -|Header|BasicHeaderType| 916 -|Query|qry: ProvisionAgreementQu eryType| 949 +(% style="width:902.294px" %) 950 +|(% style="width:142px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:418px" %)**Documentation** 951 +|(% style="width:142px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:418px" %) 952 +|(% style="width:142px" %)Query|(% style="width:339px" %)qry: ProvisionAgreementQueryType|(% style="width:418px" %) 917 917 918 918 **ConstraintQueryType: **ConstraintQueryType defines the structure of a constraint query message. 919 919 920 920 Derivation: 921 921 922 -//MessageType// (restriction) 923 - 958 +* //MessageType// (restriction) 959 +** ConstraintQueryType 924 924 925 925 Content: 926 926 ... ... @@ -928,16 +928,17 @@ 928 928 929 929 Element Documentation: 930 930 931 -|**Name**|**Type**|**Documentation** 932 -|Header|BasicHeaderType| 933 -|Query|qry: ConstraintQueryType| 967 +(% style="width:902.294px" %) 968 +|(% style="width:167px" %)**Name**|(% style="width:287px" %)**Type**|(% style="width:445px" %)**Documentation** 969 +|(% style="width:167px" %)Header|(% style="width:287px" %)BasicHeaderType|(% style="width:445px" %) 970 +|(% style="width:167px" %)Query|(% style="width:287px" %)qry: ConstraintQueryType|(% style="width:445px" %) 934 934 935 935 **TransformationSchemeQueryType: **TransformationSchemeQueryType defines the structure of a transformation scheme query message. 936 936 937 937 Derivation: 938 938 939 -//MessageType// (restriction) 940 - 976 +* //MessageType// (restriction) 977 +** TransformationSchemeQueryType 941 941 942 942 Content: 943 943 ... ... @@ -945,16 +945,17 @@ 945 945 946 946 Element Documentation: 947 947 948 -|**Name**|**Type**|**Documentation** 949 -|Header|BasicHeaderType| 950 -|Query|qry: TransformationScheme QueryType| 985 +(% style="width:833.294px" %) 986 +|(% style="width:165px" %)**Name**|(% style="width:325px" %)**Type**|(% style="width:340px" %)**Documentation** 987 +|(% style="width:165px" %)Header|(% style="width:325px" %)BasicHeaderType|(% style="width:340px" %) 988 +|(% style="width:165px" %)Query|(% style="width:325px" %)qry: TransformationSchemeQueryType|(% style="width:340px" %) 951 951 952 952 **VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a VTL mappings scheme query message. 953 953 954 954 Derivation: 955 955 956 -//MessageType// (restriction) 957 - 994 +* //MessageType// (restriction) 995 +** VtlMappingSchemeQueryType 958 958 959 959 Content: 960 960 ... ... @@ -962,16 +962,17 @@ 962 962 963 963 Element Documentation: 964 964 965 -|**Name**|**Type**|**Documentation** 966 -|Header|BasicHeaderType| 967 -|Query|qry: VtlMappingSchemeQuer yType| 1003 +(% style="width:843.294px" %) 1004 +|(% style="width:164px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:373px" %)**Documentation** 1005 +|(% style="width:164px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:373px" %) 1006 +|(% style="width:164px" %)Query|(% style="width:303px" %)qry: VtlMappingSchemeQueryType|(% style="width:373px" %) 968 968 969 969 **NamePersonalisationSchemeQueryType: **NamePersonalisationSchemeQueryType defines the structure of a name personalisation scheme query message. 970 970 971 971 Derivation: 972 972 973 -//MessageType// (restriction) 974 - 1012 +* //MessageType// (restriction) 1013 +** NamePersonalisationSchemeQueryType 975 975 976 976 Content: 977 977 ... ... @@ -979,16 +979,17 @@ 979 979 980 980 Element Documentation: 981 981 982 -|**Name**|**Type**|**Documentation** 983 -|Header|BasicHeaderType| 984 -|Query|qry: NamePersonalisationS chemeQueryType| 1021 +(% style="width:895.294px" %) 1022 +|(% style="width:186px" %)**Name**|(% style="width:363px" %)**Type**|(% style="width:343px" %)**Documentation** 1023 +|(% style="width:186px" %)Header|(% style="width:363px" %)BasicHeaderType|(% style="width:343px" %) 1024 +|(% style="width:186px" %)Query|(% style="width:363px" %)qry: NamePersonalisationSchemeQueryType|(% style="width:343px" %) 985 985 986 986 **RulesetSchemeQueryType: **RulesetSchemeQueryType defines the structure of a ruleset scheme query message. 987 987 988 988 Derivation: 989 989 990 -//MessageType// (restriction) 991 - 1030 +* //MessageType// (restriction) 1031 +** RulesetSchemeQueryType 992 992 993 993 Content: 994 994 ... ... @@ -996,16 +996,17 @@ 996 996 997 997 Element Documentation: 998 998 999 -|**Name**|**Type**|**Documentation** 1000 -|Header|BasicHeaderType| 1001 -|Query|qry: RulesetSchemeQueryTy pe| 1039 +(% style="width:886.294px" %) 1040 +|(% style="width:152px" %)**Name**|(% style="width:311px" %)**Type**|(% style="width:420px" %)**Documentation** 1041 +|(% style="width:152px" %)Header|(% style="width:311px" %)BasicHeaderType|(% style="width:420px" %) 1042 +|(% style="width:152px" %)Query|(% style="width:311px" %)qry: RulesetSchemeQueryType|(% style="width:420px" %) 1002 1002 1003 1003 **UserDefinedOperatorSchemeQueryType: **UserDefinedOperatorSchemeQueryType defines the structure of a user defined operator scheme query message. 1004 1004 1005 1005 Derivation: 1006 1006 1007 -//MessageType// (restriction) 1008 - 1048 +* //MessageType// (restriction) 1049 +** UserDefinedOperatorSchemeQueryType 1009 1009 1010 1010 Content: 1011 1011 ... ... @@ -1013,16 +1013,17 @@ 1013 1013 1014 1014 Element Documentation: 1015 1015 1016 -|**Name**|**Type**|**Documentation** 1017 -|Header|BasicHeaderType| 1018 -|Query|qry: UserDefinedOperatorS chemeQueryType| 1057 +(% style="width:866.294px" %) 1058 +|(% style="width:174px" %)**Name**|(% style="width:358px" %)**Type**|(% style="width:331px" %)**Documentation** 1059 +|(% style="width:174px" %)Header|(% style="width:358px" %)BasicHeaderType|(% style="width:331px" %) 1060 +|(% style="width:174px" %)Query|(% style="width:358px" %)qry: UserDefinedOperatorSchemeQueryType|(% style="width:331px" %) 1019 1019 1020 1020 **CustomTypeSchemeQueryType: **CustomTypeSchemeQueryType defines the structure of a custom type scheme query message. 1021 1021 1022 1022 Derivation: 1023 1023 1024 -//MessageType// (restriction) 1025 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]CustomTypeSchemeQueryType1066 +* //MessageType// (restriction) 1067 +** CustomTypeSchemeQueryType 1026 1026 1027 1027 Content: 1028 1028 ... ... @@ -1030,9 +1030,10 @@ 1030 1030 1031 1031 Element Documentation: 1032 1032 1033 -|**Name**|**Type**|**Documentation** 1034 -|Header|BasicHeaderType| 1035 -|Query|qry: CustomTypeSchemeQuer yType| 1075 +(% style="width:828.294px" %) 1076 +|(% style="width:200px" %)**Name**|(% style="width:308px" %)**Type**|(% style="width:317px" %)**Documentation** 1077 +|(% style="width:200px" %)Header|(% style="width:308px" %)BasicHeaderType|(% style="width:317px" %) 1078 +|(% style="width:200px" %)Query|(% style="width:308px" %)qry: CustomTypeSchemeQueryType|(% style="width:317px" %) 1036 1036 1037 1037 **ErrorType: **ErrorType describes the structure of an error response. 1038 1038 ... ... @@ -1042,8 +1042,9 @@ 1042 1042 1043 1043 Element Documentation: 1044 1044 1045 -|**Name**|**Type**|**Documentation** 1046 -|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. 1088 +(% style="width:899.294px" %) 1089 +|**Name**|**Type**|(% style="width:546px" %)**Documentation** 1090 +|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. 1047 1047 1048 1048 **//BaseHeaderType//: **BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this 1049 1049 ... ... @@ -1053,29 +1053,30 @@ 1053 1053 1054 1054 Element Documentation: 1055 1055 1056 -|**Name**|**Type**|**Documentation** 1057 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1058 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1059 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1060 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1061 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1062 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1063 -|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. 1064 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1065 -|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). 1066 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1067 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1068 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1069 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1070 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1071 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1100 +(% style="width:891.294px" %) 1101 +|**Name**|**Type**|(% style="width:552px" %)**Documentation** 1102 +|ID|com:IDType|(% style="width:552px" %)ID identifies an identification for the message, assigned by the sender. 1103 +|Test|xs:boolean|(% style="width:552px" %)Test indicates whether the message is for test purposes or not. 1104 +|Prepared|HeaderTimeType|(% style="width:552px" %)Prepared is the date the message was prepared. 1105 +|Sender|SenderType|(% style="width:552px" %)Sender is information about the party that is transmitting the message. 1106 +|Receiver|PartyType|(% style="width:552px" %)Receiver is information about the party that is the intended recipient of the message. 1107 +|com:Name|com:TextType|(% style="width:552px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1108 +|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. 1109 +|DataProvider|com: DataProviderReferenceType|(% style="width:552px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1110 +|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). 1111 +|DataSetID|com:IDType|(% style="width:552px" %)DataSetID provides an identifier for a contained data set. 1112 +|Extracted|xs:dateTime|(% style="width:552px" %)Extracted is a time-stamp from the system rendering the data. 1113 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data). 1114 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data). 1115 +|EmbargoDate|xs:dateTime|(% style="width:552px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1116 +|Source|com:TextType|(% style="width:552px" %)Source provides human-readable information about the source of the data. 1072 1072 1073 1073 **StructureHeaderType: **StructureHeaderType defines the structure for structural metadata messages. 1074 1074 1075 1075 Derivation: 1076 1076 1077 -//BaseHeaderType// (restriction) 1078 - 1122 +* //BaseHeaderType// (restriction) 1123 +** StructureHeaderType 1079 1079 1080 1080 Content: 1081 1081 ... ... @@ -1083,21 +1083,22 @@ 1083 1083 1084 1084 Element Documentation: 1085 1085 1086 -|**Name**|**Type**|**Documentation** 1087 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1088 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1089 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1090 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1091 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1092 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1093 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1131 +(% style="width:1099.29px" %) 1132 +|**Name**|(% style="width:224px" %)**Type**|(% style="width:663px" %)**Documentation** 1133 +|ID|(% style="width:224px" %)com:IDType|(% style="width:663px" %)ID identifies an identification for the message, assigned by the sender. 1134 +|Test|(% style="width:224px" %)xs:boolean|(% style="width:663px" %)Test indicates whether the message is for test purposes or not. 1135 +|Prepared|(% style="width:224px" %)HeaderTimeType|(% style="width:663px" %)Prepared is the date the message was prepared. 1136 +|Sender|(% style="width:224px" %)SenderType|(% style="width:663px" %)Sender is information about the party that is transmitting the message. 1137 +|Receiver|(% style="width:224px" %)PartyType|(% style="width:663px" %)Receiver is information about the party that is the intended recipient of the message. 1138 +|com:Name|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1139 +|Source|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Source provides human-readable information about the source of the data. 1094 1094 1095 1095 **GenericDataHeaderType: **GenericDataHeaderType defines the header structure for a generic data message. 1096 1096 1097 1097 Derivation: 1098 1098 1099 -//BaseHeaderType// (restriction) 1100 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]GenericDataHeaderType1145 +* //BaseHeaderType// (restriction) 1146 +** GenericDataHeaderType 1101 1101 1102 1102 Content: 1103 1103 ... ... @@ -1105,30 +1105,31 @@ 1105 1105 1106 1106 Element Documentation: 1107 1107 1108 -|**Name**|**Type**|**Documentation** 1109 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1110 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1111 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1112 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1113 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1114 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1115 -|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. 1116 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1117 -|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). 1118 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1119 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1120 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1121 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1122 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1123 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1154 +(% style="width:895.294px" %) 1155 +|**Name**|**Type**|(% style="width:556px" %)**Documentation** 1156 +|ID|com:IDType|(% style="width:556px" %)ID identifies an identification for the message, assigned by the sender. 1157 +|Test|xs:boolean|(% style="width:556px" %)Test indicates whether the message is for test purposes or not. 1158 +|Prepared|HeaderTimeType|(% style="width:556px" %)Prepared is the date the message was prepared. 1159 +|Sender|SenderType|(% style="width:556px" %)Sender is information about the party that is transmitting the message. 1160 +|Receiver|PartyType|(% style="width:556px" %)Receiver is information about the party that is the intended recipient of the message. 1161 +|com:Name|com:TextType|(% style="width:556px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1162 +|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. 1163 +|DataProvider|com: DataProviderReferenceType|(% style="width:556px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1164 +|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). 1165 +|DataSetID|com:IDType|(% style="width:556px" %)DataSetID provides an identifier for a contained data set. 1166 +|Extracted|xs:dateTime|(% style="width:556px" %)Extracted is a time-stamp from the system rendering the data. 1167 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data). 1168 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data). 1169 +|EmbargoDate|xs:dateTime|(% style="width:556px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1170 +|Source|com:TextType|(% style="width:556px" %)Source provides human-readable information about the source of the data. 1124 1124 1125 1125 **GenericTimeSeriesDataHeaderType: **GenericTimeSeriesDataHeaderType defines the header structure for a time series only generic data message. 1126 1126 1127 1127 Derivation: 1128 1128 1129 -//BaseHeaderType// (restriction) 1130 - 1131 - 1176 +* //BaseHeaderType// (restriction) 1177 +** GenericDataHeaderType (restriction) 1178 +*** GenericTimeSeriesDataHeaderType 1132 1132 1133 1133 Content: 1134 1134 ... ... @@ -1136,29 +1136,30 @@ 1136 1136 1137 1137 Element Documentation: 1138 1138 1139 -|**Name**|**Type**|**Documentation** 1140 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1141 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1142 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1143 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1144 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1145 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1146 -|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. 1147 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1148 -|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). 1149 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1150 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1151 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1152 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1153 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1154 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1186 +(% style="width:926.294px" %) 1187 +|**Name**|**Type**|(% style="width:497px" %)**Documentation** 1188 +|ID|com:IDType|(% style="width:497px" %)ID identifies an identification for the message, assigned by the sender. 1189 +|Test|xs:boolean|(% style="width:497px" %)Test indicates whether the message is for test purposes or not. 1190 +|Prepared|HeaderTimeType|(% style="width:497px" %)Prepared is the date the message was prepared. 1191 +|Sender|SenderType|(% style="width:497px" %)Sender is information about the party that is transmitting the message. 1192 +|Receiver|PartyType|(% style="width:497px" %)Receiver is information about the party that is the intended recipient of the message. 1193 +|com:Name|com:TextType|(% style="width:497px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1194 +|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. 1195 +|DataProvider|com: DataProviderReferenceType|(% style="width:497px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1196 +|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). 1197 +|DataSetID|com:IDType|(% style="width:497px" %)DataSetID provides an identifier for a contained data set. 1198 +|Extracted|xs:dateTime|(% style="width:497px" %)Extracted is a time-stamp from the system rendering the data. 1199 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data). 1200 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data). 1201 +|EmbargoDate|xs:dateTime|(% style="width:497px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1202 +|Source|com:TextType|(% style="width:497px" %)Source provides human-readable information about the source of the data. 1155 1155 1156 1156 **StructureSpecificDataHeaderType: **StructureSpecificDataHeaderType defines the header structure for a structure specific data message. 1157 1157 1158 1158 Derivation: 1159 1159 1160 -//BaseHeaderType// (restriction) 1161 - 1208 +* //BaseHeaderType// (restriction) 1209 +** StructureSpecificDataHeaderType 1162 1162 1163 1163 Content: 1164 1164 ... ... @@ -1166,30 +1166,31 @@ 1166 1166 1167 1167 Element Documentation: 1168 1168 1169 -|**Name**|**Type**|**Documentation** 1170 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1171 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1172 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1173 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1174 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1175 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1176 -|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. 1177 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1178 -|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). 1179 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1180 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1181 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1182 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1183 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1184 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1217 +(% style="width:930.294px" %) 1218 +|**Name**|**Type**|(% style="width:578px" %)**Documentation** 1219 +|ID|com:IDType|(% style="width:578px" %)ID identifies an identification for the message, assigned by the sender. 1220 +|Test|xs:boolean|(% style="width:578px" %)Test indicates whether the message is for test purposes or not. 1221 +|Prepared|HeaderTimeType|(% style="width:578px" %)Prepared is the date the message was prepared. 1222 +|Sender|SenderType|(% style="width:578px" %)Sender is information about the party that is transmitting the message. 1223 +|Receiver|PartyType|(% style="width:578px" %)Receiver is information about the party that is the intended recipient of the message. 1224 +|com:Name|com:TextType|(% style="width:578px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1225 +|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. 1226 +|DataProvider|com: DataProviderReferenceType|(% style="width:578px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1227 +|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). 1228 +|DataSetID|com:IDType|(% style="width:578px" %)DataSetID provides an identifier for a contained data set. 1229 +|Extracted|xs:dateTime|(% style="width:578px" %)Extracted is a time-stamp from the system rendering the data. 1230 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data). 1231 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data). 1232 +|EmbargoDate|xs:dateTime|(% style="width:578px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1233 +|Source|com:TextType|(% style="width:578px" %)Source provides human-readable information about the source of the data. 1185 1185 1186 1186 **StructureSpecificTimeSeriesDataHeaderType: **StructureSpecificTimeSeriesDataHeaderType defines the header structure for a time series only structure specific data message. 1187 1187 1188 1188 Derivation: 1189 1189 1190 -//BaseHeaderType// (restriction) 1191 - 1192 - 1239 +* //BaseHeaderType// (restriction) 1240 +** StructureSpecificDataHeaderType (restriction) 1241 +*** StructureSpecificTimeSeriesDataHeaderType 1193 1193 1194 1194 Content: 1195 1195 ... ... @@ -1197,29 +1197,30 @@ 1197 1197 1198 1198 Element Documentation: 1199 1199 1200 -|**Name**|**Type**|**Documentation** 1201 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1202 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1203 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1204 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1205 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1206 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1207 -|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. 1208 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1209 -|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). 1210 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1211 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1212 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1213 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1214 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1215 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1249 +(% style="width:943.294px" %) 1250 +|**Name**|(% style="width:352px" %)**Type**|(% style="width:461px" %)**Documentation** 1251 +|ID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)ID identifies an identification for the message, assigned by the sender. 1252 +|Test|(% style="width:352px" %)xs:boolean|(% style="width:461px" %)Test indicates whether the message is for test purposes or not. 1253 +|Prepared|(% style="width:352px" %)HeaderTimeType|(% style="width:461px" %)Prepared is the date the message was prepared. 1254 +|Sender|(% style="width:352px" %)SenderType|(% style="width:461px" %)Sender is information about the party that is transmitting the message. 1255 +|Receiver|(% style="width:352px" %)PartyType|(% style="width:461px" %)Receiver is information about the party that is the intended recipient of the message. 1256 +|com:Name|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1257 +|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. 1258 +|DataProvider|(% style="width:352px" %)com: DataProviderReferenceType|(% style="width:461px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1259 +|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). 1260 +|DataSetID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)DataSetID provides an identifier for a contained data set. 1261 +|Extracted|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)Extracted is a time-stamp from the system rendering the data. 1262 +|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). 1263 +|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). 1264 +|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. 1265 +|Source|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Source provides human-readable information about the source of the data. 1216 1216 1217 1217 **GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic reference metadata. 1218 1218 1219 1219 Derivation: 1220 1220 1221 -//BaseHeaderType// (restriction) 1222 - 1271 +* //BaseHeaderType// (restriction) 1272 +** GenericMetadataHeaderType 1223 1223 1224 1224 Content: 1225 1225 ... ... @@ -1227,26 +1227,27 @@ 1227 1227 1228 1228 Element Documentation: 1229 1229 1230 -|**Name**|**Type**|**Documentation** 1231 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1232 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1233 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1234 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1235 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1236 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1237 -|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. 1238 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1239 -|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). 1240 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1241 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1242 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1280 +(% style="width:928.294px" %) 1281 +|**Name**|**Type**|(% style="width:554px" %)**Documentation** 1282 +|ID|com:IDType|(% style="width:554px" %)ID identifies an identification for the message, assigned by the sender. 1283 +|Test|xs:boolean|(% style="width:554px" %)Test indicates whether the message is for test purposes or not. 1284 +|Prepared|HeaderTimeType|(% style="width:554px" %)Prepared is the date the message was prepared. 1285 +|Sender|SenderType|(% style="width:554px" %)Sender is information about the party that is transmitting the message. 1286 +|Receiver|PartyType|(% style="width:554px" %)Receiver is information about the party that is the intended recipient of the message. 1287 +|com:Name|com:TextType|(% style="width:554px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1288 +|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. 1289 +|DataProvider|com: DataProviderReferenceType|(% style="width:554px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1290 +|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). 1291 +|DataSetID|com:IDType|(% style="width:554px" %)DataSetID provides an identifier for a contained data set. 1292 +|Extracted|xs:dateTime|(% style="width:554px" %)Extracted is a time-stamp from the system rendering the data. 1293 +|Source|com:TextType|(% style="width:554px" %)Source provides human-readable information about the source of the data. 1243 1243 1244 1244 **StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for metadata structure definition specific reference metadata messages. 1245 1245 1246 1246 Derivation: 1247 1247 1248 -//BaseHeaderType// (restriction) 1249 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureSpecificMetadataHeaderType1299 +* //BaseHeaderType// (restriction) 1300 +** StructureSpecificMetadataHeaderType 1250 1250 1251 1251 Content: 1252 1252 ... ... @@ -1254,26 +1254,27 @@ 1254 1254 1255 1255 Element Documentation: 1256 1256 1257 -|**Name**|**Type**|**Documentation** 1258 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1259 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1260 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1261 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1262 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1263 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1264 -|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. 1265 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1266 -|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). 1267 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1268 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1269 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1308 +(% style="width:996.294px" %) 1309 +|**Name**|**Type**|(% style="width:557px" %)**Documentation** 1310 +|ID|com:IDType|(% style="width:557px" %)ID identifies an identification for the message, assigned by the sender. 1311 +|Test|xs:boolean|(% style="width:557px" %)Test indicates whether the message is for test purposes or not. 1312 +|Prepared|HeaderTimeType|(% style="width:557px" %)Prepared is the date the message was prepared. 1313 +|Sender|SenderType|(% style="width:557px" %)Sender is information about the party that is transmitting the message. 1314 +|Receiver|PartyType|(% style="width:557px" %)Receiver is information about the party that is the intended recipient of the message. 1315 +|com:Name|com:TextType|(% style="width:557px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1316 +|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. 1317 +|DataProvider|com: DataProviderReferenceType|(% style="width:557px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1318 +|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). 1319 +|DataSetID|com:IDType|(% style="width:557px" %)DataSetID provides an identifier for a contained data set. 1320 +|Extracted|xs:dateTime|(% style="width:557px" %)Extracted is a time-stamp from the system rendering the data. 1321 +|Source|com:TextType|(% style="width:557px" %)Source provides human-readable information about the source of the data. 1270 1270 1271 1271 **BasicHeaderType: **BasicHeaderType defines the most basic header information used in simple message exchanges. 1272 1272 1273 1273 Derivation: 1274 1274 1275 -//BaseHeaderType// (restriction) 1276 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]BasicHeaderType1327 +* //BaseHeaderType// (restriction) 1328 +** BasicHeaderType 1277 1277 1278 1278 Content: 1279 1279 ... ... @@ -1281,12 +1281,13 @@ 1281 1281 1282 1282 Element Documentation: 1283 1283 1284 -|**Name**|**Type**|**Documentation** 1285 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1286 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1287 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1288 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1289 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1336 +(% style="width:903.294px" %) 1337 +|**Name**|(% style="width:236px" %)**Type**|(% style="width:457px" %)**Documentation** 1338 +|ID|(% style="width:236px" %)com:IDType|(% style="width:457px" %)ID identifies an identification for the message, assigned by the sender. 1339 +|Test|(% style="width:236px" %)xs:boolean|(% style="width:457px" %)Test indicates whether the message is for test purposes or not. 1340 +|Prepared|(% style="width:236px" %)HeaderTimeType|(% style="width:457px" %)Prepared is the date the message was prepared. 1341 +|Sender|(% style="width:236px" %)SenderType|(% style="width:457px" %)Sender is information about the party that is transmitting the message. 1342 +|Receiver|(% style="width:236px" %)PartyType|(% style="width:457px" %)Receiver is information about the party that is the intended recipient of the message. 1290 1290 1291 1291 **PartyType: **PartyType defines the information which is sent about various parties such as senders and receivers of messages. 1292 1292 ... ... @@ -1300,21 +1300,23 @@ 1300 1300 1301 1301 Attribute Documentation: 1302 1302 1303 -|**Name**|**Type**|**Documentation** 1304 -|id|com:IDType|The id attribute holds the identification of the party. 1356 +(% style="width:739.294px" %) 1357 +|(% style="width:125px" %)**Name**|(% style="width:190px" %)**Type**|(% style="width:421px" %)**Documentation** 1358 +|(% style="width:125px" %)id|(% style="width:190px" %)com:IDType|(% style="width:421px" %)The id attribute holds the identification of the party. 1305 1305 1306 1306 Element Documentation: 1307 1307 1308 -|**Name**|**Type**|**Documentation** 1309 -|com:Name|com:TextType|Name is a human-readable name of the party. 1310 -|Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message. 1362 +(% style="width:751.294px" %) 1363 +|(% style="width:134px" %)**Name**|(% style="width:183px" %)**Type**|(% style="width:431px" %)**Documentation** 1364 +|(% style="width:134px" %)com:Name|(% style="width:183px" %)com:TextType|(% style="width:431px" %)Name is a human-readable name of the party. 1365 +|(% style="width:134px" %)Contact|(% style="width:183px" %)ContactType|(% style="width:431px" %)Contact provides contact information for the party in regard to the transmission of the message. 1311 1311 1312 1312 **SenderType: **SenderType extends the basic party structure to add an optional time zone declaration. 1313 1313 1314 1314 Derivation: 1315 1315 1316 -PartyType (extension) 1317 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SenderType1371 +* PartyType (extension) 1372 +** SenderType 1318 1318 1319 1319 Attributes: 1320 1320 ... ... @@ -1326,8 +1326,9 @@ 1326 1326 1327 1327 Attribute Documentation: 1328 1328 1329 -|**Name**|**Type**|**Documentation** 1330 -|id|com:IDType|The id attribute holds the identification of the party. 1384 +(% style="width:824.294px" %) 1385 +|(% style="width:177px" %)**Name**|(% style="width:241px" %)**Type**|(% style="width:403px" %)**Documentation** 1386 +|(% style="width:177px" %)id|(% style="width:241px" %)com:IDType|(% style="width:403px" %)The id attribute holds the identification of the party. 1331 1331 1332 1332 Element Documentation: 1333 1333 ... ... @@ -1354,9 +1354,7 @@ 1354 1354 |URI|xs:anyURI|URI holds an information URL for the contact person. 1355 1355 |Email|xs:string|Email holds the email address for the contact person. 1356 1356 1357 -1. 1358 -11. 1359 -111. Simple Types 1413 +=== 2.1.4 Simple Types === 1360 1360 1361 1361 **HeaderTimeType: **Provides a union type of xs:date and xs:dateTime for the header fields in the message. 1362 1362 ... ... @@ -1364,14 +1364,11 @@ 1364 1364 1365 1365 xs:dateTime, xs:date. 1366 1366 1367 -1. 1368 -11. Message Footer Namespace 1421 +== 2.2 Message Footer Namespace == 1369 1369 1370 1370 **http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer** 1371 1371 1372 -1. 1373 -11. 1374 -111. Summary 1425 +=== 2.2.1 Summary === 1375 1375 1376 1376 Referenced Namespaces: 1377 1377 ... ... @@ -1385,15 +1385,11 @@ 1385 1385 2 Complex Types 1386 1386 1 Simple Type 1387 1387 1388 -1. 1389 -11. 1390 -111. Global Elements 1439 +=== 2.2.2 Global Elements === 1391 1391 1392 1392 **Footer (FooterType): **Footer is used to communicate information such as error and warnings after the payload of a message. 1393 1393 1394 -1. 1395 -11. 1396 -111. Complex Types 1443 +=== 2.2.3 Complex Types === 1397 1397 1398 1398 **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. 1399 1399 ... ... @@ -1411,8 +1411,8 @@ 1411 1411 Derivation: 1412 1412 1413 1413 com:StatusMessageType (restriction) 1414 - 1415 - 1461 +[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension) 1462 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType 1416 1416 1417 1417 Attributes: 1418 1418 ... ... @@ -1433,9 +1433,7 @@ 1433 1433 |**Name**|**Type**|**Documentation** 1434 1434 |com:Text|com:TextType|Text contains the text of the message, in parallel language values. 1435 1435 1436 -1. 1437 -11. 1438 -111. Simple Types 1483 +=== 2.2.4 Simple Types === 1439 1439 1440 1440 **SeverityCodeType:** 1441 1441