From: cvs@openprivacy.orgCVS update: openprivacy/htdocs
Date: Tuesday February 6, 19101 @ 12:42
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:
opd.shtml
Log Message:
removed capabilities; updated definitions
*****************************************************************
File: openprivacy/htdocs/opd.shtml
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/opd.shtml?annotate=1.23
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/opd.shtml?rev=1.23&content-type=text/x-cvsweb-markup
CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/opd.shtml.diff?r1=1.23&r2=1.22
-----------------------------------
Index: openprivacy/htdocs/opd.shtml
diff -u openprivacy/htdocs/opd.shtml:1.22 openprivacy/htdocs/opd.shtml:1.23
--- openprivacy/htdocs/opd.shtml:1.22 Fri Feb 2 15:10:26 2001
+++ openprivacy/htdocs/opd.shtml Tue Feb 6 12:42:48 2001
@@ -1,56 +1,27 @@
<!--#include virtual="/includes/top.html"-->
<!--#include virtual="/includes/navigation.html"-->
-<!-- $Id: opd.shtml,v 1.22 2001/02/02 23:10:26 fen Exp $ -->
+<!-- $Id: opd.shtml,v 1.23 2001/02/06 20:42:48 fen Exp $ -->
-<h3>OpenPrivacy Definition</h2>
+<h3>Definitions</h3>
-The Open Privacy Definition aims to help individuals better understand and
-maintain their privacy rights and capabilities when using the OpenPrivacy
-system. Misuse of the OpenPrivacy system could result in a temporary
-privacy violation, though generally of far less magnitude than created by
-current standard information practices.
-
-<h3>Definitions:</h3>
-
<ul>
<li>
- <b>User:</b>
- Any individual, organization or electronic entity
- that <i>generates</i> profile and/or offer data sent into
- the OpenPrivacy system for purposes of joining the anonymous
- demographics marketplace.
- </li>
- <p>
- <li>
- <b>Agent:</b>
- Any individual, organization or electronic entity that
- can receive requests and return responses.
- An agent has an internal state and can initiate communications
- with peers when set conditions are met.
- Agents inter-communicate using "Profile Reputation Objects," based on
- the XMLDsig standard, providing a secure, capability-based environment
- for information sharing.
-
- <p>
-
- OpenPrivacy Agents form a peer-to-peer network and may simultaneously
- function as a client (or "Primary Agent") for a local user and as a
- server (or "Secondary Agent") providing reputation and potentially
- other services ("facilities") for remote agents.
- </li>
- <p>
- <li>
<b>Nym:</b>
OpenPrivacy ensures privacy while enabling useful communications
through the use of strong, cryptographically secure pseudonyms, or
- "nyms." The nyms are generally comprised of public key pairs
- maintained by the user's Primary Agent, and allow for trust (or
- "reputation") to accumulate over time and usage.
+ <i>nyms</i>. A nym is generally comprised of a public key pair
+ maintained by an entity, allowing for trust (or "reputation") to
+ accumulate over time and usage. Every agent may be represented by one
+ or more nyms.
</li>
<p>
<li>
<b>Reputation:</b>
+ Information that adds subjective depth to an entity. Reputation data
+ can include personal profile information, opinions, and accumulated
+ bias. A reputation must include a unique signature to be valid, but
+ the issuer need not be known nor identifiable
Profile data, nyms, brokers and even reputations themselves can accrue
<i>reputation capital</i> that has several useful properties:
<dl>
@@ -74,9 +45,39 @@
</li>
<p>
<li>
+ <b>Agent:</b>
+ Any individual, organization or electronic entity that
+ <i>creates</i>, <i>filters</i>, <i>gathers</i> and/or
+ <i>publishes</i> reputation data.
+ Doing so enables entrance into the OpenPrivacy system for purposes of
+ joining the anonymous demographics marketplace.
+ Agents have an internal state and can initiate communications
+ with peers when set conditions are met.
+
+ <p>
+
+ OpenPrivacy Agents inter-communicate using "Profile Reputation
+ Objects," based on the XMLDsig standard, providing a secure,
+ capability-based environment for information sharing.
+ They form a peer-to-peer network and may simultaneously
+ function as a client (or "Primary Agent") for a local user and as a
+ server (or "Secondary Agent") providing reputation and potentially
+ other services ("facilities") for remote agents.
+ </li>
+ <p>
+ <li>
+ <b>User:</b>
+ An end point of communications. Also, an intelligent agent (e.g., a
+ human).
+ </li>
+ <p>
+ <li>
<b>Reputation Server:</b>
A Reputation Server is an agent that can respond to reputation
- requests such as <tt>setReputation()</tt> and <tt>getReputation()</tt>.
+ requests such as <tt>setReputation()</tt> and
+ <tt>getReputation()</tt>.
+ In addition, reputation servers provide the communications and storage
+ platform for Reputation Calculation Engines (RCEs).
</li>
<p>
<li>
@@ -119,64 +120,4 @@
negotiation mechanisms to enable autonomous operations.
</ul>
-<h3>Capabilities for Trust:</h3>
-<ul>
- <li>
- <b>User posts profile data through pseudonymous mechanism</b>
- </li>
- All profile data that resides on the OpenPrivacy system is
- disassociated from the user's true identity prior to submission.
- This is the primary mechanism through which
- a user can be assured that their privacy is safe throughout the
- system.
- <p>
- <li>
- <b>User contact by third-party entities is always opt-in</b>
- </li>
- The user is in complete control over when and what agents can and
- cannot contact her.
- If at any time an agent is behaving in a fashion disagreeable to
- the user, she can take steps to modify that behavior. If the offensive
- behavior continues, she can cleanly disconnect from the agent leaving
- it with anonymous demographic data of little value because it cannot be
- validated.
- <p>
- <li>
- <b>User owns her own data and is in complete control</b>
- </li>
- Since the user has her own local data store of information, if she ever
- chooses to change agents or decommission a nym, she can load up a new
- agent with as much or as little of her profile data as she chooses,
- potentially with no loss of profile knowledge or functionality.
- <p>
- <li>
- <b>User profile data traded between agents (and servers) is protected</b>
- </li>
- Agents can trade pseudonymous demographic information, but will usually
- find it to their mutual advantage (data compactness, speed) to trade
- entirely anonymous aggregate demographic data.
- <p>
- <li>
- <b>The OpenPrivacy platform is Open Source</b>
- </li>
- The open source aspect of the
- OpenPrivacy platform ensures that the entire system is available for
- public inspection and auditing. While this activity is beyond the
- scope of most of the expected user populace, we hope that privacy
- watchdog groups will help us by ensuring that there are no "back doors"
- that allow misuse of your private information.
- <p>
-</ul>
-
<!--#include virtual="/includes/bottom.html"-->
-
-
-
-
-
-
-
-
-
-
-
This archive was generated by hypermail 2b30 : Tue Feb 06 2001 - 12:42:49 PST