OID

Object Identifier.

The describing entity of a place. A universally unique identifier.

This identifier is, in conceptual contrast to names, always choosen automatically. (TODO refer to (german) tax law's archival demands and others)

TODO oid's are "endpoint references" in the sense if web service addressing;

Furthermore OID's are self-certifying identifiers. The OID value allows to verify that the so called deed-slots have never been tampered with.

(define deed-slots
  '(dc-creator       ; creator-OID see Dublin Core
    dc-date          ; creation date
    action-document  ; behavior
    body             ; serialized content
    ))

Rationale behind those deed-slots: creator, date and body are exactly the same as for paper documents. (see also "self archiving") For processes we need to acertain the behaviour in time, the action-document. The equivalent of certificates (as in "paper") is a special case of such a process: the constant process, which raises an exception for any kind of modification attempt. NameSpaceDSSSL there's a function public-place we're using for that purpose.

TODO document link table handling (as attachment and thus handled along with the content.