Changes for page Part II.Common Namespace

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

From version 6.2
edited by Helena K.
on 2025/07/03 12:21
Change comment: There is no comment for this version
To version 6.17
edited by Helena K.
on 2025/07/03 12:40
Change comment: There is no comment for this version

Summary

Details

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