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.

Similarity Of Contracts: Ricardian And Askemos

Looking at Ricardian and Askemos contracts we've been asking ourself: are contracts in Askemos Ricardian Contracts, vice versa or not related?

Am 29.07.2014 16:49, ianG wrote:

On 28/07/2014 20:31 pm, "Jörg F. Wittenberger" wrote:

Am 22.07.2014 17:48, ianG wrote:

Hey Chris and Jörg,

I'd like to introduce you to each other.

Chris: Jörg created something called Askemos which is a payment system based on contracts. Implemented as a set of notaries running on servers, providing access over browser using HTML5/style/etc.

Well, actually, the more I understand Ricardian Contract, the more I tend to claim that a Ricardian Contract is functionally indistinguishable from the "governing" or "type" contract in Askemos.

I suspect so too. A Ricardian Contract is a master contract signed by one party, the issuer. The issuer offers to any 'holders' various conditions.

Without any holders (additional parties), the Ricardian Contract is a null instrument. Only when parties take and make payment in the unit do then they form a proper legal contract with the issuer, the agreement of which is spelt out in the RC.

Let me substitute terms from Askemos to illustrate the relationship:

A "governing contract" is a master contract signed by one party, the "author". The author offers to any 'agents' various conditions. Without any agents (additional parties), the governing contract is a publication. Only when parties execute a processing step in compliance with the terms do then they form a proper legal contract with (or without) the author, the agreement of which is spelt out in the type contract.

The question is somewhat philosophical: what's the RC of an RC? How does an agent learn about a contract? It needs to be disclosed to the agent somehow. Do strings apply? May agents learning about a RC disclose it to third parties?

That's the question Askemos cares about when loading code to execute a transition in support of an agent. At this level is does not have a remote idea what a "payment" even could be. It does understand "various conditions" as in "executable source code" (recommended, but not checked: human readable comments included).

Important to note: it checks the same logic. Therefore a Ricardian Contract is IMHO a subclass of Askemos type contract specialized to fungible (financial) instruments.

do we need this link?