CVS update: openprivacy/htdocs/notes/reputations

From: cvs@openprivacy.org
Date: Fri Dec 08 2000 - 17:12:24 PST

Date: Friday December 8, 19100 @ 17:12
Author: fen
CVSWEB Options: -------------------

Main CVSWeb: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi

View this module: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations

-----------------------------------

Update of /usr/local/cvsroot/openprivacy/htdocs/notes/reputations
In directory openprivacy.org:/home/fen/projects/openprivacy/htdocs/notes/reputations

Modified Files:
        goals.txt
Log Message:
merged in some soc comments

*****************************************************************
File: openprivacy/htdocs/notes/reputations/goals.txt

CVSWEB Options: -------------------

CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/goals.txt?annotate=1.5

CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/goals.txt?rev=1.5&content-type=text/x-cvsweb-markup

CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/goals.txt.diff?r1=1.5&r2=1.4

-----------------------------------

Index: openprivacy/htdocs/notes/reputations/goals.txt
diff -u openprivacy/htdocs/notes/reputations/goals.txt:1.4 openprivacy/htdocs/notes/reputations/goals.txt:1.5
--- openprivacy/htdocs/notes/reputations/goals.txt:1.4 Fri Dec 8 16:53:20 2000
+++ openprivacy/htdocs/notes/reputations/goals.txt Fri Dec 8 17:12:24 2000
@@ -1,36 +1,34 @@
-$Id: goals.txt,v 1.4 2000/12/09 00:53:20 burton Exp $
+$Id: goals.txt,v 1.5 2000/12/09 01:12:24 fen Exp $
 
 Goals for a distributed reputation system:
 
-TODO... something like:
+=== high level goals ===
 
-
-
 System should be infrastructure agnostic. You should be able to develop with
 any programming language on any Operating System.
 
-Reputation servers are just a comunications 'daemon' which any Internet
+Reputation servers are just a communications 'daemon' which any Internet
 technology can support (HTTP servers, db servers, etc)
 
+Every object in an OpenPrivacy system
+ extends a class Reputation
+ or can respond to a getReputation method request
+ or ReputationFactory.getReputation(object) works
+ Also, every object can have a Reputation attached to it
+
+Every OpenPrivacy Agent is a ReputationServer
+ or at least can pass reputation requests on to another server
+
+=== ontology / meaning ===
+
 Support reputation by ontology/semantics. Systems can define their own
 vocabulary which can be used to markup reputations. (reputations will try to
 become standardized)
 
-Reputation data is based on public/private key pairs. 3rd parties can not fake
-your opinions.
+=== security ===
 
-Since reputation data is based on a public key information it is very hard
-(impossible?) to spoof another user.
+Third parties can not forge opinions or spoof other users
+(since Reputation data is based on public key certificates)
   http://slashdot.org/comments.pl?sid=00/12/06/0126224&cid=157
   http://slashdot.org/search.pl?query=perens&op=users
-
-Provide query mechanisms so that the data can be mined in a standard manner.
-
-Facility for 'blending' reputation results from multiple sources.
-
-Ability to verify calculated results by requesting the 'opinions' which were
-used to determine a calculation and then compare the results of the calculation
-with the opinion.
-
-
 

This archive was generated by hypermail 2b30 : Mon Jan 22 2001 - 15:52:14 PST