From: cvs@openprivacy.orgCVS update: openprivacy/htdocs/notes/reputations
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:
requirements.txt
Log Message:
merged in some soc comments
*****************************************************************
File: openprivacy/htdocs/notes/reputations/requirements.txt
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/requirements.txt?annotate=1.3
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/requirements.txt?rev=1.3&content-type=text/x-cvsweb-markup
CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/requirements.txt.diff?r1=1.3&r2=1.2
-----------------------------------
Index: openprivacy/htdocs/notes/reputations/requirements.txt
diff -u openprivacy/htdocs/notes/reputations/requirements.txt:1.2 openprivacy/htdocs/notes/reputations/requirements.txt:1.3
--- openprivacy/htdocs/notes/reputations/requirements.txt:1.2 Fri Dec 8 16:31:13 2000
+++ openprivacy/htdocs/notes/reputations/requirements.txt Fri Dec 8 17:12:31 2000
@@ -1,4 +1,4 @@
-$Id: requirements.txt,v 1.2 2000/12/09 00:31:13 burton Exp $
+$Id: requirements.txt,v 1.3 2000/12/09 01:12:31 fen Exp $
Requirements:
@@ -17,3 +17,40 @@
-
+=== access ===
+
+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.
+
+Local garbage collection, editing, enhancement and censorship
+ A reputation server can sweep its objects and, based on local criteria:
+ remove the object if:
+ the signature/hash is no longer valid
+ the signature cannot be validated (purely anonymous)
+ the signature belongs to a low-reputation source (potential for local censorship)
+ enhance the object with high billing or additional local reputation if:
+ the signature/content/object has high reputation according to the local agent
+ Note that overall, there are many possibilities for a local reputation server
+ if the local reputation server is found to be too biased, it will lose reputation
+ if it is found to yield very good results within some particular domain space
+
+Reputation Server Requirements - top level feature list
+ basic database features (insert, select, delete)
+ define selection criteria constraints
+ define retrieval set format
+ define exceptions
+ define admin features, such as size, number of objects, etc.
+ object validation
+ does the object that was grafted to still exist / has it changed?
+ are signatures valid/reputable?
+ sorting, ranking
+ results may be returned ranked according to local server rules
+ reputation calculation (may require peer communications)
+ given an object, return its full reputation
+ as a set of object grafts
+ as a merged value
This archive was generated by hypermail 2b30 : Mon Jan 22 2001 - 15:52:14 PST