CVS update: openprivacy/htdocs/notes

From: cvs@openprivacy.org
Date: Wed Feb 28 2001 - 11:58:14 PST

  • Next message: cvs@openprivacy.org: "CVS update: openprivacy/htdocs/notes"

    Date: Wednesday February 28, 19101 @ 11:58
    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:
    nix "servant" - more on bias management

    *****************************************************************
    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.37

    CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/whitepaper.shtml?rev=1.37&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.37&r2=1.36

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

    Index: openprivacy/htdocs/notes/whitepaper.shtml
    diff -u openprivacy/htdocs/notes/whitepaper.shtml:1.36 openprivacy/htdocs/notes/whitepaper.shtml:1.37
    --- openprivacy/htdocs/notes/whitepaper.shtml:1.36 Wed Feb 28 02:33:08 2001
    +++ openprivacy/htdocs/notes/whitepaper.shtml Wed Feb 28 11:58:14 2001
    @@ -9,7 +9,7 @@
       </head>
       <body bgcolor="#ffffff">
     
    - <!-- $Id: whitepaper.shtml,v 1.36 2001/02/28 10:33:08 fen Exp $ -->
    + <!-- $Id: whitepaper.shtml,v 1.37 2001/02/28 19:58:14 fen Exp $ -->
         
         <h1>OpenPrivacy - Enhancing the Internet with Reputations</h1>
     
    @@ -124,7 +124,7 @@
             avail themselves of targeted, high-quality profile information with
             the full cooperation and confidence of a pseudonymous user.
           </p>
    - <h3><a name="servant">Reputation Services</a></h3>
    + <h3><a name="rms">Reputation Services</a></h3>
           <p>
             We introduce a set of <i>Reputation Services</i> that form the
             cornerstone of the OpenPrivacy framework. These services provide a
    @@ -138,13 +138,13 @@
             violating user privacy.
           </p>
           <p>
    - A reputation servant - our name for the combined client and 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 servant implements the following
    - interfaces:
    + A reputation management system, 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. More
    + specifically, a reputation management system implements the
    + following interfaces:
           </p>
           <blockquote>
             <h4>Nym Service</h4>
    @@ -177,32 +177,33 @@
               of the proof without permission would directly - and adversely -
               affect the reputation of the receiver.
             </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.</p>
    -
    -
    -
    -
    -
    -
    + <p>
    + A reputation server's <i>opinion store</i> supports the
    + putReputation() and getReputation() methods which access some form
    + of persistent data store.
    + </p>
             <h4>Bias Management</h4>
    -
    - <p> A reputation management system may assemble a set of related opinions
    - into a <i>bias</i>. Bias is maintained via additional RCEs (possibly
    - object clones) with different opinion sets. When Ji creates new
    - Opinions and adds these to an RCE, a smart RCE implementation will use
    - this information as bias for future getReputation request so that
    - results are tailored for the user. </p>
    -
    -
    -
    -
    -
    + <p>
    + A reputation management system may assemble a set of related
    + opinions into a <i>bias</i>. Bias is maintained via additional
    + RCEs (possibly object clones) with different opinion sets. When a
    + nym Ji creates new Opinions and adds these to an RCE, a smart
    + implementation may choose to append these to Ji's bias for later
    + use by getReputation requests so that results are better tailored
    + for the nym.
    + </p>
    + <p>
    + Often, a bias may consist of Opinions from multiple nyms,
    + particularly since a parent nym may use multiple child nyms to
    + make successive requests. Further, a nym may want to use the bias
    + from someone else altogether, for it may want to benefit from the
    + bias of someone it holds in high regard. Finally, a RCE itself
    + may be created with and/or develop a bias through its standard
    + activities. For example, it may use sophisticated collaborative
    + filtering techniques to develop its own opinions and associated
    + bias.
    + </p>
             <h4>Reputation Calculation Engine (RCE)</h4>
             <p>
               The <i>reputation calculation engine</i> is the brains of a

    This archive was generated by hypermail 2b30 : Wed Feb 28 2001 - 11:58:17 PST