From: cvs@openprivacy.orgCVS update: openprivacy/htdocs/notes
Date: Tuesday February 27, 19101 @ 0:47
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/cvs/public/openprivacy/htdocs/notes
In directory giga:/home/fen/projects/openprivacy/htdocs/notes
Modified Files:
whitepaper.shtml
Log Message:
first cut at reputation service - need to have Kevin go over this!
*****************************************************************
File: openprivacy/htdocs/notes/whitepaper.shtml
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/whitepaper.shtml?annotate=1.21
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/whitepaper.shtml?rev=1.21&content-type=text/x-cvsweb-markup
CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/whitepaper.shtml.diff?r1=1.21&r2=1.20
-----------------------------------
Index: openprivacy/htdocs/notes/whitepaper.shtml
diff -u openprivacy/htdocs/notes/whitepaper.shtml:1.20 openprivacy/htdocs/notes/whitepaper.shtml:1.21
--- openprivacy/htdocs/notes/whitepaper.shtml:1.20 Mon Feb 26 22:11:39 2001
+++ openprivacy/htdocs/notes/whitepaper.shtml Tue Feb 27 00:47:12 2001
@@ -9,7 +9,7 @@
</head>
<body bgcolor="#ffffff">
- <!-- $Id: whitepaper.shtml,v 1.20 2001/02/27 06:11:39 fen Exp $ -->
+ <!-- $Id: whitepaper.shtml,v 1.21 2001/02/27 08:47:12 fen Exp $ -->
<h1>OpenPrivacy - Building a Better Internet</h1>
@@ -90,8 +90,8 @@
power to do the right thing.
</p>
<p>
- Systems like the Anonymizer[<a href="#anon">anon</a>] and Freedom
- [<a href="#free">free</a>] provide the essential anonymity needed to
+ Systems like the Anonymizer[<a href="#anon">anon</a>] and Freedom[<a
+ href="#free">free</a>] provide the essential anonymity needed to
protect oneself from being watched while online, but they lack a way
to create and profit from a long-lived pseudonymous identity. In
today's world, people want enhanced services such as personalized
@@ -124,28 +124,75 @@
avail themselves of targeted, high-quality profile information with
the full cooperation and confidence of a pseudonymous user.
</p>
- <h3>The Reputation Server</h3>
+ <h3>Reputation Services</h3>
<p>
- We introduce the concept of a Reputation Server, which fills a key
- role in the OpenPrivacy framework. Every agent or <i>principal</i>
- within the OpenPrivacy system supports the Reputation Server
- facility. A reputation server acts as a peer in a distributed
- network, supplying the capability to create opinions (either
- autonomously or under user control) and calculate reputations. A
- Reputation Server implements the following interfaces:
+ We introduce a set of <i>Reputation Services</i> that form the
+ cornerstone of the OpenPrivacy framework. A reputation server -
+ which implements the reputation services - acts as a peer in a
+ distributed network, supplying the capability to create, store and
+ forward opinions (either autonomously or under user control), manage
+ bias structures (including creation and validation) and calculate
+ reputations. A Reputation Server implements the following
+ interfaces:
+ </p>
<blockquote>
<h4>Nym Service</h4>
+ <p>
+ OpenPrivacy uses a <i>nym service</i> to to create and manage a
+ set of pseudonymous virtual users - generaly represented by
+ public-key pairs - that inhabit OpenPrivacy space. These nyms are
+ hierarchically organized within the service, so that a few main
+ (parent) nyms can beget a large number of child nyms and child
+ nyms can recursively employ a nym service to beget grandchildren.
+ A validation mechanism exists that can assert and prove that a set
+ of child nyms were created from the same parent.
+ </p>
<h4>Opinion Store</h4>
+ <p>
+ A reputation server's <i>opinion store</i> supports the
+ putReputation() and getReputation() methods which access some form
+ of persistent data store. Data enters and leaves the store in a
+ signed XML format.
+ </p>
+ <h4>Bias Management</h4>
+ <p>
+ A reputation server can assemble a set of related opinions into a
+ <i>bias</i> and cache this structure for use by a reputation
+ calculation engine. Additionally, bias structures may be traded
+ with external entities and used for remote reputation calculation
+ or for purposes of <i>offer template</i> matching.
+ </p>
<h4>Reputation Calculation Engine (RCE)</h4>
+ <p>
+ The <i>reputation calculation engine</i> is the brains of a
+ reputation service, as it determines opinions on the information
+ it has available. In its simplest incarnation, an RCE might do
+ little more than mechanical collaborative filtering to create its
+ opinions. But a sophisticated RCE has additional information at
+ its disposal, such as the reputations of the various local
+ opinions (and their, recursive, reputations), access to the
+ opinions of other, remote RCEs, the calculated or gifted bias of
+ the requestor, and even hand-tweaking by its human maintainer.
+ Ultimately, what form its opinions take, their quality and other
+ factors are judged by its peers who may then assign it a
+ reputation, and seek its advice -- or not.
+ </p>
</blockquote>
- </p>
<h3>Reference Applications</h3>
<blockquote>
- <h4>Sierra - The Reference Reputation Server</h4>
+ <h4>Sierra - The Reference Reputation Servant</h4>
+ <p>
+ </p>
<h4>Talon - Reputation-based Component Loading</h4>
+ <p>
+ </p>
<h4>JetsPeek - A Privacy and Reputation-enhanced Internet Portal</h4>
+ <p>
+ </p>
<h4>OpenPrivacy-enabled Communities, or<br>
Slashdot Moderation for Advogato and Trust Metrics for Slashdot</h4>
+ <p>
+ </p>
</blockquote>
<h3>Security, Trust, Validation and Verifiability</h3>
<p>
@@ -476,11 +523,22 @@
descriptive opinions).
</dd>
<p>
+ <dt><li><b>Offer Template</b></dt>
+ <dd>
+ A set of seemingly disparate opinions can be grouped together
+ (in a bias-like structure) for the purpose of finding
+ best matches in a universe of unconnected data. A reputation
+ service that receives an offer template may advertise prizes for
+ parent nyms that can validate ownership of a subset of the
+ template.
+ </dd>
+ <p>
<dt><li><b>Profile</b></dt>
<dd>
- A collection of pseudonymous opinions that an entity claims
- that it can prove belong to a single (parent) entity. (The
- proof itself is called <i>validation</i>.)
+ A collection of pseudonymous opinions (also in a bias-like
+ structure) that an entity claims that it can prove belong to a
+ single (parent) entity. (The proof itself is called
+ <i>validation</i>.)
</dd>
</dl>
</blockquote>
This archive was generated by hypermail 2b30 : Tue Feb 27 2001 - 00:47:12 PST