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.19
edited by Helena K.
on 2025/07/03 12:43
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  
... ... @@ -1079,24 +1079,25 @@
1079 1079  
1080 1080  Enumerations:
1081 1081  
1082 -|**Value**|**Documentation**
1083 -|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.
1084 -|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.
1085 -|BasicTimePeriod|BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time.
1086 -|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.
1087 -|GregorianYear|A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601.
1088 -|GregorianYearMonth|A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601.
1089 -|GregorianDay|A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601.
1090 -|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.
1091 -|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.
1092 -|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.
1093 -|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.
1094 -|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.
1095 -|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.
1096 -|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.
1097 -|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.
1098 -|DateTime|A time datatype corresponding to W3C XML Schema's xs:dateTime datatype.
1099 -|TimeRange|TimeRange defines a time period by providing a distinct start (date or date time) and a duration.
1108 +(% style="width:1002.29px" %)
1109 +|**Value**|(% style="width:802px" %)**Documentation**
1110 +|ObservationalTimePeriod|(% style="width:802px" %)Observational time periods are the superset of all time periods in SDMX. It is the union of the standard time periods (i.e. Gregorian time periods, the reporting time periods, and date time) and a time range.
1111 +|StandardTimePeriod|(% style="width:802px" %)Standard time periods is a superset of distinct time period in SDMX. It is the union of the basic time periods (i.e. the Gregorian time periods and date time) and the reporting time periods.
1112 +|BasicTimePeriod|(% style="width:802px" %)BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time.
1113 +|GregorianTimePeriod|(% style="width:802px" %)Gregorian time periods correspond to calendar periods and are represented in ISO-8601 formats. This is the union of the year, year month, and date formats.
1114 +|GregorianYear|(% style="width:802px" %)A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601.
1115 +|GregorianYearMonth|(% style="width:802px" %)A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601.
1116 +|GregorianDay|(% style="width:802px" %)A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601.
1117 +|ReportingTimePeriod|(% style="width:802px" %)Reporting time periods represent periods of a standard length within a reporting year, where to start of the year (defined as a month and day) must be defined elsewhere or it is assumed to be January 1. This is the union of the reporting year, semester, trimester, quarter, month, week, and day.
1118 +|ReportingYear|(% style="width:802px" %)A reporting year represents a period of 1 year (P1Y) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingYearType.
1119 +|ReportingSemester|(% style="width:802px" %)A reporting semester represents a period of 6 months (P6M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingSemesterType.
1120 +|ReportingTrimester|(% style="width:802px" %)A reporting trimester represents a period of 4 months (P4M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingTrimesterType.
1121 +|ReportingQuarter|(% style="width:802px" %)A reporting quarter represents a period of 3 months (P3M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingQuarterType.
1122 +|ReportingMonth|(% style="width:802px" %)A reporting month represents a period of 1 month (P1M) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingMonthType.
1123 +|ReportingWeek|(% style="width:802px" %)A reporting week represents a period of 7 days (P7D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingWeekType.
1124 +|ReportingDay|(% style="width:802px" %)A reporting day represents a period of 1 day (P1D) from the start date of the reporting year. This is expressed as using the SDMX specific ReportingDayType.
1125 +|DateTime|(% style="width:802px" %)A time datatype corresponding to W3C XML Schema's xs:dateTime datatype.
1126 +|TimeRange|(% style="width:802px" %)TimeRange defines a time period by providing a distinct start (date or date time) and a duration.
1100 1100  
1101 1101  **UrnPrefixPart:** This is validates the first part of the URN (urn:sdmx.org.infomodel.<package>.<class=). It is intended to be further restricted.
1102 1102  
... ... @@ -1131,57 +1131,19 @@
1131 1131  **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.
1132 1132  
1133 1133  Derived by restriction of UrnMaintainableIdPart.
1134 -Regular Expression Pattern: . +\((0|[1-9]\d*)(\.(0|[1-9]\d*))?\).*.+\((0|[1-9]\d*)(\.(0|[1-9]\d*)){2}(\-(([A-Za-z\-]|([A-Za-z\-][A-Za-z0-9\-]+)|([A-Za-z0-9\-]+[A-Za-z\-][A-Za-z0-9\-]*))|(0|[1-9][0-9]*))(\.(([A-Za-z\-]|([A-Za-z\-][A-Za-z0-9\-]+)|([A-Za-z0-9\-]+[A-Za-z\-][A-Za-z0-9\-]*))|(0|[1-9][0-9]*
1161 +Regular Expression Pattern: . +\((0|[1-9]\d*)(\.(0|[1-9]\d*))?\).*.+\((0|[1-9]\d*)(\.(0|[1-9]\d*)){2}(\-(([A-Za-z\-]|([A-Za-z\-][A-Za-z0-9\-]+)|([A-Za-z0-9\-]+[A-Za-z\-][A-Za-z0-9\-]*))|(0|[1-9][0-9]*))(\.(([A-Za-z\-]|([A-Za-z\-][A-Za-z0-9\-]+)|([A-Za-z0-9\-]+[A-Za-z\-][A-Za-z0-9\-]*))|(0|[1-9][0-9]~*~*)?\).
1135 1135  )))
1136 1136  
1137 -*)?\).
1138 -
1139 1139  **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.
1140 1140  
1141 1141  Derived by restriction of UrnMaintainableIdPart.
1142 -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]*~)~)~)*)?\).*.+\
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*)\+?))\).
1143 1143  
1144 -(((
1145 -0|[1-9]\d*)\+?)(\.((0|[1-9]\d*
1146 -)))
1147 -
1148 -{2}\).*.+\
1149 -
1150 -(((
1151 -0|[1-9]\d*))(\.((0|[1-9]\d*)\+?))(\.((0|[1-9]\d*
1152 -)))
1153 -
1154 -\).*.+\
1155 -
1156 -(((
1157 -0|[1-9]\d*)\+?)(\.((0|[1-9]\d*
1158 -)))
1159 -
1160 -(\.((0|[1-9]\d*)\+?))\).
1161 -
1162 1162  **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.
1163 1163  
1164 1164  Derived by restriction of WildcardUrnMaintainableIdPart.
1165 -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]*~)~)~)*)?\).*.+\
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*)\+?))\).*.+\(\*\).
1166 1166  
1167 -(((
1168 -0|[1-9]\d*)\+?)(\.((0|[1-9]\d*
1169 -)))
1170 -
1171 -{2}\).*.+\
1172 -
1173 -(((
1174 -0|[1-9]\d*))(\.((0|[1-9]\d*)\+?))(\.((0|[1-9]\d*
1175 -)))
1176 -
1177 -\).*.+\
1178 -
1179 -(((
1180 -0|[1-9]\d*)\+?)(\.((0|[1-9]\d*
1181 -)))
1182 -
1183 -(\.((0|[1-9]\d*)\+?))\).*.+\(\*\).
1184 -
1185 1185  **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.
1186 1186  
1187 1187  Derived by restriction of UrnVersionPart.
... ... @@ -1597,17 +1597,17 @@
1597 1597  Derived by restriction of OrganisationReferenceType.
1598 1598  Regular Expression Pattern: . +\.base\.DataConsumer=.+:DATA_CONSUMERS\(.+\).+
1599 1599  
1600 -**DataConsumerSchemeReferenceType:** A reference type for a data consumer scheme.
1589 +**DataConsumerSchemeReferenceType:** A reference type for a [[data consumer scheme>>doc:sdmx:Glossary.Data consumer scheme.WebHome]].
1601 1601  
1602 1602  Derived by restriction of OrganisationSchemeReferenceType.
1603 1603  Regular Expression Pattern: . +\.base\.DataConsumerScheme=.+:DATA_CONSUMERS\(.+\)
1604 1604  
1605 -**DataProviderReferenceType:** A reference type for a data provider.
1594 +**DataProviderReferenceType:** A reference type for a [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]].
1606 1606  
1607 1607  Derived by restriction of OrganisationReferenceType.
1608 1608  Regular Expression Pattern: . +\.base\.DataProvider=.+:DATA_PROVIDERS\(.+\).+
1609 1609  
1610 -**DataProviderSchemeReferenceType:** A reference type for a data provider scheme.
1599 +**DataProviderSchemeReferenceType:** A reference type for a [[data provider scheme>>doc:sdmx:Glossary.Data provider scheme.WebHome]].
1611 1611  
1612 1612  Derived by restriction of OrganisationSchemeReferenceType.
1613 1613  Regular Expression Pattern: . +\.base\.DataProviderScheme=.+:DATA_PROVIDERS\(.+\)
... ... @@ -1627,7 +1627,7 @@
1627 1627  Derived by restriction of OrganisationReferenceType.
1628 1628  Regular Expression Pattern: . +\.base\.OrganisationUnit=.+
1629 1629  
1630 -**OrganisationUnitSchemeReferenceType:** A reference type for an organisation unit scheme.
1619 +**OrganisationUnitSchemeReferenceType:** A reference type for an [[organisation unit scheme>>doc:sdmx:Glossary.Organisation unit scheme.WebHome]].
1631 1631  
1632 1632  Derived by restriction of OrganisationSchemeReferenceType.
1633 1633  Regular Expression Pattern: . +\.base\.OrganisationUnitScheme=.+
... ... @@ -1637,7 +1637,7 @@
1637 1637  Derived by restriction of MaintainableUrnReferenceType.
1638 1638  Regular Expression Pattern: . +\.categoryscheme\.Categorisation=.+
1639 1639  
1640 -**CategoryReferenceType:** A reference type for a category.
1629 +**CategoryReferenceType:** A reference type for a [[category>>doc:sdmx:Glossary.Category.WebHome]].
1641 1641  
1642 1642  Derived by restriction of UrnReferenceType.
1643 1643  Regular Expression Pattern: . +\.categoryscheme\.Category=.+
... ... @@ -1647,7 +1647,7 @@
1647 1647  Derived by restriction of MaintainableUrnReferenceType.
1648 1648  Regular Expression Pattern: . +\.categoryscheme\.CategoryScheme=.+
1649 1649  
1650 -**ReportingCategoryReferenceType:** A reference type for a reporting category.
1639 +**ReportingCategoryReferenceType:** A reference type for a reporting [[category>>doc:sdmx:Glossary.Category.WebHome]].
1651 1651  
1652 1652  Derived by restriction of UrnReferenceType.
1653 1653  Regular Expression Pattern: . +\.categoryscheme\.ReportingCategory=.+
... ... @@ -1657,32 +1657,32 @@
1657 1657  Derived by restriction of MaintainableUrnReferenceType.
1658 1658  Regular Expression Pattern: . +\.categoryscheme\.ReportingTaxonomy=.+
1659 1659  
1660 -**CodeReferenceType:** A reference type for a code.
1649 +**CodeReferenceType:** A reference type for a [[code>>doc:sdmx:Glossary.Code.WebHome]].
1661 1661  
1662 1662  Derived by restriction of ComponentUrnReferenceType.
1663 1663  Regular Expression Pattern: . +\.codelist\.Code=.+
1664 1664  
1665 -**CodelistReferenceType:** A reference type for a codelist.
1654 +**CodelistReferenceType:** A reference type for a [[codelist>>doc:sdmx:Glossary.Code list.WebHome]].
1666 1666  
1667 1667  Derived by restriction of AnyCodelistReferenceType.
1668 1668  Regular Expression Pattern: . +\.codelist\.Codelist=.+
1669 1669  
1670 -**HierarchicalCodeReferenceType:** A reference type for a hierarchical code.
1659 +**HierarchicalCodeReferenceType:** A reference type for a [[hierarchical code>>doc:sdmx:Glossary.Hierarchical code.WebHome]].
1671 1671  
1672 1672  Derived by restriction of UrnReferenceType.
1673 1673  Regular Expression Pattern: . +\.codelist\.HierarchicalCode=.+
1674 1674  
1675 -**HierarchyReferenceType:** A reference type for a hierarchy.
1664 +**HierarchyReferenceType:** A reference type for a [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]].
1676 1676  
1677 1677  Derived by restriction of MaintainableUrnReferenceType.
1678 1678  Regular Expression Pattern: . +\.codelist\.Hierarchy=.+
1679 1679  
1680 -**HierarchyAssociationReferenceType:** A reference type for a hierarchy association.
1669 +**HierarchyAssociationReferenceType:** A reference type for a [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] association.
1681 1681  
1682 1682  Derived by restriction of MaintainableUrnReferenceType.
1683 1683  Regular Expression Pattern: . +\.codelist\.HierarchyAssociation=.+
1684 1684  
1685 -**LevelReferenceType:** A reference type for a level.
1674 +**LevelReferenceType:** A reference type for a (% style="color:#e74c3c" %)level(%%).
1686 1686  
1687 1687  Derived by restriction of ComponentUrnReferenceType.
1688 1688  Regular Expression Pattern: . +\.codelist\.Level=.+
... ... @@ -1692,27 +1692,27 @@
1692 1692  Derived by restriction of AnyCodelistReferenceType.
1693 1693  Regular Expression Pattern: . +\.codelist\.ValueList=.+
1694 1694  
1695 -**ConceptReferenceType:** A reference type for a concept.
1684 +**ConceptReferenceType:** A reference type for a (% style="color:#e74c3c" %)concept(%%).
1696 1696  
1697 1697  Derived by restriction of ComponentUrnReferenceType.
1698 1698  Regular Expression Pattern: . +\.conceptscheme\.Concept=.+
1699 1699  
1700 -**ConceptSchemeReferenceType:** A reference type for a concept scheme.
1689 +**ConceptSchemeReferenceType:** A reference type for a [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]].
1701 1701  
1702 1702  Derived by restriction of MaintainableUrnReferenceType.
1703 1703  Regular Expression Pattern: . +\.conceptscheme\.ConceptScheme=.+
1704 1704  
1705 -**AttributeDescriptorReferenceType:** A reference type for an attribute descriptor.
1694 +**AttributeDescriptorReferenceType:** A reference type for an [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] descriptor.
1706 1706  
1707 1707  Derived by restriction of ComponentUrnReferenceType.
1708 1708  Regular Expression Pattern: . +\.datastructure\.AttributeDescriptor=.+
1709 1709  
1710 -**DataAttributeReferenceType:** A reference type for a data attribute.
1699 +**DataAttributeReferenceType:** A reference type for a data [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]].
1711 1711  
1712 1712  Derived by restriction of ComponentUrnReferenceType.
1713 1713  Regular Expression Pattern: . +\.datastructure\.DataAttribute=.+
1714 1714  
1715 -**DataflowReferenceType:** A reference type for a dataflow.
1704 +**DataflowReferenceType:** A reference type for a [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]].
1716 1716  
1717 1717  Derived by restriction of StructureUsageReferenceType.
1718 1718  Regular Expression Pattern: . +\.datastructure\.Dataflow=.+
... ... @@ -1722,42 +1722,42 @@
1722 1722  Derived by restriction of StructureReferenceType.
1723 1723  Regular Expression Pattern: . +\.datastructure\.DataStructure=.+
1724 1724  
1725 -**DimensionReferenceType:** A reference type for a dimension.
1714 +**DimensionReferenceType:** A reference type for a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]].
1726 1726  
1727 1727  Derived by restriction of ComponentUrnReferenceType.
1728 1728  Regular Expression Pattern: . +\.datastructure\.Dimension=.+
1729 1729  
1730 -**DimensionDescriptorReferenceType:** A reference type for a dimension descriptor.
1719 +**DimensionDescriptorReferenceType:** A reference type for a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] descriptor.
1731 1731  
1732 1732  Derived by restriction of ComponentUrnReferenceType.
1733 1733  Regular Expression Pattern: . +\.datastructure\.DimensionDescriptor=.+
1734 1734  
1735 -**GroupDimensionDescriptorReferenceType:** A reference type for a group dimension descriptor.
1724 +**GroupDimensionDescriptorReferenceType:** A reference type for a group [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] descriptor.
1736 1736  
1737 1737  Derived by restriction of ComponentUrnReferenceType.
1738 1738  Regular Expression Pattern: . +\.datastructure\.GroupDimensionDescriptor=.+
1739 1739  
1740 -**MeasureReferenceType:** A reference type for a measure.
1729 +**MeasureReferenceType:** A reference type for a [[measure>>doc:sdmx:Glossary.Measure.WebHome]].
1741 1741  
1742 1742  Derived by restriction of ComponentUrnReferenceType.
1743 1743  Regular Expression Pattern: . +\.datastructure\.Measure=.+
1744 1744  
1745 -**MeasureDescriptorReferenceType:** A reference type for a measure descriptor.
1734 +**MeasureDescriptorReferenceType:** A reference type for a [[measure>>doc:sdmx:Glossary.Measure.WebHome]] descriptor.
1746 1746  
1747 1747  Derived by restriction of ComponentUrnReferenceType.
1748 1748  Regular Expression Pattern: . +\.datastructure\.MeasureDescriptor=.+
1749 1749  
1750 -**TimeDimensionReferenceType:** A reference type for a time dimension.
1739 +**TimeDimensionReferenceType:** A reference type for a time [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]].
1751 1751  
1752 1752  Derived by restriction of ComponentUrnReferenceType.
1753 1753  Regular Expression Pattern: . +\.datastructure\.TimeDimension=.+
1754 1754  
1755 -**MetadataAttributeReferenceType:** A reference type for a metadata attribute.
1744 +**MetadataAttributeReferenceType:** A reference type for a metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]].
1756 1756  
1757 1757  Derived by restriction of UrnReferenceType.
1758 1758  Regular Expression Pattern: . +\.metadatastructure\.MetadataAttribute=.+
1759 1759  
1760 -**MetadataflowReferenceType:** A reference type for a metadataflow.
1749 +**MetadataflowReferenceType:** A reference type for a [[metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]].
1761 1761  
1762 1762  Derived by restriction of StructureUsageReferenceType.
1763 1763  Regular Expression Pattern: . +\.metadatastructure\.Metadataflow=.+
... ... @@ -1787,42 +1787,42 @@
1787 1787  Derived by restriction of UrnReferenceType.
1788 1788  Regular Expression Pattern: . +\.process\.Transition=.+
1789 1789  
1790 -**DataConstraintReferenceType:** A reference type for a data constraint.
1779 +**DataConstraintReferenceType:** A reference type for a data (% style="color:#e74c3c" %)constraint(%%).
1791 1791  
1792 1792  Derived by restriction of ConstraintReferenceType.
1793 1793  Regular Expression Pattern: . +\.registry\.DataConstraint=.+
1794 1794  
1795 -**MetadataConstraintReferenceType:** A reference type for a metadata constraint.
1784 +**MetadataConstraintReferenceType:** A reference type for a metadata (% style="color:#e74c3c" %)constraint(%%).
1796 1796  
1797 1797  Derived by restriction of ConstraintReferenceType.
1798 1798  Regular Expression Pattern: . +\.registry\.MetadataConstraint=.+
1799 1799  
1800 -**MetadataProvisionAgreementReferenceType:** A reference type for a metadata provision agreement.
1789 +**MetadataProvisionAgreementReferenceType:** A reference type for a metadata [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]].
1801 1801  
1802 1802  Derived by restriction of MaintainableUrnReferenceType.
1803 1803  Regular Expression Pattern: . +\.registry\.MetadataProvisionAgreement=.+
1804 1804  
1805 -**ProvisionAgreementReferenceType:** A reference type for a provision agreement.
1794 +**ProvisionAgreementReferenceType:** A reference type for a [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]].
1806 1806  
1807 1807  Derived by restriction of MaintainableUrnReferenceType.
1808 1808  Regular Expression Pattern: . +\.registry\.ProvisionAgreement=.+
1809 1809  
1810 -**CategorySchemeMapReferenceType:** A reference type for a category scheme map.
1799 +**CategorySchemeMapReferenceType:** A reference type for a [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] (% style="color:#e74c3c" %)map(%%).
1811 1811  
1812 1812  Derived by restriction of MaintainableUrnReferenceType.
1813 1813  Regular Expression Pattern: . +\.structuremapping\.CategorySchemeMap=.+
1814 1814  
1815 -**ConceptSchemeMapReferenceType:** A reference type for a concept scheme map.
1804 +**ConceptSchemeMapReferenceType:** A reference type for a [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] (% style="color:#e74c3c" %)map(%%).
1816 1816  
1817 1817  Derived by restriction of MaintainableUrnReferenceType.
1818 1818  Regular Expression Pattern: . +\.structuremapping\.ConceptSchemeMap=.+
1819 1819  
1820 -**DatePatternMapReferenceType:** A reference type for a date pattern map.
1809 +**DatePatternMapReferenceType:** A reference type for a date pattern (% style="color:#e74c3c" %)map(%%).
1821 1821  
1822 1822  Derived by restriction of ComponentUrnReferenceType.
1823 1823  Regular Expression Pattern: . +\.structuremapping\.DatePatternMap=.+
1824 1824  
1825 -**EpochMapReferenceType:** A reference type for an epoch map.
1814 +**EpochMapReferenceType:** A reference type for an epoch (% style="color:#e74c3c" %)map(%%).
1826 1826  
1827 1827  Derived by restriction of ComponentUrnReferenceType.
1828 1828  Regular Expression Pattern: . +\.structuremapping\.EpochMap=.+
... ... @@ -1832,22 +1832,22 @@
1832 1832  Derived by restriction of ComponentUrnReferenceType.
1833 1833  Regular Expression Pattern: . +\.structuremapping\.FrequencyFormatMapping=.+
1834 1834  
1835 -**OrganisationSchemeMapReferenceType:** A reference type for a organisation scheme map.
1824 +**OrganisationSchemeMapReferenceType:** A reference type for a organisation scheme (% style="color:#e74c3c" %)map(%%).
1836 1836  
1837 1837  Derived by restriction of MaintainableUrnReferenceType.
1838 1838  Regular Expression Pattern: . +\.structuremapping\.OrganisationSchemeMap=.+
1839 1839  
1840 -**ReportingTaxonomyMapReferenceType:** A reference type for a reporting taxonomy map.
1829 +**ReportingTaxonomyMapReferenceType:** A reference type for a reporting taxonomy (% style="color:#e74c3c" %)map(%%).
1841 1841  
1842 1842  Derived by restriction of MaintainableUrnReferenceType.
1843 1843  Regular Expression Pattern: . +\.structuremapping\.ReportingTaxonomyMap=.+
1844 1844  
1845 -**RepresentationMapReferenceType:** A reference type for a representation map.
1834 +**RepresentationMapReferenceType:** A reference type for a [[representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)map(%%).
1846 1846  
1847 1847  Derived by restriction of MaintainableUrnReferenceType.
1848 1848  Regular Expression Pattern: . +\.structuremapping\.RepresentationMap=.+
1849 1849  
1850 -**StructureMapReferenceType:** A reference type for a structure map.
1839 +**StructureMapReferenceType:** A reference type for a structure (% style="color:#e74c3c" %)map(%%).
1851 1851  
1852 1852  Derived by restriction of MaintainableUrnReferenceType.
1853 1853  Regular Expression Pattern: . +\.structuremapping\.StructureMap=.+
... ... @@ -1902,84 +1902,86 @@
1902 1902  Derived by restriction of MaintainableUrnReferenceType.
1903 1903  Regular Expression Pattern: . +\.transformation\.UserDefinedOperatorScheme=.+
1904 1904  
1905 -**VtlMappingReferenceType:** A reference type for a VTL mapping.
1894 +**VtlMappingReferenceType:** A reference type for a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] mapping.
1906 1906  
1907 1907  Derived by restriction of ComponentUrnReferenceType.
1908 1908  Regular Expression Pattern: . +\.transformation\.VtlCodelistMapping=.+.+\.transformation\.VtlConceptMapping=.+.+\.transformation\.VtlDataflowMapping=.+
1909 1909  
1910 -**VtlMappingSchemeReferenceType:** A reference type for a VTL mapping scheme.
1899 +**VtlMappingSchemeReferenceType:** A reference type for a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] mapping scheme.
1911 1911  
1912 1912  Derived by restriction of MaintainableUrnReferenceType.
1913 1913  Regular Expression Pattern: . +\.transformation\.VtlMappingScheme=.+
1914 1914  
1915 -**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.
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.
1916 1916  
1917 1917  Union of:
1918 1918  
1919 1919  LegacyVersionNumberType, SemanticVersionNumberType, SemanticVersionReferenceType.
1920 1920  
1921 -**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 "+".
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 "+".
1922 1922  
1923 1923  Derived by restriction of xs:string.
1913 +
1924 1924  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*)\+?))
1925 1925  
1926 -**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.
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.
1927 1927  
1928 1928  Union of:
1929 1929  
1930 1930  LegacyVersionNumberType, SemanticVersionNumberType, SemanticVersionReferenceType, WildcardType.
1931 1931  
1932 -**WildcardType:** WildcardType is a single value code list, used to include the '*' character - indicating that the identification component is wildcarded.
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.
1933 1933  
1934 1934  Derived by restriction of xs:string.
1935 1935  
1936 1936  Enumerations:
1937 1937  
1938 -|**Value**|**Documentation**
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.
1939 1939  
1940 -|\*|Indicates that any value of the identifier component is allowed.|
1932 +**NestedIDType:** NestedIDType is the least restrictive form of an identifier used throughout all [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] 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, \_, -, $.
1941 1941  
1942 -**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, \_, -, $.
1943 -
1944 1944  Derived by restriction of xs:string.
1945 1945  Regular Expression Pattern: [A-Za-z0-9_@$\-]+(\.[A-Za-z0-9_@$\-]+)
1946 1946  
1947 -**TwoLevelIDType:** TwoLevelIDType defines an identifier with exactly two levels.
1937 +**TwoLevelIDType:** TwoLevelIDType defines an identifier with exactly two (% style="color:#e74c3c" %)levels(%%).
1948 1948  
1949 1949  Derived by restriction of NestedIDType.
1950 1950  Regular Expression Pattern: [A-Za-z0-9_@$\-]+\.[A-Za-z0-9_@$\-]+
1951 1951  
1952 -**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, \_, -, $.
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, \_, -, $.
1953 1953  
1954 1954  Derived by restriction of NestedIDType.
1955 1955  Regular Expression Pattern: [A-Za-z0-9_@$\-]+
1956 1956  
1957 -**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.
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.
1958 1958  
1959 1959  Derived by restriction of IDType.
1960 1960  Regular Expression Pattern: [A-Za-z][A-Za-z0-9_\-]
1961 1961  
1962 -**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.
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.
1963 1963  
1964 1964  Derived by restriction of NestedIDType.
1965 1965  Regular Expression Pattern: [A-Za-z][A-Za-z0-9_\-]*(\.[A-Za-z][A-Za-z0-9_\-]*)
1966 1966  
1967 -**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).
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).
1968 1968  
1969 1969  Derived by restriction of NestedNCNameIDType.
1970 1970  Regular Expression Pattern: [A-Za-z][A-Za-z0-9_\-]
1971 1971  
1972 -**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.
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.Statistical data and metadata exchange.WebHome]] (% style="color:#e74c3c" %)version(%%) format is also support.
1973 1973  
1974 1974  Union of:
1975 1975  LegacyVersionNumberType, SemanticVersionNumberType.
1976 1976  
1977 -**SemanticVersionNumberType:** SemanticVersionNumberType is a simple type for validating semantic version in the format (major.minor.patch[-extension]).
1967 +**SemanticVersionNumberType:** SemanticVersionNumberType is a simple type for validating semantic (% style="color:#e74c3c" %)version(%%) in the format (major.minor.patch[-extension]).
1978 1978  
1979 1979  Derived by restriction of xs:string.
1980 1980  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]*~)~)~)*)?
1981 1981  
1982 -**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.
1972 +**LegacyVersionNumberType:** LegacyVersionNumberType describes the (% style="color:#e74c3c" %)version(%%) number format previously supported in [[SDMX>>doc:sdmx:Glossary.Statistical data 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.
1983 1983  
1984 1984  Derived by restriction of xs:string.
1975 +
1985 1985  Regular Expression Pattern: (0|[1-9]\d*)(\.(0|[1-9]\d*))?
© Semantic R&D Group, 2026