Changes for page Part II.Common Namespace

Last modified by Elena Yasinovskaya on 2025/09/10 11:19

From version 6.5
edited by Helena K.
on 2025/07/03 12:23
Change comment: There is no comment for this version
To version 6.12
edited by Helena K.
on 2025/07/03 12:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -397,23 +397,25 @@
397 397  
398 398  Attribute Documentation:
399 399  
400 -|**Name**|**Type**|**Documentation**
401 -|id|IDType|The id is the identifier for the object.
402 -|urn|MaintainableUrnType|The urn attribute holds a valid SDMX Registry URN (see SDMX Registry Specification for details).
403 -|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.
404 -|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.
405 -|validFrom|xs:dateTime|The validFrom attribute provides the inclusive start date for providing supplemental validity information about the version.
406 -|validTo|xs:dateTime|The validTo attribute provides the inclusive end date for providing supplemental validity information about the version.
400 +(% style="width:1004.29px" %)
401 +|**Name**|**Type**|(% style="width:625px" %)**Documentation**
402 +|id|IDType|(% style="width:625px" %)The id is the identifier for the object.
403 +|urn|MaintainableUrnType|(% style="width:625px" %)The urn attribute holds a valid SDMX Registry URN (see SDMX Registry Specification for details).
404 +|uri|xs:anyURI|(% style="width:625px" %)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.
405 +|version|VersionType|(% style="width:625px" %)This version attribute holds a version number (see common:VersionType definition for details). If not supplied, artefact is considered to be un-versioned.
406 +|validFrom|xs:dateTime|(% style="width:625px" %)The validFrom attribute provides the inclusive start date for providing supplemental validity information about the version.
407 +|validTo|xs:dateTime|(% style="width:625px" %)The validTo attribute provides the inclusive end date for providing supplemental validity information about the version.
407 407  
408 408  Element Documentation:
409 409  
410 -|**Name**|**Type**|**Documentation**
411 -|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.
412 -|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.
413 -|Name|TextType|Name provides for a human-readable name for the object. This may be provided in multiple, parallel language-equivalent forms.
414 -|Description|TextType|Description provides for a longer human-readable description of the object. This may be provided in multiple, parallel language-equivalent forms.
411 +(% style="width:1005.29px" %)
412 +|**Name**|**Type**|(% style="width:728px" %)**Documentation**
413 +|Annotations|AnnotationsType|(% style="width:728px" %)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.
414 +|Link|LinkType|(% style="width:728px" %)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.
415 +|Name|TextType|(% style="width:728px" %)Name provides for a human-readable name for the object. This may be provided in multiple, parallel language-equivalent forms.
416 +|Description|TextType|(% style="width:728px" %)Description provides for a longer human-readable description of the object. This may be provided in multiple, parallel language-equivalent forms.
415 415  
416 -***MaintainableType*:** MaintainableType is an abstract base type for all maintainable objects.
418 +//**MaintainableType:**// MaintainableType is an abstract base type for all maintainable objects.
417 417  
418 418  Derivation:
419 419  
... ... @@ -432,26 +432,28 @@
432 432  
433 433  Attribute Documentation:
434 434  
435 -|**Name**|**Type**|**Documentation**
436 -|id|IDType|The id is the identifier for the object.
437 -|urn|MaintainableUrnType|The urn attribute holds a valid SDMX Registry URN (see SDMX Registry Specification for details).
438 -|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.
439 -|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.
440 -|validFrom|xs:dateTime|The validFrom attribute provides the inclusive start date for providing supplemental validity information about the version.
441 -|validTo|xs:dateTime|The validTo attribute provides the inclusive end date for providing supplemental validity information about the version.
442 -|agencyID|NestedNCNameIDType|The agencyID must be provided, and identifies the maintenance agency of the object.
443 -|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.
444 -|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.
445 -|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.
446 -|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’.
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’.
447 447  
448 448  Element Documentation:
449 449  
450 -|**Name**|**Type**|**Documentation**
451 -|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.
452 -|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.
453 -|Name|TextType|Name provides for a human-readable name for the object. This may be provided in multiple, parallel language-equivalent forms.
454 -|Description|TextType|Description provides for a longer human-readable description of the object. This may be provided in multiple, parallel language-equivalent forms.
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.
455 455  
456 456  **ReferencePeriodType:** Specifies the inclusive start and end times.
457 457  
... ... @@ -463,9 +463,10 @@
463 463  
464 464  Attribute Documentation:
465 465  
466 -|**Name**|**Type**|**Documentation**
467 -|startTime|xs:dateTime|The startTime attributes contains the inclusive start date for the reference period.
468 -|endTime|xs:dateTime|The endTime attributes contains the inclusive end date for the reference period.
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.
469 469  
470 470  **QueryableDataSourceType:** QueryableDataSourceType describes a data source which is accepts an standard SDMX Query message and responds appropriately.
471 471  
... ... @@ -477,16 +477,18 @@
477 477  
478 478  Attribute Documentation:
479 479  
480 -|**Name**|**Type**|**Documentation**
481 -|isRESTDatasource|xs:boolean|The isRESTDatasource attribute indicates, if true, that the queryable data source is accessible via the REST protocol.
482 -|isWebServiceDatasource|xs:boolean|The isWebServiceDatasource attribute indicates, if true, that the queryable data source is accessible via Web Services protocols.
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.
483 483  
484 484  Element Documentation:
485 485  
486 -|**Name**|**Type**|**Documentation**
487 -|DataURL|xs:anyURI|DataURL contains the URL of the data source.
488 -|WSDLURL|xs:anyURI|WSDLURL provides the location of a WSDL instance on the internet which describes the queryable data source.
489 -|WADLURL|xs:anyURI|WADLURL provides the location of a WADL instance on the internet which describes the REST protocol of the queryable data source.
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.
490 490  
491 491  **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.
492 492  
... ... @@ -494,12 +494,13 @@
494 494  xml:lang?
495 495  
496 496  Content:
497 -{text} x {any element with namespace of http://www.w3.org/1999/xhtml}
504 +{text} x {any element with namespace of http:~/~/www.w3.org/1999/xhtml}
498 498  
499 499  Attribute Documentation:
500 500  
501 -|**Name**|**Type**|**Documentation**
502 -|xml:lang (default: en)|xs:language
508 +(% style="width:1009.29px" %)
509 +|(% style="width:228px" %)**Name**|(% style="width:221px" %)**Type**|(% style="width:699px" %)**Documentation**
510 +|(% style="width:228px" %)xml:lang (default: en)|(% style="width:221px" %)xs:language
503 503  
504 504  ***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).
505 505  
... ... @@ -511,23 +511,25 @@
511 511  
512 512  Attribute Documentation:
513 513  
514 -|**Name**|**Type**|**Documentation**
515 -|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.
516 -|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located.
517 -|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.
518 -|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.
519 -|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.
520 -|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.
521 -|structureURL|xs:anyURI|The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.
522 +(% style="width:1003.29px" %)
523 +|**Name**|**Type**|(% style="width:598px" %)**Documentation**
524 +|structureID|xs:ID|(% style="width:598px" %)The structureID attribute uniquely identifies the structure for the purpose of referencing it from the payload. This is only used in structure specific formats. Although it is required, it is only useful when more than one data set is present in the message.
525 +|schemaURL|xs:anyURI|(% style="width:598px" %)The schemaURL attribute provides a location from which the structure specific schema can be located.
526 +|namespace|xs:anyURI|(% style="width:598px" %)The namespace attribute is used to provide the namespace for structure-specific formats. By communicating this information in the header, it is possible to generate the structure specific schema while processing the message.
527 +|dimensionAtObservation|ObservationDimensionType|(% style="width:598px" %)The dimensionAtObservation is used to reference the dimension at the observation level for data messages. This can also be given the explicit value of "AllDimensions" which denotes that the cross sectional data is in the flat format.
528 +|explicitMeasures|xs:boolean|(% style="width:598px" %)The explicitMeasures indicates whether explicit measures are used in the cross sectional format. This is only applicable for the measure dimension as the dimension at the observation level or the flat structure.
529 +|serviceURL|xs:anyURI|(% style="width:598px" %)The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface.
530 +|structureURL|xs:anyURI|(% style="width:598px" %)The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.
522 522  
523 523  Element Documentation:
524 524  
525 -|**Name**|**Type**|**Documentation**
526 -|ProvisionAgreement|ProvisionAgreementRe ferenceType|ProvisionAgreement references a provision agreement which the data or metadata is reported against.
527 -|StructureUsage|StructureUsageRefere nceType|StructureUsage references a flow which the data or metadata is reported against.
528 -|Structure|StructureReferenceTy pe|Structure references the structure which defines the structure of the data or metadata set.
534 +(% style="width:1005.29px" %)
535 +|(% style="width:188px" %)**Name**|(% style="width:287px" %)**Type**|(% style="width:527px" %)**Documentation**
536 +|(% style="width:188px" %)ProvisionAgreement|(% style="width:287px" %)ProvisionAgreementReferenceType|(% style="width:527px" %)ProvisionAgreement references a provision agreement which the data or metadata is reported against.
537 +|(% style="width:188px" %)StructureUsage|(% style="width:287px" %)StructureUsageReferenceType|(% style="width:527px" %)StructureUsage references a flow which the data or metadata is reported against.
538 +|(% style="width:188px" %)Structure|(% style="width:287px" %)StructureReferenceType|(% style="width:527px" %)Structure references the structure which defines the structure of the data or metadata set.
529 529  
530 -***DataStructureType*:** DataStructureType is an abstract base type the forms the basis for the structural information for a data set.
540 +//**DataStructureType:**// DataStructureType is an abstract base type the forms the basis for the structural information for a data set.
531 531  
532 532  Derivation:
533 533  
... ... @@ -542,21 +542,23 @@
542 542  
543 543  Attribute Documentation:
544 544  
545 -|**Name**|**Type**|**Documentation**
546 -|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.
547 -|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located.
548 -|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.
549 -|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.
550 -|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.
551 -|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.
552 -|structureURL|xs:anyURI|The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.
555 +(% style="width:1006.29px" %)
556 +|**Name**|**Type**|(% style="width:598px" %)**Documentation**
557 +|structureID|xs:ID|(% style="width:598px" %)The structureID attribute uniquely identifies the structure for the purpose of referencing it from the payload. This is only used in structure specific formats. Although it is required, it is only useful when more than one data set is present in the message.
558 +|schemaURL|xs:anyURI|(% style="width:598px" %)The schemaURL attribute provides a location from which the structure specific schema can be located.
559 +|namespace|xs:anyURI|(% style="width:598px" %)The namespace attribute is used to provide the namespace for structure-specific formats. By communicating this information in the header, it is possible to generate the structure specific schema while processing the message.
560 +|dimensionAtObservation|ObservationDimensionType|(% style="width:598px" %)The dimensionAtObservation is used to reference the dimension at the observation level for data messages. This can also be given the explicit value of "AllDimensions" which denotes that the cross sectional data is in the flat format.
561 +|explicitMeasures|xs:boolean|(% style="width:598px" %)The explicitMeasures indicates whether explicit measures are used in the cross sectional format. This is only applicable for the measure dimension as the dimension at the observation level or the flat structure.
562 +|serviceURL|xs:anyURI|(% style="width:598px" %)The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface.
563 +|structureURL|xs:anyURI|(% style="width:598px" %)The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.
553 553  
554 554  Element Documentation:
555 555  
556 -|**Name**|**Type**|**Documentation**
557 -|ProvisionAgreement|ProvisionAgreementRe ferenceType|ProvisionAgreement references a provision agreement which the data is reported against.
558 -|StructureUsage|DataflowReferenceTyp e|StructureUsage references a dataflow which the data is reported against.
559 -|Structure|DataStructureReferen ceType|Structure references the data structure definition which defines the structure of the data.
567 +(% style="width:1012.29px" %)
568 +|(% style="width:184px" %)**Name**|(% style="width:295px" %)**Type**|(% style="width:530px" %)**Documentation**
569 +|(% style="width:184px" %)ProvisionAgreement|(% style="width:295px" %)ProvisionAgreementReferenceType|(% style="width:530px" %)ProvisionAgreement references a provision agreement which the data is reported against.
570 +|(% style="width:184px" %)StructureUsage|(% style="width:295px" %)DataflowReferenceType|(% style="width:530px" %)StructureUsage references a dataflow which the data is reported against.
571 +|(% style="width:184px" %)Structure|(% style="width:295px" %)DataStructureReferenceType|(% style="width:530px" %)Structure references the data structure definition which defines the structure of the data.
560 560  
561 561  **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.
562 562  
... ... @@ -574,23 +574,25 @@
574 574  
575 575  Attribute Documentation:
576 576  
577 -|**Name**|**Type**|**Documentation**
578 -|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.
579 -|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located.
580 -|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.
581 -|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.
582 -|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.
583 -|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.
584 -|structureURL|xs:anyURI|The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.
589 +(% style="width:1010.29px" %)
590 +|**Name**|**Type**|(% style="width:562px" %)**Documentation**
591 +|structureID|xs:ID|(% style="width:562px" %)The structureID attribute uniquely identifies the structure for the purpose of referencing it from the payload. This is only used in structure specific formats. Although it is required, it is only useful when more than one data set is present in the message.
592 +|schemaURL|xs:anyURI|(% style="width:562px" %)The schemaURL attribute provides a location from which the structure specific schema can be located.
593 +|namespace|xs:anyURI|(% style="width:562px" %)The namespace attribute is used to provide the namespace for structure-specific formats. By communicating this information in the header, it is possible to generate the structure specific schema while processing the message.
594 +|dimensionAtObservation|ObservationDimensionType|(% style="width:562px" %)The dimensionAtObservation is used to reference the dimension at the observation level for data messages. This can also be given the explicit value of "AllDimensions" which denotes that the cross sectional data is in the flat format.
595 +|explicitMeasures (default: false)|xs:boolean|(% style="width:562px" %)The explicitMeasures indicates whether explicit measures are used in the cross sectional format. This is only applicable for the measure dimension as the dimension at the observation level or the flat structure.
596 +|serviceURL|xs:anyURI|(% style="width:562px" %)The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface.
597 +|structureURL|xs:anyURI|(% style="width:562px" %)The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.
585 585  
586 586  Element Documentation:
587 587  
588 -|**Name**|**Type**|**Documentation**
589 -|ProvisionAgreement|ProvisionAgreementReferenceType|ProvisionAgreement references a provision agreement which the data is reported against.
590 -|StructureUsage|DataflowReferenceType|StructureUsage references a dataflow which the data is reported against.
591 -|Structure|DataStructureReferen ceType|Structure references the data structure definition which defines the structure of the data.
601 +(% style="width:1018.29px" %)
602 +|(% style="width:202px" %)**Name**|(% style="width:284px" %)**Type**|(% style="width:529px" %)**Documentation**
603 +|(% style="width:202px" %)ProvisionAgreement|(% style="width:284px" %)ProvisionAgreementReferenceType|(% style="width:529px" %)ProvisionAgreement references a provision agreement which the data is reported against.
604 +|(% style="width:202px" %)StructureUsage|(% style="width:284px" %)DataflowReferenceType|(% style="width:529px" %)StructureUsage references a dataflow which the data is reported against.
605 +|(% style="width:202px" %)Structure|(% style="width:284px" %)DataStructureReferenceType|(% style="width:529px" %)Structure references the data structure definition which defines the structure of the data.
592 592  
593 -***MetadataStructureType*:** MetadataStructureType is an abstract base type the forms the basis of the structural information for any metadata message. A reference to the metadata structure definition or a metadataflow must be provided. This can be used to determine the structure of the message.
607 +//**MetadataStructureType:**// MetadataStructureType is an abstract base type the forms the basis of the structural information for any metadata message. A reference to the metadata structure definition or a metadataflow must be provided. This can be used to determine the structure of the message.
594 594  
595 595  Derivation:
596 596  
... ... @@ -605,19 +605,21 @@
605 605  
606 606  Attribute Documentation:
607 607  
608 -|**Name**|**Type**|**Documentation**
609 -|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.
610 -|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located.
611 -|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.
612 -|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.
613 -|structureURL|xs:anyURI|The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.
622 +(% style="width:1007.29px" %)
623 +|**Name**|**Type**|(% style="width:802px" %)**Documentation**
624 +|structureID|xs:ID|(% style="width:802px" %)The structureID attribute uniquely identifies the structure for the purpose of referencing it from the payload. This is only used in structure specific formats. Although it is required, it is only useful when more than one data set is present in the message.
625 +|schemaURL|xs:anyURI|(% style="width:802px" %)The schemaURL attribute provides a location from which the structure specific schema can be located.
626 +|namespace|xs:anyURI|(% style="width:802px" %)The namespace attribute is used to provide the namespace for structure-specific formats. By communicating this information in the header, it is possible to generate the structure specific schema while processing the message.
627 +|serviceURL|xs:anyURI|(% style="width:802px" %)The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface.
628 +|structureURL|xs:anyURI|(% style="width:802px" %)The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.
614 614  
615 615  Element Documentation:
616 616  
617 -|**Name**|**Type**|**Documentation**
618 -|ProvisionAgreement|ProvisionAgreementReferenceType|ProvisionAgreement references a provision agreement which the metadata is reported against.
619 -|StructureUsage|MetadataflowReferenceType|StructureUsage references a metadataflow which the metadata is reported against.
620 -|Structure|MetadataStructureReferenceType|Structure references the metadata structure definition which defines the structure of the metadata.
632 +(% style="width:1014.29px" %)
633 +|(% style="width:162px" %)**Name**|(% style="width:277px" %)**Type**|(% style="width:573px" %)**Documentation**
634 +|(% style="width:162px" %)ProvisionAgreement|(% style="width:277px" %)ProvisionAgreementReferenceType|(% style="width:573px" %)ProvisionAgreement references a provision agreement which the metadata is reported against.
635 +|(% style="width:162px" %)StructureUsage|(% style="width:277px" %)MetadataflowReferenceType|(% style="width:573px" %)StructureUsage references a metadataflow which the metadata is reported against.
636 +|(% style="width:162px" %)Structure|(% style="width:277px" %)MetadataStructureReferenceType|(% style="width:573px" %)Structure references the metadata structure definition which defines the structure of the metadata.
621 621  
622 622  **GenericMetadataStructureType:** GenericMetadataStructureType defines the structural information for a generic metadata message.
623 623  
... ... @@ -635,18 +635,20 @@
635 635  
636 636  Attribute Documentation:
637 637  
638 -|**Name**|**Type**|**Documentation**
639 -|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.
640 -|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located.
641 -|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.
642 -|structureURL|xs:anyURI|The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.
654 +(% style="width:997.294px" %)
655 +|**Name**|**Type**|(% style="width:792px" %)**Documentation**
656 +|structureID|xs:ID|(% style="width:792px" %)The structureID attribute uniquely identifies the structure for the purpose of referencing it from the payload. This is only used in structure specific formats. Although it is required, it is only useful when more than one data set is present in the message.
657 +|schemaURL|xs:anyURI|(% style="width:792px" %)The schemaURL attribute provides a location from which the structure specific schema can be located.
658 +|serviceURL|xs:anyURI|(% style="width:792px" %)The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface.
659 +|structureURL|xs:anyURI|(% style="width:792px" %)The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.
643 643  
644 644  Element Documentation:
645 645  
646 -|**Name**|**Type**|**Documentation**
647 -|ProvisionAgreement|ProvisionAgreementReferenceType|ProvisionAgreement references a provision agreement which the metadata is reported against.
648 -|StructureUsage|MetadataflowReferenceType|StructureUsage references a metadataflow which the metadata is reported against.
649 -|Structure|MetadataStructureReferenceType|Structure references the metadata structure definition which defines the structure of the metadata.
663 +(% style="width:1001.29px" %)
664 +|(% style="width:181px" %)**Name**|(% style="width:280px" %)**Type**|(% style="width:537px" %)**Documentation**
665 +|(% style="width:181px" %)ProvisionAgreement|(% style="width:280px" %)ProvisionAgreementReferenceType|(% style="width:537px" %)ProvisionAgreement references a provision agreement which the metadata is reported against.
666 +|(% style="width:181px" %)StructureUsage|(% style="width:280px" %)MetadataflowReferenceType|(% style="width:537px" %)StructureUsage references a metadataflow which the metadata is reported against.
667 +|(% style="width:181px" %)Structure|(% style="width:280px" %)MetadataStructureReferenceType|(% style="width:537px" %)Structure references the metadata structure definition which defines the structure of the metadata.
650 650  
651 651  === 2.1.4 Simple Types ===
652 652  
... ... @@ -871,8 +871,9 @@
871 871  
872 872  Enumerations:
873 873  
874 -|**Value**|**Documentation**
875 -|unbounded|Object has no upper limit on occurrences.
892 +(% style="width:625.294px" %)
893 +|(% style="width:144px" %)**Value**|(% style="width:478px" %)**Documentation**
894 +|(% style="width:144px" %)unbounded|(% style="width:478px" %)Object has no upper limit on occurrences.
876 876  
877 877  **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.
878 878  
... ... @@ -880,11 +880,12 @@
880 880  
881 881  Enumerations:
882 882  
883 -|**Value**|**Documentation**
884 -|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.
885 -|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.
886 -|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.
887 -|Information|Informational - data/metadata is being exchanged for informational purposes only, and not meant to update a system.
902 +(% style="width:1005.29px" %)
903 +|**Value**|(% style="width:905px" %)**Documentation**
904 +|Append|(% style="width:905px" %)Append - this is an incremental update for an existing data/metadata set or the provision of new data or documentation (attribute values) formerly absent. If any of the supplied data or metadata is already present, it will not replace that data or metadata. This corresponds to the "Update" value found in version 1.0 of the SDMX Technical Standards.
905 +|Replace|(% style="width:905px" %)Replace - data/metadata is to be replaced, and may also include additional data/metadata to be appended. The replacement occurs at the level of the observation - that is, it is not possible to replace an entire series.
906 +|Delete|(% style="width:905px" %)Delete - data/metadata is to be deleted. Deletion occurs at the lowest level object. For instance, if a delete data message contains a series with no observations, then the entire series will be deleted. If the series contains observations, then only those observations specified will be deleted. The same basic concept applies for attributes. If a series or observation in a delete message contains attributes, then only those attributes will be deleted.
907 +|Information|(% style="width:905px" %)Informational - data/metadata is being exchanged for informational purposes only, and not meant to update a system.
888 888  
889 889  **WildCardValueType:** WildCardValueType is a single value code list, used to include the '%' character - indicating that an entire field is wild carded.
890 890  
... ... @@ -892,8 +892,9 @@
892 892  
893 893  Enumerations:
894 894  
895 -|**Value**|**Documentation**
896 -|%|Indicates a wild card value.
915 +(% style="width:505.294px" %)
916 +|(% style="width:169px" %)**Value**|(% style="width:333px" %)**Documentation**
917 +|(% style="width:169px" %)%|(% style="width:333px" %)Indicates a wild card value.
897 897  
898 898  **CascadeSelectionType:**
899 899  
... ... @@ -906,8 +906,9 @@
906 906  
907 907  Enumerations:
908 908  
909 -|**Value**|**Documentation**
910 -|excluderoot|
930 +(% style="width:504.294px" %)
931 +|(% style="width:165px" %)**Value**|(% style="width:336px" %)**Documentation**
932 +|(% style="width:165px" %)excluderoot|(% style="width:336px" %)
911 911  
912 912  **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".
913 913  
... ... @@ -920,9 +920,10 @@
920 920  
921 921  Enumerations:
922 922  
923 -|**Value**|**Documentation**
924 -|AllDimensions|AllDimensions notes that the cross sectional format shall be flat; that is all dimensions should be contained at the observation level.
925 -|TIME_PERIOD|TIME_PERIOD refers to the fixed identifier for the time dimension.
945 +(% style="width:997.294px" %)
946 +|(% style="width:168px" %)**Value**|(% style="width:826px" %)**Documentation**
947 +|(% style="width:168px" %)AllDimensions|(% style="width:826px" %)AllDimensions notes that the cross sectional format shall be flat; that is all dimensions should be contained at the observation level.
948 +|(% style="width:168px" %)TIME_PERIOD|(% style="width:826px" %)TIME_PERIOD refers to the fixed identifier for the time dimension.
926 926  
927 927  **DataType:** DataTypeType provides an enumerated list of the types of data formats allowed as the for the representation of an object.
928 928  
... ... @@ -930,51 +930,52 @@
930 930  
931 931  Enumerations:
932 932  
933 -|**Value**|**Documentation**
934 -|String|A string datatype corresponding to W3C XML Schema's xs:string datatype.
935 -|Alpha|A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z.
936 -|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.
937 -|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.
938 -|BigInteger|An integer datatype corresponding to W3C XML Schema's xs:integer datatype.
939 -|Integer|An integer datatype corresponding to W3C XML Schema's xs:int datatype.
940 -|Long|A numeric datatype corresponding to W3C XML Schema's xs:long datatype.
941 -|Short|A numeric datatype corresponding to W3C XML Schema's xs:short datatype.
942 -|Decimal|A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype.
943 -|Float|A numeric datatype corresponding to W3C XML Schema's xs:float datatype.
944 -|Double|A numeric datatype corresponding to W3C XML Schema's xs:double datatype.
945 -|Boolean|A datatype corresponding to W3C XML Schema's xs:boolean datatype.
946 -|URI|A datatype corresponding to W3C XML Schema's xs:anyURI datatype.
947 -|Count|A simple incrementing Integer type. The isSequence facet must be set to true, and the interval facet must be set to "1".
948 -|InclusiveValueRange|This value indicates that the startValue and endValue attributes provide the inclusive boundaries of a numeric range of type xs:decimal.
949 -|ExclusiveValueRange|This value indicates that the startValue and endValue attributes provide the exclusive boundaries of a numeric range, of type xs:decimal.
950 -|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.
951 -|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.
952 -|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.
953 -|BasicTimePeriod|BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time.
954 -|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.
955 -|GregorianYear|A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601.
956 -|GregorianYearMonth|A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601.
957 -|GregorianDay|A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601.
958 -|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.
959 -|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.
960 -|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.
961 -|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.
962 -|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.
963 -|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.
964 -|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.
965 -|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.
966 -|DateTime|A time datatype corresponding to W3C XML Schema's xs:dateTime datatype.
967 -|TimeRange|TimeRange defines a time period by providing a distinct start (date or date time) and a duration.
968 -|Month|A time datatype corresponding to W3C XML Schema's xs:gMonth datatype.
969 -|MonthDay|A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype.
970 -|Day|A time datatype corresponding to W3C XML Schema's xs:gDay datatype.
971 -|Time|A time datatype corresponding to W3C XML Schema's xs:time datatype.
972 -|Duration|A time datatype corresponding to W3C XML Schema's xs:duration datatype.
973 -|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.
974 -|XHTML|This value indicates that the content of the component can contain XHTML markup.
975 -|KeyValues|This value indicates that the content of the component will be data key (a set of dimension references and values for the dimensions).
976 -|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.
977 -|DataSetReference|This value indicates that the content of the component will be reference to a data provider, which is actually a formal reference to a data provider and a data set identifier value.
956 +(% style="width:996.294px" %)
957 +|**Value**|(% style="width:796px" %)**Documentation**
958 +|String|(% style="width:796px" %)A string datatype corresponding to W3C XML Schema's xs:string datatype.
959 +|Alpha|(% style="width:796px" %)A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z.
960 +|AlphaNumeric|(% style="width:796px" %)A string datatype which only allows for the simple alphabetic character set of A-Z, a-z plus the simple numeric character set of 0-9.
961 +|Numeric|(% style="width:796px" %)A string datatype which only allows for the simple numeric character set of 0-9. This format is not treated as an integer, and therefore can having leading zeros.
962 +|BigInteger|(% style="width:796px" %)An integer datatype corresponding to W3C XML Schema's xs:integer datatype.
963 +|Integer|(% style="width:796px" %)An integer datatype corresponding to W3C XML Schema's xs:int datatype.
964 +|Long|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:long datatype.
965 +|Short|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:short datatype.
966 +|Decimal|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype.
967 +|Float|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:float datatype.
968 +|Double|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:double datatype.
969 +|Boolean|(% style="width:796px" %)A datatype corresponding to W3C XML Schema's xs:boolean datatype.
970 +|URI|(% style="width:796px" %)A datatype corresponding to W3C XML Schema's xs:anyURI datatype.
971 +|Count|(% style="width:796px" %)A simple incrementing Integer type. The isSequence facet must be set to true, and the interval facet must be set to "1".
972 +|InclusiveValueRange|(% style="width:796px" %)This value indicates that the startValue and endValue attributes provide the inclusive boundaries of a numeric range of type xs:decimal.
973 +|ExclusiveValueRange|(% style="width:796px" %)This value indicates that the startValue and endValue attributes provide the exclusive boundaries of a numeric range, of type xs:decimal.
974 +|Incremental|(% style="width:796px" %)This value indicates that the value increments according to the value provided in the interval facet, and has a true value for the isSequence facet.
975 +|ObservationalTimePeriod|(% style="width:796px" %)Observational time periods are the superset of all time periods in SDMX. It is the union of the standard time periods (i.e. Gregorian time periods, the reporting time periods, and date time) and a time range.
976 +|StandardTimePeriod|(% style="width:796px" %)Standard time periods is a superset of distinct time period in SDMX. It is the union of the basic time periods (i.e. the Gregorian time periods and date time) and the reporting time periods.
977 +|BasicTimePeriod|(% style="width:796px" %)BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time.
978 +|GregorianTimePeriod|(% style="width:796px" %)Gregorian time periods correspond to calendar periods and are represented in ISO-8601 formats. This is the union of the year, year month, and date formats.
979 +|GregorianYear|(% style="width:796px" %)A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601.
980 +|GregorianYearMonth|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601.
981 +|GregorianDay|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601.
982 +|ReportingTimePeriod|(% style="width:796px" %)Reporting time periods represent periods of a standard length within a reporting year, where to start of the year (defined as a month and day) must be defined elsewhere or it is assumed to be January 1. This is the union of the reporting year, semester, trimester, quarter, month, week, and day.
983 +|ReportingYear|(% style="width:796px" %)A reporting year represents a period of 1 year (P1Y) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingYearType.
984 +|ReportingSemester|(% style="width:796px" %)A reporting semester represents a period of 6 months (P6M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingSemesterType.
985 +|ReportingTrimester|(% style="width:796px" %)A reporting trimester represents a period of 4 months (P4M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingTrimesterType.
986 +|ReportingQuarter|(% style="width:796px" %)A reporting quarter represents a period of 3 months (P3M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingQuarterType.
987 +|ReportingMonth|(% style="width:796px" %)A reporting month represents a period of 1 month (P1M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingMonthType.
988 +|ReportingWeek|(% style="width:796px" %)A reporting week represents a period of 7 days (P7D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingWeekType.
989 +|ReportingDay|(% style="width:796px" %)A reporting day represents a period of 1 day (P1D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingDayType.
990 +|DateTime|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:dateTime datatype.
991 +|TimeRange|(% style="width:796px" %)TimeRange defines a time period by providing a distinct start (date or date time) and a duration.
992 +|Month|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gMonth datatype.
993 +|MonthDay|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype.
994 +|Day|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gDay datatype.
995 +|Time|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:time datatype.
996 +|Duration|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:duration datatype.
997 +|GeospatialInformation|(% style="width:796px" %)A string used to describe geographical features like points (e.g., locations of places, landmarks, buildings, etc.), lines (e.g., rivers, roads, streets, etc.), or areas (e.g., geographical regions, countries, islands, land lots, etc.). A mix of different features is possible too, e.g., combining polygons and geographical points to describe a country and the location of its capital.
998 +|XHTML|(% style="width:796px" %)This value indicates that the content of the component can contain XHTML markup.
999 +|KeyValues|(% style="width:796px" %)This value indicates that the content of the component will be data key (a set of dimension references and values for the dimensions).
1000 +|IdentifiableReference|(% style="width:796px" %)This value indicates that the content of the component will be complete reference (either URN or full set of reference fields) to an Identifiable object in the SDMX Information Model.
1001 +|DataSetReference|(% style="width:796px" %)This value indicates that the content of the component will be reference to a data provider, which is actually a formal reference to a data provider and a data set identifier value.
978 978  
979 979  **BasicComponentDataType:** BasicComponentDataType provides an enumerated list of the types of characters allowed in the textType attribute for all non-target object components.
980 980  
... ... @@ -982,48 +982,49 @@
982 982  
983 983  Enumerations:
984 984  
985 -|**Value**|**Documentation**
986 -|String|A string datatype corresponding to W3C XML Schema's xs:string datatype.
987 -|Alpha|A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z.
988 -|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.
989 -|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.
990 -|BigInteger|An integer datatype corresponding to W3C XML Schema's xs:integer datatype.
991 -|Integer|An integer datatype corresponding to W3C XML Schema's xs:int datatype.
992 -|Long|A numeric datatype corresponding to W3C XML Schema's xs:long datatype.
993 -|Short|A numeric datatype corresponding to W3C XML Schema's xs:short datatype.
994 -|Decimal|A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype.
995 -|Float|A numeric datatype corresponding to W3C XML Schema's xs:float datatype.
996 -|Double|A numeric datatype corresponding to W3C XML Schema's xs:double datatype.
997 -|Boolean|A datatype corresponding to W3C XML Schema's xs:boolean datatype.
998 -|URI|A datatype corresponding to W3C XML Schema's xs:anyURI datatype.
999 -|Count|A simple incrementing Integer type. The isSequence facet must be set to true, and the interval facet must be set to "1".
1000 -|InclusiveValueRange|This value indicates that the startValue and endValue attributes provide the inclusive boundaries of a numeric range of type xs:decimal.
1001 -|ExclusiveValueRange|This value indicates that the startValue and endValue attributes provide the exclusive boundaries of a numeric range, of type xs:decimal.
1002 -|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.
1003 -|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.
1004 -|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.
1005 -|BasicTimePeriod|BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time.
1006 -|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.
1007 -|GregorianYear|A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601.
1008 -|GregorianYearMonth|A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601.
1009 -|GregorianDay|A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601.
1010 -|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.
1011 -|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.
1012 -|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.
1013 -|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.
1014 -|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.
1015 -|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.
1016 -|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.
1017 -|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.
1018 -|DateTime|A time datatype corresponding to W3C XML Schema's xs:dateTime datatype.
1019 -|TimeRange|TimeRange defines a time period by providing a distinct start (date or date time) and a duration.
1020 -|Month|A time datatype corresponding to W3C XML Schema's xs:gMonth datatype.
1021 -|MonthDay|A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype.
1022 -|Day|A time datatype corresponding to W3C XML Schema's xs:gDay datatype.
1023 -|Time|A time datatype corresponding to W3C XML Schema's xs:time datatype.
1024 -|Duration|A time datatype corresponding to W3C XML Schema's xs:duration datatype.
1025 -|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.
1026 -|XHTML|This value indicates that the content of the component can contain XHTML markup.
1009 +(% style="width:999.294px" %)
1010 +|**Value**|(% style="width:799px" %)**Documentation**
1011 +|String|(% style="width:799px" %)A string datatype corresponding to W3C XML Schema's xs:string datatype.
1012 +|Alpha|(% style="width:799px" %)A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z.
1013 +|AlphaNumeric|(% style="width:799px" %)A string datatype which only allows for the simple alphabetic character set of A-Z, a-z plus the simple numeric character set of 0-9.
1014 +|Numeric|(% style="width:799px" %)A string datatype which only allows for the simple numeric character set of 0-9. This format is not treated as an integer, and therefore can having leading zeros.
1015 +|BigInteger|(% style="width:799px" %)An integer datatype corresponding to W3C XML Schema's xs:integer datatype.
1016 +|Integer|(% style="width:799px" %)An integer datatype corresponding to W3C XML Schema's xs:int datatype.
1017 +|Long|(% style="width:799px" %)A numeric datatype corresponding to W3C XML Schema's xs:long datatype.
1018 +|Short|(% style="width:799px" %)A numeric datatype corresponding to W3C XML Schema's xs:short datatype.
1019 +|Decimal|(% style="width:799px" %)A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype.
1020 +|Float|(% style="width:799px" %)A numeric datatype corresponding to W3C XML Schema's xs:float datatype.
1021 +|Double|(% style="width:799px" %)A numeric datatype corresponding to W3C XML Schema's xs:double datatype.
1022 +|Boolean|(% style="width:799px" %)A datatype corresponding to W3C XML Schema's xs:boolean datatype.
1023 +|URI|(% style="width:799px" %)A datatype corresponding to W3C XML Schema's xs:anyURI datatype.
1024 +|Count|(% style="width:799px" %)A simple incrementing Integer type. The isSequence facet must be set to true, and the interval facet must be set to "1".
1025 +|InclusiveValueRange|(% style="width:799px" %)This value indicates that the startValue and endValue attributes provide the inclusive boundaries of a numeric range of type xs:decimal.
1026 +|ExclusiveValueRange|(% style="width:799px" %)This value indicates that the startValue and endValue attributes provide the exclusive boundaries of a numeric range, of type xs:decimal.
1027 +|Incremental|(% style="width:799px" %)This value indicates that the value increments according to the value provided in the interval facet, and has a true value for the isSequence facet.
1028 +|ObservationalTimePeriod|(% style="width:799px" %)Observational time periods are the superset of all time periods in SDMX. It is the union of the standard time periods (i.e. Gregorian time periods, the reporting time periods, and date time) and a time range.
1029 +|StandardTimePeriod|(% style="width:799px" %)Standard time periods is a superset of distinct time period in SDMX. It is the union of the basic time periods (i.e. the Gregorian time periods and date time) and the reporting time periods.
1030 +|BasicTimePeriod|(% style="width:799px" %)BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time.
1031 +|GregorianTimePeriod|(% style="width:799px" %)Gregorian time periods correspond to calendar periods and are represented in ISO-8601 formats. This is the union of the year, year month, and date formats.
1032 +|GregorianYear|(% style="width:799px" %)A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601.
1033 +|GregorianYearMonth|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601.
1034 +|GregorianDay|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601.
1035 +|ReportingTimePeriod|(% style="width:799px" %)Reporting time periods represent periods of a standard length within a reporting year, where to start of the year (defined as a month and day) must be defined elsewhere or it is assumed to be January 1. This is the union of the reporting year, semester, trimester, quarter, month, week, and day.
1036 +|ReportingYear|(% style="width:799px" %)A reporting year represents a period of 1 year (P1Y) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingYearType.
1037 +|ReportingSemester|(% style="width:799px" %)A reporting semester represents a period of 6 months (P6M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingSemesterType.
1038 +|ReportingTrimester|(% style="width:799px" %)A reporting trimester represents a period of 4 months (P4M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingTrimesterType.
1039 +|ReportingQuarter|(% style="width:799px" %)A reporting quarter represents a period of 3 months (P3M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingQuarterType.
1040 +|ReportingMonth|(% style="width:799px" %)A reporting month represents a period of 1 month (P1M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingMonthType.
1041 +|ReportingWeek|(% style="width:799px" %)A reporting week represents a period of 7 days (P7D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingWeekType.
1042 +|ReportingDay|(% style="width:799px" %)A reporting day represents a period of 1 day (P1D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingDayType.
1043 +|DateTime|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:dateTime datatype.
1044 +|TimeRange|(% style="width:799px" %)TimeRange defines a time period by providing a distinct start (date or date time) and a duration.
1045 +|Month|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:gMonth datatype.
1046 +|MonthDay|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype.
1047 +|Day|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:gDay datatype.
1048 +|Time|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:time datatype.
1049 +|Duration|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:duration datatype.
1050 +|GeospatialInformation|(% style="width:799px" %)A string used to describe geographical features like points (e.g., locations of places, landmarks, buildings, etc.), lines (e.g., rivers, roads, streets, etc.), or areas (e.g., geographical regions, countries, islands, land lots, etc.). A mix of different features is possible too, e.g., combining polygons and geographical points to describe a country and the location of its capital.
1051 +|XHTML|(% style="width:799px" %)This value indicates that the content of the component can contain XHTML markup.
1027 1027  
1028 1028  **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.
1029 1029  
... ... @@ -1031,47 +1031,48 @@
1031 1031  
1032 1032  Enumerations:
1033 1033  
1034 -|**Value**|**Documentation**
1035 -|String|A string datatype corresponding to W3C XML Schema's xs:string datatype.
1036 -|Alpha|A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z.
1037 -|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.
1038 -|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.
1039 -|BigInteger|An integer datatype corresponding to W3C XML Schema's xs:integer datatype.
1040 -|Integer|An integer datatype corresponding to W3C XML Schema's xs:int datatype.
1041 -|Long|A numeric datatype corresponding to W3C XML Schema's xs:long datatype.
1042 -|Short|A numeric datatype corresponding to W3C XML Schema's xs:short datatype.
1043 -|Decimal|A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype.
1044 -|Float|A numeric datatype corresponding to W3C XML Schema's xs:float datatype.
1045 -|Double|A numeric datatype corresponding to W3C XML Schema's xs:double datatype.
1046 -|Boolean|A datatype corresponding to W3C XML Schema's xs:boolean datatype.
1047 -|URI|A datatype corresponding to W3C XML Schema's xs:anyURI datatype.
1048 -|Count|A simple incrementing Integer type. The isSequence facet must be set to true, and the interval facet must be set to "1".
1049 -|InclusiveValueRange|This value indicates that the startValue and endValue attributes provide the inclusive boundaries of a numeric range of type xs:decimal.
1050 -|ExclusiveValueRange|This value indicates that the startValue and endValue attributes provide the exclusive boundaries of a numeric range, of type xs:decimal.
1051 -|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.
1052 -|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.
1053 -|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.
1054 -|BasicTimePeriod|BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time.
1055 -|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.
1056 -|GregorianYear|A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601.
1057 -|GregorianYearMonth|A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601.
1058 -|GregorianDay|A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601.
1059 -|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.
1060 -|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.
1061 -|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.
1062 -|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.
1063 -|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.
1064 -|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.
1065 -|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.
1066 -|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.
1067 -|DateTime|A time datatype corresponding to W3C XML Schema's xs:dateTime datatype.
1068 -|TimeRange|TimeRange defines a time period by providing a distinct start (date or date time) and a duration.
1069 -|Month|A time datatype corresponding to W3C XML Schema's xs:gMonth datatype.
1070 -|MonthDay|A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype.
1071 -|Day|A time datatype corresponding to W3C XML Schema's xs:gDay datatype.
1072 -|Time|A time datatype corresponding to W3C XML Schema's xs:time datatype.
1073 -|Duration|A time datatype corresponding to W3C XML Schema's xs:duration datatype.
1074 -|GeospatialInformation|A string used to describe geographical features like points (e.g., locations of places, landmarks, buildings, etc.), lines (e.g., rivers, roads, streets, etc.), or areas (e.g., geographical regions, countries, islands, land lots, etc.). A mix of different features is possible too, e.g., combining polygons and geographical points to describe a country and the location of its capital.
1059 +(% style="width:996.294px" %)
1060 +|**Value**|(% style="width:796px" %)**Documentation**
1061 +|String|(% style="width:796px" %)A string datatype corresponding to W3C XML Schema's xs:string datatype.
1062 +|Alpha|(% style="width:796px" %)A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z.
1063 +|AlphaNumeric|(% style="width:796px" %)A string datatype which only allows for the simple alphabetic character set of A-Z, a-z plus the simple numeric character set of 0-9.
1064 +|Numeric|(% style="width:796px" %)A string datatype which only allows for the simple numeric character set of 0-9. This format is not treated as an integer, and therefore can having leading zeros.
1065 +|BigInteger|(% style="width:796px" %)An integer datatype corresponding to W3C XML Schema's xs:integer datatype.
1066 +|Integer|(% style="width:796px" %)An integer datatype corresponding to W3C XML Schema's xs:int datatype.
1067 +|Long|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:long datatype.
1068 +|Short|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:short datatype.
1069 +|Decimal|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype.
1070 +|Float|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:float datatype.
1071 +|Double|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:double datatype.
1072 +|Boolean|(% style="width:796px" %)A datatype corresponding to W3C XML Schema's xs:boolean datatype.
1073 +|URI|(% style="width:796px" %)A datatype corresponding to W3C XML Schema's xs:anyURI datatype.
1074 +|Count|(% style="width:796px" %)A simple incrementing Integer type. The isSequence facet must be set to true, and the interval facet must be set to "1".
1075 +|InclusiveValueRange|(% style="width:796px" %)This value indicates that the startValue and endValue attributes provide the inclusive boundaries of a numeric range of type xs:decimal.
1076 +|ExclusiveValueRange|(% style="width:796px" %)This value indicates that the startValue and endValue attributes provide the exclusive boundaries of a numeric range, of type xs:decimal.
1077 +|Incremental|(% style="width:796px" %)This value indicates that the value increments according to the value provided in the interval facet, and has a true value for the isSequence facet.
1078 +|ObservationalTimePeriod|(% style="width:796px" %)Observational time periods are the superset of all time periods in SDMX. It is the union of the standard time periods (i.e. Gregorian time periods, the reporting time periods, and date time) and a time range.
1079 +|StandardTimePeriod|(% style="width:796px" %)Standard time periods is a superset of distinct time period in SDMX. It is the union of the basic time periods (i.e. the Gregorian time periods and date time) and the reporting time periods.
1080 +|BasicTimePeriod|(% style="width:796px" %)BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time.
1081 +|GregorianTimePeriod|(% style="width:796px" %)Gregorian time periods correspond to calendar periods and are represented in ISO-8601 formats. This is the union of the year, year month, and date formats.
1082 +|GregorianYear|(% style="width:796px" %)A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601.
1083 +|GregorianYearMonth|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601.
1084 +|GregorianDay|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601.
1085 +|ReportingTimePeriod|(% style="width:796px" %)Reporting time periods represent periods of a standard length within a reporting year, where to start of the year (defined as a month and day) must be defined elsewhere or it is assumed to be January 1. This is the union of the reporting year, semester, trimester, quarter, month, week, and day.
1086 +|ReportingYear|(% style="width:796px" %)A reporting year represents a period of 1 year (P1Y) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingYearType.
1087 +|ReportingSemester|(% style="width:796px" %)A reporting semester represents a period of 6 months (P6M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingSemesterType.
1088 +|ReportingTrimester|(% style="width:796px" %)A reporting trimester represents a period of 4 months (P4M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingTrimesterType.
1089 +|ReportingQuarter|(% style="width:796px" %)A reporting quarter represents a period of 3 months (P3M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingQuarterType.
1090 +|ReportingMonth|(% style="width:796px" %)A reporting month represents a period of 1 month (P1M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingMonthType.
1091 +|ReportingWeek|(% style="width:796px" %)A reporting week represents a period of 7 days (P7D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingWeekType.
1092 +|ReportingDay|(% style="width:796px" %)A reporting day represents a period of 1 day (P1D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingDayType.
1093 +|DateTime|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:dateTime datatype.
1094 +|TimeRange|(% style="width:796px" %)TimeRange defines a time period by providing a distinct start (date or date time) and a duration.
1095 +|Month|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gMonth datatype.
1096 +|MonthDay|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype.
1097 +|Day|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gDay datatype.
1098 +|Time|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:time datatype.
1099 +|Duration|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:duration datatype.
1100 +|GeospatialInformation|(% style="width:796px" %)A string used to describe geographical features like points (e.g., locations of places, landmarks, buildings, etc.), lines (e.g., rivers, roads, streets, etc.), or areas (e.g., geographical regions, countries, islands, land lots, etc.). A mix of different features is possible too, e.g., combining polygons and geographical points to describe a country and the location of its capital.
1075 1075  
1076 1076  **TimeDataType:** TimeDataType restricts SimpleDataType to specify the allowable data types for representing a time value.
1077 1077  
© Semantic R&D Group, 2026