From: cvs@openprivacy.orgCVS update: openprivacy/htdocs
Date: Wednesday December 13, 19100 @ 16:39
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:
opr.shtml
Log Message:
updated reputation section
*****************************************************************
File: openprivacy/htdocs/opr.shtml
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/opr.shtml?annotate=1.15
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/opr.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/opr.shtml.diff?r1=1.15&r2=1.14
-----------------------------------
Index: openprivacy/htdocs/opr.shtml
diff -u openprivacy/htdocs/opr.shtml:1.14 openprivacy/htdocs/opr.shtml:1.15
--- openprivacy/htdocs/opr.shtml:1.14 Wed Oct 25 15:00:15 2000
+++ openprivacy/htdocs/opr.shtml Wed Dec 13 16:39:40 2000
@@ -1,10 +1,10 @@
<!--#include virtual="/includes/top.html"-->
<!--#include virtual="/includes/navigation.html"-->
-<!-- $Id: opr.shtml,v 1.14 2000/10/25 22:00:15 fen Exp $ -->
+<!-- $Id: opr.shtml,v 1.15 2000/12/14 00:39:40 fen Exp $ -->
<h3>OpenPrivacy Requirements</h3>
-Version: 0.2
+Version: 0.3
<p>
The following facilities, capabilities and mechanisms are required for a
@@ -28,9 +28,8 @@
<ul>
<li>creation - agents will create nyms for various operations they may
- want to be temporarily disassociated from themselves
+ want to be temporarily or permanently disassociated from themselves
<li>authentication - is this nym owned or created by a known source?
- <li>semantic categorization - within what realm is this nym asserted?
<li>reputation query - what do we know about this nym, and from whom?
<li>reputation attachment - adding new or modifying existing reputation
capital to an entity
@@ -43,35 +42,25 @@
<h3>Reputations</h3>
<p>
-Reputations are first class objects associated with a nym that can be
+Reputations are first class objects - based on XMLDSig - that can be
applied to any entity within the OpenPrivacy system. In a sense, all
objects derive from class reputation. Reputations have several static
component parts, including:
<ul>
- <li>Identity - a unique identifier (perhaps an MD5 hash?)
- <li>Created - date when this reputation was created
- <li>From - the unique identifier of the assigning party (can be null)
- <li>To - the entity to which this reputation is attached
+ <li>Reference - the entity URI to which this reputation is attached
+ <li>Identity - a unique URL (used for naming and assigning additional reputation)
+ <li>Signature - the signature of the assigning party
</ul>
-Further, reputations have mutable slots that may carry reputations on
-them recursively, including:
+Additional fields may exist that give additional information to the reputation:
<ul>
- <li>Type - a semantic name or type for this reputation
- <li>Value - the subjective value given by the assigner
-</ul>
-
-Note that Type and Value may be URIs that point to terms in a
-well-know ontology. Finally, reputations carry information that makes
-them immutable by third parties and provide other useful capabilities,such
-as non-repudiation:
-
-<ul>
- <li>Modified - date when last updated
- <li>Signature - signed by the creator, and thus can only be modified by
- the creator
+ <li>Payload - one or more semantic names, types and/or values for this reputation
+ <li>Ontology - provides semantic categorization for the payload
+ <li>KeyInfo - provides direct reference to assigner
+ <li>CreatedDate - date when this reputation was created
+ <li>ExpiryDate - date when this reputation is no longer valid
<li>Eternity_checksum - persistent, time-stamped value that ensures
non-repudiation (definition TBD)
</ul>
This archive was generated by hypermail 2b30 : Mon Jan 22 2001 - 15:52:14 PST