CVS update: openprivacy/htdocs/notes

From: cvs@openprivacy.org
Date: Wed Feb 28 2001 - 12:46:06 PST

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

    Date: Wednesday February 28, 19101 @ 12:46
    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:
    added jetspeek

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

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

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

    Index: openprivacy/htdocs/notes/whitepaper.shtml
    diff -u openprivacy/htdocs/notes/whitepaper.shtml:1.38 openprivacy/htdocs/notes/whitepaper.shtml:1.39
    --- openprivacy/htdocs/notes/whitepaper.shtml:1.38 Wed Feb 28 12:01:34 2001
    +++ openprivacy/htdocs/notes/whitepaper.shtml Wed Feb 28 12:46:06 2001
    @@ -9,7 +9,7 @@
       </head>
       <body bgcolor="#ffffff">
     
    - <!-- $Id: whitepaper.shtml,v 1.38 2001/02/28 20:01:34 fen Exp $ -->
    + <!-- $Id: whitepaper.shtml,v 1.39 2001/02/28 20:46:06 fen Exp $ -->
         
         <h1>OpenPrivacy - Enhancing the Internet with Reputations</h1>
     
    @@ -247,45 +247,58 @@
           <h3>Reference Applications</h3>
           <blockquote>
     
    - <h4><a href="http://sierra.openprivacy.org">Sierra</a> - The Reference
    - Reputation Management System</h4>
    -
    + <h4><a href="http://sierra.openprivacy.org/">Sierra</a>
    + - The Reference Reputation Management System</h4>
             <p>
    - Sierra is the reference implementation of our Reputation Management
    - System. It is based on the Talon component framework and defines our
    - RCE plugin mechanism.
    -
    - <p>Sierra incorporates various subsystems which should be used by most
    - RCE implementations. It defines our Nym management system, Store
    - interface, Query interface and the Reputation objects which we use as
    - Payload holders. Developers which wish to build RCEs or incorporate a
    - Reputation Management System with their application should evaluate
    - Sierra.
    -
    + Sierra is the reference implementation of our Reputation
    + Management System. It is based on the Talon component framework
    + and defines our RCE plugin mechanism.
             </p>
    -
    - <h4><a href="http://talon.openprivacy.org">Talon</a> - Reputation based
    - Component Management System</h4>
    -
    - <p> Sierra is based on a flexible component system which we call Talon.
    - Talon is designed to be a simple yet powerful component system similar
    - to <a href="http://www.mozilla.org/projects/xpcom/">XPCOM</a> or <a
    - href="http://www.microsoft.com/com/">Microsoft COM</a>. Talon solves a
    - number of problems with these existing systems and also incorporates
    - Reputations (Sierra) as part of its Component factory mechanism. Since
    - Talon uses RCEs to determine what components to return, natural
    - selection can take hold and a Talon-based system can "evolve" over time
    - to become more efficient and powerful. This mechanism is very similar
    - to advanced <a href="http://java.sun.com/products/hotspot/">profiler
    - technologies</a> but works with distributed systems.</p>
    -
    + <p>
    + Sierra incorporates various subsystems which should be used by
    + most RCE implementations. It defines our Nym management system,
    + Store interface, Query interface and the Reputation objects which
    + we use as Payload holders. Developers which wish to build RCEs or
    + incorporate a Reputation Management System with their application
    + should evaluate Sierra.
    + </p>
    + <h4><a href="http://talon.openprivacy.org/">Talon</a>
    + - Reputation based Component Management System</h4>
    + <p>
    + Sierra is based on a flexible component system which we call
    + Talon. Talon is designed to be a simple yet powerful component
    + system similar to <a href="http://www.mozilla.org/projects/xpcom/"
    + target="_new">XPCOM</a> or <a href="http://www.microsoft.com/com/"
    + target="_new">Microsoft COM</a>. Talon solves a number of
    + problems with these existing systems and also incorporates
    + Reputations (Sierra) as part of its Component factory mechanism.
    + Since Talon uses RCEs to determine what components to return,
    + natural selection can take hold and a Talon-based system can
    + "evolve" over time to become more efficient and powerful. This
    + mechanism is very similar to advanced <a
    + href="http://java.sun.com/products/hotspot/"
    + target="_new">profiler technologies</a> but works with distributed
    + systems.
    + </p>
             <h4>JetsPeek - A Privacy and Reputation-enhanced Internet Portal</h4>
             <p>
    + JetsPeek is an OpenPrivacy-enhanced personal portal builder that
    + keeps a user's profile anonymous. Further, it allows for the
    + attachment of Opinions to news stories (and to Opinion makers),
    + which enables using reputation mechanisms to more accurately
    + find and filter information.
             </p>
    -
    + <p>
    + JetsPeek taps XML (RSS) channels that are published via the Open
    + Content Syndication (OCS) mechanism. JetsPeek also supports the
    + pseudonymous publishing of preferences as well as the creation of
    + nym-based RSS channels that may be subscribed to (and earn
    + reputation from) other peers on the network.
    + </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>



    This archive was generated by hypermail 2b30 : Wed Feb 28 2001 - 12:46:07 PST