SDMX Common References Module The common references module contains common constructs that are used to reference objects. This is validates the first part of the URN (urn:sdmx.org.infomodel.<package>.<class=). It is intended to be further restricted. This refines the prefix to make specific restrictions of package and class values. Note that only one of the patterns must match. It is intended to be further restricted. This restricts the prefix and classes patterns to validate the agency part of the URN (=<agency_id>:). This restricts the prefix and classes patterns to validate the agency part of a wildcarded URN reference (=<agency_id>:). 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. 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. 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. 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. 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. 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. 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. 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. Restricts the URN so that the pattern ends after the version part. Restricts the URN reference so that the pattern ends after the version part. Restricts the URN so that the pattern ends after the first component part. Restricts the URN reference so that the pattern ends after the first component part. Urn type for an agency. Urn type for an agency scheme. Urn type for a data consumer. Urn type for a data consumer scheme. Urn type for a data provider. Urn type for a data provider scheme. Urn type for a metadata provider. Urn type for a metadata provider scheme. Urn type for an organisation unit. Urn type for an organisation unit scheme. Urn type for a categorisation. Urn type for a category. Urn type for a category scheme. Urn type for a reporting category. Urn type for a reporting taxonomy. Urn type for a code. Urn type for a codelist. Urn type for a hierarchical code. Urn type for a hierarchy. Urn type for a hierarchy association. Urn type for a level. Urn type for a value list. Urn type for a concept. Urn type for a concept scheme. Urn type for an attribute descriptor. Urn type for a data attribute. Urn type for a dataflow. Urn type for a data structure. Urn type for a dimension. Urn type for a dimension descriptor. Urn type for a group dimension descriptor. Urn type for a measure. Urn type for a measure descriptor. Urn type for a time dimension. Urn type for a metadata attibute. Urn type for a metadataflow. Urn type for a metadata set. Urn type for a metadata structure. Urn type for a process. Urn type for a process step. Urn type for a transition. Urn type for a data constraint. Urn type for a metadata constraint. Urn type for a metadata provision agreement. Urn type for a provision agreement. Urn type for a category scheme map. Urn type for a concept scheme map. Urn type for a date pattern map. Urn type for a epoch map. Urn type for a frequency format mapping. Urn type for a organisation scheme map. Urn type for a reporting taxonomy map. Urn type for a representation map. Urn type for a structure map. Urn type for a custom type. Urn type for a custom type scheme. Urn type for a name personalisation. Urn type for a name personalisation scheme. Urn type for a ruleset. Urn type for a ruleste scheme. Urn type for a transformation. Urn type for a transformation scheme. Urn type for a user defined operator. Urn type for a user defined operator scheme. Urn type for a VTL mapping. Urn type for a VTL mapping scheme. A reference type for a structure or structure usage. A reference type for structure usage. A reference type for a structure. A reference type for a codelist or value list. A reference type for any type of organisation scheme. A reference type for any type of organisation. A reference for any type of constraint. A reference type for an agency. A reference type for an agency scheme. A reference type for a data consumer. A reference type for a data consumer scheme. A reference type for a data provider. A reference type for a data provider scheme. A reference type for a metadata provider. A reference type for a metadata provider scheme. A reference type for an organisation unit. A reference type for an organisation unit scheme. A reference type for a categorisation. A reference type for a category. A reference type for a cateogry scheme. A reference type for a reporting category. A reference type for a reporting taxonomy. A reference type for a code. A reference type for a codelist. A reference type for a hierarchical code. A reference type for a hierarchy. A reference type for a hierarchy association. A reference type for a level. A reference type for a value list. A reference type for a concept. A reference type for a concept scheme. A reference type for an attribute descriptor. A reference type for a data attribute. A reference type for a dataflow. A reference type for a data structure. A reference type for a dimension. A reference type for a dimension descriptor. A reference type for a group dimension descriptor. A reference type for a measure. A reference type for a measure descriptor. A reference type for a time dimension. A reference type for a metadata attribute. A reference type for a metadataflow. A reference type for a metadata set. A reference type for a metadata structure. A reference type for a process. A reference type for a process step. A reference type for a transition. A reference type for a data constraint. A reference type for a metadata constraint. A reference type for a metadata provision agreement. A reference type for a provision agreement. A reference type for a category scheme map. A reference type for a concept scheme map. A reference type for a date pattern map. A reference type for an epoch map. A reference type for a frequnecy format mapping. A reference type for a organisation scheme map. A reference type for a reporting taxonomy map. A reference type for a representation map. A reference type for a structure map. A reference type for a custom type. A reference type for a custom type scheme. A reference type for a name personalisation. A reference type for a name personalisation scheme. A reference type for a ruleset. A reference type for a ruleset scheme. A reference type for a transformation. A reference type for a transformation scheme. A reference type for a user defined operator. A reference type for a user defined operator scheme. A reference type for a VTL mapping. A reference type for a VTL mapping scheme. VersionReferenceType defines the structure of version number in a reference. When semantic versioning is used, the major, minor, or patch version parts can be wildcarded using "+" as an extension. For example, 2+.3.1 means the currently latest available version >= 2.3.1 (even if not backwards compatible). Note that wildcarded semantic version references cannot be combined with version extended reference (e.g. 2.3+.1-draft is not permissable). Version-extended (e.g. 1.3.1-draft) and legacy version numbers (e.g. 1 or 1.0) are also supported. 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 "+". 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. WildcardType is a single value code list, used to include the '*' character - indicating that the identification component is wildcarded. Indicates that any value of the identifier component is allowed. 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, _, -, $. TwoLevelIDType defines an identifier with exactly two levels. 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, _, -, $. 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. 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. 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). 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. SemanticVersionNumberType is a simple type for validating semantic version in the format (major.minor.patch[-extension]). 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.