From: cvs@openprivacy.orgCVS update: openprivacy/htdocs/notes
Date: Thursday December 7, 19100 @ 20:21
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
-----------------------------------
Update of /usr/local/cvsroot/openprivacy/htdocs/notes
In directory openprivacy.org:/home/fen/projects/openprivacy/htdocs/notes
Modified Files:
soc-reputation.txt
Log Message:
some updates -- more to come tonight
*****************************************************************
File: openprivacy/htdocs/notes/soc-reputation.txt
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/soc-reputation.txt?annotate=1.3
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/soc-reputation.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/soc-reputation.txt.diff?r1=1.3&r2=1.2
-----------------------------------
Index: openprivacy/htdocs/notes/soc-reputation.txt
diff -u openprivacy/htdocs/notes/soc-reputation.txt:1.2 openprivacy/htdocs/notes/soc-reputation.txt:1.3
--- openprivacy/htdocs/notes/soc-reputation.txt:1.2 Thu Dec 7 14:31:05 2000
+++ openprivacy/htdocs/notes/soc-reputation.txt Thu Dec 7 20:21:10 2000
@@ -1,4 +1,4 @@
-$Id: soc-reputation.txt,v 1.2 2000/12/07 22:31:05 fen Exp $
+$Id: soc-reputation.txt,v 1.3 2000/12/08 04:21:10 fen Exp $
some more SOC on reputations - in temporal order.
I have left older ideas that are superseded by newer ideas below
@@ -14,28 +14,10 @@
Every OpenPrivacy Agent is a ReputationServer
or at least can pass reputation requests on to another server
-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
-
-A Reputation is a Signed Semantic Link
- the Signature assures that it cannot be forged
- the Semantic Link provides a context and/or meaning
- the Semantic Link can be null or missing,
- in which case the reputation is a signature
-
<!-- example simple reputation -->
<reputation>
- <pubkey>aSignature/pubkey>
+ <pubkey>aSignature</pubkey>
</reputation>
<!-- example reputation with semantic link and time stamp -->
@@ -171,6 +153,48 @@
<SignatureValue>MC0CFFrVLtRlk=...</SignatureValue>
</Signature>
+
+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
+
+What to build:
+ A Reputation Server
+
+A Reputation is a URI-addressable DSig with optional additional features (elements)
+<Signature>
+ <!--
+ the Signature assures that it cannot be forged
+ -->
+ <SignedInfo>
+ <CanonicalizationMethod Algorithm="http://www.w3.org/TR/2000/CR-xml-c14n-20001026"/>
+ <SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#dsa-sha1"/>
+ <Reference URI="...">
+ <!--
+ The Reference URI points to the object to which we are attaching
+ this Reputation
+ -->
+ <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
+ <DigestValue>...</DigestValue>
+ </Reference>
+ <semantic-link>
+ <!--
+ the Semantic Link provides a context and/or meaning
+ -->
+ </semantic-link>
+ <rating>
+ </rating>
+ </SignedInfo>
+ <SignatureValue>MC0CFFrVLtRlk=...</SignatureValue>
+</Signature>
A Reputation can be attached to a Bias, or Rating of an object, e.g.,
This archive was generated by hypermail 2b30 : Mon Jan 22 2001 - 15:52:14 PST