Changes for page Part II.Common Namespace
Last modified by Elena Yasinovskaya on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -329,20 +329,22 @@ 329 329 330 330 Attribute Documentation: 331 331 332 -|**Name**|**Type**|**Documentation** 333 -|id|IDType|The id is the identifier for the object. 334 -|urn|UrnType|The urn attribute holds a valid SDMX Registry URN (see SDMX Registry Specification for details). 335 -|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. 332 +(% style="width:1012.29px" %) 333 +|**Name**|**Type**|(% style="width:768px" %)**Documentation** 334 +|id|IDType|(% style="width:768px" %)The id is the identifier for the object. 335 +|urn|UrnType|(% style="width:768px" %)The urn attribute holds a valid SDMX Registry URN (see SDMX Registry Specification for details). 336 +|uri|xs:anyURI|(% style="width:768px" %)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. 336 336 337 337 Element Documentation: 338 338 339 -|**Name**|**Type**|**Documentation** 340 -|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. 341 -|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. 342 -|Name|TextType|Name provides for a human-readable name for the object. This may be provided in multiple, parallel language-equivalent forms. 343 -|Description|TextType|Description provides for a longer human-readable description of the object. This may be provided in multiple, parallel language-equivalent forms. 340 +(% style="width:1008.29px" %) 341 +|**Name**|**Type**|(% style="width:731px" %)**Documentation** 342 +|Annotations|AnnotationsType|(% style="width:731px" %)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. 343 +|Link|LinkType|(% style="width:731px" %)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. 344 +|Name|TextType|(% style="width:731px" %)Name provides for a human-readable name for the object. This may be provided in multiple, parallel language-equivalent forms. 345 +|Description|TextType|(% style="width:731px" %)Description provides for a longer human-readable description of the object. This may be provided in multiple, parallel language-equivalent forms. 344 344 345 -** *VersionableType*:** VersionableType is an abstract base type for all versionable objects.347 +//**VersionableType:**// VersionableType is an abstract base type for all versionable objects. 346 346 347 347 Derivation: 348 348 ... ... @@ -359,23 +359,25 @@ 359 359 360 360 Attribute Documentation: 361 361 362 -|**Name**|**Type**|**Documentation** 363 -|id|IDType|The id is the identifier for the object. 364 -|urn|UrnType|The urn attribute holds a valid SDMX Registry URN (see SDMX Registry Specification for details). 365 -|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. 366 -|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. 367 -|validFrom|xs:dateTime|The validFrom attribute provides the inclusive start date for providing supplemental validity information about the version. 368 -|validTo|xs:dateTime|The validTo attribute provides the inclusive end date for providing supplemental validity information about the version. 364 +(% style="width:1000.29px" %) 365 +|**Name**|**Type**|(% style="width:700px" %)**Documentation** 366 +|id|IDType|(% style="width:700px" %)The id is the identifier for the object. 367 +|urn|UrnType|(% style="width:700px" %)The urn attribute holds a valid SDMX Registry URN (see SDMX Registry Specification for details). 368 +|uri|xs:anyURI|(% style="width:700px" %)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. 369 +|version|VersionType|(% style="width:700px" %)This version attribute holds a version number (see common:VersionType definition for details). If not supplied, artefact is considered to be un-versioned. 370 +|validFrom|xs:dateTime|(% style="width:700px" %)The validFrom attribute provides the inclusive start date for providing supplemental validity information about the version. 371 +|validTo|xs:dateTime|(% style="width:700px" %)The validTo attribute provides the inclusive end date for providing supplemental validity information about the version. 369 369 370 370 Element Documentation: 371 371 372 -|**Name**|**Type**|**Documentation** 373 -|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. 374 -|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. 375 -|Name|TextType|Name provides for a human-readable name for the object. This may be provided in multiple, parallel language-equivalent forms. 376 -|Description|TextType|Description provides for a longer human-readable description of the object. This may be provided in multiple, parallel language-equivalent forms. 375 +(% style="width:1004.29px" %) 376 +|**Name**|**Type**|(% style="width:727px" %)**Documentation** 377 +|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. 378 +|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. 379 +|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. 380 +|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. 377 377 378 -** *MaintainableBaseType*:** MaintainableBaseType is an abstract type that only serves the purpose of forming the base for the actual MaintainableType. The purpose of this type is to restrict the VersionableType to require the id attribute.382 +//**MaintainableBaseType:**// MaintainableBaseType is an abstract type that only serves the purpose of forming the base for the actual MaintainableType. The purpose of this type is to restrict the VersionableType to require the id attribute. 379 379 380 380 Derivation: 381 381 ... ... @@ -393,23 +393,25 @@ 393 393 394 394 Attribute Documentation: 395 395 396 -|**Name**|**Type**|**Documentation** 397 -|id|IDType|The id is the identifier for the object. 398 -|urn|MaintainableUrnType|The urn attribute holds a valid SDMX Registry URN (see SDMX Registry Specification for details). 399 -|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. 400 -|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. 401 -|validFrom|xs:dateTime|The validFrom attribute provides the inclusive start date for providing supplemental validity information about the version. 402 -|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. 403 403 404 404 Element Documentation: 405 405 406 -|**Name**|**Type**|**Documentation** 407 -|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. 408 -|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. 409 -|Name|TextType|Name provides for a human-readable name for the object. This may be provided in multiple, parallel language-equivalent forms. 410 -|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. 411 411 412 -** *MaintainableType*:** MaintainableType is an abstract base type for all maintainable objects.418 +//**MaintainableType:**// MaintainableType is an abstract base type for all maintainable objects. 413 413 414 414 Derivation: 415 415 ... ... @@ -428,26 +428,28 @@ 428 428 429 429 Attribute Documentation: 430 430 431 -|**Name**|**Type**|**Documentation** 432 -|id|IDType|The id is the identifier for the object. 433 -|urn|MaintainableUrnType|The urn attribute holds a valid SDMX Registry URN (see SDMX Registry Specification for details). 434 -|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. 435 -|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. 436 -|validFrom|xs:dateTime|The validFrom attribute provides the inclusive start date for providing supplemental validity information about the version. 437 -|validTo|xs:dateTime|The validTo attribute provides the inclusive end date for providing supplemental validity information about the version. 438 -|agencyID|NestedNCNameIDType|The agencyID must be provided, and identifies the maintenance agency of the object. 439 -|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. 440 -|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. 441 -|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. 442 -|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’. 443 443 444 444 Element Documentation: 445 445 446 -|**Name**|**Type**|**Documentation** 447 -|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. 448 -|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. 449 -|Name|TextType|Name provides for a human-readable name for the object. This may be provided in multiple, parallel language-equivalent forms. 450 -|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. 451 451 452 452 **ReferencePeriodType:** Specifies the inclusive start and end times. 453 453 ... ... @@ -459,9 +459,10 @@ 459 459 460 460 Attribute Documentation: 461 461 462 -|**Name**|**Type**|**Documentation** 463 -|startTime|xs:dateTime|The startTime attributes contains the inclusive start date for the reference period. 464 -|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. 465 465 466 466 **QueryableDataSourceType:** QueryableDataSourceType describes a data source which is accepts an standard SDMX Query message and responds appropriately. 467 467 ... ... @@ -473,16 +473,18 @@ 473 473 474 474 Attribute Documentation: 475 475 476 -|**Name**|**Type**|**Documentation** 477 -|isRESTDatasource|xs:boolean|The isRESTDatasource attribute indicates, if true, that the queryable data source is accessible via the REST protocol. 478 -|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. 479 479 480 480 Element Documentation: 481 481 482 -|**Name**|**Type**|**Documentation** 483 -|DataURL|xs:anyURI|DataURL contains the URL of the data source. 484 -|WSDLURL|xs:anyURI|WSDLURL provides the location of a WSDL instance on the internet which describes the queryable data source. 485 -|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. 486 486 487 487 **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. 488 488 ... ... @@ -490,12 +490,13 @@ 490 490 xml:lang? 491 491 492 492 Content: 493 -{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} 494 494 495 495 Attribute Documentation: 496 496 497 -|**Name**|**Type**|**Documentation** 498 -|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 499 499 500 500 ***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). 501 501 ... ... @@ -507,23 +507,25 @@ 507 507 508 508 Attribute Documentation: 509 509 510 -|**Name**|**Type**|**Documentation** 511 -|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. 512 -|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located. 513 -|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. 514 -|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. 515 -|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. 516 -|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. 517 -|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. 518 518 519 519 Element Documentation: 520 520 521 -|**Name**|**Type**|**Documentation** 522 -|ProvisionAgreement|ProvisionAgreementRe ferenceType|ProvisionAgreement references a provision agreement which the data or metadata is reported against. 523 -|StructureUsage|StructureUsageRefere nceType|StructureUsage references a flow which the data or metadata is reported against. 524 -|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. 525 525 526 -** *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. 527 527 528 528 Derivation: 529 529 ... ... @@ -538,21 +538,23 @@ 538 538 539 539 Attribute Documentation: 540 540 541 -|**Name**|**Type**|**Documentation** 542 -|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. 543 -|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located. 544 -|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. 545 -|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. 546 -|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. 547 -|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. 548 -|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. 549 549 550 550 Element Documentation: 551 551 552 -|**Name**|**Type**|**Documentation** 553 -|ProvisionAgreement|ProvisionAgreementRe ferenceType|ProvisionAgreement references a provision agreement which the data is reported against. 554 -|StructureUsage|DataflowReferenceTyp e|StructureUsage references a dataflow which the data is reported against. 555 -|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. 556 556 557 557 **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. 558 558 ... ... @@ -570,23 +570,25 @@ 570 570 571 571 Attribute Documentation: 572 572 573 -|**Name**|**Type**|**Documentation** 574 -|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. 575 -|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located. 576 -|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. 577 -|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. 578 -|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. 579 -|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. 580 -|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. 581 581 582 582 Element Documentation: 583 583 584 -|**Name**|**Type**|**Documentation** 585 -|ProvisionAgreement|ProvisionAgreementReferenceType|ProvisionAgreement references a provision agreement which the data is reported against. 586 -|StructureUsage|DataflowReferenceType|StructureUsage references a dataflow which the data is reported against. 587 -|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. 588 588 589 -** *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. 590 590 591 591 Derivation: 592 592 ... ... @@ -601,19 +601,21 @@ 601 601 602 602 Attribute Documentation: 603 603 604 -|**Name**|**Type**|**Documentation** 605 -|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. 606 -|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located. 607 -|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. 608 -|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. 609 -|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. 610 610 611 611 Element Documentation: 612 612 613 -|**Name**|**Type**|**Documentation** 614 -|ProvisionAgreement|ProvisionAgreementReferenceType|ProvisionAgreement references a provision agreement which the metadata is reported against. 615 -|StructureUsage|MetadataflowReferenceType|StructureUsage references a metadataflow which the metadata is reported against. 616 -|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. 617 617 618 618 **GenericMetadataStructureType:** GenericMetadataStructureType defines the structural information for a generic metadata message. 619 619 ... ... @@ -631,18 +631,20 @@ 631 631 632 632 Attribute Documentation: 633 633 634 -|**Name**|**Type**|**Documentation** 635 -|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. 636 -|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located. 637 -|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. 638 -|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. 639 639 640 640 Element Documentation: 641 641 642 -|**Name**|**Type**|**Documentation** 643 -|ProvisionAgreement|ProvisionAgreementReferenceType|ProvisionAgreement references a provision agreement which the metadata is reported against. 644 -|StructureUsage|MetadataflowReferenceType|StructureUsage references a metadataflow which the metadata is reported against. 645 -|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. 646 646 647 647 === 2.1.4 Simple Types === 648 648 ... ... @@ -867,8 +867,9 @@ 867 867 868 868 Enumerations: 869 869 870 -|**Value**|**Documentation** 871 -|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. 872 872 873 873 **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. 874 874 ... ... @@ -876,11 +876,12 @@ 876 876 877 877 Enumerations: 878 878 879 -|**Value**|**Documentation** 880 -|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. 881 -|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. 882 -|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. 883 -|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. 884 884 885 885 **WildCardValueType:** WildCardValueType is a single value code list, used to include the '%' character - indicating that an entire field is wild carded. 886 886 ... ... @@ -888,8 +888,9 @@ 888 888 889 889 Enumerations: 890 890 891 -|**Value**|**Documentation** 892 -|%|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. 893 893 894 894 **CascadeSelectionType:** 895 895 ... ... @@ -902,8 +902,9 @@ 902 902 903 903 Enumerations: 904 904 905 -|**Value**|**Documentation** 906 -|excluderoot| 930 +(% style="width:504.294px" %) 931 +|(% style="width:165px" %)**Value**|(% style="width:336px" %)**Documentation** 932 +|(% style="width:165px" %)excluderoot|(% style="width:336px" %) 907 907 908 908 **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". 909 909 ... ... @@ -916,9 +916,10 @@ 916 916 917 917 Enumerations: 918 918 919 -|**Value**|**Documentation** 920 -|AllDimensions|AllDimensions notes that the cross sectional format shall be flat; that is all dimensions should be contained at the observation level. 921 -|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. 922 922 923 923 **DataType:** DataTypeType provides an enumerated list of the types of data formats allowed as the for the representation of an object. 924 924 ... ... @@ -926,51 +926,52 @@ 926 926 927 927 Enumerations: 928 928 929 -|**Value**|**Documentation** 930 -|String|A string datatype corresponding to W3C XML Schema's xs:string datatype. 931 -|Alpha|A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z. 932 -|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. 933 -|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. 934 -|BigInteger|An integer datatype corresponding to W3C XML Schema's xs:integer datatype. 935 -|Integer|An integer datatype corresponding to W3C XML Schema's xs:int datatype. 936 -|Long|A numeric datatype corresponding to W3C XML Schema's xs:long datatype. 937 -|Short|A numeric datatype corresponding to W3C XML Schema's xs:short datatype. 938 -|Decimal|A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype. 939 -|Float|A numeric datatype corresponding to W3C XML Schema's xs:float datatype. 940 -|Double|A numeric datatype corresponding to W3C XML Schema's xs:double datatype. 941 -|Boolean|A datatype corresponding to W3C XML Schema's xs:boolean datatype. 942 -|URI|A datatype corresponding to W3C XML Schema's xs:anyURI datatype. 943 -|Count|A simple incrementing Integer type. The isSequence facet must be set to true, and the interval facet must be set to "1". 944 -|InclusiveValueRange|This value indicates that the startValue and endValue attributes provide the inclusive boundaries of a numeric range of type xs:decimal. 945 -|ExclusiveValueRange|This value indicates that the startValue and endValue attributes provide the exclusive boundaries of a numeric range, of type xs:decimal. 946 -|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. 947 -|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. 948 -|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. 949 -|BasicTimePeriod|BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time. 950 -|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. 951 -|GregorianYear|A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601. 952 -|GregorianYearMonth|A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601. 953 -|GregorianDay|A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601. 954 -|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. 955 -|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. 956 -|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. 957 -|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. 958 -|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. 959 -|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. 960 -|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. 961 -|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. 962 -|DateTime|A time datatype corresponding to W3C XML Schema's xs:dateTime datatype. 963 -|TimeRange|TimeRange defines a time period by providing a distinct start (date or date time) and a duration. 964 -|Month|A time datatype corresponding to W3C XML Schema's xs:gMonth datatype. 965 -|MonthDay|A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype. 966 -|Day|A time datatype corresponding to W3C XML Schema's xs:gDay datatype. 967 -|Time|A time datatype corresponding to W3C XML Schema's xs:time datatype. 968 -|Duration|A time datatype corresponding to W3C XML Schema's xs:duration datatype. 969 -|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. 970 -|XHTML|This value indicates that the content of the component can contain XHTML markup. 971 -|KeyValues|This value indicates that the content of the component will be data key (a set of dimension references and values for the dimensions). 972 -|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. 973 -|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. 974 974 975 975 **BasicComponentDataType:** BasicComponentDataType provides an enumerated list of the types of characters allowed in the textType attribute for all non-target object components. 976 976 ... ... @@ -978,48 +978,49 @@ 978 978 979 979 Enumerations: 980 980 981 -|**Value**|**Documentation** 982 -|String|A string datatype corresponding to W3C XML Schema's xs:string datatype. 983 -|Alpha|A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z. 984 -|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. 985 -|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. 986 -|BigInteger|An integer datatype corresponding to W3C XML Schema's xs:integer datatype. 987 -|Integer|An integer datatype corresponding to W3C XML Schema's xs:int datatype. 988 -|Long|A numeric datatype corresponding to W3C XML Schema's xs:long datatype. 989 -|Short|A numeric datatype corresponding to W3C XML Schema's xs:short datatype. 990 -|Decimal|A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype. 991 -|Float|A numeric datatype corresponding to W3C XML Schema's xs:float datatype. 992 -|Double|A numeric datatype corresponding to W3C XML Schema's xs:double datatype. 993 -|Boolean|A datatype corresponding to W3C XML Schema's xs:boolean datatype. 994 -|URI|A datatype corresponding to W3C XML Schema's xs:anyURI datatype. 995 -|Count|A simple incrementing Integer type. The isSequence facet must be set to true, and the interval facet must be set to "1". 996 -|InclusiveValueRange|This value indicates that the startValue and endValue attributes provide the inclusive boundaries of a numeric range of type xs:decimal. 997 -|ExclusiveValueRange|This value indicates that the startValue and endValue attributes provide the exclusive boundaries of a numeric range, of type xs:decimal. 998 -|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. 999 -|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. 1000 -|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. 1001 -|BasicTimePeriod|BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time. 1002 -|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. 1003 -|GregorianYear|A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601. 1004 -|GregorianYearMonth|A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601. 1005 -|GregorianDay|A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601. 1006 -|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. 1007 -|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. 1008 -|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. 1009 -|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. 1010 -|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. 1011 -|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. 1012 -|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. 1013 -|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. 1014 -|DateTime|A time datatype corresponding to W3C XML Schema's xs:dateTime datatype. 1015 -|TimeRange|TimeRange defines a time period by providing a distinct start (date or date time) and a duration. 1016 -|Month|A time datatype corresponding to W3C XML Schema's xs:gMonth datatype. 1017 -|MonthDay|A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype. 1018 -|Day|A time datatype corresponding to W3C XML Schema's xs:gDay datatype. 1019 -|Time|A time datatype corresponding to W3C XML Schema's xs:time datatype. 1020 -|Duration|A time datatype corresponding to W3C XML Schema's xs:duration datatype. 1021 -|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. 1022 -|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. 1023 1023 1024 1024 **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. 1025 1025 ... ... @@ -1027,47 +1027,48 @@ 1027 1027 1028 1028 Enumerations: 1029 1029 1030 -|**Value**|**Documentation** 1031 -|String|A string datatype corresponding to W3C XML Schema's xs:string datatype. 1032 -|Alpha|A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z. 1033 -|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. 1034 -|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. 1035 -|BigInteger|An integer datatype corresponding to W3C XML Schema's xs:integer datatype. 1036 -|Integer|An integer datatype corresponding to W3C XML Schema's xs:int datatype. 1037 -|Long|A numeric datatype corresponding to W3C XML Schema's xs:long datatype. 1038 -|Short|A numeric datatype corresponding to W3C XML Schema's xs:short datatype. 1039 -|Decimal|A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype. 1040 -|Float|A numeric datatype corresponding to W3C XML Schema's xs:float datatype. 1041 -|Double|A numeric datatype corresponding to W3C XML Schema's xs:double datatype. 1042 -|Boolean|A datatype corresponding to W3C XML Schema's xs:boolean datatype. 1043 -|URI|A datatype corresponding to W3C XML Schema's xs:anyURI datatype. 1044 -|Count|A simple incrementing Integer type. The isSequence facet must be set to true, and the interval facet must be set to "1". 1045 -|InclusiveValueRange|This value indicates that the startValue and endValue attributes provide the inclusive boundaries of a numeric range of type xs:decimal. 1046 -|ExclusiveValueRange|This value indicates that the startValue and endValue attributes provide the exclusive boundaries of a numeric range, of type xs:decimal. 1047 -|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. 1048 -|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. 1049 -|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. 1050 -|BasicTimePeriod|BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time. 1051 -|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. 1052 -|GregorianYear|A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601. 1053 -|GregorianYearMonth|A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601. 1054 -|GregorianDay|A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601. 1055 -|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. 1056 -|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. 1057 -|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. 1058 -|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. 1059 -|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. 1060 -|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. 1061 -|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. 1062 -|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. 1063 -|DateTime|A time datatype corresponding to W3C XML Schema's xs:dateTime datatype. 1064 -|TimeRange|TimeRange defines a time period by providing a distinct start (date or date time) and a duration. 1065 -|Month|A time datatype corresponding to W3C XML Schema's xs:gMonth datatype. 1066 -|MonthDay|A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype. 1067 -|Day|A time datatype corresponding to W3C XML Schema's xs:gDay datatype. 1068 -|Time|A time datatype corresponding to W3C XML Schema's xs:time datatype. 1069 -|Duration|A time datatype corresponding to W3C XML Schema's xs:duration datatype. 1070 -|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. 1071 1071 1072 1072 **TimeDataType:** TimeDataType restricts SimpleDataType to specify the allowable data types for representing a time value. 1073 1073 ... ... @@ -1075,24 +1075,25 @@ 1075 1075 1076 1076 Enumerations: 1077 1077 1078 -|**Value**|**Documentation** 1079 -|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. 1080 -|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. 1081 -|BasicTimePeriod|BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time. 1082 -|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. 1083 -|GregorianYear|A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601. 1084 -|GregorianYearMonth|A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601. 1085 -|GregorianDay|A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601. 1086 -|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. 1087 -|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. 1088 -|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. 1089 -|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. 1090 -|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. 1091 -|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. 1092 -|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. 1093 -|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. 1094 -|DateTime|A time datatype corresponding to W3C XML Schema's xs:dateTime datatype. 1095 -|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. 1096 1096 1097 1097 **UrnPrefixPart:** This is validates the first part of the URN (urn:sdmx.org.infomodel.<package>.<class=). It is intended to be further restricted. 1098 1098 ... ... @@ -1127,57 +1127,19 @@ 1127 1127 **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. 1128 1128 1129 1129 Derived by restriction of UrnMaintainableIdPart. 1130 -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]~*~*)?\). 1131 1131 ))) 1132 1132 1133 -*)?\). 1134 - 1135 1135 **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. 1136 1136 1137 1137 Derived by restriction of UrnMaintainableIdPart. 1138 -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*)\+?))\). 1139 1139 1140 -((( 1141 -0|[1-9]\d*)\+?)(\.((0|[1-9]\d* 1142 -))) 1143 - 1144 -{2}\).*.+\ 1145 - 1146 -((( 1147 -0|[1-9]\d*))(\.((0|[1-9]\d*)\+?))(\.((0|[1-9]\d* 1148 -))) 1149 - 1150 -\).*.+\ 1151 - 1152 -((( 1153 -0|[1-9]\d*)\+?)(\.((0|[1-9]\d* 1154 -))) 1155 - 1156 -(\.((0|[1-9]\d*)\+?))\). 1157 - 1158 1158 **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. 1159 1159 1160 1160 Derived by restriction of WildcardUrnMaintainableIdPart. 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]*~)~)~)*)?\).*.+\ 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*)\+?))\).*.+\(\*\). 1162 1162 1163 -((( 1164 -0|[1-9]\d*)\+?)(\.((0|[1-9]\d* 1165 -))) 1166 - 1167 -{2}\).*.+\ 1168 - 1169 -((( 1170 -0|[1-9]\d*))(\.((0|[1-9]\d*)\+?))(\.((0|[1-9]\d* 1171 -))) 1172 - 1173 -\).*.+\ 1174 - 1175 -((( 1176 -0|[1-9]\d*)\+?)(\.((0|[1-9]\d* 1177 -))) 1178 - 1179 -(\.((0|[1-9]\d*)\+?))\).*.+\(\*\). 1180 - 1181 1181 **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. 1182 1182 1183 1183 Derived by restriction of UrnVersionPart. ... ... @@ -1703,12 +1703,12 @@ 1703 1703 Derived by restriction of ComponentUrnReferenceType. 1704 1704 Regular Expression Pattern: . +\.datastructure\.AttributeDescriptor=.+ 1705 1705 1706 -**DataAttributeReferenceType:** A reference type for a data attribute. 1699 +**DataAttributeReferenceType:** A reference type for a data [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]]. 1707 1707 1708 1708 Derived by restriction of ComponentUrnReferenceType. 1709 1709 Regular Expression Pattern: . +\.datastructure\.DataAttribute=.+ 1710 1710 1711 -**DataflowReferenceType:** A reference type for a dataflow. 1704 +**DataflowReferenceType:** A reference type for a [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]. 1712 1712 1713 1713 Derived by restriction of StructureUsageReferenceType. 1714 1714 Regular Expression Pattern: . +\.datastructure\.Dataflow=.+ ... ... @@ -1718,42 +1718,42 @@ 1718 1718 Derived by restriction of StructureReferenceType. 1719 1719 Regular Expression Pattern: . +\.datastructure\.DataStructure=.+ 1720 1720 1721 -**DimensionReferenceType:** A reference type for a dimension. 1714 +**DimensionReferenceType:** A reference type for a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]. 1722 1722 1723 1723 Derived by restriction of ComponentUrnReferenceType. 1724 1724 Regular Expression Pattern: . +\.datastructure\.Dimension=.+ 1725 1725 1726 -**DimensionDescriptorReferenceType:** A reference type for a dimension descriptor. 1719 +**DimensionDescriptorReferenceType:** A reference type for a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] descriptor. 1727 1727 1728 1728 Derived by restriction of ComponentUrnReferenceType. 1729 1729 Regular Expression Pattern: . +\.datastructure\.DimensionDescriptor=.+ 1730 1730 1731 -**GroupDimensionDescriptorReferenceType:** A reference type for a group dimension descriptor. 1724 +**GroupDimensionDescriptorReferenceType:** A reference type for a group [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] descriptor. 1732 1732 1733 1733 Derived by restriction of ComponentUrnReferenceType. 1734 1734 Regular Expression Pattern: . +\.datastructure\.GroupDimensionDescriptor=.+ 1735 1735 1736 -**MeasureReferenceType:** A reference type for a measure. 1729 +**MeasureReferenceType:** A reference type for a [[measure>>doc:sdmx:Glossary.Measure.WebHome]]. 1737 1737 1738 1738 Derived by restriction of ComponentUrnReferenceType. 1739 1739 Regular Expression Pattern: . +\.datastructure\.Measure=.+ 1740 1740 1741 -**MeasureDescriptorReferenceType:** A reference type for a measure descriptor. 1734 +**MeasureDescriptorReferenceType:** A reference type for a [[measure>>doc:sdmx:Glossary.Measure.WebHome]] descriptor. 1742 1742 1743 1743 Derived by restriction of ComponentUrnReferenceType. 1744 1744 Regular Expression Pattern: . +\.datastructure\.MeasureDescriptor=.+ 1745 1745 1746 -**TimeDimensionReferenceType:** A reference type for a time dimension. 1739 +**TimeDimensionReferenceType:** A reference type for a time [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]. 1747 1747 1748 1748 Derived by restriction of ComponentUrnReferenceType. 1749 1749 Regular Expression Pattern: . +\.datastructure\.TimeDimension=.+ 1750 1750 1751 -**MetadataAttributeReferenceType:** A reference type for a metadata attribute. 1744 +**MetadataAttributeReferenceType:** A reference type for a metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]]. 1752 1752 1753 1753 Derived by restriction of UrnReferenceType. 1754 1754 Regular Expression Pattern: . +\.metadatastructure\.MetadataAttribute=.+ 1755 1755 1756 -**MetadataflowReferenceType:** A reference type for a metadataflow. 1749 +**MetadataflowReferenceType:** A reference type for a [[metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]]. 1757 1757 1758 1758 Derived by restriction of StructureUsageReferenceType. 1759 1759 Regular Expression Pattern: . +\.metadatastructure\.Metadataflow=.+ ... ... @@ -1783,42 +1783,42 @@ 1783 1783 Derived by restriction of UrnReferenceType. 1784 1784 Regular Expression Pattern: . +\.process\.Transition=.+ 1785 1785 1786 -**DataConstraintReferenceType:** A reference type for a data constraint. 1779 +**DataConstraintReferenceType:** A reference type for a data (% style="color:#e74c3c" %)constraint(%%). 1787 1787 1788 1788 Derived by restriction of ConstraintReferenceType. 1789 1789 Regular Expression Pattern: . +\.registry\.DataConstraint=.+ 1790 1790 1791 -**MetadataConstraintReferenceType:** A reference type for a metadata constraint. 1784 +**MetadataConstraintReferenceType:** A reference type for a metadata (% style="color:#e74c3c" %)constraint(%%). 1792 1792 1793 1793 Derived by restriction of ConstraintReferenceType. 1794 1794 Regular Expression Pattern: . +\.registry\.MetadataConstraint=.+ 1795 1795 1796 -**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]]. 1797 1797 1798 1798 Derived by restriction of MaintainableUrnReferenceType. 1799 1799 Regular Expression Pattern: . +\.registry\.MetadataProvisionAgreement=.+ 1800 1800 1801 -**ProvisionAgreementReferenceType:** A reference type for a provision agreement. 1794 +**ProvisionAgreementReferenceType:** A reference type for a [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]. 1802 1802 1803 1803 Derived by restriction of MaintainableUrnReferenceType. 1804 1804 Regular Expression Pattern: . +\.registry\.ProvisionAgreement=.+ 1805 1805 1806 -**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(%%). 1807 1807 1808 1808 Derived by restriction of MaintainableUrnReferenceType. 1809 1809 Regular Expression Pattern: . +\.structuremapping\.CategorySchemeMap=.+ 1810 1810 1811 -**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(%%). 1812 1812 1813 1813 Derived by restriction of MaintainableUrnReferenceType. 1814 1814 Regular Expression Pattern: . +\.structuremapping\.ConceptSchemeMap=.+ 1815 1815 1816 -**DatePatternMapReferenceType:** A reference type for a date pattern map. 1809 +**DatePatternMapReferenceType:** A reference type for a date pattern (% style="color:#e74c3c" %)map(%%). 1817 1817 1818 1818 Derived by restriction of ComponentUrnReferenceType. 1819 1819 Regular Expression Pattern: . +\.structuremapping\.DatePatternMap=.+ 1820 1820 1821 -**EpochMapReferenceType:** A reference type for an epoch map. 1814 +**EpochMapReferenceType:** A reference type for an epoch (% style="color:#e74c3c" %)map(%%). 1822 1822 1823 1823 Derived by restriction of ComponentUrnReferenceType. 1824 1824 Regular Expression Pattern: . +\.structuremapping\.EpochMap=.+ ... ... @@ -1828,22 +1828,22 @@ 1828 1828 Derived by restriction of ComponentUrnReferenceType. 1829 1829 Regular Expression Pattern: . +\.structuremapping\.FrequencyFormatMapping=.+ 1830 1830 1831 -**OrganisationSchemeMapReferenceType:** A reference type for a organisation scheme map. 1824 +**OrganisationSchemeMapReferenceType:** A reference type for a organisation scheme (% style="color:#e74c3c" %)map(%%). 1832 1832 1833 1833 Derived by restriction of MaintainableUrnReferenceType. 1834 1834 Regular Expression Pattern: . +\.structuremapping\.OrganisationSchemeMap=.+ 1835 1835 1836 -**ReportingTaxonomyMapReferenceType:** A reference type for a reporting taxonomy map. 1829 +**ReportingTaxonomyMapReferenceType:** A reference type for a reporting taxonomy (% style="color:#e74c3c" %)map(%%). 1837 1837 1838 1838 Derived by restriction of MaintainableUrnReferenceType. 1839 1839 Regular Expression Pattern: . +\.structuremapping\.ReportingTaxonomyMap=.+ 1840 1840 1841 -**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(%%). 1842 1842 1843 1843 Derived by restriction of MaintainableUrnReferenceType. 1844 1844 Regular Expression Pattern: . +\.structuremapping\.RepresentationMap=.+ 1845 1845 1846 -**StructureMapReferenceType:** A reference type for a structure map. 1839 +**StructureMapReferenceType:** A reference type for a structure (% style="color:#e74c3c" %)map(%%). 1847 1847 1848 1848 Derived by restriction of MaintainableUrnReferenceType. 1849 1849 Regular Expression Pattern: . +\.structuremapping\.StructureMap=.+ ... ... @@ -1898,84 +1898,86 @@ 1898 1898 Derived by restriction of MaintainableUrnReferenceType. 1899 1899 Regular Expression Pattern: . +\.transformation\.UserDefinedOperatorScheme=.+ 1900 1900 1901 -**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. 1902 1902 1903 1903 Derived by restriction of ComponentUrnReferenceType. 1904 1904 Regular Expression Pattern: . +\.transformation\.VtlCodelistMapping=.+.+\.transformation\.VtlConceptMapping=.+.+\.transformation\.VtlDataflowMapping=.+ 1905 1905 1906 -**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. 1907 1907 1908 1908 Derived by restriction of MaintainableUrnReferenceType. 1909 1909 Regular Expression Pattern: . +\.transformation\.VtlMappingScheme=.+ 1910 1910 1911 -**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. 1912 1912 1913 1913 Union of: 1914 1914 1915 1915 LegacyVersionNumberType, SemanticVersionNumberType, SemanticVersionReferenceType. 1916 1916 1917 -**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 "+". 1918 1918 1919 1919 Derived by restriction of xs:string. 1913 + 1920 1920 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*)\+?)) 1921 1921 1922 -**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. 1923 1923 1924 1924 Union of: 1925 1925 1926 1926 LegacyVersionNumberType, SemanticVersionNumberType, SemanticVersionReferenceType, WildcardType. 1927 1927 1928 -**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. 1929 1929 1930 1930 Derived by restriction of xs:string. 1931 1931 1932 1932 Enumerations: 1933 1933 1934 -|**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. 1935 1935 1936 - |\*|Indicates that anyvalue ofthe 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, \_, -, $. 1937 1937 1938 -**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, \_, -, $. 1939 - 1940 1940 Derived by restriction of xs:string. 1941 1941 Regular Expression Pattern: [A-Za-z0-9_@$\-]+(\.[A-Za-z0-9_@$\-]+) 1942 1942 1943 -**TwoLevelIDType:** TwoLevelIDType defines an identifier with exactly two levels. 1937 +**TwoLevelIDType:** TwoLevelIDType defines an identifier with exactly two (% style="color:#e74c3c" %)levels(%%). 1944 1944 1945 1945 Derived by restriction of NestedIDType. 1946 1946 Regular Expression Pattern: [A-Za-z0-9_@$\-]+\.[A-Za-z0-9_@$\-]+ 1947 1947 1948 -**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, \_, -, $. 1949 1949 1950 1950 Derived by restriction of NestedIDType. 1951 1951 Regular Expression Pattern: [A-Za-z0-9_@$\-]+ 1952 1952 1953 -**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. 1954 1954 1955 1955 Derived by restriction of IDType. 1956 1956 Regular Expression Pattern: [A-Za-z][A-Za-z0-9_\-] 1957 1957 1958 -**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. 1959 1959 1960 1960 Derived by restriction of NestedIDType. 1961 1961 Regular Expression Pattern: [A-Za-z][A-Za-z0-9_\-]*(\.[A-Za-z][A-Za-z0-9_\-]*) 1962 1962 1963 -**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). 1964 1964 1965 1965 Derived by restriction of NestedNCNameIDType. 1966 1966 Regular Expression Pattern: [A-Za-z][A-Za-z0-9_\-] 1967 1967 1968 -**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. 1969 1969 1970 1970 Union of: 1971 1971 LegacyVersionNumberType, SemanticVersionNumberType. 1972 1972 1973 -**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]). 1974 1974 1975 1975 Derived by restriction of xs:string. 1976 1976 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]*~)~)~)*)? 1977 1977 1978 -**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. 1979 1979 1980 1980 Derived by restriction of xs:string. 1975 + 1981 1981 Regular Expression Pattern: (0|[1-9]\d*)(\.(0|[1-9]\d*))?