ARM4SNS: Difference between revisions

From
Jump to navigation Jump to search
No edit summary
No edit summary
Line 20: Line 20:
* Acceptability of Reputation Information by end users
* Acceptability of Reputation Information by end users


==Using/supplying Reputation Information anonymously==
==Supplying/Storing/Using Reputation Information anonymously==
* make it algorithmically impossible to derive a reputation information supplier's / user's identiy.
* make it algorithmically impossible to derive a reputation information supplier's / user's identiy.



Revision as of 14:46, 24 January 2006


Introduction

In general, what is Reputation Information good for?

  • Value Preposition: To WHOM does reputation provide WHAT value?
    • Where can the availability of reputation information help to make things better?
    • How does it help there (what does 'better' mean)?
  • Limitations: What can Reputation Information NOT provide?

What is Reputation?

  • a 0,1,2,n dimensional value?
  • a discrete or rational number?
  • comparable?

Userfriendly submission/use of Reputation Information

  • Tools for making submission of reputation information user friendly
  • Tools for making use (application) of reputation information user friendly
  • Acceptability of Reputation Information by end users

Supplying/Storing/Using Reputation Information anonymously

  • make it algorithmically impossible to derive a reputation information supplier's / user's identiy.

Toolset ... for building Reputation-based Solutions

Architecture for a Reputation Information Management System

  • building blocks for building a reputation management system (what functions do they provide, how do they intedepend on each other, feature/implmentation options/alternatives)

Method for integrating Reputation Information into a product/solution

Contributions of THIS project

Ongoing Work

which building block, which requirements (expected outcome)

Future Work

which building block, which requirements (expected outcome)