Changes for page Part II.Common Namespace
Last modified by Elena Yasinovskaya on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -519,23 +519,25 @@ 519 519 520 520 Attribute Documentation: 521 521 522 -|**Name**|**Type**|**Documentation** 523 -|structureID|xs:ID|The structureID attribute uniquely identifies the structure for the purpose of referencing it from the payload. This is only used in structure specific formats. Although it is required, it is only useful when more than one data set is present in the message. 524 -|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located. 525 -|namespace|xs:anyURI|The namespace attribute is used to provide the namespace for structure-specific formats. By communicating this information in the header, it is possible to generate the structure specific schema while processing the message. 526 -|dimensionAtObservation|ObservationDimension Type|The dimensionAtObservation is used to reference the dimension at the observation level for data messages. This can also be given the explicit value of "AllDimensions" which denotes that the cross sectional data is in the flat format. 527 -|explicitMeasures|xs:boolean|The explicitMeasures indicates whether explicit measures are used in the cross sectional format. This is only applicable for the measure dimension as the dimension at the observation level or the flat structure. 528 -|serviceURL|xs:anyURI|The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface. 529 -|structureURL|xs:anyURI|The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object. 522 +(% style="width:1003.29px" %) 523 +|**Name**|**Type**|(% style="width:598px" %)**Documentation** 524 +|structureID|xs:ID|(% style="width:598px" %)The structureID attribute uniquely identifies the structure for the purpose of referencing it from the payload. This is only used in structure specific formats. Although it is required, it is only useful when more than one data set is present in the message. 525 +|schemaURL|xs:anyURI|(% style="width:598px" %)The schemaURL attribute provides a location from which the structure specific schema can be located. 526 +|namespace|xs:anyURI|(% style="width:598px" %)The namespace attribute is used to provide the namespace for structure-specific formats. By communicating this information in the header, it is possible to generate the structure specific schema while processing the message. 527 +|dimensionAtObservation|ObservationDimensionType|(% style="width:598px" %)The dimensionAtObservation is used to reference the dimension at the observation level for data messages. This can also be given the explicit value of "AllDimensions" which denotes that the cross sectional data is in the flat format. 528 +|explicitMeasures|xs:boolean|(% style="width:598px" %)The explicitMeasures indicates whether explicit measures are used in the cross sectional format. This is only applicable for the measure dimension as the dimension at the observation level or the flat structure. 529 +|serviceURL|xs:anyURI|(% style="width:598px" %)The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface. 530 +|structureURL|xs:anyURI|(% style="width:598px" %)The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object. 530 530 531 531 Element Documentation: 532 532 533 -|**Name**|**Type**|**Documentation** 534 -|ProvisionAgreement|ProvisionAgreementRe ferenceType|ProvisionAgreement references a provision agreement which the data or metadata is reported against. 535 -|StructureUsage|StructureUsageRefere nceType|StructureUsage references a flow which the data or metadata is reported against. 536 -|Structure|StructureReferenceTy pe|Structure references the structure which defines the structure of the data or metadata set. 534 +(% style="width:1005.29px" %) 535 +|(% style="width:188px" %)**Name**|(% style="width:287px" %)**Type**|(% style="width:527px" %)**Documentation** 536 +|(% style="width:188px" %)ProvisionAgreement|(% style="width:287px" %)ProvisionAgreementReferenceType|(% style="width:527px" %)ProvisionAgreement references a provision agreement which the data or metadata is reported against. 537 +|(% style="width:188px" %)StructureUsage|(% style="width:287px" %)StructureUsageReferenceType|(% style="width:527px" %)StructureUsage references a flow which the data or metadata is reported against. 538 +|(% style="width:188px" %)Structure|(% style="width:287px" %)StructureReferenceType|(% style="width:527px" %)Structure references the structure which defines the structure of the data or metadata set. 537 537 538 -** *DataStructureType*:** DataStructureType is an abstract base type the forms the basis for the structural information for a data set.540 +//**DataStructureType:**// DataStructureType is an abstract base type the forms the basis for the structural information for a data set. 539 539 540 540 Derivation: 541 541 ... ... @@ -550,21 +550,23 @@ 550 550 551 551 Attribute Documentation: 552 552 553 -|**Name**|**Type**|**Documentation** 554 -|structureID|xs:ID|The structureID attribute uniquely identifies the structure for the purpose of referencing it from the payload. This is only used in structure specific formats. Although it is required, it is only useful when more than one data set is present in the message. 555 -|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located. 556 -|namespace|xs:anyURI|The namespace attribute is used to provide the namespace for structure-specific formats. By communicating this information in the header, it is possible to generate the structure specific schema while processing the message. 557 -|dimensionAtObservation|ObservationDimension Type|The dimensionAtObservation is used to reference the dimension at the observation level for data messages. This can also be given the explicit value of "AllDimensions" which denotes that the cross sectional data is in the flat format. 558 -|explicitMeasures|xs:boolean|The explicitMeasures indicates whether explicit measures are used in the cross sectional format. This is only applicable for the measure dimension as the dimension at the observation level or the flat structure. 559 -|serviceURL|xs:anyURI|The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface. 560 -|structureURL|xs:anyURI|The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object. 555 +(% style="width:1006.29px" %) 556 +|**Name**|**Type**|(% style="width:598px" %)**Documentation** 557 +|structureID|xs:ID|(% style="width:598px" %)The structureID attribute uniquely identifies the structure for the purpose of referencing it from the payload. This is only used in structure specific formats. Although it is required, it is only useful when more than one data set is present in the message. 558 +|schemaURL|xs:anyURI|(% style="width:598px" %)The schemaURL attribute provides a location from which the structure specific schema can be located. 559 +|namespace|xs:anyURI|(% style="width:598px" %)The namespace attribute is used to provide the namespace for structure-specific formats. By communicating this information in the header, it is possible to generate the structure specific schema while processing the message. 560 +|dimensionAtObservation|ObservationDimensionType|(% style="width:598px" %)The dimensionAtObservation is used to reference the dimension at the observation level for data messages. This can also be given the explicit value of "AllDimensions" which denotes that the cross sectional data is in the flat format. 561 +|explicitMeasures|xs:boolean|(% style="width:598px" %)The explicitMeasures indicates whether explicit measures are used in the cross sectional format. This is only applicable for the measure dimension as the dimension at the observation level or the flat structure. 562 +|serviceURL|xs:anyURI|(% style="width:598px" %)The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface. 563 +|structureURL|xs:anyURI|(% style="width:598px" %)The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object. 561 561 562 562 Element Documentation: 563 563 564 -|**Name**|**Type**|**Documentation** 565 -|ProvisionAgreement|ProvisionAgreementRe ferenceType|ProvisionAgreement references a provision agreement which the data is reported against. 566 -|StructureUsage|DataflowReferenceTyp e|StructureUsage references a dataflow which the data is reported against. 567 -|Structure|DataStructureReferen ceType|Structure references the data structure definition which defines the structure of the data. 567 +(% style="width:1012.29px" %) 568 +|(% style="width:184px" %)**Name**|(% style="width:295px" %)**Type**|(% style="width:530px" %)**Documentation** 569 +|(% style="width:184px" %)ProvisionAgreement|(% style="width:295px" %)ProvisionAgreementReferenceType|(% style="width:530px" %)ProvisionAgreement references a provision agreement which the data is reported against. 570 +|(% style="width:184px" %)StructureUsage|(% style="width:295px" %)DataflowReferenceType|(% style="width:530px" %)StructureUsage references a dataflow which the data is reported against. 571 +|(% style="width:184px" %)Structure|(% style="width:295px" %)DataStructureReferenceType|(% style="width:530px" %)Structure references the data structure definition which defines the structure of the data. 568 568 569 569 **StructureSpecificDataStructureType:** StructureSpecificDataStructureType defines the structural information for a structured data set. In addition to referencing the data structure or dataflow which defines the structure of the data, the namespace for the data structure specific schema as well as which dimension is used at the observation level must be provided. It is also necessary to state whether the format uses explicit measures, although this is technically only applicable is the dimension at the observation level is the measure dimension or the flat data format is used. 570 570 ... ... @@ -582,23 +582,25 @@ 582 582 583 583 Attribute Documentation: 584 584 585 -|**Name**|**Type**|**Documentation** 586 -|structureID|xs:ID|The structureID attribute uniquely identifies the structure for the purpose of referencing it from the payload. This is only used in structure specific formats. Although it is required, it is only useful when more than one data set is present in the message. 587 -|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located. 588 -|namespace|xs:anyURI|The namespace attribute is used to provide the namespace for structure-specific formats. By communicating this information in the header, it is possible to generate the structure specific schema while processing the message. 589 -|dimensionAtObservation|ObservationDimension Type|The dimensionAtObservation is used to reference the dimension at the observation level for data messages. This can also be given the explicit value of "AllDimensions" which denotes that the cross sectional data is in the flat format. 590 -|explicitMeasures (default: false)|xs:boolean|The explicitMeasures indicates whether explicit measures are used in the cross sectional format. This is only applicable for the measure dimension as the dimension at the observation level or the flat structure. 591 -|serviceURL|xs:anyURI|The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface. 592 -|structureURL|xs:anyURI|The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object. 589 +(% style="width:1010.29px" %) 590 +|**Name**|**Type**|(% style="width:562px" %)**Documentation** 591 +|structureID|xs:ID|(% style="width:562px" %)The structureID attribute uniquely identifies the structure for the purpose of referencing it from the payload. This is only used in structure specific formats. Although it is required, it is only useful when more than one data set is present in the message. 592 +|schemaURL|xs:anyURI|(% style="width:562px" %)The schemaURL attribute provides a location from which the structure specific schema can be located. 593 +|namespace|xs:anyURI|(% style="width:562px" %)The namespace attribute is used to provide the namespace for structure-specific formats. By communicating this information in the header, it is possible to generate the structure specific schema while processing the message. 594 +|dimensionAtObservation|ObservationDimensionType|(% style="width:562px" %)The dimensionAtObservation is used to reference the dimension at the observation level for data messages. This can also be given the explicit value of "AllDimensions" which denotes that the cross sectional data is in the flat format. 595 +|explicitMeasures (default: false)|xs:boolean|(% style="width:562px" %)The explicitMeasures indicates whether explicit measures are used in the cross sectional format. This is only applicable for the measure dimension as the dimension at the observation level or the flat structure. 596 +|serviceURL|xs:anyURI|(% style="width:562px" %)The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface. 597 +|structureURL|xs:anyURI|(% style="width:562px" %)The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object. 593 593 594 594 Element Documentation: 595 595 596 -|**Name**|**Type**|**Documentation** 597 -|ProvisionAgreement|ProvisionAgreementReferenceType|ProvisionAgreement references a provision agreement which the data is reported against. 598 -|StructureUsage|DataflowReferenceType|StructureUsage references a dataflow which the data is reported against. 599 -|Structure|DataStructureReferen ceType|Structure references the data structure definition which defines the structure of the data. 601 +(% style="width:1018.29px" %) 602 +|(% style="width:202px" %)**Name**|(% style="width:284px" %)**Type**|(% style="width:529px" %)**Documentation** 603 +|(% style="width:202px" %)ProvisionAgreement|(% style="width:284px" %)ProvisionAgreementReferenceType|(% style="width:529px" %)ProvisionAgreement references a provision agreement which the data is reported against. 604 +|(% style="width:202px" %)StructureUsage|(% style="width:284px" %)DataflowReferenceType|(% style="width:529px" %)StructureUsage references a dataflow which the data is reported against. 605 +|(% style="width:202px" %)Structure|(% style="width:284px" %)DataStructureReferenceType|(% style="width:529px" %)Structure references the data structure definition which defines the structure of the data. 600 600 601 -** *MetadataStructureType*:** MetadataStructureType is an abstract base type the forms the basis of the structural information for any metadata message. A reference to the metadata structure definition or a metadataflow must be provided. This can be used to determine the structure of the message.607 +//**MetadataStructureType:**// MetadataStructureType is an abstract base type the forms the basis of the structural information for any metadata message. A reference to the metadata structure definition or a metadataflow must be provided. This can be used to determine the structure of the message. 602 602 603 603 Derivation: 604 604 ... ... @@ -613,19 +613,21 @@ 613 613 614 614 Attribute Documentation: 615 615 616 -|**Name**|**Type**|**Documentation** 617 -|structureID|xs:ID|The structureID attribute uniquely identifies the structure for the purpose of referencing it from the payload. This is only used in structure specific formats. Although it is required, it is only useful when more than one data set is present in the message. 618 -|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located. 619 -|namespace|xs:anyURI|The namespace attribute is used to provide the namespace for structure-specific formats. By communicating this information in the header, it is possible to generate the structure specific schema while processing the message. 620 -|serviceURL|xs:anyURI|The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface. 621 -|structureURL|xs:anyURI|The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object. 622 +(% style="width:1007.29px" %) 623 +|**Name**|**Type**|(% style="width:802px" %)**Documentation** 624 +|structureID|xs:ID|(% style="width:802px" %)The structureID attribute uniquely identifies the structure for the purpose of referencing it from the payload. This is only used in structure specific formats. Although it is required, it is only useful when more than one data set is present in the message. 625 +|schemaURL|xs:anyURI|(% style="width:802px" %)The schemaURL attribute provides a location from which the structure specific schema can be located. 626 +|namespace|xs:anyURI|(% style="width:802px" %)The namespace attribute is used to provide the namespace for structure-specific formats. By communicating this information in the header, it is possible to generate the structure specific schema while processing the message. 627 +|serviceURL|xs:anyURI|(% style="width:802px" %)The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface. 628 +|structureURL|xs:anyURI|(% style="width:802px" %)The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object. 622 622 623 623 Element Documentation: 624 624 625 -|**Name**|**Type**|**Documentation** 626 -|ProvisionAgreement|ProvisionAgreementReferenceType|ProvisionAgreement references a provision agreement which the metadata is reported against. 627 -|StructureUsage|MetadataflowReferenceType|StructureUsage references a metadataflow which the metadata is reported against. 628 -|Structure|MetadataStructureReferenceType|Structure references the metadata structure definition which defines the structure of the metadata. 632 +(% style="width:1014.29px" %) 633 +|(% style="width:162px" %)**Name**|(% style="width:277px" %)**Type**|(% style="width:573px" %)**Documentation** 634 +|(% style="width:162px" %)ProvisionAgreement|(% style="width:277px" %)ProvisionAgreementReferenceType|(% style="width:573px" %)ProvisionAgreement references a provision agreement which the metadata is reported against. 635 +|(% style="width:162px" %)StructureUsage|(% style="width:277px" %)MetadataflowReferenceType|(% style="width:573px" %)StructureUsage references a metadataflow which the metadata is reported against. 636 +|(% style="width:162px" %)Structure|(% style="width:277px" %)MetadataStructureReferenceType|(% style="width:573px" %)Structure references the metadata structure definition which defines the structure of the metadata. 629 629 630 630 **GenericMetadataStructureType:** GenericMetadataStructureType defines the structural information for a generic metadata message. 631 631 ... ... @@ -643,18 +643,20 @@ 643 643 644 644 Attribute Documentation: 645 645 646 -|**Name**|**Type**|**Documentation** 647 -|structureID|xs:ID|The structureID attribute uniquely identifies the structure for the purpose of referencing it from the payload. This is only used in structure specific formats. Although it is required, it is only useful when more than one data set is present in the message. 648 -|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located. 649 -|serviceURL|xs:anyURI|The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface. 650 -|structureURL|xs:anyURI|The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object. 654 +(% style="width:997.294px" %) 655 +|**Name**|**Type**|(% style="width:792px" %)**Documentation** 656 +|structureID|xs:ID|(% style="width:792px" %)The structureID attribute uniquely identifies the structure for the purpose of referencing it from the payload. This is only used in structure specific formats. Although it is required, it is only useful when more than one data set is present in the message. 657 +|schemaURL|xs:anyURI|(% style="width:792px" %)The schemaURL attribute provides a location from which the structure specific schema can be located. 658 +|serviceURL|xs:anyURI|(% style="width:792px" %)The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface. 659 +|structureURL|xs:anyURI|(% style="width:792px" %)The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object. 651 651 652 652 Element Documentation: 653 653 654 -|**Name**|**Type**|**Documentation** 655 -|ProvisionAgreement|ProvisionAgreementReferenceType|ProvisionAgreement references a provision agreement which the metadata is reported against. 656 -|StructureUsage|MetadataflowReferenceType|StructureUsage references a metadataflow which the metadata is reported against. 657 -|Structure|MetadataStructureReferenceType|Structure references the metadata structure definition which defines the structure of the metadata. 663 +(% style="width:1001.29px" %) 664 +|(% style="width:181px" %)**Name**|(% style="width:280px" %)**Type**|(% style="width:537px" %)**Documentation** 665 +|(% style="width:181px" %)ProvisionAgreement|(% style="width:280px" %)ProvisionAgreementReferenceType|(% style="width:537px" %)ProvisionAgreement references a provision agreement which the metadata is reported against. 666 +|(% style="width:181px" %)StructureUsage|(% style="width:280px" %)MetadataflowReferenceType|(% style="width:537px" %)StructureUsage references a metadataflow which the metadata is reported against. 667 +|(% style="width:181px" %)Structure|(% style="width:280px" %)MetadataStructureReferenceType|(% style="width:537px" %)Structure references the metadata structure definition which defines the structure of the metadata. 658 658 659 659 === 2.1.4 Simple Types === 660 660 ... ... @@ -879,8 +879,9 @@ 879 879 880 880 Enumerations: 881 881 882 -|**Value**|**Documentation** 883 -|unbounded|Object has no upper limit on occurrences. 892 +(% style="width:625.294px" %) 893 +|(% style="width:144px" %)**Value**|(% style="width:478px" %)**Documentation** 894 +|(% style="width:144px" %)unbounded|(% style="width:478px" %)Object has no upper limit on occurrences. 884 884 885 885 **ActionType:** ActionType provides a list of actions, describing the intention of the data transmission from the sender's side. Each action provided at the data or metadata set level applies to the entire data set for which it is given. Note that the actions indicated in the Message Header are optional, and used to summarize specific actions indicated with this data type for all registry interactions. The "Informational" value is used when the message contains information in response to a query, rather than being used to invoke a maintenance activity. 886 886 ... ... @@ -888,11 +888,12 @@ 888 888 889 889 Enumerations: 890 890 891 -|**Value**|**Documentation** 892 -|Append|Append - this is an incremental update for an existing data/metadata set or the provision of new data or documentation (attribute values) formerly absent. If any of the supplied data or metadata is already present, it will not replace that data or metadata. This corresponds to the "Update" value found in version 1.0 of the SDMX Technical Standards. 893 -|Replace|Replace - data/metadata is to be replaced, and may also include additional data/metadata to be appended. The replacement occurs at the level of the observation - that is, it is not possible to replace an entire series. 894 -|Delete|Delete - data/metadata is to be deleted. Deletion occurs at the lowest level object. For instance, if a delete data message contains a series with no observations, then the entire series will be deleted. If the series contains observations, then only those observations specified will be deleted. The same basic concept applies for attributes. If a series or observation in a delete message contains attributes, then only those attributes will be deleted. 895 -|Information|Informational - data/metadata is being exchanged for informational purposes only, and not meant to update a system. 902 +(% style="width:1005.29px" %) 903 +|**Value**|(% style="width:905px" %)**Documentation** 904 +|Append|(% style="width:905px" %)Append - this is an incremental update for an existing data/metadata set or the provision of new data or documentation (attribute values) formerly absent. If any of the supplied data or metadata is already present, it will not replace that data or metadata. This corresponds to the "Update" value found in version 1.0 of the SDMX Technical Standards. 905 +|Replace|(% style="width:905px" %)Replace - data/metadata is to be replaced, and may also include additional data/metadata to be appended. The replacement occurs at the level of the observation - that is, it is not possible to replace an entire series. 906 +|Delete|(% style="width:905px" %)Delete - data/metadata is to be deleted. Deletion occurs at the lowest level object. For instance, if a delete data message contains a series with no observations, then the entire series will be deleted. If the series contains observations, then only those observations specified will be deleted. The same basic concept applies for attributes. If a series or observation in a delete message contains attributes, then only those attributes will be deleted. 907 +|Information|(% style="width:905px" %)Informational - data/metadata is being exchanged for informational purposes only, and not meant to update a system. 896 896 897 897 **WildCardValueType:** WildCardValueType is a single value code list, used to include the '%' character - indicating that an entire field is wild carded. 898 898 ... ... @@ -900,8 +900,9 @@ 900 900 901 901 Enumerations: 902 902 903 -|**Value**|**Documentation** 904 -|%|Indicates a wild card value. 915 +(% style="width:505.294px" %) 916 +|(% style="width:169px" %)**Value**|(% style="width:333px" %)**Documentation** 917 +|(% style="width:169px" %)%|(% style="width:333px" %)Indicates a wild card value. 905 905 906 906 **CascadeSelectionType:** 907 907 ... ... @@ -914,8 +914,9 @@ 914 914 915 915 Enumerations: 916 916 917 -|**Value**|**Documentation** 918 -|excluderoot| 930 +(% style="width:504.294px" %) 931 +|(% style="width:165px" %)**Value**|(% style="width:336px" %)**Documentation** 932 +|(% style="width:165px" %)excluderoot|(% style="width:336px" %) 919 919 920 920 **ObservationDimensionType:** ObservationDimensionType allows for the dimension at the observation level to be specified by either providing the dimension identifier or using the explicit value "AllDimensions". 921 921