Changes for page Part I. Message Namespace

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

From version 3.6
edited by Helena
on 2025/06/23 17:06
Change comment: There is no comment for this version
To version 3.29
edited by Helena
on 2025/06/23 17:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -321,83 +321,84 @@
321 321  
322 322  Element Documentation:
323 323  
324 -|**Name**|**Type**|**Documentation**
325 -|Header|BasicHeaderType|
326 -|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.
327 -|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.
328 -|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.
329 -|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.
330 -|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.
331 -|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.
332 -|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.
333 -|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.
334 -|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
335 -|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.
336 -|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.
337 -|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.
338 338  
339 339  **SubmitRegistrationsRequestType: **SubmitRegistrationsRequestType defines the structure of a registry submit registration requests document.
340 340  
341 341  Derivation:
342 342  
343 -//MessageType// (restriction)
344 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
345 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitRegistrationsRequestType
344 +* //MessageType// (restriction)
345 +** RegistryInterfaceType (restriction)
346 +*** SubmitRegistrationsRequestType
346 346  
347 347  Content:
348 348  
349 -Header, SubmitRegistrationsRequest
350 +* Header, SubmitRegistrationsRequest
351 +* Element Documentation:
350 350  
351 -Element Documentation:
353 +(% style="width:844.294px" %)
354 +|**Name**|**Type**|(% style="width:377px" %)**Documentation**
355 +|Header|BasicHeaderType|(% style="width:377px" %)
356 +|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:377px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
352 352  
353 -|**Name**|**Type**|**Documentation**
354 -|Header|BasicHeaderType|
355 -|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.
356 -
357 357  **SubmitRegistrationsResponseType: **SubmitRegistrationsResponseType defines the structure of a registry submit registration response document.
358 358  
359 359  Derivation:
360 360  
361 -//MessageType// (restriction)
362 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
363 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitRegistrationsResponseType
362 +* //MessageType// (restriction)
363 +** RegistryInterfaceType (restriction)
364 +*** SubmitRegistrationsResponseType
364 364  
365 365  Content:
366 366  
367 -Header, SubmitRegistrationsResponse, ftr:Footer?
368 +* Header, SubmitRegistrationsResponse, ftr:Footer?
369 +* Element Documentation:
368 368  
369 -Element Documentation:
371 +(% style="width:847.294px" %)
372 +|**Name**|(% style="width:210px" %)**Type**|(% style="width:408px" %)**Documentation**
373 +|Header|(% style="width:210px" %)BasicHeaderType|(% style="width:408px" %)
374 +|SubmitRegistrationsR esponse|(% style="width:210px" %)ref: SubmitRegistrationsR esponseType|(% style="width:408px" %)SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
375 +|ftr:Footer|(% style="width:210px" %)ftr:FooterType|(% style="width:408px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
370 370  
371 -|**Name**|**Type**|**Documentation**
372 -|Header|BasicHeaderType|
373 -|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.
374 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
375 -
376 376  **QueryRegistrationRequestType: **QueryRegistrationRequestType defines the structure of a registry query registration request document.
377 377  
378 378  Derivation:
379 379  
380 -//MessageType// (restriction)
381 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
382 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationRequestType
381 +* //MessageType// (restriction)
382 +** RegistryInterfaceType (restriction)
383 +*** QueryRegistrationRequestType
383 383  
384 384  Content:
385 385  
386 -Header, QueryRegistrationRequest
387 +* Header, QueryRegistrationRequest
388 +* Element Documentation:
387 387  
388 -Element Documentation:
390 +(% style="width:847.294px" %)
391 +|**Name**|**Type**|(% style="width:397px" %)**Documentation**
392 +|Header|BasicHeaderType|(% style="width:397px" %)
393 +|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:397px" %)QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys.
389 389  
390 -|**Name**|**Type**|**Documentation**
391 -|Header|BasicHeaderType|
392 -|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 -
394 394  **QueryRegistrationResponseType: **SubmitRegistrationRequestType defines the structure of a registry submit registration response document.
395 395  
396 396  Derivation:
397 397  
398 -//MessageType// (restriction)
399 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
400 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationResponseType
399 +* //MessageType// (restriction)
400 +** RegistryInterfaceType (restriction)
401 +*** QueryRegistrationResponseType
401 401  
402 402  Content:
403 403  
... ... @@ -405,18 +405,19 @@
405 405  
406 406  Element Documentation:
407 407  
408 -|**Name**|**Type**|**Documentation**
409 -|Header|BasicHeaderType|
410 -|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.
411 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
409 +(% style="width:856.294px" %)
410 +|**Name**|(% style="width:235px" %)**Type**|(% style="width:407px" %)**Documentation**
411 +|Header|(% style="width:235px" %)BasicHeaderType|(% style="width:407px" %)
412 +|QueryRegistrationRes ponse|(% style="width:235px" %)ref: QueryRegistrationRes ponseType|(% style="width:407px" %)QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.
413 +|ftr:Footer|(% style="width:235px" %)ftr:FooterType|(% style="width:407px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
412 412  
413 413  **SubmitStructureRequestType: **SubmitStructureRequestType defines the structure of a registry submit structure request document.
414 414  
415 415  Derivation:
416 416  
417 -//MessageType// (restriction)
418 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
419 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureRequestType
419 +* //MessageType// (restriction)
420 +** RegistryInterfaceType (restriction)
421 +*** SubmitStructureRequestType
420 420  
421 421  Content:
422 422  
... ... @@ -424,629 +424,630 @@
424 424  
425 425  Element Documentation:
426 426  
427 -|**Name**|**Type**|**Documentation**
428 -|Header|BasicHeaderType|
429 -|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.
429 +(% style="width:870.294px" %)
430 +|**Name**|**Type**|(% style="width:453px" %)**Documentation**
431 +|Header|BasicHeaderType|(% style="width:453px" %)
432 +|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:453px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information.
430 430  
431 431  **SubmitStructureResponseType: **SubmitStructureResponseType defines the structure of a registry submit registration response document.
432 432  
433 433  Derivation:
434 434  
435 -//MessageType// (restriction)
436 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
437 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureResponseType
438 +* //MessageType// (restriction)
439 +** RegistryInterfaceType (restriction)
440 +*** SubmitStructureResponseType
438 438  
439 439  Content:
440 440  
441 -Header, SubmitStructureResponse, ftr:Footer?
444 +* Header, SubmitStructureResponse, ftr:Footer?
445 +* Element Documentation:
442 442  
443 -Element Documentation:
447 +(% style="width:835.294px" %)
448 +|**Name**|(% style="width:246px" %)**Type**|(% style="width:366px" %)**Documentation**
449 +|Header|(% style="width:246px" %)BasicHeaderType|(% style="width:366px" %)
450 +|SubmitStructureRespo nse|(% style="width:246px" %)ref: SubmitStructureRespo nseType|(% style="width:366px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
451 +|ftr:Footer|(% style="width:246px" %)ftr:FooterType|(% style="width:366px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
444 444  
445 -|**Name**|**Type**|**Documentation**
446 -|Header|BasicHeaderType|
447 -|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.
448 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
449 -
450 450  **SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit subscription request document.
451 451  
452 452  Derivation:
453 453  
454 -//MessageType// (restriction)
455 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
456 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsRequestType
457 +* //MessageType// (restriction)
458 +** RegistryInterfaceType (restriction)
459 +*** SubmitSubscriptionsRequestType
457 457  
458 458  Content:
459 459  
460 -Header, SubmitSubscriptionsRequest
463 +* Header, SubmitSubscriptionsRequest
464 +* Element Documentation:
461 461  
462 -Element Documentation:
466 +(% style="width:832.294px" %)
467 +|**Name**|(% style="width:227px" %)**Type**|(% style="width:319px" %)**Documentation**
468 +|Header|(% style="width:227px" %)BasicHeaderType|(% style="width:319px" %)
469 +|SubmitSubscriptionsR equest|(% style="width:227px" %)ref: SubmitSubscriptionsR equestType|(% style="width:319px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
463 463  
464 -|**Name**|**Type**|**Documentation**
465 -|Header|BasicHeaderType|
466 -|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.
467 -
468 468  **SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit subscription response document.
469 469  
470 470  Derivation:
471 471  
472 -//MessageType// (restriction)
473 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
474 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsResponseType
475 +* //MessageType// (restriction)
476 +** RegistryInterfaceType (restriction)
477 +*** SubmitSubscriptionsResponseType
475 475  
476 476  Content:
477 477  
478 -Header, SubmitSubscriptionsResponse, ftr:Footer?
481 +* Header, SubmitSubscriptionsResponse, ftr:Footer?
482 +* Element Documentation:
479 479  
480 -Element Documentation:
484 +(% style="width:843.294px" %)
485 +|**Name**|**Type**|(% style="width:362px" %)**Documentation**
486 +|Header|BasicHeaderType|(% style="width:362px" %)
487 +|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:362px" %)SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID.
488 +|ftr:Footer|ftr:FooterType|(% style="width:362px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
481 481  
482 -|**Name**|**Type**|**Documentation**
483 -|Header|BasicHeaderType|
484 -|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.
485 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
486 -
487 487  **QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query subscription request document.
488 488  
489 489  Derivation:
490 490  
491 -//MessageType// (restriction)
492 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
493 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionRequestType
494 +* //MessageType// (restriction)
495 +** RegistryInterfaceType (restriction)
496 +*** QuerySubscriptionRequestType
494 494  
495 495  Content:
496 496  
497 -Header, QuerySubscriptionRequest
500 +* Header, QuerySubscriptionRequest
501 +* Element Documentation:
498 498  
499 -Element Documentation:
503 +(% style="width:839.294px" %)
504 +|(% style="width:230px" %)**Name**|(% style="width:254px" %)**Type**|(% style="width:352px" %)**Documentation**
505 +|(% style="width:230px" %)Header|(% style="width:254px" %)BasicHeaderType|(% style="width:352px" %)
506 +|(% style="width:230px" %)QuerySubscriptionReq uest|(% style="width:254px" %)ref: QuerySubscriptionReq uestType|(% style="width:352px" %)QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
500 500  
501 -|**Name**|**Type**|**Documentation**
502 -|Header|BasicHeaderType|
503 -|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
504 -
505 505  **QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query subscription response document.
506 506  
507 507  Derivation:
508 508  
509 -//MessageType// (restriction)
510 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
511 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionResponseType
512 +* //MessageType// (restriction)
513 +** RegistryInterfaceType (restriction)
514 +*** QuerySubscriptionResponseType
512 512  
513 513  Content:
514 514  
515 -Header, QuerySubscriptionResponse, ftr:Footer?
518 +* Header, QuerySubscriptionResponse, ftr:Footer?
519 +* Element Documentation:
516 516  
517 -Element Documentation:
521 +(% style="width:912.294px" %)
522 +|**Name**|(% style="width:304px" %)**Type**|(% style="width:336px" %)**Documentation**
523 +|Header|(% style="width:304px" %)BasicHeaderType|(% style="width:336px" %)
524 +|QuerySubscriptionRes ponse|(% style="width:304px" %)ref: QuerySubscriptionRes ponseType|(% style="width:336px" %)QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent.
525 +|ftr:Footer|(% style="width:304px" %)ftr:FooterType|(% style="width:336px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
518 518  
519 -|**Name**|**Type**|**Documentation**
520 -|Header|BasicHeaderType|
521 -|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.
522 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
523 -
524 524  **NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry notification document.
525 525  
526 526  Derivation:
527 527  
528 -//MessageType// (restriction)
529 - RegistryInterfaceType (restriction)
530 - NotifyRegistryEventType
531 +* //MessageType// (restriction)
532 +** RegistryInterfaceType (restriction)
533 +*** NotifyRegistryEventType
531 531  
532 532  Content:
533 533  
534 -Header, NotifyRegistryEvent
537 +* Header, NotifyRegistryEvent
538 +* Element Documentation:
535 535  
536 -Element Documentation:
540 +(% style="width:836.294px" %)
541 +|**Name**|**Type**|(% style="width:473px" %)**Documentation**
542 +|Header|BasicHeaderType|(% style="width:473px" %)
543 +|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|(% style="width:473px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided.
537 537  
538 -|**Name**|**Type**|**Documentation**
539 -|Header|BasicHeaderType|
540 -|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.
541 -
542 542  **DataQueryType: **DataQueryType defines the structure of a data query message.
543 543  
544 544  Derivation:
545 545  
546 -//MessageType// (restriction)
547 - DataQueryType
549 +* //MessageType// (restriction)
550 +** DataQueryType
548 548  
549 549  Content:
550 550  
551 -Header, Query
554 +* Header, Query
555 +* Element Documentation:
552 552  
553 -Element Documentation:
557 +(% style="width:839.294px" %)
558 +|(% style="width:244px" %)**Name**|(% style="width:262px" %)**Type**|(% style="width:330px" %)**Documentation**
559 +|(% style="width:244px" %)Header|(% style="width:262px" %)BasicHeaderType|(% style="width:330px" %)
560 +|(% style="width:244px" %)Query|(% style="width:262px" %)qry:DataQueryType|(% style="width:330px" %)
554 554  
555 -|**Name**|**Type**|**Documentation**
556 -|Header|BasicHeaderType|
557 -|Query|qry:DataQueryType|
558 -
559 559  **GenericDataQueryType: **DataQueryType defines the structure of a generic data query message.
560 560  
561 561  Derivation:
562 562  
563 -//MessageType// (restriction)
564 - DataQueryType (restriction)
565 - GenericDataQueryType
566 +* //MessageType// (restriction)
567 +** DataQueryType (restriction)
568 +*** GenericDataQueryType
566 566  
567 567  Content:
568 568  
569 -Header, Query
572 +* Header, Query
573 +* Element Documentation:
570 570  
571 -Element Documentation:
575 +(% style="width:833.294px" %)
576 +|(% style="width:213px" %)**Name**|(% style="width:243px" %)**Type**|(% style="width:374px" %)**Documentation**
577 +|(% style="width:213px" %)Header|(% style="width:243px" %)BasicHeaderType|(% style="width:374px" %)
578 +|(% style="width:213px" %)Query|(% style="width:243px" %)qry: GenericDataQueryType|(% style="width:374px" %)
572 572  
573 -|**Name**|**Type**|**Documentation**
574 -|Header|BasicHeaderType|
575 -|Query|qry: GenericDataQueryType|
576 -
577 577  **GenericTimeSeriesDataQueryType: **GenericTimeSeriesDataQueryType defines the structure of a time series generic data query message.
578 578  
579 579  Derivation:
580 580  
581 -//MessageType// (restriction)
582 - DataQueryType (restriction)
583 - GenericDataQueryType (restriction)
584 - GenericTimeSeriesDataQueryType
584 +* //MessageType// (restriction)
585 +** DataQueryType (restriction)
586 +*** GenericDataQueryType (restriction)
587 +**** GenericTimeSeriesDataQueryType
585 585  
586 586  Content:
587 587  
588 -Header, Query
591 +* Header, Query
592 +* Element Documentation:
589 589  
590 -Element Documentation:
594 +(% style="width:909.294px" %)
595 +|(% style="width:221px" %)**Name**|(% style="width:305px" %)**Type**|(% style="width:380px" %)**Documentation**
596 +|(% style="width:221px" %)Header|(% style="width:305px" %)BasicHeaderType|(% style="width:380px" %)
597 +|(% style="width:221px" %)Query|(% style="width:305px" %)qry: GenericTimeSeriesDat aQueryType|(% style="width:380px" %)
591 591  
592 -|**Name**|**Type**|**Documentation**
593 -|Header|BasicHeaderType|
594 -|Query|qry: GenericTimeSeriesDat aQueryType|
595 -
596 596  **StructureSpecificTimeSeriesDataQueryType: **StructureSpecificTimeSeriesDataQueryType defines the structure of a time series generic data query message.
597 597  
598 598  Derivation:
599 599  
600 -//MessageType// (restriction)
601 - DataQueryType (restriction)
602 - StructureSpecificTimeSeriesDataQueryType
603 +* //MessageType// (restriction)
604 +** DataQueryType (restriction)
605 +*** StructureSpecificTimeSeriesDataQueryType
603 603  
604 604  Content:
605 605  
606 -Header, Query
609 +* Header, Query
610 +* Element Documentation:
607 607  
608 -Element Documentation:
612 +(% style="width:903.294px" %)
613 +|(% style="width:189px" %)**Name**|(% style="width:259px" %)**Type**|(% style="width:452px" %)**Documentation**
614 +|(% style="width:189px" %)Header|(% style="width:259px" %)BasicHeaderType|(% style="width:452px" %)
615 +|(% style="width:189px" %)Query|(% style="width:259px" %)qry: TimeSeriesDataQueryType|(% style="width:452px" %)
609 609  
610 -|**Name**|**Type**|**Documentation**
611 -|Header|BasicHeaderType|
612 -|Query|qry: TimeSeriesDataQueryT ype|
613 -
614 614  **MetadataQueryType: **MetadataQueryType defines the structure of a reference metadata query message.
615 615  
616 616  Derivation:
617 617  
618 -//MessageType// (restriction)
619 - MetadataQueryType
621 +* //MessageType// (restriction)
622 +** MetadataQueryType
620 620  
621 621  Content:
622 622  
623 -Header, Query
626 +* Header, Query
627 +* Element Documentation:
624 624  
625 -Element Documentation:
629 +(% style="width:858.294px" %)
630 +|(% style="width:138px" %)**Name**|(% style="width:246px" %)**Type**|(% style="width:471px" %)**Documentation**
631 +|(% style="width:138px" %)Header|(% style="width:246px" %)BasicHeaderType|(% style="width:471px" %)
632 +|(% style="width:138px" %)Query|(% style="width:246px" %)qry: MetadataQueryType|(% style="width:471px" %)
626 626  
627 -|**Name**|**Type**|**Documentation**
628 -|Header|BasicHeaderType|
629 -|Query|qry: MetadataQueryType|
630 -
631 631  **DataSchemaQueryType: **DataSchemaQueryType defines the structure of a data schema query message.
632 632  
633 633  Derivation:
634 634  
635 -//MessageType// (restriction)
636 - DataSchemaQueryType
638 +* //MessageType// (restriction)
639 +** DataSchemaQueryType
637 637  
638 638  Content:
639 639  
640 -Header, Query
643 +* Header, Query
644 +* Element Documentation:
641 641  
642 -Element Documentation:
646 +(% style="width:895.294px" %)
647 +|(% style="width:185px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:413px" %)**Documentation**
648 +|(% style="width:185px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:413px" %)
649 +|(% style="width:185px" %)Query|(% style="width:294px" %)qry: DataSchemaQueryType|(% style="width:413px" %)
643 643  
644 -|**Name**|**Type**|**Documentation**
645 -|Header|BasicHeaderType|
646 -|Query|qry: DataSchemaQueryType|
647 -
648 648  **MetadataSchemaQueryType: **MetadataSchemaQueryType defines the structure of a metadata schema query message.
649 649  
650 650  Derivation:
651 651  
652 -//MessageType// (restriction)
653 - MetadataSchemaQueryType
655 +* //MessageType// (restriction)
656 +** MetadataSchemaQueryType
654 654  
655 655  Content:
656 656  
657 -Header, Query
660 +* Header, Query
661 +* Element Documentation:
658 658  
659 -Element Documentation:
663 +(% style="width:897.294px" %)
664 +|(% style="width:166px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:447px" %)**Documentation**
665 +|(% style="width:166px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:447px" %)
666 +|(% style="width:166px" %)Query|(% style="width:281px" %)qry: MetadataSchemaQueryType|(% style="width:447px" %)
660 660  
661 -|**Name**|**Type**|**Documentation**
662 -|Header|BasicHeaderType|
663 -|Query|qry: MetadataSchemaQueryT ype|
664 -
665 665  **StructuresQueryType: **StructuresQueryType defines the structure of a structures query message.
666 666  
667 667  Derivation:
668 668  
669 -//MessageType// (restriction)
670 - StructuresQueryType
672 +* //MessageType// (restriction)
673 +** StructuresQueryType
671 671  
672 672  Content:
673 673  
674 -Header, Query
677 +* Header, Query
678 +* Element Documentation:
675 675  
676 -Element Documentation:
680 +(% style="width:886.294px" %)
681 +|(% style="width:223px" %)**Name**|(% style="width:255px" %)**Type**|(% style="width:405px" %)**Documentation**
682 +|(% style="width:223px" %)Header|(% style="width:255px" %)BasicHeaderType|(% style="width:405px" %)
683 +|(% style="width:223px" %)Query|(% style="width:255px" %)qry: StructuresQueryType|(% style="width:405px" %)
677 677  
678 -|**Name**|**Type**|**Documentation**
679 -|Header|BasicHeaderType|
680 -|Query|qry: StructuresQueryType|
681 -
682 682  **DataflowQueryType: **DataflowQueryType defines the structure of a dataflow query message.
683 683  
684 684  Derivation:
685 685  
686 -//MessageType// (restriction)
687 - DataflowQueryType
689 +* //MessageType// (restriction)
690 +** DataflowQueryType
688 688  
689 689  Content:
690 690  
691 -Header, Query
694 +* Header, Query
695 +* Element Documentation:
692 692  
693 -Element Documentation:
697 +(% style="width:888.294px" %)
698 +|(% style="width:176px" %)**Name**|(% style="width:260px" %)**Type**|(% style="width:449px" %)**Documentation**
699 +|(% style="width:176px" %)Header|(% style="width:260px" %)BasicHeaderType|(% style="width:449px" %)
700 +|(% style="width:176px" %)Query|(% style="width:260px" %)qry: DataflowQueryType|(% style="width:449px" %)
694 694  
695 -|**Name**|**Type**|**Documentation**
696 -|Header|BasicHeaderType|
697 -|Query|qry: DataflowQueryType|
698 -
699 699  **MetadataflowQueryType: **MetadataflowQueryType defines the structure of a metadata flow query message.
700 700  
701 701  Derivation:
702 702  
703 -//MessageType// (restriction)
704 - MetadataflowQueryType
706 +* //MessageType// (restriction)
707 +** MetadataflowQueryType
705 705  
706 706  Content:
707 707  
708 -Header, Query
711 +* Header, Query
712 +* Element Documentation:
709 709  
710 -Element Documentation:
714 +(% style="width:886.294px" %)
715 +|(% style="width:199px" %)**Name**|(% style="width:296px" %)**Type**|(% style="width:388px" %)**Documentation**
716 +|(% style="width:199px" %)Header|(% style="width:296px" %)BasicHeaderType|(% style="width:388px" %)
717 +|(% style="width:199px" %)Query|(% style="width:296px" %)qry: MetadataflowQueryType|(% style="width:388px" %)
711 711  
712 -|**Name**|**Type**|**Documentation**
713 -|Header|BasicHeaderType|
714 -|Query|qry: MetadataflowQueryTyp e|
715 -
716 716  **DataStructureQueryType: **KeyFamilyQueryType defines the structure of a data structure query message.
717 717  
718 718  Derivation:
719 719  
720 -//MessageType// (restriction)
721 - DataStructureQueryType
723 +* //MessageType// (restriction)
724 +** DataStructureQueryType
722 722  
723 723  Content:
724 724  
725 -Header, Query
728 +* Header, Query
729 +* Element Documentation:
726 726  
727 -Element Documentation:
731 +(% style="width:901.294px" %)
732 +|(% style="width:202px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:393px" %)**Documentation**
733 +|(% style="width:202px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:393px" %)
734 +|(% style="width:202px" %)Query|(% style="width:303px" %)qry: DataStructureQueryType|(% style="width:393px" %)
728 728  
729 -|**Name**|**Type**|**Documentation**
730 -|Header|BasicHeaderType|
731 -|Query|qry: DataStructureQueryTy pe|
732 -
733 733  **MetadataStructureQueryType: **MetadataStructureQueryType defines the structure of a metadata structure query message.
734 734  
735 735  Derivation:
736 736  
737 -//MessageType// (restriction)
738 - MetadataStructureQueryType
740 +* //MessageType// (restriction)
741 +** MetadataStructureQueryType
739 739  
740 740  Content:
741 741  
742 -Header, Query
745 +* Header, Query
746 +* Element Documentation:
743 743  
744 -Element Documentation:
748 +(% style="width:904.294px" %)
749 +|(% style="width:226px" %)**Name**|(% style="width:275px" %)**Type**|(% style="width:400px" %)**Documentation**
750 +|(% style="width:226px" %)Header|(% style="width:275px" %)BasicHeaderType|(% style="width:400px" %)
751 +|(% style="width:226px" %)Query|(% style="width:275px" %)qry: MetadataStructureQueryType|(% style="width:400px" %)
745 745  
746 -|**Name**|**Type**|**Documentation**
747 -|Header|BasicHeaderType|
748 -|Query|qry: MetadataStructureQue ryType|
749 -
750 750  **CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a category scheme query message.
751 751  
752 752  Derivation:
753 753  
754 -//MessageType// (restriction)
755 - CategorySchemeQueryType
757 +* //MessageType// (restriction)
758 +** CategorySchemeQueryType
756 756  
757 757  Content:
758 758  
759 -Header, Query
762 +* Header, Query
763 +* Element Documentation:
760 760  
761 -Element Documentation:
765 +(% style="width:915.294px" %)
766 +|(% style="width:196px" %)**Name**|(% style="width:347px" %)**Type**|(% style="width:369px" %)**Documentation**
767 +|(% style="width:196px" %)Header|(% style="width:347px" %)BasicHeaderType|(% style="width:369px" %)
768 +|(% style="width:196px" %)Query|(% style="width:347px" %)qry: CategorySchemeQueryType|(% style="width:369px" %)
762 762  
763 -|**Name**|**Type**|**Documentation**
764 -|Header|BasicHeaderType|
765 -|Query|qry: CategorySchemeQueryT ype|
766 -
767 767  **ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a concept scheme query message.
768 768  
769 769  Derivation:
770 770  
771 -//MessageType// (restriction)
772 - ConceptSchemeQueryType
774 +* //MessageType// (restriction)
775 +** ConceptSchemeQueryType
773 773  
774 774  Content:
775 775  
776 -Header, Query
779 +* Header, Query
780 +* Element Documentation:
777 777  
778 -Element Documentation:
782 +(% style="width:895.294px" %)
783 +|(% style="width:222px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:331px" %)**Documentation**
784 +|(% style="width:222px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:331px" %)
785 +|(% style="width:222px" %)Query|(% style="width:339px" %)qry: ConceptSchemeQueryType|(% style="width:331px" %)
779 779  
780 -|**Name**|**Type**|**Documentation**
781 -|Header|BasicHeaderType|
782 -|Query|qry: ConceptSchemeQueryTy pe|
783 -
784 784  **CodelistQueryType: **CodelistQueryType defines the structure of a codelist query message.
785 785  
786 786  Derivation:
787 787  
788 -//MessageType// (restriction)
789 - CodelistQueryType
791 +* //MessageType// (restriction)
792 +** CodelistQueryType
790 790  
791 791  Content:
792 792  
793 -Header, Query
796 +* Header, Query
797 +* Element Documentation:
794 794  
795 -Element Documentation:
799 +(% style="width:911.294px" %)
800 +|(% style="width:204px" %)**Name**|(% style="width:295px" %)**Type**|(% style="width:409px" %)**Documentation**
801 +|(% style="width:204px" %)Header|(% style="width:295px" %)BasicHeaderType|(% style="width:409px" %)
802 +|(% style="width:204px" %)Query|(% style="width:295px" %)qry:CodelistQueryType|(% style="width:409px" %)
796 796  
797 -|**Name**|**Type**|**Documentation**
798 -|Header|BasicHeaderType|
799 -|Query|qry: CodelistQueryType|
800 -
801 801  **HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical codelist query message.
802 802  
803 803  Derivation:
804 804  
805 -//MessageType// (restriction)
806 - HierarchicalCodelistQueryType
808 +* //MessageType// (restriction)
809 +** HierarchicalCodelistQueryType
807 807  
808 808  Content:
809 809  
810 -Header, Query
813 +* Header, Query
814 +* Element Documentation:
811 811  
812 -Element Documentation:
816 +(% style="width:906.294px" %)
817 +|(% style="width:191px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:430px" %)**Documentation**
818 +|(% style="width:191px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:430px" %)
819 +|(% style="width:191px" %)Query|(% style="width:281px" %)qry: HierarchicalCodelist QueryType|(% style="width:430px" %)
813 813  
814 -|**Name**|**Type**|**Documentation**
815 -|Header|BasicHeaderType|
816 -|Query|qry: HierarchicalCodelist QueryType|
817 -
818 818  **OrganisationSchemeQueryType: **OrganisationSchemeQueryType defines the structure of an organisation scheme query message.
819 819  
820 820  Derivation:
821 821  
822 -//MessageType// (restriction)
823 - OrganisationSchemeQueryType
825 +* //MessageType// (restriction)
826 +** OrganisationSchemeQueryType
824 824  
825 825  Content:
826 826  
827 -Header, Query
830 +* Header, Query
831 +* Element Documentation:
828 828  
829 -Element Documentation:
833 +(% style="width:891.294px" %)
834 +|(% style="width:174px" %)**Name**|(% style="width:292px" %)**Type**|(% style="width:422px" %)**Documentation**
835 +|(% style="width:174px" %)Header|(% style="width:292px" %)BasicHeaderType|(% style="width:422px" %)
836 +|(% style="width:174px" %)Query|(% style="width:292px" %)qry: OrganisationSchemeQueryType|(% style="width:422px" %)
830 830  
831 -|**Name**|**Type**|**Documentation**
832 -|Header|BasicHeaderType|
833 -|Query|qry: OrganisationSchemeQu eryType|
834 -
835 835  **ReportingTaxonomyQueryType: **ReportingTaxonomyQueryType defines the structure of a reporting taxonomy query message.
836 836  
837 837  Derivation:
838 838  
839 -//MessageType// (restriction)
840 - ReportingTaxonomyQueryType
842 +* //MessageType// (restriction)
843 +** ReportingTaxonomyQueryType
841 841  
842 842  Content:
843 843  
844 -Header, Query
847 +* Header, Query
848 +* Element Documentation:
845 845  
846 -Element Documentation:
850 +(% style="width:916.294px" %)
851 +|(% style="width:162px" %)**Name**|(% style="width:318px" %)**Type**|(% style="width:434px" %)**Documentation**
852 +|(% style="width:162px" %)Header|(% style="width:318px" %)BasicHeaderType|(% style="width:434px" %)
853 +|(% style="width:162px" %)Query|(% style="width:318px" %)qry: ReportingTaxonomyQueryType|(% style="width:434px" %)
847 847  
848 -|**Name**|**Type**|**Documentation**
849 -|Header|BasicHeaderType|
850 -|Query|qry: ReportingTaxonomyQue ryType|
851 -
852 852  **StructureSetQueryType: **StructureSetQueryType defines the structure of a structure set query message.
853 853  
854 854  Derivation:
855 855  
856 -//MessageType// (restriction)
857 - StructureSetQueryType
859 +* //MessageType// (restriction)
860 +** StructureSetQueryType
858 858  
859 859  Content:
860 860  
861 -Header, Query
864 +* Header, Query
865 +* Element Documentation:
862 862  
863 -Element Documentation:
867 +(% style="width:896.294px" %)
868 +|(% style="width:182px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:417px" %)**Documentation**
869 +|(% style="width:182px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:417px" %)
870 +|(% style="width:182px" %)Query|(% style="width:294px" %)qry: StructureSetQueryType|(% style="width:417px" %)
864 864  
865 -|**Name**|**Type**|**Documentation**
866 -|Header|BasicHeaderType|
867 -|Query|qry: StructureSetQueryTyp e|
868 -
869 869  **ProcessQueryType: **CategorizationQueryType defines the structure of a categorization query message.
870 870  
871 871  Derivation:
872 872  
873 -//MessageType// (restriction)
874 - ProcessQueryType
876 +* //MessageType// (restriction)
877 +** ProcessQueryType
875 875  
876 876  Content:
877 877  
878 -Header, Query
881 +* Header, Query
882 +* Element Documentation:
879 879  
880 -Element Documentation:
884 +(% style="width:907.294px" %)
885 +|(% style="width:189px" %)**Name**|(% style="width:394px" %)**Type**|(% style="width:321px" %)**Documentation**
886 +|(% style="width:189px" %)Header|(% style="width:394px" %)BasicHeaderType|(% style="width:321px" %)
887 +|(% style="width:189px" %)Query|(% style="width:394px" %)qry:ProcessQueryType|(% style="width:321px" %)
881 881  
882 -|**Name**|**Type**|**Documentation**
883 -|Header|BasicHeaderType|
884 -|Query|qry:ProcessQueryType|
885 -
886 886  **CategorisationQueryType: **CategorisationQueryType defines the structure of a categorisation query message.
887 887  
888 888  Derivation:
889 889  
890 -//MessageType// (restriction)
891 - CategorisationQueryType
893 +* //MessageType// (restriction)
894 +** CategorisationQueryType
892 892  
893 893  Content:
894 894  
895 -Header, Query
898 +* Header, Query
899 +* Element Documentation:
896 896  
897 -Element Documentation:
901 +(% style="width:897.294px" %)
902 +|(% style="width:230px" %)**Name**|(% style="width:300px" %)**Type**|(% style="width:363px" %)**Documentation**
903 +|(% style="width:230px" %)Header|(% style="width:300px" %)BasicHeaderType|(% style="width:363px" %)
904 +|(% style="width:230px" %)Query|(% style="width:300px" %)qry: CategorisationQueryType|(% style="width:363px" %)
898 898  
899 -|**Name**|**Type**|**Documentation**
900 -|Header|BasicHeaderType|
901 -|Query|qry: CategorisationQueryT ype|
902 -
903 903  **ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a provision agreement query message.
904 904  
905 905  Derivation:
906 906  
907 -//MessageType// (restriction)
908 - ProvisionAgreementQueryType
910 +* //MessageType// (restriction)
911 +** ProvisionAgreementQueryType
909 909  
910 910  Content:
911 911  
912 -Header, Query
915 +* Header, Query
916 +* Element Documentation:
913 913  
914 -Element Documentation:
918 +(% style="width:902.294px" %)
919 +|(% style="width:142px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:418px" %)**Documentation**
920 +|(% style="width:142px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:418px" %)
921 +|(% style="width:142px" %)Query|(% style="width:339px" %)qry: ProvisionAgreementQueryType|(% style="width:418px" %)
915 915  
916 -|**Name**|**Type**|**Documentation**
917 -|Header|BasicHeaderType|
918 -|Query|qry: ProvisionAgreementQu eryType|
919 -
920 920  **ConstraintQueryType: **ConstraintQueryType defines the structure of a constraint query message.
921 921  
922 922  Derivation:
923 923  
924 -//MessageType// (restriction)
925 - ConstraintQueryType
927 +* //MessageType// (restriction)
928 +** ConstraintQueryType
926 926  
927 927  Content:
928 928  
929 -Header, Query
932 +* Header, Query
933 +* Element Documentation:
930 930  
931 -Element Documentation:
935 +(% style="width:902.294px" %)
936 +|(% style="width:167px" %)**Name**|(% style="width:287px" %)**Type**|(% style="width:445px" %)**Documentation**
937 +|(% style="width:167px" %)Header|(% style="width:287px" %)BasicHeaderType|(% style="width:445px" %)
938 +|(% style="width:167px" %)Query|(% style="width:287px" %)qry: ConstraintQueryType|(% style="width:445px" %)
932 932  
933 -|**Name**|**Type**|**Documentation**
934 -|Header|BasicHeaderType|
935 -|Query|qry: ConstraintQueryType|
936 -
937 937  **TransformationSchemeQueryType: **TransformationSchemeQueryType defines the structure of a transformation scheme query message.
938 938  
939 939  Derivation:
940 940  
941 -//MessageType// (restriction)
942 - TransformationSchemeQueryType
944 +* //MessageType// (restriction)
945 +** TransformationSchemeQueryType
943 943  
944 944  Content:
945 945  
946 -Header, Query
949 +* Header, Query
950 +* Element Documentation:
947 947  
948 -Element Documentation:
952 +(% style="width:833.294px" %)
953 +|(% style="width:165px" %)**Name**|(% style="width:325px" %)**Type**|(% style="width:340px" %)**Documentation**
954 +|(% style="width:165px" %)Header|(% style="width:325px" %)BasicHeaderType|(% style="width:340px" %)
955 +|(% style="width:165px" %)Query|(% style="width:325px" %)qry: TransformationSchemeQueryType|(% style="width:340px" %)
949 949  
950 -|**Name**|**Type**|**Documentation**
951 -|Header|BasicHeaderType|
952 -|Query|qry: TransformationScheme QueryType|
953 -
954 954  **VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a VTL mappings scheme query message.
955 955  
956 956  Derivation:
957 957  
958 -//MessageType// (restriction)
959 - VtlMappingSchemeQueryType
961 +* //MessageType// (restriction)
962 +** VtlMappingSchemeQueryType
960 960  
961 961  Content:
962 962  
963 -Header, Query
966 +* Header, Query
967 +* Element Documentation:
964 964  
965 -Element Documentation:
969 +(% style="width:843.294px" %)
970 +|(% style="width:164px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:373px" %)**Documentation**
971 +|(% style="width:164px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:373px" %)
972 +|(% style="width:164px" %)Query|(% style="width:303px" %)qry: VtlMappingSchemeQueryType|(% style="width:373px" %)
966 966  
967 -|**Name**|**Type**|**Documentation**
968 -|Header|BasicHeaderType|
969 -|Query|qry: VtlMappingSchemeQuer yType|
970 -
971 971  **NamePersonalisationSchemeQueryType: **NamePersonalisationSchemeQueryType defines the structure of a name personalisation scheme query message.
972 972  
973 973  Derivation:
974 974  
975 -//MessageType// (restriction)
976 - NamePersonalisationSchemeQueryType
978 +* //MessageType// (restriction)
979 +** NamePersonalisationSchemeQueryType
977 977  
978 978  Content:
979 979  
980 -Header, Query
983 +* Header, Query
984 +* Element Documentation:
981 981  
982 -Element Documentation:
986 +(% style="width:895.294px" %)
987 +|(% style="width:186px" %)**Name**|(% style="width:363px" %)**Type**|(% style="width:343px" %)**Documentation**
988 +|(% style="width:186px" %)Header|(% style="width:363px" %)BasicHeaderType|(% style="width:343px" %)
989 +|(% style="width:186px" %)Query|(% style="width:363px" %)qry: NamePersonalisationSchemeQueryType|(% style="width:343px" %)
983 983  
984 -|**Name**|**Type**|**Documentation**
985 -|Header|BasicHeaderType|
986 -|Query|qry: NamePersonalisationS chemeQueryType|
987 -
988 988  **RulesetSchemeQueryType: **RulesetSchemeQueryType defines the structure of a ruleset scheme query message.
989 989  
990 990  Derivation:
991 991  
992 -//MessageType// (restriction)
993 - RulesetSchemeQueryType
995 +* //MessageType// (restriction)
996 +** RulesetSchemeQueryType
994 994  
995 995  Content:
996 996  
997 -Header, Query
1000 +* Header, Query
1001 +* Element Documentation:
998 998  
999 -Element Documentation:
1003 +(% style="width:886.294px" %)
1004 +|(% style="width:152px" %)**Name**|(% style="width:311px" %)**Type**|(% style="width:420px" %)**Documentation**
1005 +|(% style="width:152px" %)Header|(% style="width:311px" %)BasicHeaderType|(% style="width:420px" %)
1006 +|(% style="width:152px" %)Query|(% style="width:311px" %)qry: RulesetSchemeQueryType|(% style="width:420px" %)
1000 1000  
1001 -|**Name**|**Type**|**Documentation**
1002 -|Header|BasicHeaderType|
1003 -|Query|qry: RulesetSchemeQueryTy pe|
1004 -
1005 1005  **UserDefinedOperatorSchemeQueryType: **UserDefinedOperatorSchemeQueryType defines the structure of a user defined operator scheme query message.
1006 1006  
1007 1007  Derivation:
1008 1008  
1009 -//MessageType// (restriction)
1010 - UserDefinedOperatorSchemeQueryType
1012 +* //MessageType// (restriction)
1013 +** UserDefinedOperatorSchemeQueryType
1011 1011  
1012 1012  Content:
1013 1013  
1014 -Header, Query
1017 +* Header, Query
1018 +* Element Documentation:
1015 1015  
1016 -Element Documentation:
1020 +(% style="width:866.294px" %)
1021 +|(% style="width:174px" %)**Name**|(% style="width:358px" %)**Type**|(% style="width:331px" %)**Documentation**
1022 +|(% style="width:174px" %)Header|(% style="width:358px" %)BasicHeaderType|(% style="width:331px" %)
1023 +|(% style="width:174px" %)Query|(% style="width:358px" %)qry: UserDefinedOperatorSchemeQueryType|(% style="width:331px" %)
1017 1017  
1018 -|**Name**|**Type**|**Documentation**
1019 -|Header|BasicHeaderType|
1020 -|Query|qry: UserDefinedOperatorS chemeQueryType|
1021 -
1022 1022  **CustomTypeSchemeQueryType: **CustomTypeSchemeQueryType defines the structure of a custom type scheme query message.
1023 1023  
1024 1024  Derivation:
1025 1025  
1026 -//MessageType// (restriction)
1027 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] CustomTypeSchemeQueryType
1029 +* //MessageType// (restriction)
1030 +** CustomTypeSchemeQueryType
1028 1028  
1029 1029  Content:
1030 1030  
1031 -Header, Query
1034 +* Header, Query
1035 +* Element Documentation:
1032 1032  
1033 -Element Documentation:
1037 +(% style="width:828.294px" %)
1038 +|(% style="width:200px" %)**Name**|(% style="width:308px" %)**Type**|(% style="width:317px" %)**Documentation**
1039 +|(% style="width:200px" %)Header|(% style="width:308px" %)BasicHeaderType|(% style="width:317px" %)
1040 +|(% style="width:200px" %)Query|(% style="width:308px" %)qry: CustomTypeSchemeQueryType|(% style="width:317px" %)
1034 1034  
1035 -|**Name**|**Type**|**Documentation**
1036 -|Header|BasicHeaderType|
1037 -|Query|qry: CustomTypeSchemeQuer yType|
1038 -
1039 1039  **ErrorType: **ErrorType describes the structure of an error response.
1040 1040  
1041 1041  Content:
1042 1042  
1043 -ErrorMessage+
1046 +* ErrorMessage+
1047 +* Element Documentation:
1044 1044  
1045 -Element Documentation:
1049 +(% style="width:899.294px" %)
1050 +|**Name**|**Type**|(% style="width:546px" %)**Documentation**
1051 +|ErrorMessage|com: CodedStatusMessageTy pe|(% style="width:546px" %)ErrorMessage contains the error message. It can occur multiple times to communicate message for multiple errors, or to communicate the error message in parallel languages. If both messages for multiple errors and parallel language messages are used, then each error message should be given a code in order to distinguish message for unique errors.
1046 1046  
1047 -|**Name**|**Type**|**Documentation**
1048 -|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.
1049 -
1050 1050  **//BaseHeaderType//: **BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this
1051 1051  
1052 1052  Content:
... ... @@ -1055,29 +1055,30 @@
1055 1055  
1056 1056  Element Documentation:
1057 1057  
1058 -|**Name**|**Type**|**Documentation**
1059 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1060 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1061 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1062 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1063 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1064 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1065 -|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.
1066 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1067 -|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).
1068 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1069 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1070 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1071 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1072 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1073 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1061 +(% style="width:891.294px" %)
1062 +|**Name**|**Type**|(% style="width:552px" %)**Documentation**
1063 +|ID|com:IDType|(% style="width:552px" %)ID identifies an identification for the message, assigned by the sender.
1064 +|Test|xs:boolean|(% style="width:552px" %)Test indicates whether the message is for test purposes or not.
1065 +|Prepared|HeaderTimeType|(% style="width:552px" %)Prepared is the date the message was prepared.
1066 +|Sender|SenderType|(% style="width:552px" %)Sender is information about the party that is transmitting the message.
1067 +|Receiver|PartyType|(% style="width:552px" %)Receiver is information about the party that is the intended recipient of the message.
1068 +|com:Name|com:TextType|(% style="width:552px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1069 +|Structure|//com: PayloadStructureType//|(% style="width:552px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1070 +|DataProvider|com: DataProviderReferenceType|(% style="width:552px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1071 +|DataSetAction|com:ActionType|(% style="width:552px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1072 +|DataSetID|com:IDType|(% style="width:552px" %)DataSetID provides an identifier for a contained data set.
1073 +|Extracted|xs:dateTime|(% style="width:552px" %)Extracted is a time-stamp from the system rendering the data.
1074 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1075 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1076 +|EmbargoDate|xs:dateTime|(% style="width:552px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1077 +|Source|com:TextType|(% style="width:552px" %)Source provides human-readable information about the source of the data.
1074 1074  
1075 1075  **StructureHeaderType: **StructureHeaderType defines the structure for structural metadata messages.
1076 1076  
1077 1077  Derivation:
1078 1078  
1079 -//BaseHeaderType// (restriction)
1080 - StructureHeaderType
1083 +* //BaseHeaderType// (restriction)
1084 +** StructureHeaderType
1081 1081  
1082 1082  Content:
1083 1083  
... ... @@ -1085,21 +1085,22 @@
1085 1085  
1086 1086  Element Documentation:
1087 1087  
1088 -|**Name**|**Type**|**Documentation**
1089 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1090 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1091 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1092 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1093 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1094 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1095 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1092 +(% style="width:1099.29px" %)
1093 +|**Name**|(% style="width:224px" %)**Type**|(% style="width:663px" %)**Documentation**
1094 +|ID|(% style="width:224px" %)com:IDType|(% style="width:663px" %)ID identifies an identification for the message, assigned by the sender.
1095 +|Test|(% style="width:224px" %)xs:boolean|(% style="width:663px" %)Test indicates whether the message is for test purposes or not.
1096 +|Prepared|(% style="width:224px" %)HeaderTimeType|(% style="width:663px" %)Prepared is the date the message was prepared.
1097 +|Sender|(% style="width:224px" %)SenderType|(% style="width:663px" %)Sender is information about the party that is transmitting the message.
1098 +|Receiver|(% style="width:224px" %)PartyType|(% style="width:663px" %)Receiver is information about the party that is the intended recipient of the message.
1099 +|com:Name|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1100 +|Source|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Source provides human-readable information about the source of the data.
1096 1096  
1097 1097  **GenericDataHeaderType: **GenericDataHeaderType defines the header structure for a generic data message.
1098 1098  
1099 1099  Derivation:
1100 1100  
1101 -//BaseHeaderType// (restriction)
1102 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataHeaderType
1106 +* //BaseHeaderType// (restriction)
1107 +** GenericDataHeaderType
1103 1103  
1104 1104  Content:
1105 1105  
... ... @@ -1107,30 +1107,31 @@
1107 1107  
1108 1108  Element Documentation:
1109 1109  
1110 -|**Name**|**Type**|**Documentation**
1111 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1112 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1113 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1114 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1115 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1116 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1117 -|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.
1118 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1119 -|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).
1120 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1121 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1122 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1123 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1124 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1125 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1115 +(% style="width:895.294px" %)
1116 +|**Name**|**Type**|(% style="width:556px" %)**Documentation**
1117 +|ID|com:IDType|(% style="width:556px" %)ID identifies an identification for the message, assigned by the sender.
1118 +|Test|xs:boolean|(% style="width:556px" %)Test indicates whether the message is for test purposes or not.
1119 +|Prepared|HeaderTimeType|(% style="width:556px" %)Prepared is the date the message was prepared.
1120 +|Sender|SenderType|(% style="width:556px" %)Sender is information about the party that is transmitting the message.
1121 +|Receiver|PartyType|(% style="width:556px" %)Receiver is information about the party that is the intended recipient of the message.
1122 +|com:Name|com:TextType|(% style="width:556px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1123 +|Structure|com: GenericDataStructureType|(% style="width:556px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1124 +|DataProvider|com: DataProviderReferenceType|(% style="width:556px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1125 +|DataSetAction|com:ActionType|(% style="width:556px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1126 +|DataSetID|com:IDType|(% style="width:556px" %)DataSetID provides an identifier for a contained data set.
1127 +|Extracted|xs:dateTime|(% style="width:556px" %)Extracted is a time-stamp from the system rendering the data.
1128 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1129 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1130 +|EmbargoDate|xs:dateTime|(% style="width:556px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1131 +|Source|com:TextType|(% style="width:556px" %)Source provides human-readable information about the source of the data.
1126 1126  
1127 1127  **GenericTimeSeriesDataHeaderType: **GenericTimeSeriesDataHeaderType defines the header structure for a time series only generic data message.
1128 1128  
1129 1129  Derivation:
1130 1130  
1131 -//BaseHeaderType// (restriction)
1132 - GenericDataHeaderType (restriction)
1133 - GenericTimeSeriesDataHeaderType
1137 +* //BaseHeaderType// (restriction)
1138 +** GenericDataHeaderType (restriction)
1139 +*** GenericTimeSeriesDataHeaderType
1134 1134  
1135 1135  Content:
1136 1136  
... ... @@ -1138,29 +1138,30 @@
1138 1138  
1139 1139  Element Documentation:
1140 1140  
1141 -|**Name**|**Type**|**Documentation**
1142 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1143 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1144 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1145 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1146 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1147 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1148 -|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.
1149 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1150 -|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).
1151 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1152 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1153 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1154 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1155 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1156 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1147 +(% style="width:926.294px" %)
1148 +|**Name**|**Type**|(% style="width:497px" %)**Documentation**
1149 +|ID|com:IDType|(% style="width:497px" %)ID identifies an identification for the message, assigned by the sender.
1150 +|Test|xs:boolean|(% style="width:497px" %)Test indicates whether the message is for test purposes or not.
1151 +|Prepared|HeaderTimeType|(% style="width:497px" %)Prepared is the date the message was prepared.
1152 +|Sender|SenderType|(% style="width:497px" %)Sender is information about the party that is transmitting the message.
1153 +|Receiver|PartyType|(% style="width:497px" %)Receiver is information about the party that is the intended recipient of the message.
1154 +|com:Name|com:TextType|(% style="width:497px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1155 +|Structure|com: GenericTimeSeriesDataStructureType|(% style="width:497px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1156 +|DataProvider|com: DataProviderReferenceType|(% style="width:497px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1157 +|DataSetAction|com:ActionType|(% style="width:497px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1158 +|DataSetID|com:IDType|(% style="width:497px" %)DataSetID provides an identifier for a contained data set.
1159 +|Extracted|xs:dateTime|(% style="width:497px" %)Extracted is a time-stamp from the system rendering the data.
1160 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1161 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1162 +|EmbargoDate|xs:dateTime|(% style="width:497px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1163 +|Source|com:TextType|(% style="width:497px" %)Source provides human-readable information about the source of the data.
1157 1157  
1158 1158  **StructureSpecificDataHeaderType: **StructureSpecificDataHeaderType defines the header structure for a structure specific data message.
1159 1159  
1160 1160  Derivation:
1161 1161  
1162 -//BaseHeaderType// (restriction)
1163 - StructureSpecificDataHeaderType
1169 +* //BaseHeaderType// (restriction)
1170 +** StructureSpecificDataHeaderType
1164 1164  
1165 1165  Content:
1166 1166  
... ... @@ -1168,30 +1168,31 @@
1168 1168  
1169 1169  Element Documentation:
1170 1170  
1171 -|**Name**|**Type**|**Documentation**
1172 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1173 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1174 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1175 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1176 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1177 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1178 -|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.
1179 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1180 -|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).
1181 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1182 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1183 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1184 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1185 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1186 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1178 +(% style="width:930.294px" %)
1179 +|**Name**|**Type**|(% style="width:578px" %)**Documentation**
1180 +|ID|com:IDType|(% style="width:578px" %)ID identifies an identification for the message, assigned by the sender.
1181 +|Test|xs:boolean|(% style="width:578px" %)Test indicates whether the message is for test purposes or not.
1182 +|Prepared|HeaderTimeType|(% style="width:578px" %)Prepared is the date the message was prepared.
1183 +|Sender|SenderType|(% style="width:578px" %)Sender is information about the party that is transmitting the message.
1184 +|Receiver|PartyType|(% style="width:578px" %)Receiver is information about the party that is the intended recipient of the message.
1185 +|com:Name|com:TextType|(% style="width:578px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1186 +|Structure|com: StructureSpecificDataStructureType|(% style="width:578px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1187 +|DataProvider|com: DataProviderReferenceType|(% style="width:578px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1188 +|DataSetAction|com:ActionType|(% style="width:578px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1189 +|DataSetID|com:IDType|(% style="width:578px" %)DataSetID provides an identifier for a contained data set.
1190 +|Extracted|xs:dateTime|(% style="width:578px" %)Extracted is a time-stamp from the system rendering the data.
1191 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1192 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1193 +|EmbargoDate|xs:dateTime|(% style="width:578px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1194 +|Source|com:TextType|(% style="width:578px" %)Source provides human-readable information about the source of the data.
1187 1187  
1188 1188  **StructureSpecificTimeSeriesDataHeaderType: **StructureSpecificTimeSeriesDataHeaderType defines the header structure for a time series only structure specific data message.
1189 1189  
1190 1190  Derivation:
1191 1191  
1192 -//BaseHeaderType// (restriction)
1193 - StructureSpecificDataHeaderType (restriction)
1194 - StructureSpecificTimeSeriesDataHeaderType
1200 +* //BaseHeaderType// (restriction)
1201 +** StructureSpecificDataHeaderType (restriction)
1202 +*** StructureSpecificTimeSeriesDataHeaderType
1195 1195  
1196 1196  Content:
1197 1197  
... ... @@ -1199,29 +1199,30 @@
1199 1199  
1200 1200  Element Documentation:
1201 1201  
1202 -|**Name**|**Type**|**Documentation**
1203 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1204 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1205 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1206 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1207 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1208 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1209 -|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.
1210 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1211 -|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).
1212 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1213 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1214 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1215 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1216 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1217 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1210 +(% style="width:943.294px" %)
1211 +|**Name**|(% style="width:352px" %)**Type**|(% style="width:461px" %)**Documentation**
1212 +|ID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)ID identifies an identification for the message, assigned by the sender.
1213 +|Test|(% style="width:352px" %)xs:boolean|(% style="width:461px" %)Test indicates whether the message is for test purposes or not.
1214 +|Prepared|(% style="width:352px" %)HeaderTimeType|(% style="width:461px" %)Prepared is the date the message was prepared.
1215 +|Sender|(% style="width:352px" %)SenderType|(% style="width:461px" %)Sender is information about the party that is transmitting the message.
1216 +|Receiver|(% style="width:352px" %)PartyType|(% style="width:461px" %)Receiver is information about the party that is the intended recipient of the message.
1217 +|com:Name|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1218 +|Structure|(% style="width:352px" %)com: StructureSpecificDataTimeSeriesStructureType|(% style="width:461px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1219 +|DataProvider|(% style="width:352px" %)com: DataProviderReferenceType|(% style="width:461px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1220 +|DataSetAction|(% style="width:352px" %)com:ActionType|(% style="width:461px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1221 +|DataSetID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)DataSetID provides an identifier for a contained data set.
1222 +|Extracted|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)Extracted is a time-stamp from the system rendering the data.
1223 +|ReportingBegin|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1224 +|ReportingEnd|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1225 +|EmbargoDate|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1226 +|Source|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Source provides human-readable information about the source of the data.
1218 1218  
1219 1219  **GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic reference metadata.
1220 1220  
1221 1221  Derivation:
1222 1222  
1223 -//BaseHeaderType// (restriction)
1224 - GenericMetadataHeaderType
1232 +* //BaseHeaderType// (restriction)
1233 +** GenericMetadataHeaderType
1225 1225  
1226 1226  Content:
1227 1227  
... ... @@ -1229,26 +1229,27 @@
1229 1229  
1230 1230  Element Documentation:
1231 1231  
1232 -|**Name**|**Type**|**Documentation**
1233 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1234 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1235 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1236 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1237 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1238 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1239 -|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.
1240 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1241 -|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).
1242 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1243 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1244 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1241 +(% style="width:928.294px" %)
1242 +|**Name**|**Type**|(% style="width:554px" %)**Documentation**
1243 +|ID|com:IDType|(% style="width:554px" %)ID identifies an identification for the message, assigned by the sender.
1244 +|Test|xs:boolean|(% style="width:554px" %)Test indicates whether the message is for test purposes or not.
1245 +|Prepared|HeaderTimeType|(% style="width:554px" %)Prepared is the date the message was prepared.
1246 +|Sender|SenderType|(% style="width:554px" %)Sender is information about the party that is transmitting the message.
1247 +|Receiver|PartyType|(% style="width:554px" %)Receiver is information about the party that is the intended recipient of the message.
1248 +|com:Name|com:TextType|(% style="width:554px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1249 +|Structure|com: GenericMetadataStructureType|(% style="width:554px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1250 +|DataProvider|com: DataProviderReferenceType|(% style="width:554px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1251 +|DataSetAction|com:ActionType|(% style="width:554px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1252 +|DataSetID|com:IDType|(% style="width:554px" %)DataSetID provides an identifier for a contained data set.
1253 +|Extracted|xs:dateTime|(% style="width:554px" %)Extracted is a time-stamp from the system rendering the data.
1254 +|Source|com:TextType|(% style="width:554px" %)Source provides human-readable information about the source of the data.
1245 1245  
1246 1246  **StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for metadata structure definition specific reference metadata messages.
1247 1247  
1248 1248  Derivation:
1249 1249  
1250 -//BaseHeaderType// (restriction)
1251 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType
1260 +* //BaseHeaderType// (restriction)
1261 +** StructureSpecificMetadataHeaderType
1252 1252  
1253 1253  Content:
1254 1254  
... ... @@ -1256,26 +1256,27 @@
1256 1256  
1257 1257  Element Documentation:
1258 1258  
1259 -|**Name**|**Type**|**Documentation**
1260 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1261 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1262 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1263 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1264 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1265 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1266 -|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.
1267 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1268 -|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).
1269 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1270 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1271 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1269 +(% style="width:996.294px" %)
1270 +|**Name**|**Type**|(% style="width:557px" %)**Documentation**
1271 +|ID|com:IDType|(% style="width:557px" %)ID identifies an identification for the message, assigned by the sender.
1272 +|Test|xs:boolean|(% style="width:557px" %)Test indicates whether the message is for test purposes or not.
1273 +|Prepared|HeaderTimeType|(% style="width:557px" %)Prepared is the date the message was prepared.
1274 +|Sender|SenderType|(% style="width:557px" %)Sender is information about the party that is transmitting the message.
1275 +|Receiver|PartyType|(% style="width:557px" %)Receiver is information about the party that is the intended recipient of the message.
1276 +|com:Name|com:TextType|(% style="width:557px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1277 +|Structure|com: StructureSpecificMetadataStructureType|(% style="width:557px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1278 +|DataProvider|com: DataProviderReferenceType|(% style="width:557px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1279 +|DataSetAction|com:ActionType|(% style="width:557px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1280 +|DataSetID|com:IDType|(% style="width:557px" %)DataSetID provides an identifier for a contained data set.
1281 +|Extracted|xs:dateTime|(% style="width:557px" %)Extracted is a time-stamp from the system rendering the data.
1282 +|Source|com:TextType|(% style="width:557px" %)Source provides human-readable information about the source of the data.
1272 1272  
1273 1273  **BasicHeaderType: **BasicHeaderType defines the most basic header information used in simple message exchanges.
1274 1274  
1275 1275  Derivation:
1276 1276  
1277 -//BaseHeaderType// (restriction)
1278 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType
1288 +* //BaseHeaderType// (restriction)
1289 +** BasicHeaderType
1279 1279  
1280 1280  Content:
1281 1281  
... ... @@ -1283,12 +1283,13 @@
1283 1283  
1284 1284  Element Documentation:
1285 1285  
1286 -|**Name**|**Type**|**Documentation**
1287 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1288 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1289 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1290 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1291 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1297 +(% style="width:903.294px" %)
1298 +|**Name**|(% style="width:236px" %)**Type**|(% style="width:457px" %)**Documentation**
1299 +|ID|(% style="width:236px" %)com:IDType|(% style="width:457px" %)ID identifies an identification for the message, assigned by the sender.
1300 +|Test|(% style="width:236px" %)xs:boolean|(% style="width:457px" %)Test indicates whether the message is for test purposes or not.
1301 +|Prepared|(% style="width:236px" %)HeaderTimeType|(% style="width:457px" %)Prepared is the date the message was prepared.
1302 +|Sender|(% style="width:236px" %)SenderType|(% style="width:457px" %)Sender is information about the party that is transmitting the message.
1303 +|Receiver|(% style="width:236px" %)PartyType|(% style="width:457px" %)Receiver is information about the party that is the intended recipient of the message.
1292 1292  
1293 1293  **PartyType: **PartyType defines the information which is sent about various parties such as senders and receivers of messages.
1294 1294  
... ... @@ -1302,21 +1302,23 @@
1302 1302  
1303 1303  Attribute Documentation:
1304 1304  
1305 -|**Name**|**Type**|**Documentation**
1306 -|id|com:IDType|The id attribute holds the identification of the party.
1317 +(% style="width:739.294px" %)
1318 +|(% style="width:125px" %)**Name**|(% style="width:190px" %)**Type**|(% style="width:421px" %)**Documentation**
1319 +|(% style="width:125px" %)id|(% style="width:190px" %)com:IDType|(% style="width:421px" %)The id attribute holds the identification of the party.
1307 1307  
1308 1308  Element Documentation:
1309 1309  
1310 -|**Name**|**Type**|**Documentation**
1311 -|com:Name|com:TextType|Name is a human-readable name of the party.
1312 -|Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message.
1323 +(% style="width:751.294px" %)
1324 +|(% style="width:134px" %)**Name**|(% style="width:183px" %)**Type**|(% style="width:431px" %)**Documentation**
1325 +|(% style="width:134px" %)com:Name|(% style="width:183px" %)com:TextType|(% style="width:431px" %)Name is a human-readable name of the party.
1326 +|(% style="width:134px" %)Contact|(% style="width:183px" %)ContactType|(% style="width:431px" %)Contact provides contact information for the party in regard to the transmission of the message.
1313 1313  
1314 1314  **SenderType: **SenderType extends the basic party structure to add an optional time zone declaration.
1315 1315  
1316 1316  Derivation:
1317 1317  
1318 -PartyType (extension)
1319 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType
1332 +* PartyType (extension)
1333 +** SenderType
1320 1320  
1321 1321  Attributes:
1322 1322