Changes for page Part II.Common Namespace

Last modified by Helena K. on 2026/06/09 12:56

From 6.6 to 6.7 From 15.2 to 15.3

From version 6.7

edited by Helena K.
on 2025/07/03 12:24

Change comment: There is no comment for this version

To version 15.2

edited by Helena K.
on 2026/06/09 12:29

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Objects (0 modified, 1 added, 1 removed)
- SUZ.Methodology.Code.MethodologyClass[0]
- SKMS.Methodology.Code.MethodologyClass[0]

Details

Page properties

Title

@@ -1,1 +1,1 @@
--Part II.Common: This details the common namespace schemas
++Part II.Common Namespace

Content

@@ -4,17 +4,17 @@
  = 1 Introduction =
--The common namespace defines a collection of constructs that are reused across the various [[components>>doc:sdmx:Glossary.Component.WebHome]] of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]. Most important of these are the referencing mechanism. The goal of the reference construct was to define a generic structure that could be processed uniformly regardless of the context where the reference was used. But it was also important that references be required to be complete whenever possible.
++The common namespace defines a collection of constructs that are reused across the various components of SDMX. Most important of these are the referencing mechanism. The goal of the reference construct was to define a generic structure that could be processed uniformly regardless of the context where the reference was used. But it was also important that references be required to be complete whenever possible.
--Any object can be referenced either explicitly with a URN or by a set of complete reference fields. To meet the previously stated requirements, and very general mechanism was created based on the URN structure of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] objects for these reference fields.
++Any object can be referenced either explicitly with a URN or by a set of complete reference fields. To meet the previously stated requirements, and very general mechanism was created based on the URN structure of SDMX objects for these reference fields.
  There was also a requirement that the references be able to be refined to meet particular needs outside of the common namespace. An example of this is in the metadata structure specific schemas. It is a requirement that if a target object is specified as having to come from a particular scheme, that a type based on the reference structure be created that enforced the requirement.
--Typically, this would not have been an issues as all of the [[components>>doc:sdmx:Glossary.Component.WebHome]] which make up the references are of atomic types, and therefore can be expressed as XML [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] which are easily refined and restricted since the XML Schema design principles in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] always treats [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] as unqualified.
++Typically, this would not have been an issues as all of the components which make up the references are of atomic types, and therefore can be expressed as XML attributes which are easily refined and restricted since the XML Schema design principles in SDMX always treats attributes as unqualified.
  However, the requirement to allow both a URN and/or a complete set of reference field necessitate that these properties be contained in elements. The fact that they are elements typically would mean that the only way a refinement outside of the namespace could happen was if the element were global and allowed for substitutions. This however would mean that every distinct type of referenced object would have a unique set of elements. This moved away from the requirement that the structure be easy to process regardless of context.
--The solution to this problem was to deviate from the normal [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] XML Schema design principle of always using qualified elements and allowing for these to be unqualified. Doing so allows other namespace to derive from these types and place further restrictions on what can be referenced. The deviation from this principle was justified in that it met all of the requirements and was not deemed to major of a shift since these properties normally would have been expressed as unqualified [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] if it weren't for the complete reference requirement.
++The solution to this problem was to deviate from the normal SDMX XML Schema design principle of always using qualified elements and allowing for these to be unqualified. Doing so allows other namespace to derive from these types and place further restrictions on what can be referenced. The deviation from this principle was justified in that it met all of the requirements and was not deemed to major of a shift since these properties normally would have been expressed as unqualified attributes if it weren't for the complete reference requirement.
  == 2 Schema Documentation ==
@@ -52,7 +52,7 @@
  === 2.1.3 Complex Types ===
--***ValueType*:** ValueType is an abstract class that is the basis for any component value that cannot be simply represented as a space-normalized value (e.g. in an XML attribute). Although its content is mixed, it should be restricted so that only character data or the Text or Structured text is used. See StringValueType, IntValueType, ObserverationalTimeValueType, TextValueType, and StructuredTextValueType for details.
++//**ValueType:**// ValueType is an abstract class that is the basis for any component value that cannot be simply represented as a space-normalized value (e.g. in an XML attribute). Although its content is mixed, it should be restricted so that only character data or the Text or Structured text is used. See StringValueType, IntValueType, ObserverationalTimeValueType, TextValueType, and StructuredTextValueType for details.
  Content:
  {text} x (Text\* | StructuredText\*)?
@@ -70,8 +70,8 @@
  ValueType (restriction)
     BooleanValueType
--Content:
++Content:
  **StringValueType:** StringValueType is a refinement of SimpleValueType limiting the content to be a string. This can be further refined with facets, patterns, etc.
  Derivation:
@@ -204,7 +204,7 @@
  |(% style="width:150px" %)**Name**|(% style="width:206px" %)**Type**|(% style="width:652px" %)**Documentation**
  |(% style="width:150px" %)Text|(% style="width:206px" %)TextType|(% style="width:652px" %)Text contains the text of the message, in parallel language values.
--***AnnotableType*:** AnnotableType is an abstract base type used for all annotable artefacts. Any type that provides for annotations should extend this type.
++//**AnnotableType:** //AnnotableType is an abstract base type used for all annotable artefacts. Any type that provides for annotations should extend this type.
  Content:
  Annotations?
@@ -290,7 +290,7 @@
  Derivation:
  AnnotableType (extension)
--   IdentifiableType*
++   IdentifiableType
  Attributes:
  id?, urn?, uri?
@@ -319,7 +319,7 @@
  AnnotableType (extension)
     IdentifiableType (extension)
--         NameableType*
++         NameableType
  Attributes:
  id?, urn?, uri?
@@ -351,7 +351,7 @@
  AnnotableType (extension)
     IdentifiableType (extension)
           NameableType (extension)
--               VersionableType*
++               VersionableType
  Attributes:
  id?, urn?, uri?, version?, validFrom?, validTo?
@@ -387,7 +387,7 @@
     IdentifiableType (extension)
           NameableType (extension)
                 VersionableType (restriction)
--                     MaintainableBaseType*
++                     MaintainableBaseType
  Attributes:
  id, urn?, uri?, version?, validFrom?, validTo?
@@ -421,10 +421,10 @@
  AnnotableType (extension)
     IdentifiableType (extension)
--         NameableType* (extension)
++         NameableType (extension)
                 VersionableType (restriction)
                       MaintainableBaseType (extension)
--                           MaintainableType*
++                           MaintainableType
  Attributes:
  id, urn?, uri?, version?, validFrom?, validTo?, agencyID, isPartialLanguage?, isExternalReference?, serviceURL?, structureURL?
@@ -505,10 +505,11 @@
  Attribute Documentation:
--|**Name**|**Type**|**Documentation**
--|xml:lang (default: en)|xs:language
++(% style="width:1009.29px" %)
++|(% style="width:228px" %)**Name**|(% style="width:221px" %)**Type**|(% style="width:699px" %)**Documentation**
++|(% style="width:228px" %)xml:lang (default: en)|(% style="width:221px" %)xs:language
--***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).
++//**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).
  Attributes:
  structureID, schemaURL?, namespace?, dimensionAtObservation?, explicitMeasures?, serviceURL?, structureURL?
@@ -518,28 +518,30 @@
  Attribute Documentation:
--|**Name**|**Type**|**Documentation**
--|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.
--|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located.
--|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.
--|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.
--|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.
--|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.
--|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.
++(% style="width:1003.29px" %)
++|**Name**|**Type**|(% style="width:598px" %)**Documentation**
++|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.
++|schemaURL|xs:anyURI|(% style="width:598px" %)The schemaURL attribute provides a location from which the structure specific schema can be located.
++|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.
++|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.
++|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.
++|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.
++|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.
  Element Documentation:
--|**Name**|**Type**|**Documentation**
--|ProvisionAgreement|ProvisionAgreementRe ferenceType|ProvisionAgreement references a provision agreement which the data or metadata is reported against.
--|StructureUsage|StructureUsageRefere nceType|StructureUsage references a flow which the data or metadata is reported against.
--|Structure|StructureReferenceTy pe|Structure references the structure which defines the structure of the data or metadata set.
++(% style="width:1005.29px" %)
++|(% style="width:188px" %)**Name**|(% style="width:287px" %)**Type**|(% style="width:527px" %)**Documentation**
++|(% style="width:188px" %)ProvisionAgreement|(% style="width:287px" %)ProvisionAgreementReferenceType|(% style="width:527px" %)ProvisionAgreement references a provision agreement which the data or metadata is reported against.
++|(% style="width:188px" %)StructureUsage|(% style="width:287px" %)StructureUsageReferenceType|(% style="width:527px" %)StructureUsage references a flow which the data or metadata is reported against.
++|(% 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.
--***DataStructureType*:** DataStructureType is an abstract base type the forms the basis for the structural information for a data set.
++//**DataStructureType:**// DataStructureType is an abstract base type the forms the basis for the structural information for a data set.
  Derivation:
  PayloadStructureType (restriction)
--   DataStructureType*
++   DataStructureType
  Attributes:
  structureID, schemaURL?, namespace?, dimensionAtObservation?, explicitMeasures?, serviceURL?, structureURL?
@@ -549,21 +549,23 @@
  Attribute Documentation:
--|**Name**|**Type**|**Documentation**
--|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.
--|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located.
--|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.
--|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.
--|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.
--|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.
--|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.
++(% style="width:1006.29px" %)
++|**Name**|**Type**|(% style="width:598px" %)**Documentation**
++|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.
++|schemaURL|xs:anyURI|(% style="width:598px" %)The schemaURL attribute provides a location from which the structure specific schema can be located.
++|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.
++|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.
++|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.
++|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.
++|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.
  Element Documentation:
--|**Name**|**Type**|**Documentation**
--|ProvisionAgreement|ProvisionAgreementRe ferenceType|ProvisionAgreement references a provision agreement which the data is reported against.
--|StructureUsage|DataflowReferenceTyp e|StructureUsage references a dataflow which the data is reported against.
--|Structure|DataStructureReferen ceType|Structure references the data structure definition which defines the structure of the data.
++(% style="width:1012.29px" %)
++|(% style="width:184px" %)**Name**|(% style="width:295px" %)**Type**|(% style="width:530px" %)**Documentation**
++|(% style="width:184px" %)ProvisionAgreement|(% style="width:295px" %)ProvisionAgreementReferenceType|(% style="width:530px" %)ProvisionAgreement references a provision agreement which the data is reported against.
++|(% style="width:184px" %)StructureUsage|(% style="width:295px" %)DataflowReferenceType|(% style="width:530px" %)StructureUsage references a dataflow which the data is reported against.
++|(% style="width:184px" %)Structure|(% style="width:295px" %)DataStructureReferenceType|(% style="width:530px" %)Structure references the data structure definition which defines the structure of the data.
  **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.
@@ -581,28 +581,30 @@
  Attribute Documentation:
--|**Name**|**Type**|**Documentation**
--|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.
--|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located.
--|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.
--|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.
--|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.
--|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.
--|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.
++(% style="width:1010.29px" %)
++|**Name**|**Type**|(% style="width:562px" %)**Documentation**
++|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.
++|schemaURL|xs:anyURI|(% style="width:562px" %)The schemaURL attribute provides a location from which the structure specific schema can be located.
++|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.
++|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.
++|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.
++|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.
++|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.
  Element Documentation:
--|**Name**|**Type**|**Documentation**
--|ProvisionAgreement|ProvisionAgreementReferenceType|ProvisionAgreement references a provision agreement which the data is reported against.
--|StructureUsage|DataflowReferenceType|StructureUsage references a dataflow which the data is reported against.
--|Structure|DataStructureReferen ceType|Structure references the data structure definition which defines the structure of the data.
++(% style="width:1018.29px" %)
++|(% style="width:202px" %)**Name**|(% style="width:284px" %)**Type**|(% style="width:529px" %)**Documentation**
++|(% style="width:202px" %)ProvisionAgreement|(% style="width:284px" %)ProvisionAgreementReferenceType|(% style="width:529px" %)ProvisionAgreement references a provision agreement which the data is reported against.
++|(% style="width:202px" %)StructureUsage|(% style="width:284px" %)DataflowReferenceType|(% style="width:529px" %)StructureUsage references a dataflow which the data is reported against.
++|(% style="width:202px" %)Structure|(% style="width:284px" %)DataStructureReferenceType|(% style="width:529px" %)Structure references the data structure definition which defines the structure of the data.
--***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.
++//**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.
  Derivation:
  PayloadStructureType (restriction)
--   MetadataStructureType*
++   MetadataStructureType
  Attributes:
  structureID, schemaURL?, namespace?, serviceURL?, structureURL?
@@ -612,19 +612,21 @@
  Attribute Documentation:
--|**Name**|**Type**|**Documentation**
--|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.
--|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located.
--|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.
--|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.
--|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.
++(% style="width:1007.29px" %)
++|**Name**|**Type**|(% style="width:802px" %)**Documentation**
++|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.
++|schemaURL|xs:anyURI|(% style="width:802px" %)The schemaURL attribute provides a location from which the structure specific schema can be located.
++|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.
++|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.
++|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.
  Element Documentation:
--|**Name**|**Type**|**Documentation**
--|ProvisionAgreement|ProvisionAgreementReferenceType|ProvisionAgreement references a provision agreement which the metadata is reported against.
--|StructureUsage|MetadataflowReferenceType|StructureUsage references a metadataflow which the metadata is reported against.
--|Structure|MetadataStructureReferenceType|Structure references the metadata structure definition which defines the structure of the metadata.
++(% style="width:1014.29px" %)
++|(% style="width:162px" %)**Name**|(% style="width:277px" %)**Type**|(% style="width:573px" %)**Documentation**
++|(% style="width:162px" %)ProvisionAgreement|(% style="width:277px" %)ProvisionAgreementReferenceType|(% style="width:573px" %)ProvisionAgreement references a provision agreement which the metadata is reported against.
++|(% style="width:162px" %)StructureUsage|(% style="width:277px" %)MetadataflowReferenceType|(% style="width:573px" %)StructureUsage references a metadataflow which the metadata is reported against.
++|(% style="width:162px" %)Structure|(% style="width:277px" %)MetadataStructureReferenceType|(% style="width:573px" %)Structure references the metadata structure definition which defines the structure of the metadata.
  **GenericMetadataStructureType:** GenericMetadataStructureType defines the structural information for a generic metadata message.
@@ -642,18 +642,20 @@
  Attribute Documentation:
--|**Name**|**Type**|**Documentation**
--|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.
--|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located.
--|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.
--|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.
++(% style="width:997.294px" %)
++|**Name**|**Type**|(% style="width:792px" %)**Documentation**
++|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.
++|schemaURL|xs:anyURI|(% style="width:792px" %)The schemaURL attribute provides a location from which the structure specific schema can be located.
++|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.
++|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.
  Element Documentation:
--|**Name**|**Type**|**Documentation**
--|ProvisionAgreement|ProvisionAgreementReferenceType|ProvisionAgreement references a provision agreement which the metadata is reported against.
--|StructureUsage|MetadataflowReferenceType|StructureUsage references a metadataflow which the metadata is reported against.
--|Structure|MetadataStructureReferenceType|Structure references the metadata structure definition which defines the structure of the metadata.
++(% style="width:1001.29px" %)
++|(% style="width:181px" %)**Name**|(% style="width:280px" %)**Type**|(% style="width:537px" %)**Documentation**
++|(% style="width:181px" %)ProvisionAgreement|(% style="width:280px" %)ProvisionAgreementReferenceType|(% style="width:537px" %)ProvisionAgreement references a provision agreement which the metadata is reported against.
++|(% style="width:181px" %)StructureUsage|(% style="width:280px" %)MetadataflowReferenceType|(% style="width:537px" %)StructureUsage references a metadataflow which the metadata is reported against.
++|(% style="width:181px" %)Structure|(% style="width:280px" %)MetadataStructureReferenceType|(% style="width:537px" %)Structure references the metadata structure definition which defines the structure of the metadata.
  === 2.1.4 Simple Types ===
@@ -878,8 +878,9 @@
  Enumerations:
--|**Value**|**Documentation**
--|unbounded|Object has no upper limit on occurrences.
++(% style="width:625.294px" %)
++|(% style="width:144px" %)**Value**|(% style="width:478px" %)**Documentation**
++|(% style="width:144px" %)unbounded|(% style="width:478px" %)Object has no upper limit on occurrences.
  **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.
@@ -887,11 +887,12 @@
  Enumerations:
--|**Value**|**Documentation**
--|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.
--|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.
--|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.
--|Information|Informational - data/metadata is being exchanged for informational purposes only, and not meant to update a system.
++(% style="width:1005.29px" %)
++|**Value**|(% style="width:905px" %)**Documentation**
++|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.
++|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.
++|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.
++|Information|(% style="width:905px" %)Informational - data/metadata is being exchanged for informational purposes only, and not meant to update a system.
  **WildCardValueType:** WildCardValueType is a single value code list, used to include the '%' character - indicating that an entire field is wild carded.
@@ -899,8 +899,9 @@
  Enumerations:
--|**Value**|**Documentation**
--|%|Indicates a wild card value.
++(% style="width:505.294px" %)
++|(% style="width:169px" %)**Value**|(% style="width:333px" %)**Documentation**
++|(% style="width:169px" %)%|(% style="width:333px" %)Indicates a wild card value.
  **CascadeSelectionType:**
@@ -913,8 +913,9 @@
  Enumerations:
--|**Value**|**Documentation**
--|excluderoot|
++(% style="width:504.294px" %)
++|(% style="width:165px" %)**Value**|(% style="width:336px" %)**Documentation**
++|(% style="width:165px" %)excluderoot|(% style="width:336px" %)
  **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".
@@ -927,9 +927,10 @@
  Enumerations:
--|**Value**|**Documentation**
--|AllDimensions|AllDimensions notes that the cross sectional format shall be flat; that is all dimensions should be contained at the observation level.
--|TIME_PERIOD|TIME_PERIOD refers to the fixed identifier for the time dimension.
++(% style="width:997.294px" %)
++|(% style="width:168px" %)**Value**|(% style="width:826px" %)**Documentation**
++|(% 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.
++|(% style="width:168px" %)TIME_PERIOD|(% style="width:826px" %)TIME_PERIOD refers to the fixed identifier for the time dimension.
  **DataType:** DataTypeType provides an enumerated list of the types of data formats allowed as the for the representation of an object.
@@ -937,51 +937,52 @@
  Enumerations:
--|**Value**|**Documentation**
--|String|A string datatype corresponding to W3C XML Schema's xs:string datatype.
--|Alpha|A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z.
--|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.
--|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.
--|BigInteger|An integer datatype corresponding to W3C XML Schema's xs:integer datatype.
--|Integer|An integer datatype corresponding to W3C XML Schema's xs:int datatype.
--|Long|A numeric datatype corresponding to W3C XML Schema's xs:long datatype.
--|Short|A numeric datatype corresponding to W3C XML Schema's xs:short datatype.
--|Decimal|A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype.
--|Float|A numeric datatype corresponding to W3C XML Schema's xs:float datatype.
--|Double|A numeric datatype corresponding to W3C XML Schema's xs:double datatype.
--|Boolean|A datatype corresponding to W3C XML Schema's xs:boolean datatype.
--|URI|A datatype corresponding to W3C XML Schema's xs:anyURI datatype.
--|Count|A simple incrementing Integer type. The isSequence facet must be set to true, and the interval facet must be set to "1".
--|InclusiveValueRange|This value indicates that the startValue and endValue attributes provide the inclusive boundaries of a numeric range of type xs:decimal.
--|ExclusiveValueRange|This value indicates that the startValue and endValue attributes provide the exclusive boundaries of a numeric range, of type xs:decimal.
--|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.
--|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.
--|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.
--|BasicTimePeriod|BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time.
--|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.
--|GregorianYear|A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601.
--|GregorianYearMonth|A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601.
--|GregorianDay|A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601.
--|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.
--|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.
--|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.
--|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.
--|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.
--|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.
--|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.
--|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.
--|DateTime|A time datatype corresponding to W3C XML Schema's xs:dateTime datatype.
--|TimeRange|TimeRange defines a time period by providing a distinct start (date or date time) and a duration.
--|Month|A time datatype corresponding to W3C XML Schema's xs:gMonth datatype.
--|MonthDay|A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype.
--|Day|A time datatype corresponding to W3C XML Schema's xs:gDay datatype.
--|Time|A time datatype corresponding to W3C XML Schema's xs:time datatype.
--|Duration|A time datatype corresponding to W3C XML Schema's xs:duration datatype.
--|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.
--|XHTML|This value indicates that the content of the component can contain XHTML markup.
--|KeyValues|This value indicates that the content of the component will be data key (a set of dimension references and values for the dimensions).
--|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.
--|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.
++(% style="width:996.294px" %)
++|**Value**|(% style="width:796px" %)**Documentation**
++|String|(% style="width:796px" %)A string datatype corresponding to W3C XML Schema's xs:string datatype.
++|Alpha|(% style="width:796px" %)A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z.
++|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.
++|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.
++|BigInteger|(% style="width:796px" %)An integer datatype corresponding to W3C XML Schema's xs:integer datatype.
++|Integer|(% style="width:796px" %)An integer datatype corresponding to W3C XML Schema's xs:int datatype.
++|Long|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:long datatype.
++|Short|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:short datatype.
++|Decimal|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype.
++|Float|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:float datatype.
++|Double|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:double datatype.
++|Boolean|(% style="width:796px" %)A datatype corresponding to W3C XML Schema's xs:boolean datatype.
++|URI|(% style="width:796px" %)A datatype corresponding to W3C XML Schema's xs:anyURI datatype.
++|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".
++|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.
++|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.
++|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.
++|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.
++|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.
++|BasicTimePeriod|(% style="width:796px" %)BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time.
++|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.
++|GregorianYear|(% style="width:796px" %)A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601.
++|GregorianYearMonth|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601.
++|GregorianDay|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601.
++|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.
++|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.
++|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.
++|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.
++|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.
++|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.
++|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.
++|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.
++|DateTime|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:dateTime datatype.
++|TimeRange|(% style="width:796px" %)TimeRange defines a time period by providing a distinct start (date or date time) and a duration.
++|Month|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gMonth datatype.
++|MonthDay|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype.
++|Day|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gDay datatype.
++|Time|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:time datatype.
++|Duration|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:duration datatype.
++|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.
++|XHTML|(% style="width:796px" %)This value indicates that the content of the component can contain XHTML markup.
++|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).
++|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.
++|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.
  **BasicComponentDataType:** BasicComponentDataType provides an enumerated list of the types of characters allowed in the textType attribute for all non-target object components.
@@ -989,48 +989,49 @@
  Enumerations:
--|**Value**|**Documentation**
--|String|A string datatype corresponding to W3C XML Schema's xs:string datatype.
--|Alpha|A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z.
--|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.
--|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.
--|BigInteger|An integer datatype corresponding to W3C XML Schema's xs:integer datatype.
--|Integer|An integer datatype corresponding to W3C XML Schema's xs:int datatype.
--|Long|A numeric datatype corresponding to W3C XML Schema's xs:long datatype.
--|Short|A numeric datatype corresponding to W3C XML Schema's xs:short datatype.
--|Decimal|A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype.
--|Float|A numeric datatype corresponding to W3C XML Schema's xs:float datatype.
--|Double|A numeric datatype corresponding to W3C XML Schema's xs:double datatype.
--|Boolean|A datatype corresponding to W3C XML Schema's xs:boolean datatype.
--|URI|A datatype corresponding to W3C XML Schema's xs:anyURI datatype.
--|Count|A simple incrementing Integer type. The isSequence facet must be set to true, and the interval facet must be set to "1".
--|InclusiveValueRange|This value indicates that the startValue and endValue attributes provide the inclusive boundaries of a numeric range of type xs:decimal.
--|ExclusiveValueRange|This value indicates that the startValue and endValue attributes provide the exclusive boundaries of a numeric range, of type xs:decimal.
--|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.
--|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.
--|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.
--|BasicTimePeriod|BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time.
--|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.
--|GregorianYear|A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601.
--|GregorianYearMonth|A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601.
--|GregorianDay|A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601.
--|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.
--|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.
--|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.
--|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.
--|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.
--|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.
--|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.
--|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.
--|DateTime|A time datatype corresponding to W3C XML Schema's xs:dateTime datatype.
--|TimeRange|TimeRange defines a time period by providing a distinct start (date or date time) and a duration.
--|Month|A time datatype corresponding to W3C XML Schema's xs:gMonth datatype.
--|MonthDay|A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype.
--|Day|A time datatype corresponding to W3C XML Schema's xs:gDay datatype.
--|Time|A time datatype corresponding to W3C XML Schema's xs:time datatype.
--|Duration|A time datatype corresponding to W3C XML Schema's xs:duration datatype.
--|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.
--|XHTML|This value indicates that the content of the component can contain XHTML markup.
++(% style="width:999.294px" %)
++|**Value**|(% style="width:799px" %)**Documentation**
++|String|(% style="width:799px" %)A string datatype corresponding to W3C XML Schema's xs:string datatype.
++|Alpha|(% style="width:799px" %)A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z.
++|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.
++|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.
++|BigInteger|(% style="width:799px" %)An integer datatype corresponding to W3C XML Schema's xs:integer datatype.
++|Integer|(% style="width:799px" %)An integer datatype corresponding to W3C XML Schema's xs:int datatype.
++|Long|(% style="width:799px" %)A numeric datatype corresponding to W3C XML Schema's xs:long datatype.
++|Short|(% style="width:799px" %)A numeric datatype corresponding to W3C XML Schema's xs:short datatype.
++|Decimal|(% style="width:799px" %)A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype.
++|Float|(% style="width:799px" %)A numeric datatype corresponding to W3C XML Schema's xs:float datatype.
++|Double|(% style="width:799px" %)A numeric datatype corresponding to W3C XML Schema's xs:double datatype.
++|Boolean|(% style="width:799px" %)A datatype corresponding to W3C XML Schema's xs:boolean datatype.
++|URI|(% style="width:799px" %)A datatype corresponding to W3C XML Schema's xs:anyURI datatype.
++|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".
++|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.
++|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.
++|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.
++|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.
++|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.
++|BasicTimePeriod|(% style="width:799px" %)BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time.
++|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.
++|GregorianYear|(% style="width:799px" %)A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601.
++|GregorianYearMonth|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601.
++|GregorianDay|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601.
++|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.
++|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.
++|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.
++|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.
++|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.
++|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.
++|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.
++|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.
++|DateTime|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:dateTime datatype.
++|TimeRange|(% style="width:799px" %)TimeRange defines a time period by providing a distinct start (date or date time) and a duration.
++|Month|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:gMonth datatype.
++|MonthDay|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype.
++|Day|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:gDay datatype.
++|Time|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:time datatype.
++|Duration|(% style="width:799px" %)A time datatype corresponding to W3C XML Schema's xs:duration datatype.
++|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.
++|XHTML|(% style="width:799px" %)This value indicates that the content of the component can contain XHTML markup.
  **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.
@@ -1038,47 +1038,48 @@
  Enumerations:
--|**Value**|**Documentation**
--|String|A string datatype corresponding to W3C XML Schema's xs:string datatype.
--|Alpha|A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z.
--|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.
--|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.
--|BigInteger|An integer datatype corresponding to W3C XML Schema's xs:integer datatype.
--|Integer|An integer datatype corresponding to W3C XML Schema's xs:int datatype.
--|Long|A numeric datatype corresponding to W3C XML Schema's xs:long datatype.
--|Short|A numeric datatype corresponding to W3C XML Schema's xs:short datatype.
--|Decimal|A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype.
--|Float|A numeric datatype corresponding to W3C XML Schema's xs:float datatype.
--|Double|A numeric datatype corresponding to W3C XML Schema's xs:double datatype.
--|Boolean|A datatype corresponding to W3C XML Schema's xs:boolean datatype.
--|URI|A datatype corresponding to W3C XML Schema's xs:anyURI datatype.
--|Count|A simple incrementing Integer type. The isSequence facet must be set to true, and the interval facet must be set to "1".
--|InclusiveValueRange|This value indicates that the startValue and endValue attributes provide the inclusive boundaries of a numeric range of type xs:decimal.
--|ExclusiveValueRange|This value indicates that the startValue and endValue attributes provide the exclusive boundaries of a numeric range, of type xs:decimal.
--|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.
--|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.
--|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.
--|BasicTimePeriod|BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time.
--|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.
--|GregorianYear|A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601.
--|GregorianYearMonth|A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601.
--|GregorianDay|A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601.
--|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.
--|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.
--|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.
--|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.
--|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.
--|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.
--|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.
--|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.
--|DateTime|A time datatype corresponding to W3C XML Schema's xs:dateTime datatype.
--|TimeRange|TimeRange defines a time period by providing a distinct start (date or date time) and a duration.
--|Month|A time datatype corresponding to W3C XML Schema's xs:gMonth datatype.
--|MonthDay|A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype.
--|Day|A time datatype corresponding to W3C XML Schema's xs:gDay datatype.
--|Time|A time datatype corresponding to W3C XML Schema's xs:time datatype.
--|Duration|A time datatype corresponding to W3C XML Schema's xs:duration datatype.
--|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.
++(% style="width:996.294px" %)
++|**Value**|(% style="width:796px" %)**Documentation**
++|String|(% style="width:796px" %)A string datatype corresponding to W3C XML Schema's xs:string datatype.
++|Alpha|(% style="width:796px" %)A string datatype which only allows for the simple aplhabetic charcter set of A-Z, a-z.
++|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.
++|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.
++|BigInteger|(% style="width:796px" %)An integer datatype corresponding to W3C XML Schema's xs:integer datatype.
++|Integer|(% style="width:796px" %)An integer datatype corresponding to W3C XML Schema's xs:int datatype.
++|Long|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:long datatype.
++|Short|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:short datatype.
++|Decimal|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:decimal datatype.
++|Float|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:float datatype.
++|Double|(% style="width:796px" %)A numeric datatype corresponding to W3C XML Schema's xs:double datatype.
++|Boolean|(% style="width:796px" %)A datatype corresponding to W3C XML Schema's xs:boolean datatype.
++|URI|(% style="width:796px" %)A datatype corresponding to W3C XML Schema's xs:anyURI datatype.
++|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".
++|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.
++|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.
++|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.
++|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.
++|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.
++|BasicTimePeriod|(% style="width:796px" %)BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time.
++|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.
++|GregorianYear|(% style="width:796px" %)A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601.
++|GregorianYearMonth|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601.
++|GregorianDay|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601.
++|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.
++|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.
++|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.
++|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.
++|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.
++|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.
++|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.
++|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.
++|DateTime|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:dateTime datatype.
++|TimeRange|(% style="width:796px" %)TimeRange defines a time period by providing a distinct start (date or date time) and a duration.
++|Month|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gMonth datatype.
++|MonthDay|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gMonthDay datatype.
++|Day|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:gDay datatype.
++|Time|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:time datatype.
++|Duration|(% style="width:796px" %)A time datatype corresponding to W3C XML Schema's xs:duration datatype.
++|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.
  **TimeDataType:** TimeDataType restricts SimpleDataType to specify the allowable data types for representing a time value.
@@ -1086,26 +1086,27 @@
  Enumerations:
--|**Value**|**Documentation**
--|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.
--|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.
--|BasicTimePeriod|BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time.
--|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.
--|GregorianYear|A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601.
--|GregorianYearMonth|A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601.
--|GregorianDay|A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601.
--|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.
--|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.
--|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.
--|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.
--|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.
--|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.
--|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.
--|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.
--|DateTime|A time datatype corresponding to W3C XML Schema's xs:dateTime datatype.
--|TimeRange|TimeRange defines a time period by providing a distinct start (date or date time) and a duration.
++(% style="width:1002.29px" %)
++|**Value**|(% style="width:802px" %)**Documentation**
++|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.
++|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.
++|BasicTimePeriod|(% style="width:802px" %)BasicTimePeriod time periods is a superset of the Gregorian time periods and a date time.
++|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.
++|GregorianYear|(% style="width:802px" %)A Gregorian time period corresponding to W3C XML Schema's xs:gYear datatype, which is based on ISO-8601.
++|GregorianYearMonth|(% style="width:802px" %)A time datatype corresponding to W3C XML Schema's xs:gYearMonth datatype, which is based on ISO-8601.
++|GregorianDay|(% style="width:802px" %)A time datatype corresponding to W3C XML Schema's xs:date datatype, which is based on ISO-8601.
++|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.
++|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.
++|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.
++|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.
++|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.
++|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.
++|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.
++|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.
++|DateTime|(% style="width:802px" %)A time datatype corresponding to W3C XML Schema's xs:dateTime datatype.
++|TimeRange|(% style="width:802px" %)TimeRange defines a time period by providing a distinct start (date or date time) and a duration.
--**UrnPrefixPart:** This is validates the first part of the URN (urn:sdmx.org.infomodel.<package>.<class=). It is intended to be further restricted.
++**UrnPrefixPart:** This is validates the first part of the URN (urn:sdmx.org.infomodel..<class=). It is intended to be further restricted.
  Derived by restriction of xs:string.
  Regular Expression Pattern: urn:sdmx:org\.sdmx\.infomodel\.[a-z]+\.[A-Za-z]+=[^=]+
@@ -1125,81 +1125,44 @@
  Derived by restriction of UrnClassesPart.
  Regular Expression Pattern: .  +=([A-Za-z][A-Za-z0-9_\-]*(\.[A-Za-z][A-Za-z0-9_\-]*)*):[^:]+.+=\*:[^:]+
--**UrnMaintainableIdPart:** This refines the prefix, classes, and agnecy patterns to validate the maintainable ID part of the URN (:<maintainable_id(<version_number>)). Note that it does not restrict the version part as it is intended to be further restricted.
++**UrnMaintainableIdPart:** This refines the prefix, classes, and agnecy patterns to validate the maintainable ID part of the URN (:)). Note that it does not restrict the version part as it is intended to be further restricted.
  Derived by restriction of UrnAgencyPart.
  Regular Expression Pattern: .  +:([A-Za-z0-9_@$\-]+)\([0-9A-Za-z\-\.\+]+\)[^(\(\))]
--**WildcardUrnMaintainableIdPart:** This refines the prefix, classes, and agnecy patterns to validate the maintainable ID part of a wildcarded URN reference (:<maintainable_id(<version_number>)). Note that it does not restrict the version part as it is intended to be further restricted.
++**WildcardUrnMaintainableIdPart:** This refines the prefix, classes, and agnecy patterns to validate the maintainable ID part of a wildcarded URN reference (:)). Note that it does not restrict the version part as it is intended to be further restricted.
  Derived by restriction of WildcardUrnAgencyPart.
  Regular Expression Pattern: .  +:([A-Za-z0-9_@$\-]+)\([0-9A-Za-z\-\.\+\*]+\)[^(\(\))]*.+:\*\([0-9A-Za-z\-\.\+\*]+\)[^(\(\))]
++(((
  **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.
  Derived by restriction of UrnMaintainableIdPart.
--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]*
++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]~*~*)?\).
  )))
--*)?\).
--
  **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.
  Derived by restriction of UrnMaintainableIdPart.
--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]*~)~)~)*)?\).*.+\
++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*)\+?))\).
--(((
--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*)\+?))\).
--
  **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.
  Derived by restriction of WildcardUrnMaintainableIdPart.
--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]*~)~)~)*)?\).*.+\
++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*)\+?))\).*.+\(\*\).
--(((
--0|[1-9]\d*)\+?)(\.((0|[1-9]\d*
--)))
++**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. ().\*). The nested patterns provide a complete validation of the URN pattern.
--{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*)\+?))\).*.+\(\*\).
--
--**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.
--
  Derived by restriction of UrnVersionPart.
  Regular Expression Pattern: .  +\)(\.[A-Za-z0-9_@$\-]+(\.[A-Za-z0-9_@$\-]+)*)?
--**UrnReferenceType:** 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 a URN reference (e.g. (<version_number>)<containerobject-id>.<object-id>\*). The nested patterns provide a complete validation of the URN pattern.
++**UrnReferenceType:** 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 a URN reference (e.g. ().\*). The nested patterns provide a complete validation of the URN pattern.
  Derived by restriction of UrnReferenceVersionPart.
  Regular Expression Pattern: .  +\)(\.[A-Za-z0-9_@$\-]+(\.[A-Za-z0-9_@$\-]+)*)?
--**WildcardUrnType:** 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 a wildcarded URN reference (e.g. (<version_number>)<containerobject-id>.<object-id>\*). The nested patterns provide a complete validation of the URN pattern.
++**WildcardUrnType:** 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 a wildcarded URN reference (e.g. ().\*). The nested patterns provide a complete validation of the URN pattern.
  Derived by restriction of WildcardUrnVersionPart.
  Regular Expression Pattern: .  +\)(\.[A-Za-z0-9_@$\-]+(\.[A-Za-z0-9_@$\-]+)*)?.+\)(\.\*(\.\*)*)?
@@ -1215,6 +1215,7 @@
  Regular Expression Pattern: .  +\)
  **ComponentUrnType:** Restricts the URN so that the pattern ends after the first component part.
++)))
  Derived by restriction of UrnType.
  Regular Expression Pattern: .  +\)\.[A-Za-z0-9_@$\-]+
@@ -1519,7 +1519,7 @@
  Derived by restriction of ComponentUrnType.
  Regular Expression Pattern: .  +\.transformation\.Ruleset=.+
--**RulesetSchemeUrnType:** Urn type for a ruleste scheme.
++**RulesetSchemeUrnType:** Urn type for a ruleset scheme.
  Derived by restriction of MaintainableUrnType.
  Regular Expression Pattern: .  +\.transformation\.RulesetScheme=.+
@@ -1928,6 +1928,7 @@
  **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 "+".
  Derived by restriction of xs:string.
++
  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*)\+?))
  **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.
@@ -1942,10 +1942,10 @@
  Enumerations:
--|**Value**|**Documentation**
++(% style="width:1011.29px" %)
++|**Value**|(% style="width:771px" %)**Documentation**
++|\*|(% style="width:771px" %)Indicates that any value of the identifier component is allowed.
--|\*|Indicates that any value of the identifier component is allowed.|
--
  **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, \_, -, $.
  Derived by restriction of xs:string.
@@ -1984,9 +1984,10 @@
  **SemanticVersionNumberType:** SemanticVersionNumberType is a simple type for validating semantic version in the format (major.minor.patch[-extension]).
  Derived by restriction of xs:string.
--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]*~)~)~)*)?
++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]*~)~)~)*)?
  **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.
  Derived by restriction of xs:string.
++
  Regular Expression Pattern: (0|[1-9]\d*)(\.(0|[1-9]\d*))?

SUZ.Methodology.Code.MethodologyClass[0]

index

...	...	@@ -1,1 +1,0 @@
1		-3

SKMS.Methodology.Code.MethodologyClass[0]

Index

...	...	@@ -1,0 +1,1 @@
	1	+3