CVS update: openprivacy/htdocs/notes

From: cvs@openprivacy.org
Date: Tue Feb 27 2001 - 23:01:12 PST

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

    Date: Tuesday February 27, 19101 @ 23:01
    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:
    tightened up format of definitions (thanks again, elaine!)

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

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

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

    Index: openprivacy/htdocs/notes/whitepaper.shtml
    diff -u openprivacy/htdocs/notes/whitepaper.shtml:1.28 openprivacy/htdocs/notes/whitepaper.shtml:1.29
    --- openprivacy/htdocs/notes/whitepaper.shtml:1.28 Tue Feb 27 22:22:10 2001
    +++ openprivacy/htdocs/notes/whitepaper.shtml Tue Feb 27 23:01:11 2001
    @@ -9,7 +9,7 @@
       </head>
       <body bgcolor="#ffffff">
     
    - <!-- $Id: whitepaper.shtml,v 1.28 2001/02/28 06:22:10 fen Exp $ -->
    + <!-- $Id: whitepaper.shtml,v 1.29 2001/02/28 07:01:11 fen Exp $ -->
         
         <h1>OpenPrivacy - Building a Better Internet</h1>
     
    @@ -364,92 +364,89 @@
             also financially.
           </p>
         </blockquote>
    - <h2>References</h2>
    + <h2><a name="references">References</a></h2>
         <blockquote>
           <h3>Definitions</h3>
    - <blockquote>
    - <dl>
    - <dt><li><b>Reference</b></dt>
    - <dd>
    - A pointer to an entity (generally a URI, often a URL). Examples
    - include a physical or virtual object, place, person, pseudonym,
    - web page or site, opinion, reputation, bias, profile, and
    - reputation calculation engine.
    - </dd>
    - <p>
    - <dt><li><b>Nym</b></dt>
    - <dd>
    - Short for "pseudonym," a nym is a fictitious name that can refer
    - to an entity without using any of its directly identifiable
    - characteristics, such as name, location, etc. OpenPrivacy uses
    - public-key pairs to represent a nym, with the owner having sole
    - access to the private part and the public part being published
    - to at least one external party. Often, we refer to the public
    - key as the "nym," as it is how the entity is know in the outside
    - world.
    - </dd>
    - <p>
    - <dt><li><b>Principal</b></dt>
    - <dd>
    - An identifiable, pseudonymous, or anonymous entity. A principal
    - can be uniquely referenced by its public key. Any static entity
    - that can be referenced can in theory be a principal, the only
    - requirement being that it can store a private key and perform
    - signature operations.
    - </dd>
    - <p>
    - <dt><li><b>Opinion</b></dt>
    - <dd>
    - A unique description of something (pointed to by a reference).
    - Uniqueness is satisfied by attaching a hash, generally created
    - from the pricipal's signature, to the opinion such that no two
    - opinions are exactly the same. An opinion may be clearly
    - subjective (as in "openssl is a good cryptography package") or
    - appear as a statement (as in "I live in San Francisco," where
    - the reference is "San Francisco" and the description is "where I
    - live").
    - </dd>
    - <p>
    - <dt><li><b>Reputation</b></dt>
    - <dd>
    - A value that represents the collective opinion of some
    - reference. A Reputation is really just another name for an
    - Opinion, as it is the calculated opinion of the reference by the
    - reputation calculation engine. Reputations are ephemeral, and
    - the weight applied to an Opinion representing the reputation of
    - some reference is subjectively applied by the end user (person
    - or program) that requests it.
    - </dd>
    - <p>
    - <dt><li><b>Bias</b></dt>
    - <dd>
    - While reputations generally reflect the sum of many opinions of
    - a single reference, a bias is an accumulation of opinions that
    - represent the views of a single principal. Biases may be
    - divided by area or type of reference (such as groups of
    - political or demographically descriptive opinions). A RCE uses
    - one or more Bias collections in the couse of its calculations.
    - </dd>
    - <p>
    - <dt><li><b>Offer Template</b></dt>
    - <dd>
    - A set of seemingly disparate opinions can be grouped together
    - (in a bias-like structure) for the purpose of finding
    - best matches in a universe of unconnected data. A reputation
    - service that receives an offer template may advertise prizes for
    - parent nyms that can validate ownership of a subset of the
    - template.
    - </dd>
    - <p>
    - <dt><li><b>Profile</b></dt>
    - <dd>
    - A collection of pseudonymous opinions (also in a bias-like
    - structure) that an entity claims that it can prove belong to a
    - single (parent) entity. (The proof itself is called
    - <i>validation</i>.)
    - </dd>
    - </dl>
    - </blockquote>
    + <ul>
    + <li><b>Reference:</b>
    + A pointer to an entity (generally a URI, often a URL). Examples
    + include a physical or virtual object, place, person, pseudonym,
    + web page or site, opinion, reputation, bias, profile, and
    + reputation calculation engine.
    + </li>
    + <p>
    + <li><b>Nym:</b>
    + Short for "pseudonym," a nym is a fictitious name that can refer
    + to an entity without using any of its directly identifiable
    + characteristics, such as name, location, etc. OpenPrivacy uses
    + public-key pairs to represent a nym, with the owner having sole
    + access to the private part and the public part being published
    + to at least one external party. A long-lived nym is useful in
    + that it allows for trust (or "reputation") to accumulate over
    + time and usage. Often, we refer to the public key as the "nym,"
    + as it is how the entity is know in the outside world.
    + </li>
    + </p>
    + <p>
    + <li><b>Principal:</b>
    + An identifiable, pseudonymous, or anonymous entity. A principal
    + can be uniquely referenced by its public key. Any static entity
    + that can be referenced can in theory be a principal, the only
    + requirement being that it can store a private key and perform
    + signature operations.
    + </li>
    + </p>
    + <p>
    + <li><b>Opinion:</b>
    +
    + A unique description of something (pointed to by a reference).
    + Uniqueness is satisfied by attaching a hash, generally created
    + from the pricipal's signature, to the opinion such that no two
    + opinions are exactly the same. An opinion may be clearly
    + subjective (as in "openssl is a good cryptography package") or
    + appear as a statement (as in "I live in San Francisco," where
    + the reference is "San Francisco" and the description is "where I
    + live").
    + </li>
    + </p>
    + <p>
    + <li><b>Reputation:</b>
    + A value that represents the collective opinion of some
    + reference. A Reputation is really just another name for an
    + Opinion, as it is the calculated opinion of the reference by the
    + reputation calculation engine. Reputations are ephemeral, and
    + the weight applied to an Opinion representing the reputation of
    + some reference is subjectively applied by the end user (person
    + or program) that requests it.
    + </li>
    + </p>
    + <p>
    + <li><b>Bias:</b>
    + While reputations generally reflect the sum of many opinions of
    + a single reference, a bias is an accumulation of opinions that
    + represent the views of a single principal. Biases may be
    + divided by area or type of reference (such as groups of
    + political or demographically descriptive opinions). A RCE uses
    + one or more Bias collections in the couse of its calculations.
    + </li>
    + </p>
    + <p>
    + <li><b>Offer Template:</b>
    + A set of seemingly disparate opinions can be grouped together
    + (in a bias-like structure) for the purpose of finding
    + best matches in a universe of unconnected data. A reputation
    + service that receives an offer template may advertise prizes for
    + parent nyms that can validate ownership of a subset of the
    + template.
    + </li>
    + </p>
    + <p>
    + <li><b>Profile:</b>
    + A collection of pseudonymous opinions (also in a bias-like
    + structure) that an entity claims that it can prove belong to a
    + single (parent) entity. (The proof itself is called
    + <i>validation</i>.)
    + </ul>
           <h3>Bibliography</h3>
           <dl>
             <dt><a name="anon">[anon]</a> The Anonymizer



    This archive was generated by hypermail 2b30 : Tue Feb 27 2001 - 23:01:12 PST