A CITE library for the JVM, version 0.96.0 > CTS URNs >
Manipulating CTS URNs
In addition to extracting component parts of a URN, you can manipulate those components to create valid new URNs. New URNs necessarily have a different meaning, but because cite
facilitates building URNs from the components of another URN, semantically related URNs can be a automatically assembled.
Supported manipulations
- To refer to the cited text as a whole, we can remove the passage component of a URN.
- To generalize a URN referring to a version or exemplar, we can reduce the work component to the notional work level, while keeping the passage reference unchanged.
- To generalize a URN referring to a specific exemplar, we can reduce the work component to the version level (edition or translation), while keeping the passage reference unchanged.
- To generalize a URN with a subreference, we can reduce the passage reference to refer to the citable node, while keeping the work reference unchanged.
Example: version-level URN
For the version-level URN urn:cts:greekLit:tlg0012.tlg001.msA:2.75:
- referring to the cited version without the passage reference yields urn:cts:greekLit:tlg0012.tlg001.msA:
- generalizing it to the notional work level yields urn:cts:greekLit:tlg0012.tlg001:2.75
Example: exemplar-level URN
For the exemplar-level URN urn:cts:greekLit:tlg0012.tlg001.msA.lex:2.75:
- referring to the cited version without the passage reference yields urn:cts:greekLit:tlg0012.tlg001.msA.lex:. (Note required trailing colon.)
- generalizing it to the notional work level yields urn:cts:greekLit:tlg0012.tlg001:2.75
- generalizing it to the version level yields urn:cts:greekLit:tlg0012.tlg001.msA:2.75