Specify the contents of contracts
This step has to be performed for each interaction with different contracts. The designer has to make sure that all
relevant aspects of the interaction are captured in the contract. Depending on the actual interaction, this includes
prices, delivery deadlines, maximum response times, etc. |
Define the data stored in experiences
Experiences can store pre-processed data, such as deviations from the contract, or raw data, e.g., the contract and the
actual result of the experience. Depending on the trust model used, only relevant information must be stored. However,
discarding information can also mean that the system is not flexible w.r.t. later changes in the trust model. The
designer has to make a conscious and well documented decision which data is kept and which pre-processing steps have to
take place.
|
Design interfaces to the trust model and the agents
In order to make the data available to the trust model and to the agents, appropriate interfaces have to be defined. If a
reputation system is used, make sure that it can also access the trust values or it automatically
receives new trust values (pull or push). |
|