Askemos

OID

Object Identifier.

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

This ↗ identifier is, in conceptual contrast to names, always chosen automatically. Typically derived from a hash over the deed-slots at least. (TODO refer to (German) tax law's archival demands and others)

(define deed-slots
  '(dc-creator       ; creator-OID see Dublin Core
    dc-date          ; creation date
    action-document  ; contract (behavior)
    replicates       ; commissioned notary devices
    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 ascertain the behaviour in time, the contract a.k.a 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. The replicates are initially commissioned to maintain the ledger (place), the model equivalent to a jurisdiction.

TBD Detail: in NameSpaceDSSSL there's a function public-place we're using for that purpose.

For implementation specific information refer to the BALL entry on OID .


subject of: keywords&details