Changes for page Part II.Common Namespace
Last modified by Elena Yasinovskaya on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1164,13 +1164,49 @@ 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*)\+?))\).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]*~)~)~)*)?\).*.+\ 1168 1168 1169 +((( 1170 +0|[1-9]\d*)\+?)(\.((0|[1-9]\d* 1171 +))) 1172 + 1173 +{2}\).*.+\ 1174 + 1175 +((( 1176 +0|[1-9]\d*))(\.((0|[1-9]\d*)\+?))(\.((0|[1-9]\d* 1177 +))) 1178 + 1179 +\).*.+\ 1180 + 1181 +((( 1182 +0|[1-9]\d*)\+?)(\.((0|[1-9]\d* 1183 +))) 1184 + 1185 +(\.((0|[1-9]\d*)\+?))\). 1186 + 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*)\+?))\).*.+\(\*\).1190 +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]*~)~)~)*)?\).*.+\ 1173 1173 1192 +((( 1193 +0|[1-9]\d*)\+?)(\.((0|[1-9]\d* 1194 +))) 1195 + 1196 +{2}\).*.+\ 1197 + 1198 +((( 1199 +0|[1-9]\d*))(\.((0|[1-9]\d*)\+?))(\.((0|[1-9]\d* 1200 +))) 1201 + 1202 +\).*.+\ 1203 + 1204 +((( 1205 +0|[1-9]\d*)\+?)(\.((0|[1-9]\d* 1206 +))) 1207 + 1208 +(\.((0|[1-9]\d*)\+?))\).*.+\(\*\). 1209 + 1174 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 1175 1176 1176 Derived by restriction of UrnVersionPart. ... ... @@ -1924,10 +1924,10 @@ 1924 1924 1925 1925 Enumerations: 1926 1926 1927 -(% style="width:1011.29px" %) 1928 -|**Value**|(% style="width:771px" %)**Documentation** 1929 -|\*|(% style="width:771px" %)Indicates that any value of the identifier component is allowed. 1963 +|**Value**|**Documentation** 1930 1930 1965 +|\*|Indicates that any value of the identifier component is allowed.| 1966 + 1931 1931 **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. ... ... @@ -1938,38 +1938,37 @@ 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, \_, -, $.1977 +**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.1982 +**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.1987 +**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).1992 +**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.1997 +**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]).2002 +**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 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]*~)~)~)*)? 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.2007 +**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 - 1975 1975 Regular Expression Pattern: (0|[1-9]\d*)(\.(0|[1-9]\d*))?