From: cvs@openprivacy.orgCVS update: openprivacy/htdocs/notes/reputations
Date: Tuesday January 16, 19101 @ 19:18
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:
protocol.txt
Log Message:
not a search engine - a search engine enabler!
*****************************************************************
File: openprivacy/htdocs/notes/reputations/protocol.txt
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/protocol.txt?annotate=1.4
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/protocol.txt?rev=1.4&content-type=text/x-cvsweb-markup
CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/protocol.txt.diff?r1=1.4&r2=1.3
-----------------------------------
Index: openprivacy/htdocs/notes/reputations/protocol.txt
diff -u openprivacy/htdocs/notes/reputations/protocol.txt:1.3 openprivacy/htdocs/notes/reputations/protocol.txt:1.4
--- openprivacy/htdocs/notes/reputations/protocol.txt:1.3 Tue Jan 16 18:53:47 2001
+++ openprivacy/htdocs/notes/reputations/protocol.txt Tue Jan 16 19:18:32 2001
@@ -1,24 +1,43 @@
-$Id: protocol.txt,v 1.3 2001/01/17 02:53:47 fen Exp $
+$Id: protocol.txt,v 1.4 2001/01/17 03:18:32 fen Exp $
protocol requirements:
-If a query is run on the system and no data is returned. The system should
-throw an exception (fault). This exception should be thrown on an general
-calculation and also if an individual has no opinion on a given URI.
-
-RS == ReputationServer
-
-Prob R1: [uri = aURI,
- val = bad,
- pub = J1,
- sig = xyz] // xyz = J1(hash(probR1))
-R1.getURI() = reputation://RS/J1/xyz
+exceptions: noReputationFound
+ noOpinion
-// returns a single prob signed by RS
-R2 = RS.getCalculatedReputation(aURI)
-Prob R2: [uri = aURI,
- val = bad,
- pub = RSpub,
- sig = dfg] // dfg = RS(hash(probR2))
+// given: RS == ReputationServer
+//
+Opinion ref = createOpinion(
+ uri = aURI,
+ val = bad)
+Sig sig = OP.hash().sign(J1sec)
+Prob R1 = createProb( // R1.getURI() = reputation:///J1/sig
+ ref = ref,
+ pub = J1pub,
+ sig = sig)
+RS.putReputation(R1)
-//
+// return a single prob signed by RS
+R2 = RS.getCalculatedReputation(aURI)
+printProb(R2)
+>> R2: [uri = aURI, val = bad]
+>> verified signature: RSpub
+
+// return reputations created by public key J1
+// + most recent first
+// + limit to number NNN
+// + that have highest reputation
+// + given the bias aBias
+
+// return reputations attached to URI aURI
+// + most recent first
+// + limit to number NNN
+// + that have highest reputation
+// + given the bias aBias
+
+Given all these cases, it looks a bit like we need to build a general search
+engine. But the reputation system enables the creation of very specialized
+search engines, as it allows everyone to become an index. Further, special
+purpose agents can act as sophisticated caches of information so that they
+can provide quick and accutrate results given a range of in-domain bias
+inputs.
This archive was generated by hypermail 2b30 : Mon Jan 22 2001 - 15:52:15 PST