CVS update: openprivacy/htdocs/notes

From: cvs@openprivacy.org
Date: Wed Feb 28 2001 - 01:46:34 PST

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

    Date: Wednesday February 28, 19101 @ 1:46
    Author: burton
    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:/tmp/cvs-serv12673

    Modified Files:
            whitepaper.shtml
    Log Message:
    update 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.33

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

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

    Index: openprivacy/htdocs/notes/whitepaper.shtml
    diff -u openprivacy/htdocs/notes/whitepaper.shtml:1.32 openprivacy/htdocs/notes/whitepaper.shtml:1.33
    --- openprivacy/htdocs/notes/whitepaper.shtml:1.32 Tue Feb 27 23:54:01 2001
    +++ openprivacy/htdocs/notes/whitepaper.shtml Wed Feb 28 01:46:34 2001
    @@ -9,7 +9,7 @@
       </head>
       <body bgcolor="#ffffff">
     
    - <!-- $Id: whitepaper.shtml,v 1.32 2001/02/28 07:54:01 fen Exp $ -->
    + <!-- $Id: whitepaper.shtml,v 1.33 2001/02/28 09:46:34 burton Exp $ -->
         
         <h1>OpenPrivacy - Building a Better Internet</h1>
     
    @@ -177,21 +177,32 @@
               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. Data enters and leaves the store in a
    - signed XML format.
    - </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 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>
    +
    + <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>
    +
    +
    +
    +
    +
             <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 - 01:46:35 PST