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
-
... ... @@ -434,28 +434,26 @@ 434 434 435 435 Attribute Documentation: 436 436 437 -(% style="width:1005.29px" %) 438 -|**Name**|**Type**|(% style="width:623px" %)**Documentation** 439 -|id|IDType|(% style="width:623px" %)The id is the identifier for the object. 440 -|urn|MaintainableUrnType|(% style="width:623px" %)The urn attribute holds a valid SDMX Registry URN (see SDMX Registry Specification for details). 441 -|uri|xs:anyURI|(% style="width:623px" %)The uri attribute holds a URI that contains a link to a resource with additional information about the object, such as a web page. This uri is not a SDMX message. 442 -|version|VersionType|(% style="width:623px" %)This version attribute holds a version number (see common:VersionType definition for details). If not supplied, artefact is considered to be un-versioned. 443 -|validFrom|xs:dateTime|(% style="width:623px" %)The validFrom attribute provides the inclusive start date for providing supplemental validity information about the version. 444 -|validTo|xs:dateTime|(% style="width:623px" %)The validTo attribute provides the inclusive end date for providing supplemental validity information about the version. 445 -|agencyID|NestedNCNameIDType|(% style="width:623px" %)The agencyID must be provided, and identifies the maintenance agency of the object. 446 -|isExternalReference (default: false)|xs:boolean|(% style="width:623px" %)The isExternalReference attribute, if true, indicates that the actual object is not defined the corresponding element, rather its full details are defined elsewhere - indicated by either the registryURL, the repositoryURL, or the structureURL. The purpose of this is so that each structure message does not have to redefine object that are already defined elsewhere. If the isExternalReference attribute is not set, then it is assumed to be false, and the object should contain the full definition of its contents. If more than one of the registryURL, the repositoryURL, and the structureURL are supplied, then the application processing the object can choose the method it finds best suited to retrieve the details of the object. 447 -|serviceURL|xs:anyURI|(% style="width:623px" %)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. 448 -|structureURL|xs:anyURI|(% style="width:623px" %)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. 449 -|isPartialLanguage (default: false)|xs:boolean|(% style="width:623px" %)The isPartialLanguage attribute, if true, indicates that the object doesn't contain the complete set of all available languages, e.g., when obtained as a response to a GET query that requested specific languages through the HTTP header ‘Accept-Language’. 437 +|**Name**|**Type**|**Documentation** 438 +|id|IDType|The id is the identifier for the object. 439 +|urn|MaintainableUrnType|The urn attribute holds a valid SDMX Registry URN (see SDMX Registry Specification for details). 440 +|uri|xs:anyURI|The uri attribute holds a URI that contains a link to a resource with additional information about the object, such as a web page. This uri is not a SDMX message. 441 +|version|VersionType|This version attribute holds a version number (see common:VersionType definition for details). If not supplied, artefact is considered to be un-versioned. 442 +|validFrom|xs:dateTime|The validFrom attribute provides the inclusive start date for providing supplemental validity information about the version. 443 +|validTo|xs:dateTime|The validTo attribute provides the inclusive end date for providing supplemental validity information about the version. 444 +|agencyID|NestedNCNameIDType|The agencyID must be provided, and identifies the maintenance agency of the object. 445 +|isExternalReference (default: false)|xs:boolean|The isExternalReference attribute, if true, indicates that the actual object is not defined the corresponding element, rather its full details are defined elsewhere - indicated by either the registryURL, the repositoryURL, or the structureURL. The purpose of this is so that each structure message does not have to redefine object that are already defined elsewhere. If the isExternalReference attribute is not set, then it is assumed to be false, and the object should contain the full definition of its contents. If more than one of the registryURL, the repositoryURL, and the structureURL are supplied, then the application processing the object can choose the method it finds best suited to retrieve the details of the object. 446 +|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. 447 +|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. 448 +|isPartialLanguage (default: false)|xs:boolean|The isPartialLanguage attribute, if true, indicates that the object doesn't contain the complete set of all available languages, e.g., when obtained as a response to a GET query that requested specific languages through the HTTP header ‘Accept-Language’. 450 450 451 451 Element Documentation: 452 452 453 -(% style="width:1004.29px" %) 454 -|**Name**|**Type**|(% style="width:727px" %)**Documentation** 455 -|Annotations|AnnotationsType|(% style="width:727px" %)Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType may reference it. 456 -|Link|LinkType|(% style="width:727px" %)Allows for the linking of other resources to identifiable objects. For example, if there is reference metadata associated with a structure, a link to the meatadata report can be dynamically inserted in the structure metadata. 457 -|Name|TextType|(% style="width:727px" %)Name provides for a human-readable name for the object. This may be provided in multiple, parallel language-equivalent forms. 458 -|Description|TextType|(% style="width:727px" %)Description provides for a longer human-readable description of the object. This may be provided in multiple, parallel language-equivalent forms. 452 +|**Name**|**Type**|**Documentation** 453 +|Annotations|AnnotationsType|Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType may reference it. 454 +|Link|LinkType|Allows for the linking of other resources to identifiable objects. For example, if there is reference metadata associated with a structure, a link to the meatadata report can be dynamically inserted in the structure metadata. 455 +|Name|TextType|Name provides for a human-readable name for the object. This may be provided in multiple, parallel language-equivalent forms. 456 +|Description|TextType|Description provides for a longer human-readable description of the object. This may be provided in multiple, parallel language-equivalent forms. 459 459 460 460 **ReferencePeriodType:** Specifies the inclusive start and end times. 461 461 ... ... @@ -467,10 +467,9 @@ 467 467 468 468 Attribute Documentation: 469 469 470 -(% style="width:995.294px" %) 471 -|(% style="width:145px" %)**Name**|(% style="width:216px" %)**Type**|(% style="width:632px" %)**Documentation** 472 -|(% style="width:145px" %)startTime|(% style="width:216px" %)xs:dateTime|(% style="width:632px" %)The startTime attributes contains the inclusive start date for the reference period. 473 -|(% style="width:145px" %)endTime|(% style="width:216px" %)xs:dateTime|(% style="width:632px" %)The endTime attributes contains the inclusive end date for the reference period. 468 +|**Name**|**Type**|**Documentation** 469 +|startTime|xs:dateTime|The startTime attributes contains the inclusive start date for the reference period. 470 +|endTime|xs:dateTime|The endTime attributes contains the inclusive end date for the reference period. 474 474 475 475 **QueryableDataSourceType:** QueryableDataSourceType describes a data source which is accepts an standard SDMX Query message and responds appropriately. 476 476 ... ... @@ -482,18 +482,16 @@ 482 482 483 483 Attribute Documentation: 484 484 485 -(% style="width:999.294px" %) 486 -|(% style="width:259px" %)**Name**|(% style="width:236px" %)**Type**|(% style="width:502px" %)**Documentation** 487 -|(% style="width:259px" %)isRESTDatasource|(% style="width:236px" %)xs:boolean|(% style="width:502px" %)The isRESTDatasource attribute indicates, if true, that the queryable data source is accessible via the REST protocol. 488 -|(% style="width:259px" %)isWebServiceDatasource|(% style="width:236px" %)xs:boolean|(% style="width:502px" %)The isWebServiceDatasource attribute indicates, if true, that the queryable data source is accessible via Web Services protocols. 482 +|**Name**|**Type**|**Documentation** 483 +|isRESTDatasource|xs:boolean|The isRESTDatasource attribute indicates, if true, that the queryable data source is accessible via the REST protocol. 484 +|isWebServiceDatasource|xs:boolean|The isWebServiceDatasource attribute indicates, if true, that the queryable data source is accessible via Web Services protocols. 489 489 490 490 Element Documentation: 491 491 492 -(% style="width:996.294px" %) 493 -|**Name**|**Type**|(% style="width:657px" %)**Documentation** 494 -|DataURL|xs:anyURI|(% style="width:657px" %)DataURL contains the URL of the data source. 495 -|WSDLURL|xs:anyURI|(% style="width:657px" %)WSDLURL provides the location of a WSDL instance on the internet which describes the queryable data source. 496 -|WADLURL|xs:anyURI|(% style="width:657px" %)WADLURL provides the location of a WADL instance on the internet which describes the REST protocol of the queryable data source. 488 +|**Name**|**Type**|**Documentation** 489 +|DataURL|xs:anyURI|DataURL contains the URL of the data source. 490 +|WSDLURL|xs:anyURI|WSDLURL provides the location of a WSDL instance on the internet which describes the queryable data source. 491 +|WADLURL|xs:anyURI|WADLURL provides the location of a WADL instance on the internet which describes the REST protocol of the queryable data source. 497 497 498 498 **XHTMLType:** XHTMLType allows for mixed content of text and XHTML tags. When using this type, one will have to provide a reference to the XHTML schema, since the processing of the tags within this type is strict, meaning that they are validated against the XHTML schema provided. 499 499 ... ... @@ -501,13 +501,12 @@ 501 501 xml:lang? 502 502 503 503 Content: 504 -{text} x {any element with namespace of http: ~/~/www.w3.org/1999/xhtml}499 +{text} x {any element with namespace of http://www.w3.org/1999/xhtml} 505 505 506 506 Attribute Documentation: 507 507 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 503 +|**Name**|**Type**|**Documentation** 504 +|xml:lang (default: en)|xs:language 511 511 512 512 ***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). 513 513 ... ... @@ -519,25 +519,23 @@ 519 519 520 520 Attribute Documentation: 521 521 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. 516 +|**Name**|**Type**|**Documentation** 517 +|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. 518 +|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located. 519 +|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. 520 +|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. 521 +|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. 522 +|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. 523 +|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. 531 531 532 532 Element Documentation: 533 533 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. 527 +|**Name**|**Type**|**Documentation** 528 +|ProvisionAgreement|ProvisionAgreementRe ferenceType|ProvisionAgreement references a provision agreement which the data or metadata is reported against. 529 +|StructureUsage|StructureUsageRefere nceType|StructureUsage references a flow which the data or metadata is reported against. 530 +|Structure|StructureReferenceTy pe|Structure references the structure which defines the structure of the data or metadata set. 539 539 540 - //**DataStructureType:**//DataStructureType is an abstract base type the forms the basis for the structural information for a data set.532 +***DataStructureType*:** DataStructureType is an abstract base type the forms the basis for the structural information for a data set. 541 541 542 542 Derivation: 543 543 ... ... @@ -552,23 +552,21 @@ 552 552 553 553 Attribute Documentation: 554 554 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. 547 +|**Name**|**Type**|**Documentation** 548 +|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. 549 +|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located. 550 +|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. 551 +|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. 552 +|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. 553 +|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. 554 +|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. 564 564 565 565 Element Documentation: 566 566 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. 558 +|**Name**|**Type**|**Documentation** 559 +|ProvisionAgreement|ProvisionAgreementRe ferenceType|ProvisionAgreement references a provision agreement which the data is reported against. 560 +|StructureUsage|DataflowReferenceTyp e|StructureUsage references a dataflow which the data is reported against. 561 +|Structure|DataStructureReferen ceType|Structure references the data structure definition which defines the structure of the data. 572 572 573 573 **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. 574 574 ... ... @@ -586,25 +586,23 @@ 586 586 587 587 Attribute Documentation: 588 588 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. 579 +|**Name**|**Type**|**Documentation** 580 +|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. 581 +|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located. 582 +|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. 583 +|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. 584 +|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. 585 +|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. 586 +|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. 598 598 599 599 Element Documentation: 600 600 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. 590 +|**Name**|**Type**|**Documentation** 591 +|ProvisionAgreement|ProvisionAgreementReferenceType|ProvisionAgreement references a provision agreement which the data is reported against. 592 +|StructureUsage|DataflowReferenceType|StructureUsage references a dataflow which the data is reported against. 593 +|Structure|DataStructureReferen ceType|Structure references the data structure definition which defines the structure of the data. 606 606 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.595 +***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. 608 608 609 609 Derivation: 610 610 ... ... @@ -619,21 +619,19 @@ 619 619 620 620 Attribute Documentation: 621 621 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. 610 +|**Name**|**Type**|**Documentation** 611 +|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. 612 +|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located. 613 +|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. 614 +|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. 615 +|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. 629 629 630 630 Element Documentation: 631 631 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. 619 +|**Name**|**Type**|**Documentation** 620 +|ProvisionAgreement|ProvisionAgreementReferenceType|ProvisionAgreement references a provision agreement which the metadata is reported against. 621 +|StructureUsage|MetadataflowReferenceType|StructureUsage references a metadataflow which the metadata is reported against. 622 +|Structure|MetadataStructureReferenceType|Structure references the metadata structure definition which defines the structure of the metadata. 637 637 638 638 **GenericMetadataStructureType:** GenericMetadataStructureType defines the structural information for a generic metadata message. 639 639 ... ... @@ -651,20 +651,18 @@ 651 651 652 652 Attribute Documentation: 653 653 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. 640 +|**Name**|**Type**|**Documentation** 641 +|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. 642 +|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located. 643 +|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. 644 +|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. 660 660 661 661 Element Documentation: 662 662 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. 648 +|**Name**|**Type**|**Documentation** 649 +|ProvisionAgreement|ProvisionAgreementReferenceType|ProvisionAgreement references a provision agreement which the metadata is reported against. 650 +|StructureUsage|MetadataflowReferenceType|StructureUsage references a metadataflow which the metadata is reported against. 651 +|Structure|MetadataStructureReferenceType|Structure references the metadata structure definition which defines the structure of the metadata. 668 668 669 669 === 2.1.4 Simple Types === 670 670 ... ... @@ -889,9 +889,8 @@ 889 889 890 890 Enumerations: 891 891 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. 876 +|**Value**|**Documentation** 877 +|unbounded|Object has no upper limit on occurrences. 895 895 896 896 **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. 897 897 ... ... @@ -899,12 +899,11 @@ 899 899 900 900 Enumerations: 901 901 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. 885 +|**Value**|**Documentation** 886 +|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. 887 +|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. 888 +|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. 889 +|Information|Informational - data/metadata is being exchanged for informational purposes only, and not meant to update a system. 908 908 909 909 **WildCardValueType:** WildCardValueType is a single value code list, used to include the '%' character - indicating that an entire field is wild carded. 910 910 ... ... @@ -912,9 +912,8 @@ 912 912 913 913 Enumerations: 914 914 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. 897 +|**Value**|**Documentation** 898 +|%|Indicates a wild card value. 918 918 919 919 **CascadeSelectionType:** 920 920 ... ... @@ -927,9 +927,8 @@ 927 927 928 928 Enumerations: 929 929 930 -(% style="width:504.294px" %) 931 -|(% style="width:165px" %)**Value**|(% style="width:336px" %)**Documentation** 932 -|(% style="width:165px" %)excluderoot|(% style="width:336px" %) 911 +|**Value**|**Documentation** 912 +|excluderoot| 933 933 934 934 **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". 935 935 ... ... @@ -942,10 +942,9 @@ 942 942 943 943 Enumerations: 944 944 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. 925 +|**Value**|**Documentation** 926 +|AllDimensions|AllDimensions notes that the cross sectional format shall be flat; that is all dimensions should be contained at the observation level. 927 +|TIME_PERIOD|TIME_PERIOD refers to the fixed identifier for the time dimension. 949 949 950 950 **DataType:** DataTypeType provides an enumerated list of the types of data formats allowed as the for the representation of an object. 951 951 ... ... @@ -953,52 +953,51 @@ 953 953 954 954 Enumerations: 955 955 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. 935 +|**Value**|**Documentation** 936 +|String|A string datatype corresponding to W3C XML Schema's xs:string datatype. 937 +|Alpha|A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z. 938 +|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. 939 +|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. 940 +|BigInteger|An integer datatype corresponding to W3C XML Schema's xs:integer datatype. 941 +|Integer|An integer datatype corresponding to W3C XML Schema's xs:int datatype. 942 +|Long|A numeric datatype corresponding to W3C XML Schema's xs:long datatype. 943 +|Short|A numeric datatype corresponding to W3C XML Schema's xs:short datatype. 944 +|Decimal|A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype. 945 +|Float|A numeric datatype corresponding to W3C XML Schema's xs:float datatype. 946 +|Double|A numeric datatype corresponding to W3C XML Schema's xs:double datatype. 947 +|Boolean|A datatype corresponding to W3C XML Schema's xs:boolean datatype. 948 +|URI|A datatype corresponding to W3C XML Schema's xs:anyURI datatype. 949 +|Count|A simple incrementing Integer type. The isSequence facet must be set to true, and the interval facet must be set to "1". 950 +|InclusiveValueRange|This value indicates that the startValue and endValue attributes provide the inclusive boundaries of a numeric range of type xs:decimal. 951 +|ExclusiveValueRange|This value indicates that the startValue and endValue attributes provide the exclusive boundaries of a numeric range, of type xs:decimal. 952 +|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. 953 +|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. 954 +|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. 955 +|BasicTimePeriod|BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time. 956 +|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. 957 +|GregorianYear|A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601. 958 +|GregorianYearMonth|A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601. 959 +|GregorianDay|A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601. 960 +|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. 961 +|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. 962 +|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. 963 +|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. 964 +|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. 965 +|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. 966 +|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. 967 +|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. 968 +|DateTime|A time datatype corresponding to W3C XML Schema's xs:dateTime datatype. 969 +|TimeRange|TimeRange defines a time period by providing a distinct start (date or date time) and a duration. 970 +|Month|A time datatype corresponding to W3C XML Schema's xs:gMonth datatype. 971 +|MonthDay|A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype. 972 +|Day|A time datatype corresponding to W3C XML Schema's xs:gDay datatype. 973 +|Time|A time datatype corresponding to W3C XML Schema's xs:time datatype. 974 +|Duration|A time datatype corresponding to W3C XML Schema's xs:duration datatype. 975 +|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. 976 +|XHTML|This value indicates that the content of the component can contain XHTML markup. 977 +|KeyValues|This value indicates that the content of the component will be data key (a set of dimension references and values for the dimensions). 978 +|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. 979 +|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. 1002 1002 1003 1003 **BasicComponentDataType:** BasicComponentDataType provides an enumerated list of the types of characters allowed in the textType attribute for all non-target object components. 1004 1004 ... ... @@ -1006,49 +1006,48 @@ 1006 1006 1007 1007 Enumerations: 1008 1008 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. 987 +|**Value**|**Documentation** 988 +|String|A string datatype corresponding to W3C XML Schema's xs:string datatype. 989 +|Alpha|A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z. 990 +|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. 991 +|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. 992 +|BigInteger|An integer datatype corresponding to W3C XML Schema's xs:integer datatype. 993 +|Integer|An integer datatype corresponding to W3C XML Schema's xs:int datatype. 994 +|Long|A numeric datatype corresponding to W3C XML Schema's xs:long datatype. 995 +|Short|A numeric datatype corresponding to W3C XML Schema's xs:short datatype. 996 +|Decimal|A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype. 997 +|Float|A numeric datatype corresponding to W3C XML Schema's xs:float datatype. 998 +|Double|A numeric datatype corresponding to W3C XML Schema's xs:double datatype. 999 +|Boolean|A datatype corresponding to W3C XML Schema's xs:boolean datatype. 1000 +|URI|A datatype corresponding to W3C XML Schema's xs:anyURI datatype. 1001 +|Count|A simple incrementing Integer type. The isSequence facet must be set to true, and the interval facet must be set to "1". 1002 +|InclusiveValueRange|This value indicates that the startValue and endValue attributes provide the inclusive boundaries of a numeric range of type xs:decimal. 1003 +|ExclusiveValueRange|This value indicates that the startValue and endValue attributes provide the exclusive boundaries of a numeric range, of type xs:decimal. 1004 +|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. 1005 +|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. 1006 +|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. 1007 +|BasicTimePeriod|BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time. 1008 +|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. 1009 +|GregorianYear|A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601. 1010 +|GregorianYearMonth|A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601. 1011 +|GregorianDay|A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601. 1012 +|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. 1013 +|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. 1014 +|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. 1015 +|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. 1016 +|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. 1017 +|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. 1018 +|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. 1019 +|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. 1020 +|DateTime|A time datatype corresponding to W3C XML Schema's xs:dateTime datatype. 1021 +|TimeRange|TimeRange defines a time period by providing a distinct start (date or date time) and a duration. 1022 +|Month|A time datatype corresponding to W3C XML Schema's xs:gMonth datatype. 1023 +|MonthDay|A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype. 1024 +|Day|A time datatype corresponding to W3C XML Schema's xs:gDay datatype. 1025 +|Time|A time datatype corresponding to W3C XML Schema's xs:time datatype. 1026 +|Duration|A time datatype corresponding to W3C XML Schema's xs:duration datatype. 1027 +|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. 1028 +|XHTML|This value indicates that the content of the component can contain XHTML markup. 1052 1052 1053 1053 **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. 1054 1054 ... ... @@ -1056,48 +1056,47 @@ 1056 1056 1057 1057 Enumerations: 1058 1058 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. 1036 +|**Value**|**Documentation** 1037 +|String|A string datatype corresponding to W3C XML Schema's xs:string datatype. 1038 +|Alpha|A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z. 1039 +|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. 1040 +|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. 1041 +|BigInteger|An integer datatype corresponding to W3C XML Schema's xs:integer datatype. 1042 +|Integer|An integer datatype corresponding to W3C XML Schema's xs:int datatype. 1043 +|Long|A numeric datatype corresponding to W3C XML Schema's xs:long datatype. 1044 +|Short|A numeric datatype corresponding to W3C XML Schema's xs:short datatype. 1045 +|Decimal|A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype. 1046 +|Float|A numeric datatype corresponding to W3C XML Schema's xs:float datatype. 1047 +|Double|A numeric datatype corresponding to W3C XML Schema's xs:double datatype. 1048 +|Boolean|A datatype corresponding to W3C XML Schema's xs:boolean datatype. 1049 +|URI|A datatype corresponding to W3C XML Schema's xs:anyURI datatype. 1050 +|Count|A simple incrementing Integer type. The isSequence facet must be set to true, and the interval facet must be set to "1". 1051 +|InclusiveValueRange|This value indicates that the startValue and endValue attributes provide the inclusive boundaries of a numeric range of type xs:decimal. 1052 +|ExclusiveValueRange|This value indicates that the startValue and endValue attributes provide the exclusive boundaries of a numeric range, of type xs:decimal. 1053 +|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. 1054 +|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. 1055 +|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. 1056 +|BasicTimePeriod|BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time. 1057 +|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. 1058 +|GregorianYear|A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601. 1059 +|GregorianYearMonth|A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601. 1060 +|GregorianDay|A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601. 1061 +|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. 1062 +|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. 1063 +|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. 1064 +|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. 1065 +|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. 1066 +|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. 1067 +|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. 1068 +|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. 1069 +|DateTime|A time datatype corresponding to W3C XML Schema's xs:dateTime datatype. 1070 +|TimeRange|TimeRange defines a time period by providing a distinct start (date or date time) and a duration. 1071 +|Month|A time datatype corresponding to W3C XML Schema's xs:gMonth datatype. 1072 +|MonthDay|A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype. 1073 +|Day|A time datatype corresponding to W3C XML Schema's xs:gDay datatype. 1074 +|Time|A time datatype corresponding to W3C XML Schema's xs:time datatype. 1075 +|Duration|A time datatype corresponding to W3C XML Schema's xs:duration datatype. 1076 +|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. 1101 1101 1102 1102 **TimeDataType:** TimeDataType restricts SimpleDataType to specify the allowable data types for representing a time value. 1103 1103 ... ... @@ -1105,25 +1105,24 @@ 1105 1105 1106 1106 Enumerations: 1107 1107 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. 1084 +|**Value**|**Documentation** 1085 +|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. 1086 +|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. 1087 +|BasicTimePeriod|BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time. 1088 +|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. 1089 +|GregorianYear|A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601. 1090 +|GregorianYearMonth|A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601. 1091 +|GregorianDay|A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601. 1092 +|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. 1093 +|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. 1094 +|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. 1095 +|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. 1096 +|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. 1097 +|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. 1098 +|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. 1099 +|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. 1100 +|DateTime|A time datatype corresponding to W3C XML Schema's xs:dateTime datatype. 1101 +|TimeRange|TimeRange defines a time period by providing a distinct start (date or date time) and a duration. 1127 1127 1128 1128 **UrnPrefixPart:** This is validates the first part of the URN (urn:sdmx.org.infomodel.<package>.<class=). It is intended to be further restricted. 1129 1129 ... ... @@ -1158,19 +1158,57 @@ 1158 1158 **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. 1159 1159 1160 1160 Derived by restriction of UrnMaintainableIdPart. 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] ~*~*)?\).1136 +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]* 1162 1162 ))) 1163 1163 1139 +*)?\). 1140 + 1164 1164 **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. 1165 1165 1166 1166 Derived by restriction of UrnMaintainableIdPart. 1167 -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]*~)~)~)*)?\).*.+\ 0|[1-9]\d*)\+?)(\.((0|[1-9]\d*{2}\).*.+\0|[1-9]\d*))(\.((0|[1-9]\d*)\+?))(\.((0|[1-9]\d*\).*.+\0|[1-9]\d*)\+?)(\.((0|[1-9]\d*(\.((0|[1-9]\d*)\+?))\).1144 +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]*~)~)~)*)?\).*.+\ 1168 1168 1146 +((( 1147 +0|[1-9]\d*)\+?)(\.((0|[1-9]\d* 1148 +))) 1149 + 1150 +{2}\).*.+\ 1151 + 1152 +((( 1153 +0|[1-9]\d*))(\.((0|[1-9]\d*)\+?))(\.((0|[1-9]\d* 1154 +))) 1155 + 1156 +\).*.+\ 1157 + 1158 +((( 1159 +0|[1-9]\d*)\+?)(\.((0|[1-9]\d* 1160 +))) 1161 + 1162 +(\.((0|[1-9]\d*)\+?))\). 1163 + 1169 1169 **WildcardUrnVersionPart:** This refines the prefix, classes, agency, and maintainable id patterns to validate the version number part of a wildcarded 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. 1170 1170 1171 1171 Derived by restriction of WildcardUrnMaintainableIdPart. 1172 -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]*~)~)~)*)?\).*.+\ 0|[1-9]\d*)\+?)(\.((0|[1-9]\d*{2}\).*.+\0|[1-9]\d*))(\.((0|[1-9]\d*)\+?))(\.((0|[1-9]\d*\).*.+\0|[1-9]\d*)\+?)(\.((0|[1-9]\d*(\.((0|[1-9]\d*)\+?))\).*.+\(\*\).1167 +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]*~)~)~)*)?\).*.+\ 1173 1173 1169 +((( 1170 +0|[1-9]\d*)\+?)(\.((0|[1-9]\d* 1171 +))) 1172 + 1173 +{2}\).*.+\ 1174 + 1175 +((( 1176 +0|[1-9]\d*))(\.((0|[1-9]\d*)\+?))(\.((0|[1-9]\d* 1177 +))) 1178 + 1179 +\).*.+\ 1180 + 1181 +((( 1182 +0|[1-9]\d*)\+?)(\.((0|[1-9]\d* 1183 +))) 1184 + 1185 +(\.((0|[1-9]\d*)\+?))\).*.+\(\*\). 1186 + 1174 1174 **UrnType:** The completes the refinement of the prefix, classes, agency, maintainable id, and version number patterns to validate the last, and optional, nested component part of the URN (e.g. (<version_number>)<containerobject-id>.<object-id>\*). The nested patterns provide a complete validation of the URN pattern. 1175 1175 1176 1176 Derived by restriction of UrnVersionPart. ... ... @@ -1586,17 +1586,17 @@ 1586 1586 Derived by restriction of OrganisationReferenceType. 1587 1587 Regular Expression Pattern: . +\.base\.DataConsumer=.+:DATA_CONSUMERS\(.+\).+ 1588 1588 1589 -**DataConsumerSchemeReferenceType:** A reference type for a [[data consumer scheme>>doc:sdmx:Glossary.Data consumer scheme.WebHome]].1602 +**DataConsumerSchemeReferenceType:** A reference type for a data consumer scheme. 1590 1590 1591 1591 Derived by restriction of OrganisationSchemeReferenceType. 1592 1592 Regular Expression Pattern: . +\.base\.DataConsumerScheme=.+:DATA_CONSUMERS\(.+\) 1593 1593 1594 -**DataProviderReferenceType:** A reference type for a [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]].1607 +**DataProviderReferenceType:** A reference type for a data provider. 1595 1595 1596 1596 Derived by restriction of OrganisationReferenceType. 1597 1597 Regular Expression Pattern: . +\.base\.DataProvider=.+:DATA_PROVIDERS\(.+\).+ 1598 1598 1599 -**DataProviderSchemeReferenceType:** A reference type for a [[data provider scheme>>doc:sdmx:Glossary.Data provider scheme.WebHome]].1612 +**DataProviderSchemeReferenceType:** A reference type for a data provider scheme. 1600 1600 1601 1601 Derived by restriction of OrganisationSchemeReferenceType. 1602 1602 Regular Expression Pattern: . +\.base\.DataProviderScheme=.+:DATA_PROVIDERS\(.+\) ... ... @@ -1616,7 +1616,7 @@ 1616 1616 Derived by restriction of OrganisationReferenceType. 1617 1617 Regular Expression Pattern: . +\.base\.OrganisationUnit=.+ 1618 1618 1619 -**OrganisationUnitSchemeReferenceType:** A reference type for an [[organisation unit scheme>>doc:sdmx:Glossary.Organisation unit scheme.WebHome]].1632 +**OrganisationUnitSchemeReferenceType:** A reference type for an organisation unit scheme. 1620 1620 1621 1621 Derived by restriction of OrganisationSchemeReferenceType. 1622 1622 Regular Expression Pattern: . +\.base\.OrganisationUnitScheme=.+ ... ... @@ -1626,7 +1626,7 @@ 1626 1626 Derived by restriction of MaintainableUrnReferenceType. 1627 1627 Regular Expression Pattern: . +\.categoryscheme\.Categorisation=.+ 1628 1628 1629 -**CategoryReferenceType:** A reference type for a [[category>>doc:sdmx:Glossary.Category.WebHome]].1642 +**CategoryReferenceType:** A reference type for a category. 1630 1630 1631 1631 Derived by restriction of UrnReferenceType. 1632 1632 Regular Expression Pattern: . +\.categoryscheme\.Category=.+ ... ... @@ -1636,7 +1636,7 @@ 1636 1636 Derived by restriction of MaintainableUrnReferenceType. 1637 1637 Regular Expression Pattern: . +\.categoryscheme\.CategoryScheme=.+ 1638 1638 1639 -**ReportingCategoryReferenceType:** A reference type for a reporting [[category>>doc:sdmx:Glossary.Category.WebHome]].1652 +**ReportingCategoryReferenceType:** A reference type for a reporting category. 1640 1640 1641 1641 Derived by restriction of UrnReferenceType. 1642 1642 Regular Expression Pattern: . +\.categoryscheme\.ReportingCategory=.+ ... ... @@ -1646,32 +1646,32 @@ 1646 1646 Derived by restriction of MaintainableUrnReferenceType. 1647 1647 Regular Expression Pattern: . +\.categoryscheme\.ReportingTaxonomy=.+ 1648 1648 1649 -**CodeReferenceType:** A reference type for a [[code>>doc:sdmx:Glossary.Code.WebHome]].1662 +**CodeReferenceType:** A reference type for a code. 1650 1650 1651 1651 Derived by restriction of ComponentUrnReferenceType. 1652 1652 Regular Expression Pattern: . +\.codelist\.Code=.+ 1653 1653 1654 -**CodelistReferenceType:** A reference type for a [[codelist>>doc:sdmx:Glossary.Code list.WebHome]].1667 +**CodelistReferenceType:** A reference type for a codelist. 1655 1655 1656 1656 Derived by restriction of AnyCodelistReferenceType. 1657 1657 Regular Expression Pattern: . +\.codelist\.Codelist=.+ 1658 1658 1659 -**HierarchicalCodeReferenceType:** A reference type for a [[hierarchical code>>doc:sdmx:Glossary.Hierarchical code.WebHome]].1672 +**HierarchicalCodeReferenceType:** A reference type for a hierarchical code. 1660 1660 1661 1661 Derived by restriction of UrnReferenceType. 1662 1662 Regular Expression Pattern: . +\.codelist\.HierarchicalCode=.+ 1663 1663 1664 -**HierarchyReferenceType:** A reference type for a [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]].1677 +**HierarchyReferenceType:** A reference type for a hierarchy. 1665 1665 1666 1666 Derived by restriction of MaintainableUrnReferenceType. 1667 1667 Regular Expression Pattern: . +\.codelist\.Hierarchy=.+ 1668 1668 1669 -**HierarchyAssociationReferenceType:** A reference type for a [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]association.1682 +**HierarchyAssociationReferenceType:** A reference type for a hierarchy association. 1670 1670 1671 1671 Derived by restriction of MaintainableUrnReferenceType. 1672 1672 Regular Expression Pattern: . +\.codelist\.HierarchyAssociation=.+ 1673 1673 1674 -**LevelReferenceType:** A reference type for a (% style="color:#e74c3c" %)level(%%).1687 +**LevelReferenceType:** A reference type for a level. 1675 1675 1676 1676 Derived by restriction of ComponentUrnReferenceType. 1677 1677 Regular Expression Pattern: . +\.codelist\.Level=.+ ... ... @@ -1681,27 +1681,27 @@ 1681 1681 Derived by restriction of AnyCodelistReferenceType. 1682 1682 Regular Expression Pattern: . +\.codelist\.ValueList=.+ 1683 1683 1684 -**ConceptReferenceType:** A reference type for a (% style="color:#e74c3c" %)concept(%%).1697 +**ConceptReferenceType:** A reference type for a concept. 1685 1685 1686 1686 Derived by restriction of ComponentUrnReferenceType. 1687 1687 Regular Expression Pattern: . +\.conceptscheme\.Concept=.+ 1688 1688 1689 -**ConceptSchemeReferenceType:** A reference type for a [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]].1702 +**ConceptSchemeReferenceType:** A reference type for a concept scheme. 1690 1690 1691 1691 Derived by restriction of MaintainableUrnReferenceType. 1692 1692 Regular Expression Pattern: . +\.conceptscheme\.ConceptScheme=.+ 1693 1693 1694 -**AttributeDescriptorReferenceType:** A reference type for an [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]]descriptor.1707 +**AttributeDescriptorReferenceType:** A reference type for an attribute descriptor. 1695 1695 1696 1696 Derived by restriction of ComponentUrnReferenceType. 1697 1697 Regular Expression Pattern: . +\.datastructure\.AttributeDescriptor=.+ 1698 1698 1699 -**DataAttributeReferenceType:** A reference type for a data [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]].1712 +**DataAttributeReferenceType:** A reference type for a data attribute. 1700 1700 1701 1701 Derived by restriction of ComponentUrnReferenceType. 1702 1702 Regular Expression Pattern: . +\.datastructure\.DataAttribute=.+ 1703 1703 1704 -**DataflowReferenceType:** A reference type for a [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]].1717 +**DataflowReferenceType:** A reference type for a dataflow. 1705 1705 1706 1706 Derived by restriction of StructureUsageReferenceType. 1707 1707 Regular Expression Pattern: . +\.datastructure\.Dataflow=.+ ... ... @@ -1711,42 +1711,42 @@ 1711 1711 Derived by restriction of StructureReferenceType. 1712 1712 Regular Expression Pattern: . +\.datastructure\.DataStructure=.+ 1713 1713 1714 -**DimensionReferenceType:** A reference type for a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]].1727 +**DimensionReferenceType:** A reference type for a dimension. 1715 1715 1716 1716 Derived by restriction of ComponentUrnReferenceType. 1717 1717 Regular Expression Pattern: . +\.datastructure\.Dimension=.+ 1718 1718 1719 -**DimensionDescriptorReferenceType:** A reference type for a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]descriptor.1732 +**DimensionDescriptorReferenceType:** A reference type for a dimension descriptor. 1720 1720 1721 1721 Derived by restriction of ComponentUrnReferenceType. 1722 1722 Regular Expression Pattern: . +\.datastructure\.DimensionDescriptor=.+ 1723 1723 1724 -**GroupDimensionDescriptorReferenceType:** A reference type for a group [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]descriptor.1737 +**GroupDimensionDescriptorReferenceType:** A reference type for a group dimension descriptor. 1725 1725 1726 1726 Derived by restriction of ComponentUrnReferenceType. 1727 1727 Regular Expression Pattern: . +\.datastructure\.GroupDimensionDescriptor=.+ 1728 1728 1729 -**MeasureReferenceType:** A reference type for a [[measure>>doc:sdmx:Glossary.Measure.WebHome]].1742 +**MeasureReferenceType:** A reference type for a measure. 1730 1730 1731 1731 Derived by restriction of ComponentUrnReferenceType. 1732 1732 Regular Expression Pattern: . +\.datastructure\.Measure=.+ 1733 1733 1734 -**MeasureDescriptorReferenceType:** A reference type for a [[measure>>doc:sdmx:Glossary.Measure.WebHome]]descriptor.1747 +**MeasureDescriptorReferenceType:** A reference type for a measure descriptor. 1735 1735 1736 1736 Derived by restriction of ComponentUrnReferenceType. 1737 1737 Regular Expression Pattern: . +\.datastructure\.MeasureDescriptor=.+ 1738 1738 1739 -**TimeDimensionReferenceType:** A reference type for a time [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]].1752 +**TimeDimensionReferenceType:** A reference type for a time dimension. 1740 1740 1741 1741 Derived by restriction of ComponentUrnReferenceType. 1742 1742 Regular Expression Pattern: . +\.datastructure\.TimeDimension=.+ 1743 1743 1744 -**MetadataAttributeReferenceType:** A reference type for a metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]].1757 +**MetadataAttributeReferenceType:** A reference type for a metadata attribute. 1745 1745 1746 1746 Derived by restriction of UrnReferenceType. 1747 1747 Regular Expression Pattern: . +\.metadatastructure\.MetadataAttribute=.+ 1748 1748 1749 -**MetadataflowReferenceType:** A reference type for a [[metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]].1762 +**MetadataflowReferenceType:** A reference type for a metadataflow. 1750 1750 1751 1751 Derived by restriction of StructureUsageReferenceType. 1752 1752 Regular Expression Pattern: . +\.metadatastructure\.Metadataflow=.+ ... ... @@ -1776,42 +1776,42 @@ 1776 1776 Derived by restriction of UrnReferenceType. 1777 1777 Regular Expression Pattern: . +\.process\.Transition=.+ 1778 1778 1779 -**DataConstraintReferenceType:** A reference type for a data (% style="color:#e74c3c" %)constraint(%%).1792 +**DataConstraintReferenceType:** A reference type for a data constraint. 1780 1780 1781 1781 Derived by restriction of ConstraintReferenceType. 1782 1782 Regular Expression Pattern: . +\.registry\.DataConstraint=.+ 1783 1783 1784 -**MetadataConstraintReferenceType:** A reference type for a metadata (% style="color:#e74c3c" %)constraint(%%).1797 +**MetadataConstraintReferenceType:** A reference type for a metadata constraint. 1785 1785 1786 1786 Derived by restriction of ConstraintReferenceType. 1787 1787 Regular Expression Pattern: . +\.registry\.MetadataConstraint=.+ 1788 1788 1789 -**MetadataProvisionAgreementReferenceType:** A reference type for a metadata [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]].1802 +**MetadataProvisionAgreementReferenceType:** A reference type for a metadata provision agreement. 1790 1790 1791 1791 Derived by restriction of MaintainableUrnReferenceType. 1792 1792 Regular Expression Pattern: . +\.registry\.MetadataProvisionAgreement=.+ 1793 1793 1794 -**ProvisionAgreementReferenceType:** A reference type for a [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]].1807 +**ProvisionAgreementReferenceType:** A reference type for a provision agreement. 1795 1795 1796 1796 Derived by restriction of MaintainableUrnReferenceType. 1797 1797 Regular Expression Pattern: . +\.registry\.ProvisionAgreement=.+ 1798 1798 1799 -**CategorySchemeMapReferenceType:** A reference type for a [[category scheme>>doc:sdmx:Glossary.Categoryscheme.WebHome]] (% style="color:#e74c3c" %)map(%%).1812 +**CategorySchemeMapReferenceType:** A reference type for a category scheme map. 1800 1800 1801 1801 Derived by restriction of MaintainableUrnReferenceType. 1802 1802 Regular Expression Pattern: . +\.structuremapping\.CategorySchemeMap=.+ 1803 1803 1804 -**ConceptSchemeMapReferenceType:** A reference type for a [[concept scheme>>doc:sdmx:Glossary.Conceptscheme.WebHome]] (% style="color:#e74c3c" %)map(%%).1817 +**ConceptSchemeMapReferenceType:** A reference type for a concept scheme map. 1805 1805 1806 1806 Derived by restriction of MaintainableUrnReferenceType. 1807 1807 Regular Expression Pattern: . +\.structuremapping\.ConceptSchemeMap=.+ 1808 1808 1809 -**DatePatternMapReferenceType:** A reference type for a date pattern (% style="color:#e74c3c" %)map(%%).1822 +**DatePatternMapReferenceType:** A reference type for a date pattern map. 1810 1810 1811 1811 Derived by restriction of ComponentUrnReferenceType. 1812 1812 Regular Expression Pattern: . +\.structuremapping\.DatePatternMap=.+ 1813 1813 1814 -**EpochMapReferenceType:** A reference type for an epoch (% style="color:#e74c3c" %)map(%%).1827 +**EpochMapReferenceType:** A reference type for an epoch map. 1815 1815 1816 1816 Derived by restriction of ComponentUrnReferenceType. 1817 1817 Regular Expression Pattern: . +\.structuremapping\.EpochMap=.+ ... ... @@ -1821,22 +1821,22 @@ 1821 1821 Derived by restriction of ComponentUrnReferenceType. 1822 1822 Regular Expression Pattern: . +\.structuremapping\.FrequencyFormatMapping=.+ 1823 1823 1824 -**OrganisationSchemeMapReferenceType:** A reference type for a organisation scheme (% style="color:#e74c3c" %)map(%%).1837 +**OrganisationSchemeMapReferenceType:** A reference type for a organisation scheme map. 1825 1825 1826 1826 Derived by restriction of MaintainableUrnReferenceType. 1827 1827 Regular Expression Pattern: . +\.structuremapping\.OrganisationSchemeMap=.+ 1828 1828 1829 -**ReportingTaxonomyMapReferenceType:** A reference type for a reporting taxonomy (% style="color:#e74c3c" %)map(%%).1842 +**ReportingTaxonomyMapReferenceType:** A reference type for a reporting taxonomy map. 1830 1830 1831 1831 Derived by restriction of MaintainableUrnReferenceType. 1832 1832 Regular Expression Pattern: . +\.structuremapping\.ReportingTaxonomyMap=.+ 1833 1833 1834 -**RepresentationMapReferenceType:** A reference type for a [[representation>>doc:sdmx:Glossary.Representation.WebHome]](% style="color:#e74c3c" %)map(%%).1847 +**RepresentationMapReferenceType:** A reference type for a representation map. 1835 1835 1836 1836 Derived by restriction of MaintainableUrnReferenceType. 1837 1837 Regular Expression Pattern: . +\.structuremapping\.RepresentationMap=.+ 1838 1838 1839 -**StructureMapReferenceType:** A reference type for a structure (% style="color:#e74c3c" %)map(%%).1852 +**StructureMapReferenceType:** A reference type for a structure map. 1840 1840 1841 1841 Derived by restriction of MaintainableUrnReferenceType. 1842 1842 Regular Expression Pattern: . +\.structuremapping\.StructureMap=.+ ... ... @@ -1891,86 +1891,84 @@ 1891 1891 Derived by restriction of MaintainableUrnReferenceType. 1892 1892 Regular Expression Pattern: . +\.transformation\.UserDefinedOperatorScheme=.+ 1893 1893 1894 -**VtlMappingReferenceType:** A reference type for a [[VTL>>doc:sdmx:Glossary.Validationand transformation language.WebHome]] mapping.1907 +**VtlMappingReferenceType:** A reference type for a VTL mapping. 1895 1895 1896 1896 Derived by restriction of ComponentUrnReferenceType. 1897 1897 Regular Expression Pattern: . +\.transformation\.VtlCodelistMapping=.+.+\.transformation\.VtlConceptMapping=.+.+\.transformation\.VtlDataflowMapping=.+ 1898 1898 1899 -**VtlMappingSchemeReferenceType:** A reference type for a [[VTL>>doc:sdmx:Glossary.Validationand transformation language.WebHome]] mapping scheme.1912 +**VtlMappingSchemeReferenceType:** A reference type for a VTL mapping scheme. 1900 1900 1901 1901 Derived by restriction of MaintainableUrnReferenceType. 1902 1902 Regular Expression Pattern: . +\.transformation\.VtlMappingScheme=.+ 1903 1903 1904 -**VersionReferenceType:** VersionReferenceType defines the structure of (% style="color:#e74c3c" %)version(%%)number in a reference. When semantic versioning is used, the major, minor, or patch(% style="color:#e74c3c" %)version(%%)parts can be wildcarded using "+" as an extension. For example, 2+.3.1 means the currently latest available(% style="color:#e74c3c" %)version(%%)>= 2.3.1 (even if not backwards compatible). Note that wildcarded semantic(% style="color:#e74c3c" %)version(%%)references cannot be combined with(% style="color:#e74c3c" %)version(%%)extended reference (e.g. 2.3+.1-draft is not permissable).(% style="color:#e74c3c" %)Version(%%)-extended (e.g. 1.3.1-draft) and legacy(% style="color:#e74c3c" %)version(%%)numbers (e.g. 1 or 1.0) are also supported.1917 +**VersionReferenceType:** VersionReferenceType defines the structure of version number in a reference. When semantic versioning is used, the major, minor, or patch version parts can be wildcarded using "+" as an extension. For example, 2+.3.1 means the currently latest available version >= 2.3.1 (even if not backwards compatible). Note that wildcarded semantic version references cannot be combined with version extended reference (e.g. 2.3+.1-draft is not permissable). Version-extended (e.g. 1.3.1-draft) and legacy version numbers (e.g. 1 or 1.0) are also supported. 1905 1905 1906 1906 Union of: 1907 1907 1908 1908 LegacyVersionNumberType, SemanticVersionNumberType, SemanticVersionReferenceType. 1909 1909 1910 -**SemanticVersionReferenceType:** SemanticVersionReferenceType is a simple type for referencing semantic (% style="color:#e74c3c" %)version(%%)numbers. It allows for the wildcarding of only one the major, minor, or patch(% style="color:#e74c3c" %)version(%%)parts using "+".1923 +**SemanticVersionReferenceType:** SemanticVersionReferenceType is a simple type for referencing semantic version numbers. It allows for the wildcarding of only one the major, minor, or patch version parts using "+". 1911 1911 1912 1912 Derived by restriction of xs:string. 1913 - 1914 1914 Regular Expression Pattern: ((0|[1-9]\d*)\+?)(\.((0|[1-9]\d*~)~)~){2}((0|[1-9]\d*))(\.((0|[1-9]\d*)\+?))(\.((0|[1-9]\d*~)~)~)((0|[1-9]\d*)\+?)(\.((0|[1-9]\d*~)~)~)(\.((0|[1-9]\d*)\+?)) 1915 1915 1916 -**WildcardVersionType:** WildcardVersionType combines the VersionType and WildcardType to allow a reference to either a specific (% style="color:#e74c3c" %)version(%%)of an object, or to wildcard the(% style="color:#e74c3c" %)version(%%)in the reference by specifying the '*' value.1928 +**WildcardVersionType:** WildcardVersionType combines the VersionType and WildcardType to allow a reference to either a specific version of an object, or to wildcard the version in the reference by specifying the '*' value. 1917 1917 1918 1918 Union of: 1919 1919 1920 1920 LegacyVersionNumberType, SemanticVersionNumberType, SemanticVersionReferenceType, WildcardType. 1921 1921 1922 -**WildcardType:** WildcardType is a single value [[code list>>doc:sdmx:Glossary.Code list.WebHome]], used to include the '*' character - indicating that the identification[[component>>doc:sdmx:Glossary.Component.WebHome]]is wildcarded.1934 +**WildcardType:** WildcardType is a single value code list, used to include the '*' character - indicating that the identification component is wildcarded. 1923 1923 1924 1924 Derived by restriction of xs:string. 1925 1925 1926 1926 Enumerations: 1927 1927 1928 -(% style="width:1011.29px" %) 1929 -|**Value**|(% style="width:771px" %)**Documentation** 1930 -|\*|(% style="width:771px" %)Indicates that any value of the identifier [[component>>doc:sdmx:Glossary.Component.WebHome]] is allowed. 1940 +|**Value**|**Documentation** 1931 1931 1932 -* *NestedIDType:** NestedIDTypeis the least restrictive form ofan identifier usedthroughout all [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]]messages.It allowsforahierarchicalidentifier,with eachportionseparated by the '.' character. For the identifierportions,valid characters includeA-Z, a-z, @, 0-9, \_, -, $.1942 +|\*|Indicates that any value of the identifier component is allowed.| 1933 1933 1944 +**NestedIDType:** NestedIDType is the least restrictive form of an identifier used throughout all SDMX-ML messages. It allows for a hierarchical identifier, with each portion separated by the '.' character. For the identifier portions, valid characters include A-Z, a-z, @, 0-9, \_, -, $. 1945 + 1934 1934 Derived by restriction of xs:string. 1935 1935 Regular Expression Pattern: [A-Za-z0-9_@$\-]+(\.[A-Za-z0-9_@$\-]+) 1936 1936 1937 -**TwoLevelIDType:** TwoLevelIDType defines an identifier with exactly two (% style="color:#e74c3c" %)levels(%%).1949 +**TwoLevelIDType:** TwoLevelIDType defines an identifier with exactly two levels. 1938 1938 1939 1939 Derived by restriction of NestedIDType. 1940 1940 Regular Expression Pattern: [A-Za-z0-9_@$\-]+\.[A-Za-z0-9_@$\-]+ 1941 1941 1942 -**IDType:** IDType provides a type which is used for restricting the characters in [[codes>>doc:sdmx:Glossary.Code.WebHome]]and IDs throughout all[[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]]messages. Valid characters include A-Z, a-z, @, 0-9, \_, -, $.1954 +**IDType:** IDType provides a type which is used for restricting the characters in codes and IDs throughout all SDMX-ML messages. Valid characters include A-Z, a-z, @, 0-9, \_, -, $. 1943 1943 1944 1944 Derived by restriction of NestedIDType. 1945 1945 Regular Expression Pattern: [A-Za-z0-9_@$\-]+ 1946 1946 1947 -**NCNameIDType:** NCNameIDType restricts the IDType, so that the id may be used to generate valid XML [[components>>doc:sdmx:Glossary.Component.WebHome]].IDs created from this type conform to the W3C XML Schema NCNAME type, and therefore can be used as element or[[attribute>>doc:sdmx:Glossary.Attribute.WebHome]]names.1959 +**NCNameIDType:** NCNameIDType restricts the IDType, so that the id may be used to generate valid XML components. IDs created from this type conform to the W3C XML Schema NCNAME type, and therefore can be used as element or attribute names. 1948 1948 1949 1949 Derived by restriction of IDType. 1950 1950 Regular Expression Pattern: [A-Za-z][A-Za-z0-9_\-] 1951 1951 1952 -**NestedNCNameIDType:** NestedNCNameIDType restricts the NestedIDType, so that the id may be used to generate valid XML [[components>>doc:sdmx:Glossary.Component.WebHome]].IDs created from this type conform to the W3C XML Schema NCNAME type, and therefore can be used as element or[[attribute>>doc:sdmx:Glossary.Attribute.WebHome]]names.1964 +**NestedNCNameIDType:** NestedNCNameIDType restricts the NestedIDType, so that the id may be used to generate valid XML components. IDs created from this type conform to the W3C XML Schema NCNAME type, and therefore can be used as element or attribute names. 1953 1953 1954 1954 Derived by restriction of NestedIDType. 1955 1955 Regular Expression Pattern: [A-Za-z][A-Za-z0-9_\-]*(\.[A-Za-z][A-Za-z0-9_\-]*) 1956 1956 1957 -**SingleNCNameIDType:** SingleNCNameIDType restricts the NestedNCNameIDType to allow only one (% style="color:#e74c3c" %)level(%%). Note that this is the same pattern as the NCNameIDType, but can be used when the base type to be restricted is a nested NCNameIDType (where as the NCNameIDType could only restrict the IDType).1969 +**SingleNCNameIDType:** SingleNCNameIDType restricts the NestedNCNameIDType to allow only one level. Note that this is the same pattern as the NCNameIDType, but can be used when the base type to be restricted is a nested NCNameIDType (where as the NCNameIDType could only restrict the IDType). 1958 1958 1959 1959 Derived by restriction of NestedNCNameIDType. 1960 1960 Regular Expression Pattern: [A-Za-z][A-Za-z0-9_\-] 1961 1961 1962 -**VersionType:** VersionType is used to communicate (% style="color:#e74c3c" %)version(%%)information. Semantic versioning, based on 3 or 4(% style="color:#e74c3c" %)version(%%)parts (major.minor.patch[-extension]) is supported. The legency[[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] (% style="color:#e74c3c" %)version(%%)format is also support.1974 +**VersionType:** VersionType is used to communicate version information. Semantic versioning, based on 3 or 4 version parts (major.minor.patch[-extension]) is supported. The legency SDMX version format is also support. 1963 1963 1964 1964 Union of: 1965 1965 LegacyVersionNumberType, SemanticVersionNumberType. 1966 1966 1967 -**SemanticVersionNumberType:** SemanticVersionNumberType is a simple type for validating semantic (% style="color:#e74c3c" %)version(%%)in the format (major.minor.patch[-extension]).1979 +**SemanticVersionNumberType:** SemanticVersionNumberType is a simple type for validating semantic version in the format (major.minor.patch[-extension]). 1968 1968 1969 1969 Derived by restriction of xs:string. 1970 1970 Regular Expression Pattern: (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]*~)~)~)*)? 1971 1971 1972 -**LegacyVersionNumberType:** LegacyVersionNumberType describes the (% style="color:#e74c3c" %)version(%%)number format previously supported in[[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]].The format is restricted to allow for simple incrementing and sorting of(% style="color:#e74c3c" %)version(%%)number. The(% style="color:#e74c3c" %)version(%%)consists of a set of maximum 2 numeric[[components>>doc:sdmx:Glossary.Component.WebHome]], separated by the '.' character. When processing(% style="color:#e74c3c" %)version(%%), each numeric[[component>>doc:sdmx:Glossary.Component.WebHome]](the number preceding and following any '.' character) should be parsed as an integer. Thus, a(% style="color:#e74c3c" %)version(%%)of 1.3 and 1.03 would be equivalent, as both the '3'[[component>>doc:sdmx:Glossary.Component.WebHome]]and the '03'[[component>>doc:sdmx:Glossary.Component.WebHome]]would parse to an integer value of 3.1984 +**LegacyVersionNumberType:** LegacyVersionNumberType describes the version number format previously supported in SDMX. The format is restricted to allow for simple incrementing and sorting of version number. The version consists of a set of maximum 2 numeric components, separated by the '.' character. When processing version, each numeric component (the number preceding and following any '.' character) should be parsed as an integer. Thus, a version of 1.3 and 1.03 would be equivalent, as both the '3' component and the '03' component would parse to an integer value of 3. 1973 1973 1974 1974 Derived by restriction of xs:string. 1975 - 1976 1976 Regular Expression Pattern: (0|[1-9]\d*)(\.(0|[1-9]\d*))?