Changes for page Part II.Common Namespace

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

From 6.12 to 6.11 From 15.3 to 15.2

From version 15.2

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

Change comment: There is no comment for this version

To version 6.12

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Title

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

Content

@@ -4,17 +4,17 @@
  = 1 Introduction =
--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.
++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.
--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.
++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.
  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 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.
++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.
  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 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.
++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.
  == 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:
++
  **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?
@@ -509,7 +509,7 @@
  |(% 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?
@@ -542,7 +542,7 @@
  Derivation:
  PayloadStructureType (restriction)
--   DataStructureType
++   DataStructureType*
  Attributes:
  structureID, schemaURL?, namespace?, dimensionAtObservation?, explicitMeasures?, serviceURL?, structureURL?
@@ -609,7 +609,7 @@
  Derivation:
  PayloadStructureType (restriction)
--   MetadataStructureType
++   MetadataStructureType*
  Attributes:
  structureID, schemaURL?, namespace?, serviceURL?, structureURL?
@@ -1105,27 +1105,26 @@
  Enumerations:
--(% 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.
++|**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.
--**UrnPrefixPart:** This is validates the first part of the URN (urn:sdmx.org.infomodel..<class=). It is intended to be further restricted.
++**UrnPrefixPart:** This is validates the first part of the URN (urn:sdmx.org.infomodel.<package>.<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]+=[^=]+
@@ -1145,44 +1145,81 @@
  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 (:)). 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 (:<maintainable_id(<version_number>)). 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 (:)). 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 (:<maintainable_id(<version_number>)). 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]*~)~)~)*)?\).*.+\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*)\+?))\).
++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*)\+?))\).
++
  **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]*~)~)~)*)?\).*.+\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*)\+?))\).*.+\(\*\).
++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]*~)~)~)*)?\).*.+\
--**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.
++(((
++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*)\+?))\).*.+\(\*\).
++
++**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. ().\*). 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. (<version_number>)<containerobject-id>.<object-id>\*). 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. ().\*). 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. (<version_number>)<containerobject-id>.<object-id>\*). 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_@$\-]+)*)?.+\)(\.\*(\.\*)*)?
@@ -1198,7 +1198,6 @@
  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_@$\-]+
@@ -1503,7 +1503,7 @@
  Derived by restriction of ComponentUrnType.
  Regular Expression Pattern: .  +\.transformation\.Ruleset=.+
--**RulesetSchemeUrnType:** Urn type for a ruleset scheme.
++**RulesetSchemeUrnType:** Urn type for a ruleste scheme.
  Derived by restriction of MaintainableUrnType.
  Regular Expression Pattern: .  +\.transformation\.RulesetScheme=.+
@@ -1912,7 +1912,6 @@
  **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.
@@ -1927,10 +1927,10 @@
  Enumerations:
--(% style="width:1011.29px" %)
--|**Value**|(% style="width:771px" %)**Documentation**
--|\*|(% style="width:771px" %)Indicates that any value of the identifier component is allowed.
++|**Value**|**Documentation**
++|\*|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.
@@ -1969,10 +1969,9 @@
  **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*))?

SKMS.Methodology.Code.MethodologyClass[0]

Index

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

SUZ.Methodology.Code.MethodologyClass[0]

index

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