This document describes how to refer to Oracc web pages online or in print, using short, stable URIs.
Note too that in ESP must link to other web pages, whether on Oracc or elsewhere using full URLs, not the short forms ("tiny URLs") offered by services such as tiny.cc.
Background | Oracc.org | Definitions | Patterns |
The Oracc server supports URLs which are easier to remember and to use in links, persistent, and safe to cite in print. This facility is not yet fully developed and suggestions for additions are welcome.
For some background to the usefulness of these URLs (which are implemented using webserver rewrite rules) see Jakob Nielsen's fundamental article URL as UI.
You may also find it helpful to read the visitor help page on citing URLs, which gives a simple introduction to the material presented here.
When linking to Oracc resources, or citing them in print, you should not cite the
oracc.museum server directly: instead, use the hostname
http://oracc.org. Then append the relevant part of the
URL as given in the patterns below, which are designed to be
oracc.org will always redirect to the
current Oracc server.
In order to express the various URLs supported for Oracc projects we define some basic components before describing the patterns.
adhocmethod formerly recommended for including references to ad hoc collections of texts. Example:
http://oracc.org/dcclt/Q000001,Q000002. With a single PQID, this behaves similarly to the pattern PROJECT/PQID.html, but includes the pager frame around the text.
This pattern is used for several purposes.
http://oracc.org/ckst/middle assyrian(note the space instead of an underscore).
Eleanor Robson & Steve Tinney
Eleanor Robson & Steve Tinney, 'Referring to Oracc project URLs', Oracc: The Open Richly Annotated Cuneiform Corpus, Oracc, 2014 [http://oracc.museum.upenn.edu/doc/help/portals/projecturls/]