From: cvs@openprivacy.orgCVS update: openprivacy/htdocs
Date: Wednesday December 13, 19100 @ 0:40
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/cvsroot/openprivacy/htdocs
In directory openprivacy.org:/home/fen/projects/openprivacy/htdocs
Modified Files:
opd.shtml
Log Message:
updated definition from requirements
*****************************************************************
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.17
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/opd.shtml?rev=1.17&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.17&r2=1.16
-----------------------------------
Index: openprivacy/htdocs/opd.shtml
diff -u openprivacy/htdocs/opd.shtml:1.16 openprivacy/htdocs/opd.shtml:1.17
--- openprivacy/htdocs/opd.shtml:1.16 Mon Sep 25 17:22:06 2000
+++ openprivacy/htdocs/opd.shtml Wed Dec 13 00:40:47 2000
@@ -1,85 +1,92 @@
<!--#include virtual="/includes/top.html"-->
<!--#include virtual="/includes/navigation.html"-->
-<!-- $Id: opd.shtml,v 1.16 2000/09/26 00:22:06 fen Exp $ -->
+<!-- $Id: opd.shtml,v 1.17 2000/12/13 08:40:47 fen Exp $ -->
<h3>OpenPrivacy Definition</h2>
-Version: 0.3
-<p>
- <h3>Status of this document:</h3>
- This document is currently a
- <a href="/organization.shtml">Working Draft</a>.
- </p>
-<p>
-
- <h3>Editors:</h3>
- Fen Labalme <<a href="mailto:fen@openprivacy.org">fen@openprivacy.org</a>>
- <br>
- Kevin Burton <<a href="mailto:burton@openprivacy.org">burton@openprivacy.org</a>>
-
- <p>
- <h3>Overview:</h3>
- </p>
-
- <p>
- The Open Privacy Definition was created so that individuals
- can 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.
- </p>
-
- <p>
- <h3>Definitions:</h3>
- </p>
+Version: 0.4
+<h3>Status of this document:</h3>
+
+This document is currently a
+<a href="/organization.shtml">Working Draft</a>.
+
+<h3>Editors:</h3>
+
+Fen Labalme <<a href="mailto:fen@openprivacy.org">fen@openprivacy.org</a>>
+<br>
+Kevin Burton <<a href="mailto:burton@openprivacy.org">burton@openprivacy.org</a>>
+
+<h3>Overview:</h3>
+
+The Open Privacy Definition was created so that individuals can 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.
+
+<h3>Definitions:</h3>
+
<ul>
- <p>
- <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>
-
- <p>
- <li>
- <b>Agent</b> (aka <b>Broker</b> or <b>Broadcatch
- <a href="/bibliography.shtml#infomediary">Infomediary</a></b>)<b>:</b>
- Any individual, organization or electronic entity that
- <i>adds value</i> to profile data by collecting, sorting, indexing,
- matching or otherwise enhancing connections between profile data.
-
- </li>
- </p>
- <p>
- <li>
- <b>Reputation:</b>
- Profile data, nyms, brokers and even reputations can accrue
- <i>reputation capital</i> that has several useful properties:
- <dl>
- <dt>
- <b><i>Secure</i></b>
- </dt>
- <dd>Reputations cannot be subverted, and the source of reputation
- assertions can always be traced. This provides
- non-repudiation as well as the mechanism with which to decide
- which reputation information to trust.
- </dd>
- <dt>
- <b><i>Transitive</i></b>
- </dt>
- <dd>Reputations are transitive, in that if A trusts B who
- trusts C (within the constraints of a well-defined domain),
- then A can reasonably trust C (within that domain).
- </dd>
- </dl>
- </li>
- </p>
+ <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.
+ </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>.
+ </li>
+ <p>
+ <li>
+ <b>Broker</b> or <b>Broadcatch</b>
+ <a href="/bibliography.shtml#infomediary"><b>Infomediary</b></a><b>:</b>
+ A broker is a reputation server that has added intelligence for some
+ domain. Generally, a broker is capable of adding value to
+ profile and reputation information by collecting, sorting, indexing,
+ matching or otherwise enhancing connections between data.
+ <i>Note: Brokers are built on top of the OpenPrivacy platform and
+ therefore are generally outside the scope its requirements.</i>
+ </li>
+ <p>
+ <li>
+ <b>Reputation:</b>
+ Profile data, nyms, brokers and even reputations can accrue
+ <i>reputation capital</i> that has several useful properties:
+ <dl>
+ <dt>
+ <b><i>Secure</i></b>
+ </dt>
+ <dd>Reputations cannot be subverted, and the source of reputation
+ assertions can always be traced. This provides
+ non-repudiation as well as the mechanism with which to decide
+ which reputation information to trust.
+ </dd>
+ <dt>
+ <b><i>Transitive</i></b>
+ </dt>
+ <dd>Reputations are transitive, in that if A trusts B who
+ trusts C (within the constraints of a well-defined domain),
+ then A can reasonably trust C (within that domain).
+ </dd>
+ </dl>
+ </li>
</ul>
+
<h3>Assumptions</h3>
+
<h4>Basic</h4>
<ul>
<li>Users have access to personal information access and buying habits
@@ -105,91 +112,64 @@
negotiation mechanisms to enable autonomous operations.
</ul>
-
-<p>
- <h3>Capabilities for Trust:</h3>
-</p>
+<h3>Capabilities for Trust:</h3>
<ul>
+ <li>
+ <h3>User posts profile data through pseudonymous mechanism</h3>
+ </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>
+ <h3>User contact by third-party entities is always opt-in</h3>
+ </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>
+ <h3>User owns her own data and is in complete control</h3>
+ </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>
+ <h3>User profile data traded between agents (and servers) is protected</h3>
+ </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>
+ <h3>The OpenPrivacy platform is Open Source</h3>
+ </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"-->
- <li>
- <h3>
- User posts profile data through pseudonymous mechanism
- </h3>
- </li>
-
- <p>
- 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>
- <h3>
- User contact by third-party entities is always opt-in
- </h3>
- </li>
-
- <p>
- 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>
- <h3>
- User owns her own data and is in complete control
- </h3>
- </li>
-
- <p>
- 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>
- <h3>
- User profile data traded between agents (and servers) is protected
- </h3>
- </li>
-
- <p>
- 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>
- <h3>
- The OpenPrivacy platform is Open Source
- </h3>
- </li>
-
- <p>
- 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 : Mon Jan 22 2001 - 15:52:14 PST