Changes for page Part I. Message Namespace

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

From version 3.9
edited by Helena
on 2025/06/23 17:07
Change comment: There is no comment for this version
To version 5.3
edited by Helena
on 2025/06/24 10:25
Change comment: There is no comment for this version

Summary

Details

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