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
-
... ... @@ -505,8 +505,9 @@ 505 505 506 506 Attribute Documentation: 507 507 508 -|**Name**|**Type**|**Documentation** 509 -|xml:lang (default: en)|xs:language 508 +(% style="width:1009.29px" %) 509 +|(% style="width:228px" %)**Name**|(% style="width:221px" %)**Type**|(% style="width:699px" %)**Documentation** 510 +|(% style="width:228px" %)xml:lang (default: en)|(% style="width:221px" %)xs:language 510 510 511 511 ***PayloadStructureType*:** PayloadStructureType is an abstract base type used to define the structural information for data or metadata sets. A reference to the structure is provided (either explicitly or through a reference to a structure usage). 512 512 ... ... @@ -518,23 +518,25 @@ 518 518 519 519 Attribute Documentation: 520 520 521 -|**Name**|**Type**|**Documentation** 522 -|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. 523 -|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located. 524 -|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. 525 -|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. 526 -|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. 527 -|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. 528 -|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. 529 529 530 530 Element Documentation: 531 531 532 -|**Name**|**Type**|**Documentation** 533 -|ProvisionAgreement|ProvisionAgreementRe ferenceType|ProvisionAgreement references a provision agreement which the data or metadata is reported against. 534 -|StructureUsage|StructureUsageRefere nceType|StructureUsage references a flow which the data or metadata is reported against. 535 -|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. 536 536 537 -** *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. 538 538 539 539 Derivation: 540 540 ... ... @@ -549,21 +549,23 @@ 549 549 550 550 Attribute Documentation: 551 551 552 -|**Name**|**Type**|**Documentation** 553 -|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. 554 -|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located. 555 -|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. 556 -|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. 557 -|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. 558 -|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. 559 -|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. 560 560 561 561 Element Documentation: 562 562 563 -|**Name**|**Type**|**Documentation** 564 -|ProvisionAgreement|ProvisionAgreementRe ferenceType|ProvisionAgreement references a provision agreement which the data is reported against. 565 -|StructureUsage|DataflowReferenceTyp e|StructureUsage references a dataflow which the data is reported against. 566 -|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. 567 567 568 568 **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. 569 569 ... ... @@ -581,23 +581,25 @@ 581 581 582 582 Attribute Documentation: 583 583 584 -|**Name**|**Type**|**Documentation** 585 -|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. 586 -|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located. 587 -|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. 588 -|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. 589 -|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. 590 -|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. 591 -|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. 592 592 593 593 Element Documentation: 594 594 595 -|**Name**|**Type**|**Documentation** 596 -|ProvisionAgreement|ProvisionAgreementReferenceType|ProvisionAgreement references a provision agreement which the data is reported against. 597 -|StructureUsage|DataflowReferenceType|StructureUsage references a dataflow which the data is reported against. 598 -|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. 599 599 600 -** *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. 601 601 602 602 Derivation: 603 603 ... ... @@ -612,19 +612,21 @@ 612 612 613 613 Attribute Documentation: 614 614 615 -|**Name**|**Type**|**Documentation** 616 -|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. 617 -|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located. 618 -|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. 619 -|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. 620 -|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. 621 621 622 622 Element Documentation: 623 623 624 -|**Name**|**Type**|**Documentation** 625 -|ProvisionAgreement|ProvisionAgreementReferenceType|ProvisionAgreement references a provision agreement which the metadata is reported against. 626 -|StructureUsage|MetadataflowReferenceType|StructureUsage references a metadataflow which the metadata is reported against. 627 -|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. 628 628 629 629 **GenericMetadataStructureType:** GenericMetadataStructureType defines the structural information for a generic metadata message. 630 630 ... ... @@ -642,18 +642,20 @@ 642 642 643 643 Attribute Documentation: 644 644 645 -|**Name**|**Type**|**Documentation** 646 -|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. 647 -|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located. 648 -|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. 649 -|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. 650 650 651 651 Element Documentation: 652 652 653 -|**Name**|**Type**|**Documentation** 654 -|ProvisionAgreement|ProvisionAgreementReferenceType|ProvisionAgreement references a provision agreement which the metadata is reported against. 655 -|StructureUsage|MetadataflowReferenceType|StructureUsage references a metadataflow which the metadata is reported against. 656 -|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. 657 657 658 658 === 2.1.4 Simple Types === 659 659 ... ... @@ -878,8 +878,9 @@ 878 878 879 879 Enumerations: 880 880 881 -|**Value**|**Documentation** 882 -|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. 883 883 884 884 **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. 885 885 ... ... @@ -887,11 +887,12 @@ 887 887 888 888 Enumerations: 889 889 890 -|**Value**|**Documentation** 891 -|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. 892 -|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. 893 -|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. 894 -|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. 895 895 896 896 **WildCardValueType:** WildCardValueType is a single value code list, used to include the '%' character - indicating that an entire field is wild carded. 897 897 ... ... @@ -899,8 +899,9 @@ 899 899 900 900 Enumerations: 901 901 902 -|**Value**|**Documentation** 903 -|%|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. 904 904 905 905 **CascadeSelectionType:** 906 906 ... ... @@ -913,8 +913,9 @@ 913 913 914 914 Enumerations: 915 915 916 -|**Value**|**Documentation** 917 -|excluderoot| 930 +(% style="width:504.294px" %) 931 +|(% style="width:165px" %)**Value**|(% style="width:336px" %)**Documentation** 932 +|(% style="width:165px" %)excluderoot|(% style="width:336px" %) 918 918 919 919 **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". 920 920 ... ... @@ -927,9 +927,10 @@ 927 927 928 928 Enumerations: 929 929 930 -|**Value**|**Documentation** 931 -|AllDimensions|AllDimensions notes that the cross sectional format shall be flat; that is all dimensions should be contained at the observation level. 932 -|TIME_PERIOD|TIME_PERIOD refers to the fixed identifier for the time dimension. 945 +(% style="width:997.294px" %) 946 +|(% style="width:168px" %)**Value**|(% style="width:826px" %)**Documentation** 947 +|(% style="width:168px" %)AllDimensions|(% style="width:826px" %)AllDimensions notes that the cross sectional format shall be flat; that is all dimensions should be contained at the observation level. 948 +|(% style="width:168px" %)TIME_PERIOD|(% style="width:826px" %)TIME_PERIOD refers to the fixed identifier for the time dimension. 933 933 934 934 **DataType:** DataTypeType provides an enumerated list of the types of data formats allowed as the for the representation of an object. 935 935 ... ... @@ -937,51 +937,52 @@ 937 937 938 938 Enumerations: 939 939 940 -|**Value**|**Documentation** 941 -|String|A string datatype corresponding to W3C XML Schema's xs:string datatype. 942 -|Alpha|A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z. 943 -|AlphaNumeric|A string datatype which only allows for the simple alphabetic character set of A-Z, a-z plus the simple numeric character set of 0-9. 944 -|Numeric|A string datatype which only allows for the simple numeric character set of 0-9. This format is not treated as an integer, and therefore can having leading zeros. 945 -|BigInteger|An integer datatype corresponding to W3C XML Schema's xs:integer datatype. 946 -|Integer|An integer datatype corresponding to W3C XML Schema's xs:int datatype. 947 -|Long|A numeric datatype corresponding to W3C XML Schema's xs:long datatype. 948 -|Short|A numeric datatype corresponding to W3C XML Schema's xs:short datatype. 949 -|Decimal|A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype. 950 -|Float|A numeric datatype corresponding to W3C XML Schema's xs:float datatype. 951 -|Double|A numeric datatype corresponding to W3C XML Schema's xs:double datatype. 952 -|Boolean|A datatype corresponding to W3C XML Schema's xs:boolean datatype. 953 -|URI|A datatype corresponding to W3C XML Schema's xs:anyURI datatype. 954 -|Count|A simple incrementing Integer type. The isSequence facet must be set to true, and the interval facet must be set to "1". 955 -|InclusiveValueRange|This value indicates that the startValue and endValue attributes provide the inclusive boundaries of a numeric range of type xs:decimal. 956 -|ExclusiveValueRange|This value indicates that the startValue and endValue attributes provide the exclusive boundaries of a numeric range, of type xs:decimal. 957 -|Incremental|This value indicates that the value increments according to the value provided in the interval facet, and has a true value for the isSequence facet. 958 -|ObservationalTimePeriod|Observational time periods are the superset of all time periods in SDMX. It is the union of the standard time periods (i.e. Gregorian time periods, the reporting time periods, and date time) and a time range. 959 -|StandardTimePeriod|Standard time periods is a superset of distinct time period in SDMX. It is the union of the basic time periods (i.e. the Gregorian time periods and date time) and the reporting time periods. 960 -|BasicTimePeriod|BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time. 961 -|GregorianTimePeriod|Gregorian time periods correspond to calendar periods and are represented in ISO-8601 formats. This is the union of the year, year month, and date formats. 962 -|GregorianYear|A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601. 963 -|GregorianYearMonth|A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601. 964 -|GregorianDay|A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601. 965 -|ReportingTimePeriod|Reporting time periods represent periods of a standard length within a reporting year, where to start of the year (defined as a month and day) must be defined elsewhere or it is assumed to be January 1. This is the union of the reporting year, semester, trimester, quarter, month, week, and day. 966 -|ReportingYear|A reporting year represents a period of 1 year (P1Y) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingYearType. 967 -|ReportingSemester|A reporting semester represents a period of 6 months (P6M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingSemesterType. 968 -|ReportingTrimester|A reporting trimester represents a period of 4 months (P4M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingTrimesterType. 969 -|ReportingQuarter|A reporting quarter represents a period of 3 months (P3M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingQuarterType. 970 -|ReportingMonth|A reporting month represents a period of 1 month (P1M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingMonthType. 971 -|ReportingWeek|A reporting week represents a period of 7 days (P7D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingWeekType. 972 -|ReportingDay|A reporting day represents a period of 1 day (P1D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingDayType. 973 -|DateTime|A time datatype corresponding to W3C XML Schema's xs:dateTime datatype. 974 -|TimeRange|TimeRange defines a time period by providing a distinct start (date or date time) and a duration. 975 -|Month|A time datatype corresponding to W3C XML Schema's xs:gMonth datatype. 976 -|MonthDay|A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype. 977 -|Day|A time datatype corresponding to W3C XML Schema's xs:gDay datatype. 978 -|Time|A time datatype corresponding to W3C XML Schema's xs:time datatype. 979 -|Duration|A time datatype corresponding to W3C XML Schema's xs:duration datatype. 980 -|GeospatialInformation|A string used to describe geographical features like points (e.g., locations of places, landmarks, buildings, etc.), lines (e.g., rivers, roads, streets, etc.), or areas (e.g., geographical regions, countries, islands, land lots, etc.). A mix of different features is possible too, e.g., combining polygons and geographical points to describe a country and the location of its capital. 981 -|XHTML|This value indicates that the content of the component can contain XHTML markup. 982 -|KeyValues|This value indicates that the content of the component will be data key (a set of dimension references and values for the dimensions). 983 -|IdentifiableReference|This value indicates that the content of the component will be complete reference (either URN or full set of reference fields) to an Identifiable object in the SDMX Information Model. 984 -|DataSetReference|This value indicates that the content of the component will be reference to a data provider, which is actually a formal reference to a data provider and a data set identifier value. 956 +(% style="width:996.294px" %) 957 +|**Value**|(% style="width:796px" %)**Documentation** 958 +|String|(% style="width:796px" %)A string datatype corresponding to W3C XML Schema's xs:string datatype. 959 +|Alpha|(% style="width:796px" %)A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z. 960 +|AlphaNumeric|(% style="width:796px" %)A string datatype which only allows for the simple alphabetic character set of A-Z, a-z plus the simple numeric character set of 0-9. 961 +|Numeric|(% style="width:796px" %)A string datatype which only allows for the simple numeric character set of 0-9. This format is not treated as an integer, and therefore can having leading zeros. 962 +|BigInteger|(% style="width:796px" %)An integer datatype corresponding to W3C XML Schema's xs:integer datatype. 963 +|Integer|(% style="width:796px" %)An integer datatype corresponding to W3C XML Schema's xs:int datatype. 964 +|Long|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:long datatype. 965 +|Short|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:short datatype. 966 +|Decimal|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype. 967 +|Float|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:float datatype. 968 +|Double|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:double datatype. 969 +|Boolean|(% style="width:796px" %)A datatype corresponding to W3C XML Schema's xs:boolean datatype. 970 +|URI|(% style="width:796px" %)A datatype corresponding to W3C XML Schema's xs:anyURI datatype. 971 +|Count|(% style="width:796px" %)A simple incrementing Integer type. The isSequence facet must be set to true, and the interval facet must be set to "1". 972 +|InclusiveValueRange|(% style="width:796px" %)This value indicates that the startValue and endValue attributes provide the inclusive boundaries of a numeric range of type xs:decimal. 973 +|ExclusiveValueRange|(% style="width:796px" %)This value indicates that the startValue and endValue attributes provide the exclusive boundaries of a numeric range, of type xs:decimal. 974 +|Incremental|(% style="width:796px" %)This value indicates that the value increments according to the value provided in the interval facet, and has a true value for the isSequence facet. 975 +|ObservationalTimePeriod|(% style="width:796px" %)Observational time periods are the superset of all time periods in SDMX. It is the union of the standard time periods (i.e. Gregorian time periods, the reporting time periods, and date time) and a time range. 976 +|StandardTimePeriod|(% style="width:796px" %)Standard time periods is a superset of distinct time period in SDMX. It is the union of the basic time periods (i.e. the Gregorian time periods and date time) and the reporting time periods. 977 +|BasicTimePeriod|(% style="width:796px" %)BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time. 978 +|GregorianTimePeriod|(% style="width:796px" %)Gregorian time periods correspond to calendar periods and are represented in ISO-8601 formats. This is the union of the year, year month, and date formats. 979 +|GregorianYear|(% style="width:796px" %)A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601. 980 +|GregorianYearMonth|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601. 981 +|GregorianDay|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601. 982 +|ReportingTimePeriod|(% style="width:796px" %)Reporting time periods represent periods of a standard length within a reporting year, where to start of the year (defined as a month and day) must be defined elsewhere or it is assumed to be January 1. This is the union of the reporting year, semester, trimester, quarter, month, week, and day. 983 +|ReportingYear|(% style="width:796px" %)A reporting year represents a period of 1 year (P1Y) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingYearType. 984 +|ReportingSemester|(% style="width:796px" %)A reporting semester represents a period of 6 months (P6M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingSemesterType. 985 +|ReportingTrimester|(% style="width:796px" %)A reporting trimester represents a period of 4 months (P4M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingTrimesterType. 986 +|ReportingQuarter|(% style="width:796px" %)A reporting quarter represents a period of 3 months (P3M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingQuarterType. 987 +|ReportingMonth|(% style="width:796px" %)A reporting month represents a period of 1 month (P1M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingMonthType. 988 +|ReportingWeek|(% style="width:796px" %)A reporting week represents a period of 7 days (P7D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingWeekType. 989 +|ReportingDay|(% style="width:796px" %)A reporting day represents a period of 1 day (P1D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingDayType. 990 +|DateTime|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:dateTime datatype. 991 +|TimeRange|(% style="width:796px" %)TimeRange defines a time period by providing a distinct start (date or date time) and a duration. 992 +|Month|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gMonth datatype. 993 +|MonthDay|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype. 994 +|Day|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gDay datatype. 995 +|Time|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:time datatype. 996 +|Duration|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:duration datatype. 997 +|GeospatialInformation|(% style="width:796px" %)A string used to describe geographical features like points (e.g., locations of places, landmarks, buildings, etc.), lines (e.g., rivers, roads, streets, etc.), or areas (e.g., geographical regions, countries, islands, land lots, etc.). A mix of different features is possible too, e.g., combining polygons and geographical points to describe a country and the location of its capital. 998 +|XHTML|(% style="width:796px" %)This value indicates that the content of the component can contain XHTML markup. 999 +|KeyValues|(% style="width:796px" %)This value indicates that the content of the component will be data key (a set of dimension references and values for the dimensions). 1000 +|IdentifiableReference|(% style="width:796px" %)This value indicates that the content of the component will be complete reference (either URN or full set of reference fields) to an Identifiable object in the SDMX Information Model. 1001 +|DataSetReference|(% style="width:796px" %)This value indicates that the content of the component will be reference to a data provider, which is actually a formal reference to a data provider and a data set identifier value. 985 985 986 986 **BasicComponentDataType:** BasicComponentDataType provides an enumerated list of the types of characters allowed in the textType attribute for all non-target object components. 987 987 ... ... @@ -989,48 +989,49 @@ 989 989 990 990 Enumerations: 991 991 992 -|**Value**|**Documentation** 993 -|String|A string datatype corresponding to W3C XML Schema's xs:string datatype. 994 -|Alpha|A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z. 995 -|AlphaNumeric|A string datatype which only allows for the simple alphabetic character set of A-Z, a-z plus the simple numeric character set of 0-9. 996 -|Numeric|A string datatype which only allows for the simple numeric character set of 0-9. This format is not treated as an integer, and therefore can having leading zeros. 997 -|BigInteger|An integer datatype corresponding to W3C XML Schema's xs:integer datatype. 998 -|Integer|An integer datatype corresponding to W3C XML Schema's xs:int datatype. 999 -|Long|A numeric datatype corresponding to W3C XML Schema's xs:long datatype. 1000 -|Short|A numeric datatype corresponding to W3C XML Schema's xs:short datatype. 1001 -|Decimal|A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype. 1002 -|Float|A numeric datatype corresponding to W3C XML Schema's xs:float datatype. 1003 -|Double|A numeric datatype corresponding to W3C XML Schema's xs:double datatype. 1004 -|Boolean|A datatype corresponding to W3C XML Schema's xs:boolean datatype. 1005 -|URI|A datatype corresponding to W3C XML Schema's xs:anyURI datatype. 1006 -|Count|A simple incrementing Integer type. The isSequence facet must be set to true, and the interval facet must be set to "1". 1007 -|InclusiveValueRange|This value indicates that the startValue and endValue attributes provide the inclusive boundaries of a numeric range of type xs:decimal. 1008 -|ExclusiveValueRange|This value indicates that the startValue and endValue attributes provide the exclusive boundaries of a numeric range, of type xs:decimal. 1009 -|Incremental|This value indicates that the value increments according to the value provided in the interval facet, and has a true value for the isSequence facet. 1010 -|ObservationalTimePeriod|Observational time periods are the superset of all time periods in SDMX. It is the union of the standard time periods (i.e. Gregorian time periods, the reporting time periods, and date time) and a time range. 1011 -|StandardTimePeriod|Standard time periods is a superset of distinct time period in SDMX. It is the union of the basic time periods (i.e. the Gregorian time periods and date time) and the reporting time periods. 1012 -|BasicTimePeriod|BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time. 1013 -|GregorianTimePeriod|Gregorian time periods correspond to calendar periods and are represented in ISO-8601 formats. This is the union of the year, year month, and date formats. 1014 -|GregorianYear|A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601. 1015 -|GregorianYearMonth|A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601. 1016 -|GregorianDay|A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601. 1017 -|ReportingTimePeriod|Reporting time periods represent periods of a standard length within a reporting year, where to start of the year (defined as a month and day) must be defined elsewhere or it is assumed to be January 1. This is the union of the reporting year, semester, trimester, quarter, month, week, and day. 1018 -|ReportingYear|A reporting year represents a period of 1 year (P1Y) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingYearType. 1019 -|ReportingSemester|A reporting semester represents a period of 6 months (P6M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingSemesterType. 1020 -|ReportingTrimester|A reporting trimester represents a period of 4 months (P4M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingTrimesterType. 1021 -|ReportingQuarter|A reporting quarter represents a period of 3 months (P3M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingQuarterType. 1022 -|ReportingMonth|A reporting month represents a period of 1 month (P1M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingMonthType. 1023 -|ReportingWeek|A reporting week represents a period of 7 days (P7D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingWeekType. 1024 -|ReportingDay|A reporting day represents a period of 1 day (P1D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingDayType. 1025 -|DateTime|A time datatype corresponding to W3C XML Schema's xs:dateTime datatype. 1026 -|TimeRange|TimeRange defines a time period by providing a distinct start (date or date time) and a duration. 1027 -|Month|A time datatype corresponding to W3C XML Schema's xs:gMonth datatype. 1028 -|MonthDay|A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype. 1029 -|Day|A time datatype corresponding to W3C XML Schema's xs:gDay datatype. 1030 -|Time|A time datatype corresponding to W3C XML Schema's xs:time datatype. 1031 -|Duration|A time datatype corresponding to W3C XML Schema's xs:duration datatype. 1032 -|GeospatialInformation|A string used to describe geographical features like points (e.g., locations of places, landmarks, buildings, etc.), lines (e.g., rivers, roads, streets, etc.), or areas (e.g., geographical regions, countries, islands, land lots, etc.). A mix of different features is possible too, e.g., combining polygons and geographical points to describe a country and the location of its capital. 1033 -|XHTML|This value indicates that the content of the component can contain XHTML markup. 1009 +(% style="width:999.294px" %) 1010 +|**Value**|(% style="width:799px" %)**Documentation** 1011 +|String|(% style="width:799px" %)A string datatype corresponding to W3C XML Schema's xs:string datatype. 1012 +|Alpha|(% style="width:799px" %)A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z. 1013 +|AlphaNumeric|(% style="width:799px" %)A string datatype which only allows for the simple alphabetic character set of A-Z, a-z plus the simple numeric character set of 0-9. 1014 +|Numeric|(% style="width:799px" %)A string datatype which only allows for the simple numeric character set of 0-9. This format is not treated as an integer, and therefore can having leading zeros. 1015 +|BigInteger|(% style="width:799px" %)An integer datatype corresponding to W3C XML Schema's xs:integer datatype. 1016 +|Integer|(% style="width:799px" %)An integer datatype corresponding to W3C XML Schema's xs:int datatype. 1017 +|Long|(% style="width:799px" %)A numeric datatype corresponding to W3C XML Schema's xs:long datatype. 1018 +|Short|(% style="width:799px" %)A numeric datatype corresponding to W3C XML Schema's xs:short datatype. 1019 +|Decimal|(% style="width:799px" %)A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype. 1020 +|Float|(% style="width:799px" %)A numeric datatype corresponding to W3C XML Schema's xs:float datatype. 1021 +|Double|(% style="width:799px" %)A numeric datatype corresponding to W3C XML Schema's xs:double datatype. 1022 +|Boolean|(% style="width:799px" %)A datatype corresponding to W3C XML Schema's xs:boolean datatype. 1023 +|URI|(% style="width:799px" %)A datatype corresponding to W3C XML Schema's xs:anyURI datatype. 1024 +|Count|(% style="width:799px" %)A simple incrementing Integer type. The isSequence facet must be set to true, and the interval facet must be set to "1". 1025 +|InclusiveValueRange|(% style="width:799px" %)This value indicates that the startValue and endValue attributes provide the inclusive boundaries of a numeric range of type xs:decimal. 1026 +|ExclusiveValueRange|(% style="width:799px" %)This value indicates that the startValue and endValue attributes provide the exclusive boundaries of a numeric range, of type xs:decimal. 1027 +|Incremental|(% style="width:799px" %)This value indicates that the value increments according to the value provided in the interval facet, and has a true value for the isSequence facet. 1028 +|ObservationalTimePeriod|(% style="width:799px" %)Observational time periods are the superset of all time periods in SDMX. It is the union of the standard time periods (i.e. Gregorian time periods, the reporting time periods, and date time) and a time range. 1029 +|StandardTimePeriod|(% style="width:799px" %)Standard time periods is a superset of distinct time period in SDMX. It is the union of the basic time periods (i.e. the Gregorian time periods and date time) and the reporting time periods. 1030 +|BasicTimePeriod|(% style="width:799px" %)BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time. 1031 +|GregorianTimePeriod|(% style="width:799px" %)Gregorian time periods correspond to calendar periods and are represented in ISO-8601 formats. This is the union of the year, year month, and date formats. 1032 +|GregorianYear|(% style="width:799px" %)A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601. 1033 +|GregorianYearMonth|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601. 1034 +|GregorianDay|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601. 1035 +|ReportingTimePeriod|(% style="width:799px" %)Reporting time periods represent periods of a standard length within a reporting year, where to start of the year (defined as a month and day) must be defined elsewhere or it is assumed to be January 1. This is the union of the reporting year, semester, trimester, quarter, month, week, and day. 1036 +|ReportingYear|(% style="width:799px" %)A reporting year represents a period of 1 year (P1Y) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingYearType. 1037 +|ReportingSemester|(% style="width:799px" %)A reporting semester represents a period of 6 months (P6M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingSemesterType. 1038 +|ReportingTrimester|(% style="width:799px" %)A reporting trimester represents a period of 4 months (P4M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingTrimesterType. 1039 +|ReportingQuarter|(% style="width:799px" %)A reporting quarter represents a period of 3 months (P3M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingQuarterType. 1040 +|ReportingMonth|(% style="width:799px" %)A reporting month represents a period of 1 month (P1M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingMonthType. 1041 +|ReportingWeek|(% style="width:799px" %)A reporting week represents a period of 7 days (P7D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingWeekType. 1042 +|ReportingDay|(% style="width:799px" %)A reporting day represents a period of 1 day (P1D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingDayType. 1043 +|DateTime|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:dateTime datatype. 1044 +|TimeRange|(% style="width:799px" %)TimeRange defines a time period by providing a distinct start (date or date time) and a duration. 1045 +|Month|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:gMonth datatype. 1046 +|MonthDay|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype. 1047 +|Day|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:gDay datatype. 1048 +|Time|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:time datatype. 1049 +|Duration|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:duration datatype. 1050 +|GeospatialInformation|(% style="width:799px" %)A string used to describe geographical features like points (e.g., locations of places, landmarks, buildings, etc.), lines (e.g., rivers, roads, streets, etc.), or areas (e.g., geographical regions, countries, islands, land lots, etc.). A mix of different features is possible too, e.g., combining polygons and geographical points to describe a country and the location of its capital. 1051 +|XHTML|(% style="width:799px" %)This value indicates that the content of the component can contain XHTML markup. 1034 1034 1035 1035 **SimpleDataType:** SimpleDataType restricts BasicComponentDataType to specify the allowable data types for a data structure definition component. The XHTML representation is removed as a possible type. 1036 1036 ... ... @@ -1038,47 +1038,48 @@ 1038 1038 1039 1039 Enumerations: 1040 1040 1041 -|**Value**|**Documentation** 1042 -|String|A string datatype corresponding to W3C XML Schema's xs:string datatype. 1043 -|Alpha|A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z. 1044 -|AlphaNumeric|A string datatype which only allows for the simple alphabetic character set of A-Z, a-z plus the simple numeric character set of 0-9. 1045 -|Numeric|A string datatype which only allows for the simple numeric character set of 0-9. This format is not treated as an integer, and therefore can having leading zeros. 1046 -|BigInteger|An integer datatype corresponding to W3C XML Schema's xs:integer datatype. 1047 -|Integer|An integer datatype corresponding to W3C XML Schema's xs:int datatype. 1048 -|Long|A numeric datatype corresponding to W3C XML Schema's xs:long datatype. 1049 -|Short|A numeric datatype corresponding to W3C XML Schema's xs:short datatype. 1050 -|Decimal|A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype. 1051 -|Float|A numeric datatype corresponding to W3C XML Schema's xs:float datatype. 1052 -|Double|A numeric datatype corresponding to W3C XML Schema's xs:double datatype. 1053 -|Boolean|A datatype corresponding to W3C XML Schema's xs:boolean datatype. 1054 -|URI|A datatype corresponding to W3C XML Schema's xs:anyURI datatype. 1055 -|Count|A simple incrementing Integer type. The isSequence facet must be set to true, and the interval facet must be set to "1". 1056 -|InclusiveValueRange|This value indicates that the startValue and endValue attributes provide the inclusive boundaries of a numeric range of type xs:decimal. 1057 -|ExclusiveValueRange|This value indicates that the startValue and endValue attributes provide the exclusive boundaries of a numeric range, of type xs:decimal. 1058 -|Incremental|This value indicates that the value increments according to the value provided in the interval facet, and has a true value for the isSequence facet. 1059 -|ObservationalTimePeriod|Observational time periods are the superset of all time periods in SDMX. It is the union of the standard time periods (i.e. Gregorian time periods, the reporting time periods, and date time) and a time range. 1060 -|StandardTimePeriod|Standard time periods is a superset of distinct time period in SDMX. It is the union of the basic time periods (i.e. the Gregorian time periods and date time) and the reporting time periods. 1061 -|BasicTimePeriod|BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time. 1062 -|GregorianTimePeriod|Gregorian time periods correspond to calendar periods and are represented in ISO-8601 formats. This is the union of the year, year month, and date formats. 1063 -|GregorianYear|A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601. 1064 -|GregorianYearMonth|A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601. 1065 -|GregorianDay|A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601. 1066 -|ReportingTimePeriod|Reporting time periods represent periods of a standard length within a reporting year, where to start of the year (defined as a month and day) must be defined elsewhere or it is assumed to be January 1. This is the union of the reporting year, semester, trimester, quarter, month, week, and day. 1067 -|ReportingYear|A reporting year represents a period of 1 year (P1Y) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingYearType. 1068 -|ReportingSemester|A reporting semester represents a period of 6 months (P6M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingSemesterType. 1069 -|ReportingTrimester|A reporting trimester represents a period of 4 months (P4M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingTrimesterType. 1070 -|ReportingQuarter|A reporting quarter represents a period of 3 months (P3M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingQuarterType. 1071 -|ReportingMonth|A reporting month represents a period of 1 month (P1M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingMonthType. 1072 -|ReportingWeek|A reporting week represents a period of 7 days (P7D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingWeekType. 1073 -|ReportingDay|A reporting day represents a period of 1 day (P1D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingDayType. 1074 -|DateTime|A time datatype corresponding to W3C XML Schema's xs:dateTime datatype. 1075 -|TimeRange|TimeRange defines a time period by providing a distinct start (date or date time) and a duration. 1076 -|Month|A time datatype corresponding to W3C XML Schema's xs:gMonth datatype. 1077 -|MonthDay|A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype. 1078 -|Day|A time datatype corresponding to W3C XML Schema's xs:gDay datatype. 1079 -|Time|A time datatype corresponding to W3C XML Schema's xs:time datatype. 1080 -|Duration|A time datatype corresponding to W3C XML Schema's xs:duration datatype. 1081 -|GeospatialInformation|A string used to describe geographical features like points (e.g., locations of places, landmarks, buildings, etc.), lines (e.g., rivers, roads, streets, etc.), or areas (e.g., geographical regions, countries, islands, land lots, etc.). A mix of different features is possible too, e.g., combining polygons and geographical points to describe a country and the location of its capital. 1059 +(% style="width:996.294px" %) 1060 +|**Value**|(% style="width:796px" %)**Documentation** 1061 +|String|(% style="width:796px" %)A string datatype corresponding to W3C XML Schema's xs:string datatype. 1062 +|Alpha|(% style="width:796px" %)A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z. 1063 +|AlphaNumeric|(% style="width:796px" %)A string datatype which only allows for the simple alphabetic character set of A-Z, a-z plus the simple numeric character set of 0-9. 1064 +|Numeric|(% style="width:796px" %)A string datatype which only allows for the simple numeric character set of 0-9. This format is not treated as an integer, and therefore can having leading zeros. 1065 +|BigInteger|(% style="width:796px" %)An integer datatype corresponding to W3C XML Schema's xs:integer datatype. 1066 +|Integer|(% style="width:796px" %)An integer datatype corresponding to W3C XML Schema's xs:int datatype. 1067 +|Long|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:long datatype. 1068 +|Short|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:short datatype. 1069 +|Decimal|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype. 1070 +|Float|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:float datatype. 1071 +|Double|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:double datatype. 1072 +|Boolean|(% style="width:796px" %)A datatype corresponding to W3C XML Schema's xs:boolean datatype. 1073 +|URI|(% style="width:796px" %)A datatype corresponding to W3C XML Schema's xs:anyURI datatype. 1074 +|Count|(% style="width:796px" %)A simple incrementing Integer type. The isSequence facet must be set to true, and the interval facet must be set to "1". 1075 +|InclusiveValueRange|(% style="width:796px" %)This value indicates that the startValue and endValue attributes provide the inclusive boundaries of a numeric range of type xs:decimal. 1076 +|ExclusiveValueRange|(% style="width:796px" %)This value indicates that the startValue and endValue attributes provide the exclusive boundaries of a numeric range, of type xs:decimal. 1077 +|Incremental|(% style="width:796px" %)This value indicates that the value increments according to the value provided in the interval facet, and has a true value for the isSequence facet. 1078 +|ObservationalTimePeriod|(% style="width:796px" %)Observational time periods are the superset of all time periods in SDMX. It is the union of the standard time periods (i.e. Gregorian time periods, the reporting time periods, and date time) and a time range. 1079 +|StandardTimePeriod|(% style="width:796px" %)Standard time periods is a superset of distinct time period in SDMX. It is the union of the basic time periods (i.e. the Gregorian time periods and date time) and the reporting time periods. 1080 +|BasicTimePeriod|(% style="width:796px" %)BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time. 1081 +|GregorianTimePeriod|(% style="width:796px" %)Gregorian time periods correspond to calendar periods and are represented in ISO-8601 formats. This is the union of the year, year month, and date formats. 1082 +|GregorianYear|(% style="width:796px" %)A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601. 1083 +|GregorianYearMonth|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601. 1084 +|GregorianDay|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601. 1085 +|ReportingTimePeriod|(% style="width:796px" %)Reporting time periods represent periods of a standard length within a reporting year, where to start of the year (defined as a month and day) must be defined elsewhere or it is assumed to be January 1. This is the union of the reporting year, semester, trimester, quarter, month, week, and day. 1086 +|ReportingYear|(% style="width:796px" %)A reporting year represents a period of 1 year (P1Y) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingYearType. 1087 +|ReportingSemester|(% style="width:796px" %)A reporting semester represents a period of 6 months (P6M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingSemesterType. 1088 +|ReportingTrimester|(% style="width:796px" %)A reporting trimester represents a period of 4 months (P4M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingTrimesterType. 1089 +|ReportingQuarter|(% style="width:796px" %)A reporting quarter represents a period of 3 months (P3M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingQuarterType. 1090 +|ReportingMonth|(% style="width:796px" %)A reporting month represents a period of 1 month (P1M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingMonthType. 1091 +|ReportingWeek|(% style="width:796px" %)A reporting week represents a period of 7 days (P7D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingWeekType. 1092 +|ReportingDay|(% style="width:796px" %)A reporting day represents a period of 1 day (P1D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingDayType. 1093 +|DateTime|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:dateTime datatype. 1094 +|TimeRange|(% style="width:796px" %)TimeRange defines a time period by providing a distinct start (date or date time) and a duration. 1095 +|Month|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gMonth datatype. 1096 +|MonthDay|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype. 1097 +|Day|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gDay datatype. 1098 +|Time|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:time datatype. 1099 +|Duration|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:duration datatype. 1100 +|GeospatialInformation|(% style="width:796px" %)A string used to describe geographical features like points (e.g., locations of places, landmarks, buildings, etc.), lines (e.g., rivers, roads, streets, etc.), or areas (e.g., geographical regions, countries, islands, land lots, etc.). A mix of different features is possible too, e.g., combining polygons and geographical points to describe a country and the location of its capital. 1082 1082 1083 1083 **TimeDataType:** TimeDataType restricts SimpleDataType to specify the allowable data types for representing a time value. 1084 1084 ... ... @@ -1086,24 +1086,25 @@ 1086 1086 1087 1087 Enumerations: 1088 1088 1089 -|**Value**|**Documentation** 1090 -|ObservationalTimePeriod|Observational time periods are the superset of all time periods in SDMX. It is the union of the standard time periods (i.e. Gregorian time periods, the reporting time periods, and date time) and a time range. 1091 -|StandardTimePeriod|Standard time periods is a superset of distinct time period in SDMX. It is the union of the basic time periods (i.e. the Gregorian time periods and date time) and the reporting time periods. 1092 -|BasicTimePeriod|BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time. 1093 -|GregorianTimePeriod|Gregorian time periods correspond to calendar periods and are represented in ISO-8601 formats. This is the union of the year, year month, and date formats. 1094 -|GregorianYear|A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601. 1095 -|GregorianYearMonth|A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601. 1096 -|GregorianDay|A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601. 1097 -|ReportingTimePeriod|Reporting time periods represent periods of a standard length within a reporting year, where to start of the year (defined as a month and day) must be defined elsewhere or it is assumed to be January 1. This is the union of the reporting year, semester, trimester, quarter, month, week, and day. 1098 -|ReportingYear|A reporting year represents a period of 1 year (P1Y) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingYearType. 1099 -|ReportingSemester|A reporting semester represents a period of 6 months (P6M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingSemesterType. 1100 -|ReportingTrimester|A reporting trimester represents a period of 4 months (P4M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingTrimesterType. 1101 -|ReportingQuarter|A reporting quarter represents a period of 3 months (P3M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingQuarterType. 1102 -|ReportingMonth|A reporting month represents a period of 1 month (P1M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingMonthType. 1103 -|ReportingWeek|A reporting week represents a period of 7 days (P7D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingWeekType. 1104 -|ReportingDay|A reporting day represents a period of 1 day (P1D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingDayType. 1105 -|DateTime|A time datatype corresponding to W3C XML Schema's xs:dateTime datatype. 1106 -|TimeRange|TimeRange defines a time period by providing a distinct start (date or date time) and a duration. 1108 +(% style="width:1002.29px" %) 1109 +|**Value**|(% style="width:802px" %)**Documentation** 1110 +|ObservationalTimePeriod|(% style="width:802px" %)Observational time periods are the superset of all time periods in SDMX. It is the union of the standard time periods (i.e. Gregorian time periods, the reporting time periods, and date time) and a time range. 1111 +|StandardTimePeriod|(% style="width:802px" %)Standard time periods is a superset of distinct time period in SDMX. It is the union of the basic time periods (i.e. the Gregorian time periods and date time) and the reporting time periods. 1112 +|BasicTimePeriod|(% style="width:802px" %)BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time. 1113 +|GregorianTimePeriod|(% style="width:802px" %)Gregorian time periods correspond to calendar periods and are represented in ISO-8601 formats. This is the union of the year, year month, and date formats. 1114 +|GregorianYear|(% style="width:802px" %)A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601. 1115 +|GregorianYearMonth|(% style="width:802px" %)A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601. 1116 +|GregorianDay|(% style="width:802px" %)A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601. 1117 +|ReportingTimePeriod|(% style="width:802px" %)Reporting time periods represent periods of a standard length within a reporting year, where to start of the year (defined as a month and day) must be defined elsewhere or it is assumed to be January 1. This is the union of the reporting year, semester, trimester, quarter, month, week, and day. 1118 +|ReportingYear|(% style="width:802px" %)A reporting year represents a period of 1 year (P1Y) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingYearType. 1119 +|ReportingSemester|(% style="width:802px" %)A reporting semester represents a period of 6 months (P6M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingSemesterType. 1120 +|ReportingTrimester|(% style="width:802px" %)A reporting trimester represents a period of 4 months (P4M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingTrimesterType. 1121 +|ReportingQuarter|(% style="width:802px" %)A reporting quarter represents a period of 3 months (P3M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingQuarterType. 1122 +|ReportingMonth|(% style="width:802px" %)A reporting month represents a period of 1 month (P1M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingMonthType. 1123 +|ReportingWeek|(% style="width:802px" %)A reporting week represents a period of 7 days (P7D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingWeekType. 1124 +|ReportingDay|(% style="width:802px" %)A reporting day represents a period of 1 day (P1D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingDayType. 1125 +|DateTime|(% style="width:802px" %)A time datatype corresponding to W3C XML Schema's xs:dateTime datatype. 1126 +|TimeRange|(% style="width:802px" %)TimeRange defines a time period by providing a distinct start (date or date time) and a duration. 1107 1107 1108 1108 **UrnPrefixPart:** This is validates the first part of the URN (urn:sdmx.org.infomodel.<package>.<class=). It is intended to be further restricted. 1109 1109 ... ... @@ -1138,11 +1138,9 @@ 1138 1138 **UrnVersionPart:** This refines the prefix, classes, agency, and maintainable id patterns to validate the version number part of the URN ((<version_number)). It accounts for both legacy and semantic versioning, but not wildarding (for referencing). It is meant to be further refined, although all parts after this are optional. 1139 1139 1140 1140 Derived by restriction of UrnMaintainableIdPart. 1141 -Regular Expression Pattern: . +\((0|[1-9]\d*)(\.(0|[1-9]\d*))?\).*.+\((0|[1-9]\d*)(\.(0|[1-9]\d*)){2}(\-(([A-Za-z\-]|([A-Za-z\-][A-Za-z0-9\-]+)|([A-Za-z0-9\-]+[A-Za-z\-][A-Za-z0-9\-]*))|(0|[1-9][0-9]*))(\.(([A-Za-z\-]|([A-Za-z\-][A-Za-z0-9\-]+)|([A-Za-z0-9\-]+[A-Za-z\-][A-Za-z0-9\-]*))|(0|[1-9][0-9]* 1161 +Regular Expression Pattern: . +\((0|[1-9]\d*)(\.(0|[1-9]\d*))?\).*.+\((0|[1-9]\d*)(\.(0|[1-9]\d*)){2}(\-(([A-Za-z\-]|([A-Za-z\-][A-Za-z0-9\-]+)|([A-Za-z0-9\-]+[A-Za-z\-][A-Za-z0-9\-]*))|(0|[1-9][0-9]*))(\.(([A-Za-z\-]|([A-Za-z\-][A-Za-z0-9\-]+)|([A-Za-z0-9\-]+[A-Za-z\-][A-Za-z0-9\-]*))|(0|[1-9][0-9]~*~*)?\). 1142 1142 ))) 1143 1143 1144 -*)?\). 1145 - 1146 1146 **UrnReferenceVersionPart:** This refines the prefix, classes, agency, and maintainable id patterns to validate the version number part of a URN reference ((<version_number)). It accounts for both legacy and semantic versioning (including late binding). It is meant to be further refined, although all parts after this are optional. 1147 1147 1148 1148 Derived by restriction of UrnMaintainableIdPart.