CVS update: openprivacy/htdocs

From: cvs@openprivacy.org
Date: Tue Feb 06 2001 - 13:03:22 PST

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

    Date: Tuesday February 6, 19101 @ 13:03
    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

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

    Update of /usr/local/cvs/public/openprivacy/htdocs
    In directory giga:/home/fen/projects/openprivacy/htdocs

    Modified Files:
            index.shtml
    Added Files:
            platform.shtml
    Log Message:
    moved platform from index into it's own file

    *****************************************************************
    File: openprivacy/htdocs/platform.shtml

    CVSWEB Options: -------------------

    CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/platform.shtml?annotate=1.1

    CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/platform.shtml?rev=1.1&content-type=text/x-cvsweb-markup

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

    *****************************************************************
    File: openprivacy/htdocs/index.shtml

    CVSWEB Options: -------------------

    CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/index.shtml?annotate=1.15

    CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/index.shtml?rev=1.15&content-type=text/x-cvsweb-markup

    CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/index.shtml.diff?r1=1.15&r2=1.14

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

    Index: openprivacy/htdocs/index.shtml
    diff -u openprivacy/htdocs/index.shtml:1.14 openprivacy/htdocs/index.shtml:1.15
    --- openprivacy/htdocs/index.shtml:1.14 Wed Dec 13 17:17:54 2000
    +++ openprivacy/htdocs/index.shtml Tue Feb 6 13:03:22 2001
    @@ -24,94 +24,6 @@
     on the Internet.
     See the <a href="/projects/jetspeek.shtml">JetsPeek project</a> for details.
     
    -<h3>Platform</h3>
    -
    -<h4>Secure, Privacy-enhanced Reputation Facility</h4>
    -
    -Reputations are the cornerstone to any virtual community. OpenPrivacy
    -enables reputations to be used to enhance searching as well as to filter out
    -unwanted information, all while maintaining complete user privacy. In
    -addition, the reputation substrate supports the user to:
    -
    -<ul>
    - <li>accumulate valuable <i>reputation capital</i> for shared profile
    - information, ideas and publications without needing to divulge identity
    - <li>annotate any object with machine-readable opinions (grafts), thus
    - creating a general purpose and secure reputation facility
    - <li>enable opt-in profile/reputation owner contact by third parties
    -</ul>
    -
    -<h4>Open Source with Open APIs</h4>
    -
    -OpenPrivacy is an open source platform with published XML data formats and
    -APIs that provide mechanisms to:
    -
    -<ul>
    - <li>monitor and verify proper use of personal information
    - <li>post unauthenticated (heresy) profile information anonymously
    - <li>authenticate (through opt-in verification) profile segments
    - <li>most importantly, enable complete user control over her profile,
    - including providing the ability for the user to be able to
    - disassociate herself from any particular segment of profile
    - information at any time
    -</ul>
    -
    -<h4>Safety and Trust</h4>
    -<ul>
    - <li><i>The user is in control</i> - the user maintains at all times
    - complete control over her data, or more specifically, her
    - <i>connection</i> to the data. If she wishes to disassociate from
    - data or some agent who has access to her data, she may do so with
    - absolute completeness.
    - <li><i>Transparency</i> - the user should at all times be able to see how,
    - where, when and by whom their profile information is being used.
    - While this transparency does not apply to data one does not own,
    - an important side benefit is that the system is publicly auditable.
    - <li><i>Strong cryptography</i> will be utilized throughout the system for
    - purposes of
    - <ul>
    - <li>authentication of active entities as well as data
    - <li>privacy and security - encryption only allows authorized
    - entities access to your profile
    - <li>traceable - when an offer is received, the user can determine
    - exactly how and why
    - <li>non-repudiation - agents may be held accountable for their
    - actions
    - <li>reputation accrual - profile data, agents and even reputations
    - may accrue context and time-sensitive reputation data
    - </ul>
    - <li><i>No lawyers</i> - since the contracts and privacy are guaranteed
    - cryptographically, the need for lawyers to enforce contracts is
    - diminished to near zero
    - <li><i>Open</i> - since all the workings are open source and the design
    - is available for public review, the trustworthiness quotient of the
    - OpenPrivacy platform will be high
    -</ul>
    -
    -<h4>Fully Distributed</h4>
    -OpenPrivacy will create a networked peer-to-peer platform enabling <i>Open
    -Privacy Providers</i>. This platform will provide:
    -<ul>
    - <li>storage, unique naming, indexing and retrieval mechanisms for
    - profiles. (Note that this is a business opportunity in itself!)
    - <li>privacy - a user's identity cannot be determined from their profile
    - information
    - <li>security - a user can determine how their profile is to be used,
    - explicitly permitting some uses and denying others
    -</ul>
    -
    -<h4>Standards based</h4>
    -OpenPrivacy builds on standards being used throughout the Internet, including
    -<ul>
    - <li>XML - all communications and objects are represented in XML
    - <li>XMLDsig - the XML Digital Signature standard is used as the base of
    - the Profile/Reputation OBject (PROB)
    - <li>SOAP - the Simple Object Access Protocol is used for inter-agent
    - communications
    - <li>HTTP and SMTP over TCP/IP - all communications are designed to work
    - over existing standard protocols
    -</ul>
    -
     <h3>Longer Term Goals</h3>
     
     <h4>Direct User Benefits of OpenPrivacy-enabled Systems</h4>



    This archive was generated by hypermail 2b30 : Tue Feb 06 2001 - 13:03:22 PST