Help: This page shows how the referencing vocabulary definitions are maintained and interlinked for controlled consistency of documentation. Click on the hyperlinks to see how the terms are defined within the Askemos architecture. more… Tip: Remember the back-button!

This page has three main sections. (Note that the listings could be empty.)

  1. The first item displays a term, URL, text or picture.
  2. Followed by a (still unordered) listing of statements about this subject. (for details follow ">"-link)
  3. Separated by a horizontal rule a "reverse" listing of statements referring to this item in object position.
867 ↑ ... is defined by > Askemos
869 is subproperty of > Process signature
2186 is subproperty of > e-signature
913 domain > Place (Askemos)
2171 range > OidExpression
1053 is a > wiki page
2170 is a > property
1055 description >

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 .

1653 kind/genre/type >
2172 kind/genre/type > Merkle tree
2169 adheres to > Cryptographic hash function
1059 see URL >
1094 see URL >

publicOID is subproperty of
keywords&details subject (keyword)
WebID subject (keyword)