CVS update: openprivacy/htdocs/notes

From: cvs@openprivacy.org
Date: Mon Feb 26 2001 - 22:11:39 PST

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

    Date: Monday February 26, 19101 @ 22:11
    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:
    fleshed out form of reputation server section

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

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

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

    Index: openprivacy/htdocs/notes/whitepaper.shtml
    diff -u openprivacy/htdocs/notes/whitepaper.shtml:1.19 openprivacy/htdocs/notes/whitepaper.shtml:1.20
    --- openprivacy/htdocs/notes/whitepaper.shtml:1.19 Mon Feb 26 19:43:51 2001
    +++ openprivacy/htdocs/notes/whitepaper.shtml Mon Feb 26 22:11:39 2001
    @@ -9,7 +9,7 @@
       </head>
       <body bgcolor="#ffffff">
     
    - <!-- $Id: whitepaper.shtml,v 1.19 2001/02/27 03:43:51 fen Exp $ -->
    + <!-- $Id: whitepaper.shtml,v 1.20 2001/02/27 06:11:39 fen Exp $ -->
         
         <h1>OpenPrivacy - Building a Better Internet</h1>
     
    @@ -124,13 +124,33 @@
             avail themselves of targeted, high-quality profile information with
             the full cooperation and confidence of a pseudonymous user.
           </p>
    - <h3>Reputation Calculation Engine</h3>
    + <h3>The Reputation Server</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:
    + <blockquote>
    + <h4>Nym Service</h4>
    + <h4>Opinion Store</h4>
    + <h4>Reputation Calculation Engine (RCE)</h4>
    + </blockquote>
    + </p>
           <h3>Reference Applications</h3>
           <blockquote>
    - <h4>JetsPeek</h4>
    - <h4>OpenPrivacy-enabled Communities (e.g. Slashdot and Advogato)</h4>
    + <h4>Sierra - The Reference Reputation Server</h4>
    + <h4>Talon - Reputation-based Component Loading</h4>
    + <h4>JetsPeek - A Privacy and Reputation-enhanced Internet Portal</h4>
    + <h4>OpenPrivacy-enabled Communities, or<br>
    + Slashdot Moderation for Advogato and Trust Metrics for Slashdot</h4>
           </blockquote>
    - <h3>Security, Trust, Verifiability</h3>
    + <h3>Security, Trust, Validation and Verifiability</h3>
    + <p>
    +
    + </p>
           <h3>Attack Resistance</h3>
           <p>
           <ul>

    This archive was generated by hypermail 2b30 : Mon Feb 26 2001 - 22:11:40 PST