Changes for page Part II.Common Namespace
Last modified by Helena K. on 2026/06/09 12:56
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Objects (0 modified, 1 added, 1 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -Part II.Common :This details the common namespaceschemas1 +Part II.Common Namespace - Content
-
... ... @@ -4,17 +4,17 @@ 4 4 5 5 = 1 Introduction = 6 6 7 -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.Statisticaldata 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.7 +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. 8 8 9 -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.Statisticaldata and metadata exchange.WebHome]] objects for these reference fields.9 +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. 10 10 11 11 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. 12 12 13 -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.Statisticaldata and metadata exchange.WebHome]] always treats[[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]as unqualified.13 +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. 14 14 15 15 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. 16 16 17 -The solution to this problem was to deviate from the normal [[SDMX>>doc:sdmx:Glossary.Statisticaldata 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.17 +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. 18 18 19 19 == 2 Schema Documentation == 20 20 ... ... @@ -52,7 +52,7 @@ 52 52 53 53 === 2.1.3 Complex Types === 54 54 55 -** *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.55 +//**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. 56 56 57 57 Content: 58 58 {text} x (Text\* | StructuredText\*)? ... ... @@ -70,8 +70,8 @@ 70 70 71 71 ValueType (restriction) 72 72 BooleanValueType 73 -Content: 74 74 74 +Content: 75 75 **StringValueType:** StringValueType is a refinement of SimpleValueType limiting the content to be a string. This can be further refined with facets, patterns, etc. 76 76 77 77 Derivation: ... ... @@ -204,7 +204,7 @@ 204 204 |(% style="width:150px" %)**Name**|(% style="width:206px" %)**Type**|(% style="width:652px" %)**Documentation** 205 205 |(% style="width:150px" %)Text|(% style="width:206px" %)TextType|(% style="width:652px" %)Text contains the text of the message, in parallel language values. 206 206 207 -** *AnnotableType*:** AnnotableType is an abstract base type used for all annotable artefacts. Any type that provides for annotations should extend this type.207 +//**AnnotableType:** //AnnotableType is an abstract base type used for all annotable artefacts. Any type that provides for annotations should extend this type. 208 208 209 209 Content: 210 210 Annotations? ... ... @@ -290,7 +290,7 @@ 290 290 Derivation: 291 291 292 292 AnnotableType (extension) 293 - IdentifiableType *293 + IdentifiableType 294 294 295 295 Attributes: 296 296 id?, urn?, uri? ... ... @@ -319,7 +319,7 @@ 319 319 320 320 AnnotableType (extension) 321 321 IdentifiableType (extension) 322 - NameableType *322 + NameableType 323 323 324 324 Attributes: 325 325 id?, urn?, uri? ... ... @@ -351,7 +351,7 @@ 351 351 AnnotableType (extension) 352 352 IdentifiableType (extension) 353 353 NameableType (extension) 354 - VersionableType *354 + VersionableType 355 355 356 356 Attributes: 357 357 id?, urn?, uri?, version?, validFrom?, validTo? ... ... @@ -387,7 +387,7 @@ 387 387 IdentifiableType (extension) 388 388 NameableType (extension) 389 389 VersionableType (restriction) 390 - MaintainableBaseType *390 + MaintainableBaseType 391 391 392 392 Attributes: 393 393 id, urn?, uri?, version?, validFrom?, validTo? ... ... @@ -421,10 +421,10 @@ 421 421 422 422 AnnotableType (extension) 423 423 IdentifiableType (extension) 424 - NameableType *(extension)424 + NameableType (extension) 425 425 VersionableType (restriction) 426 426 MaintainableBaseType (extension) 427 - MaintainableType *427 + MaintainableType 428 428 429 429 Attributes: 430 430 id, urn?, uri?, version?, validFrom?, validTo?, agencyID, isPartialLanguage?, isExternalReference?, serviceURL?, structureURL? ... ... @@ -509,7 +509,7 @@ 509 509 |(% style="width:228px" %)**Name**|(% style="width:221px" %)**Type**|(% style="width:699px" %)**Documentation** 510 510 |(% style="width:228px" %)xml:lang (default: en)|(% style="width:221px" %)xs:language 511 511 512 -** *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).512 +//**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). 513 513 514 514 Attributes: 515 515 structureID, schemaURL?, namespace?, dimensionAtObservation?, explicitMeasures?, serviceURL?, structureURL? ... ... @@ -542,7 +542,7 @@ 542 542 Derivation: 543 543 544 544 PayloadStructureType (restriction) 545 - DataStructureType *545 + DataStructureType 546 546 547 547 Attributes: 548 548 structureID, schemaURL?, namespace?, dimensionAtObservation?, explicitMeasures?, serviceURL?, structureURL? ... ... @@ -609,7 +609,7 @@ 609 609 Derivation: 610 610 611 611 PayloadStructureType (restriction) 612 - MetadataStructureType *612 + MetadataStructureType 613 613 614 614 Attributes: 615 615 structureID, schemaURL?, namespace?, serviceURL?, structureURL? ... ... @@ -1125,7 +1125,7 @@ 1125 1125 |DateTime|(% style="width:802px" %)A time datatype corresponding to W3C XML Schema's xs:dateTime datatype. 1126 1126 |TimeRange|(% style="width:802px" %)TimeRange defines a time period by providing a distinct start (date or date time) and a duration. 1127 1127 1128 -**UrnPrefixPart:** This is validates the first part of the URN (urn:sdmx.org.infomodel. <package>.<class=). It is intended to be further restricted.1128 +**UrnPrefixPart:** This is validates the first part of the URN (urn:sdmx.org.infomodel..<class=). It is intended to be further restricted. 1129 1129 1130 1130 Derived by restriction of xs:string. 1131 1131 Regular Expression Pattern: urn:sdmx:org\.sdmx\.infomodel\.[a-z]+\.[A-Za-z]+=[^=]+ ... ... @@ -1145,43 +1145,44 @@ 1145 1145 Derived by restriction of UrnClassesPart. 1146 1146 Regular Expression Pattern: . +=([A-Za-z][A-Za-z0-9_\-]*(\.[A-Za-z][A-Za-z0-9_\-]*)*):[^:]+.+=\*:[^:]+ 1147 1147 1148 -**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.1148 +**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. 1149 1149 1150 1150 Derived by restriction of UrnAgencyPart. 1151 1151 Regular Expression Pattern: . +:([A-Za-z0-9_@$\-]+)\([0-9A-Za-z\-\.\+]+\)[^(\(\))] 1152 1152 1153 -**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.1153 +**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. 1154 1154 1155 1155 Derived by restriction of WildcardUrnAgencyPart. 1156 1156 Regular Expression Pattern: . +:([A-Za-z0-9_@$\-]+)\([0-9A-Za-z\-\.\+\*]+\)[^(\(\))]*.+:\*\([0-9A-Za-z\-\.\+\*]+\)[^(\(\))] 1157 1157 1158 +((( 1158 1158 **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. 1159 1159 1160 1160 Derived by restriction of UrnMaintainableIdPart. 1161 -Regular Expression Pattern: . +\((0|[1-9]\d*)(\.(0|[1-9]\d*))?\).*.+\((0|[1-9]\d*)(\.(0|[1-9]\d*)){2}(\-(([A-Za-z\-]|([A-Za-z\-][A-Za-z0-9\-]+)|([A-Za-z0-9\-]+[A-Za-z\-][A-Za-z0-9\-]*))|(0|[1-9][0-9]*))(\.(([A-Za-z\-]|([A-Za-z\-][A-Za-z0-9\-]+)|([A-Za-z0-9\-]+[A-Za-z\-][A-Za-z0-9\-]*))|(0|[1-9][0-9]~*~*)?\). 1162 +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]~*~*)?\). 1162 1162 ))) 1163 1163 1164 1164 **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. 1165 1165 1166 1166 Derived by restriction of UrnMaintainableIdPart. 1167 -Regular Expression Pattern: . +\((0|[1-9]\d*)(\.(0|[1-9]\d*))?\).*.+\((0|[1-9]\d*)(\.(0|[1-9]\d*)){2}(\-(([A-Za-z\-]|([A-Za-z\-][A-Za-z0-9\-]+)|([A-Za-z0-9\-]+[A-Za-z\-][A-Za-z0-9\-]*))|(0|[1-9][0-9]*))(\.(([A-Za-z\-]|([A-Za-z\-][A-Za-z0-9\-]+)|([A-Za-z0-9\-]+[A-Za-z\-][A-Za-z0-9\-]*))|(0|[1-9][0-9]*~)~)~)*)?\).*.+\0|[1-9]\d*)\+?)(\.((0|[1-9]\d*{2}\).*.+\0|[1-9]\d*))(\.((0|[1-9]\d*)\+?))(\.((0|[1-9]\d*\).*.+\0|[1-9]\d*)\+?)(\.((0|[1-9]\d*(\.((0|[1-9]\d*)\+?))\). 1168 +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*)\+?))\). 1168 1168 1169 1169 **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. 1170 1170 1171 1171 Derived by restriction of WildcardUrnMaintainableIdPart. 1172 -Regular Expression Pattern: . +\((0|[1-9]\d*)(\.(0|[1-9]\d*))?\).*.+\((0|[1-9]\d*)(\.(0|[1-9]\d*)){2}(\-(([A-Za-z\-]|([A-Za-z\-][A-Za-z0-9\-]+)|([A-Za-z0-9\-]+[A-Za-z\-][A-Za-z0-9\-]*))|(0|[1-9][0-9]*))(\.(([A-Za-z\-]|([A-Za-z\-][A-Za-z0-9\-]+)|([A-Za-z0-9\-]+[A-Za-z\-][A-Za-z0-9\-]*))|(0|[1-9][0-9]*~)~)~)*)?\).*.+\0|[1-9]\d*)\+?)(\.((0|[1-9]\d*{2}\).*.+\0|[1-9]\d*))(\.((0|[1-9]\d*)\+?))(\.((0|[1-9]\d*\).*.+\0|[1-9]\d*)\+?)(\.((0|[1-9]\d*(\.((0|[1-9]\d*)\+?))\).*.+\(\*\). 1173 +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*)\+?))\).*.+\(\*\). 1173 1173 1174 -**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.1175 +**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. 1175 1175 1176 1176 Derived by restriction of UrnVersionPart. 1177 1177 Regular Expression Pattern: . +\)(\.[A-Za-z0-9_@$\-]+(\.[A-Za-z0-9_@$\-]+)*)? 1178 1178 1179 -**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.1180 +**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. 1180 1180 1181 1181 Derived by restriction of UrnReferenceVersionPart. 1182 1182 Regular Expression Pattern: . +\)(\.[A-Za-z0-9_@$\-]+(\.[A-Za-z0-9_@$\-]+)*)? 1183 1183 1184 -**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.1185 +**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. 1185 1185 1186 1186 Derived by restriction of WildcardUrnVersionPart. 1187 1187 Regular Expression Pattern: . +\)(\.[A-Za-z0-9_@$\-]+(\.[A-Za-z0-9_@$\-]+)*)?.+\)(\.\*(\.\*)*)? ... ... @@ -1197,6 +1197,7 @@ 1197 1197 Regular Expression Pattern: . +\) 1198 1198 1199 1199 **ComponentUrnType:** Restricts the URN so that the pattern ends after the first component part. 1201 +))) 1200 1200 1201 1201 Derived by restriction of UrnType. 1202 1202 Regular Expression Pattern: . +\)\.[A-Za-z0-9_@$\-]+ ... ... @@ -1501,7 +1501,7 @@ 1501 1501 Derived by restriction of ComponentUrnType. 1502 1502 Regular Expression Pattern: . +\.transformation\.Ruleset=.+ 1503 1503 1504 -**RulesetSchemeUrnType:** Urn type for a rules te scheme.1506 +**RulesetSchemeUrnType:** Urn type for a ruleset scheme. 1505 1505 1506 1506 Derived by restriction of MaintainableUrnType. 1507 1507 Regular Expression Pattern: . +\.transformation\.RulesetScheme=.+ ... ... @@ -1910,6 +1910,7 @@ 1910 1910 **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 "+". 1911 1911 1912 1912 Derived by restriction of xs:string. 1915 + 1913 1913 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*)\+?)) 1914 1914 1915 1915 **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. ... ... @@ -1926,49 +1926,49 @@ 1926 1926 1927 1927 (% style="width:1011.29px" %) 1928 1928 |**Value**|(% style="width:771px" %)**Documentation** 1929 -|\*|(% style="width:771px" %)Indicates that any value of the identifier [[component>>doc:sdmx:Glossary.Component.WebHome]]is allowed.1932 +|\*|(% style="width:771px" %)Indicates that any value of the identifier component is allowed. 1930 1930 1931 -**NestedIDType:** NestedIDType is the least restrictive form of an identifier used throughout all [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]]messages. It allows for a hierarchical identifier, with each portion separated by the '.' character. For the identifier portions, valid characters include A-Z, a-z, @, 0-9, \_, -, $.1934 +**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, \_, -, $. 1932 1932 1933 1933 Derived by restriction of xs:string. 1934 1934 Regular Expression Pattern: [A-Za-z0-9_@$\-]+(\.[A-Za-z0-9_@$\-]+) 1935 1935 1936 -**TwoLevelIDType:** TwoLevelIDType defines an identifier with exactly two (% style="color:#e74c3c" %)levels(%%).1939 +**TwoLevelIDType:** TwoLevelIDType defines an identifier with exactly two levels. 1937 1937 1938 1938 Derived by restriction of NestedIDType. 1939 1939 Regular Expression Pattern: [A-Za-z0-9_@$\-]+\.[A-Za-z0-9_@$\-]+ 1940 1940 1941 -**IDType:** IDType provides a type which is used for restricting the characters in [[codes>>doc:sdmx:Glossary.Code.WebHome]]and IDs throughout all[[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]]messages. Valid characters include A-Z, a-z, @, 0-9, \_, -, $.1944 +**IDType:** IDType provides a type which is used for restricting the characters in codes and IDs throughout all SDMX-ML messages. Valid characters include A-Z, a-z, @, 0-9, \_, -, $. 1942 1942 1943 1943 Derived by restriction of NestedIDType. 1944 1944 Regular Expression Pattern: [A-Za-z0-9_@$\-]+ 1945 1945 1946 -**NCNameIDType:** NCNameIDType restricts the IDType, so that the id may be used to generate valid XML [[components>>doc:sdmx:Glossary.Component.WebHome]].IDs created from this type conform to the W3C XML Schema NCNAME type, and therefore can be used as element or[[attribute>>doc:sdmx:Glossary.Attribute.WebHome]]names.1949 +**NCNameIDType:** NCNameIDType restricts the IDType, so that the id may be used to generate valid XML components. IDs created from this type conform to the W3C XML Schema NCNAME type, and therefore can be used as element or attribute names. 1947 1947 1948 1948 Derived by restriction of IDType. 1949 1949 Regular Expression Pattern: [A-Za-z][A-Za-z0-9_\-] 1950 1950 1951 -**NestedNCNameIDType:** NestedNCNameIDType restricts the NestedIDType, so that the id may be used to generate valid XML [[components>>doc:sdmx:Glossary.Component.WebHome]].IDs created from this type conform to the W3C XML Schema NCNAME type, and therefore can be used as element or[[attribute>>doc:sdmx:Glossary.Attribute.WebHome]]names.1954 +**NestedNCNameIDType:** NestedNCNameIDType restricts the NestedIDType, so that the id may be used to generate valid XML components. IDs created from this type conform to the W3C XML Schema NCNAME type, and therefore can be used as element or attribute names. 1952 1952 1953 1953 Derived by restriction of NestedIDType. 1954 1954 Regular Expression Pattern: [A-Za-z][A-Za-z0-9_\-]*(\.[A-Za-z][A-Za-z0-9_\-]*) 1955 1955 1956 -**SingleNCNameIDType:** SingleNCNameIDType restricts the NestedNCNameIDType to allow only one (% style="color:#e74c3c" %)level(%%). Note that this is the same pattern as the NCNameIDType, but can be used when the base type to be restricted is a nested NCNameIDType (where as the NCNameIDType could only restrict the IDType).1959 +**SingleNCNameIDType:** SingleNCNameIDType restricts the NestedNCNameIDType to allow only one level. Note that this is the same pattern as the NCNameIDType, but can be used when the base type to be restricted is a nested NCNameIDType (where as the NCNameIDType could only restrict the IDType). 1957 1957 1958 1958 Derived by restriction of NestedNCNameIDType. 1959 1959 Regular Expression Pattern: [A-Za-z][A-Za-z0-9_\-] 1960 1960 1961 -**VersionType:** VersionType is used to communicate (% style="color:#e74c3c" %)version(%%)information. Semantic versioning, based on 3 or 4(% style="color:#e74c3c" %)version(%%)parts (major.minor.patch[-extension]) is supported. The legency[[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] (% style="color:#e74c3c" %)version(%%)format is also support.1964 +**VersionType:** VersionType is used to communicate version information. Semantic versioning, based on 3 or 4 version parts (major.minor.patch[-extension]) is supported. The legency SDMX version format is also support. 1962 1962 1963 1963 Union of: 1964 1964 LegacyVersionNumberType, SemanticVersionNumberType. 1965 1965 1966 -**SemanticVersionNumberType:** SemanticVersionNumberType is a simple type for validating semantic (% style="color:#e74c3c" %)version(%%)in the format (major.minor.patch[-extension]).1969 +**SemanticVersionNumberType:** SemanticVersionNumberType is a simple type for validating semantic version in the format (major.minor.patch[-extension]). 1967 1967 1968 1968 Derived by restriction of xs:string. 1969 -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]*~)~)~)*)? 1972 +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]*~)~)~)*)? 1970 1970 1971 -**LegacyVersionNumberType:** LegacyVersionNumberType describes the (% style="color:#e74c3c" %)version(%%)number format previously supported in[[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]].The format is restricted to allow for simple incrementing and sorting of(% style="color:#e74c3c" %)version(%%)number. The(% style="color:#e74c3c" %)version(%%)consists of a set of maximum 2 numeric[[components>>doc:sdmx:Glossary.Component.WebHome]], separated by the '.' character. When processing(% style="color:#e74c3c" %)version(%%), each numeric[[component>>doc:sdmx:Glossary.Component.WebHome]](the number preceding and following any '.' character) should be parsed as an integer. Thus, a(% style="color:#e74c3c" %)version(%%)of 1.3 and 1.03 would be equivalent, as both the '3'[[component>>doc:sdmx:Glossary.Component.WebHome]]and the '03'[[component>>doc:sdmx:Glossary.Component.WebHome]]would parse to an integer value of 3.1974 +**LegacyVersionNumberType:** LegacyVersionNumberType describes the version number format previously supported in SDMX. The format is restricted to allow for simple incrementing and sorting of version number. The version consists of a set of maximum 2 numeric components, separated by the '.' character. When processing version, each numeric component (the number preceding and following any '.' character) should be parsed as an integer. Thus, a version of 1.3 and 1.03 would be equivalent, as both the '3' component and the '03' component would parse to an integer value of 3. 1972 1972 1973 1973 Derived by restriction of xs:string. 1974 1974
- SUZ.Methodology.Code.MethodologyClass[0]
-
- index
-
... ... @@ -1,1 +1,0 @@ 1 -3
- SKMS.Methodology.Code.MethodologyClass[0]
-
- Index
-
... ... @@ -1,0 +1,1 @@ 1 +3