The technology-independent representation of a CITE URN as a string of characters is defined by the CITE URN specification.

Constructing CITE URN objects

You can construct an object representation of a CITE URN from a string conforming to the CITE URN specification. It is an Exception if you try to construct a CITE URN from a String that does not conform to the specification.

Examples

The string urn:cite:hmt:msA is a valid URN identifying a collection, so we can construct a URN object from it.
The string urn:cite:hmt:msA.12r is a valid URN identifying a notional object, so we can construct a URN object from it.
The string urn:cite:hmt:msA.12r.1 is a valid URN identifying a version of an object, so we can construct a URN object from it.
The string NOT-A-URN does not conform to the specification. Passing it to a constructor generates an Exception.

Unicode normalization

CITE URN objects can be constructed from strings in any Unicode form, but all output representations of the CITE URN or parts of the CITE URN as strings are normalized to Unicode form NFC.

Examples

Input string	Unicode form of input	Length of input in bytes	Output string identical to input string
urn:cite:examples:tokens.1@μῆνιν	NFC (composed)	38	Yes
urn:cite:examples:tokens.1@μῆνιν	NFD (decomposed)	39	No

CITE URNs

Constructing CITE URN objects

Examples

Unicode normalization

Examples