ARM4SNS: Difference between revisions

From
Jump to navigation Jump to search
No edit summary
Line 23: Line 23:
* using a tusted reputation provider who must keep all information secret
* using a tusted reputation provider who must keep all information secret
* 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.





=Toolset ... for building Reputation-based Solutions=
=Toolset ... for building Reputation-based Solutions=
Line 31: Line 34:
** how do they depend on each other?
** how do they depend on each other?
** alternative building blocks for similar functionality
** alternative building blocks for similar functionality
* sample scenario for illustrating building block's functionality and interactions


==Method for integrating Reputation Information into a product/solution==
==Method for integrating Reputation Information into a product/solution==
* Given an application and given a reputation management system, are there common techniques for integrating the two?





Revision as of 15:10, 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 1,2,n dimensional value?
  • a discrete or a rational number?
  • comparable, combinable?

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

Anonymously Supplying/Storing/Using Reputation Information

  • using a tusted reputation provider who must keep all information secret
  • 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 the building blocks provide?
    • how do they depend on each other?
    • alternative building blocks for similar functionality
  • sample scenario for illustrating building block's functionality and interactions

Method for integrating Reputation Information into a product/solution

  • Given an application and given a reputation management system, are there common techniques for integrating the two?



Working Packages

  • which building block?
  • which requirements?
  • expected outcome?



State of the art

  • Literature survey
  • Conferences to watch
  • Companies active in this area