This page has three main sections. (Note that the listings could be empty.) more… Tip: Remember the back-button! And don't click the number on the left.

  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.
1514 comment >

Derived from the would-be-spec document . (Would be nice, if hoist had a feature to link between different databases.)

Applications make use of the Askemos layer by virtue of the core application interface.

The core API is a small set of services. It is technically extensible with ease, however it is intended to be as small and beautiful as possible. Hence extensions are rare.

Concrete Syntax

The core API itself is language-neutral. Documentation presents it in form of XML bindings.

Elements of this API have the namespace


  • become Next state.
  • output Data object specification.
  • link Link channels to other places under a local name.
  • new Create new places.
  • grant Transfer rights.
  • revoke Revoke rights.
  • replicates Control commissioned notaries.
  • CoreAPI II Module defining convenience elements.
  • CoreAPI Local Module defining control elements for operation of the local peer.

For details on these follow the links at the bottom.

1479 is a > Modul
3770 is a > Application Programming Interface

become (BALL Core) ↑ ... is defined by
output (BALL Core) ↑ ... is defined by
link (BALL Core) ↑ ... is defined by
new (BALL Core) ↑ ... is defined by
grant (BALL Core) ↑ ... is defined by
revoke (BALL Core) ↑ ... is defined by
CoreAPI II ↑ ... is defined by
CoreAPI Local ↑ ... is defined by
version (CoreAPI) ↑ ... is defined by
links ↑ ... is defined by
replicates (BALL Core) ↑ ... is defined by