CVS update: openprivacy/htdocs/notes

From: cvs@openprivacy.org
Date: Mon Nov 13 2000 - 04:39:12 PST

Date: Monday November 13, 19100 @ 4:39
Author: burton
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/cvsroot/openprivacy/htdocs/notes
In directory openprivacy.org:/tmp/cvs-serv16428

Modified Files:
        description.txt
Log Message:
...

*****************************************************************
File: openprivacy/htdocs/notes/description.txt

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

CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/description.txt?annotate=1.4

CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/description.txt?rev=1.4&content-type=text/x-cvsweb-markup

CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/description.txt.diff?r1=1.4&r2=1.3

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

Index: openprivacy/htdocs/notes/description.txt
diff -u openprivacy/htdocs/notes/description.txt:1.3 openprivacy/htdocs/notes/description.txt:1.4
--- openprivacy/htdocs/notes/description.txt:1.3 Wed Nov 1 16:46:13 2000
+++ openprivacy/htdocs/notes/description.txt Mon Nov 13 04:39:12 2000
@@ -1,4 +1,4 @@
-$Id: description.txt,v 1.3 2000/11/02 00:46:13 fen Exp $
+cg$Id: description.txt,v 1.4 2000/11/13 12:39:12 burton Exp $
 
 The goal of this note is to focus on the exact minimum requirements of an
 OpenPrivacy system, particularly given the existence of similar supporting
@@ -22,7 +22,8 @@
  + anonymous publishing of profiles
    Note: censorship-resistant publishing is desired but not mandatory
    How does the user profile information get into the system?
-
+ + need to define a mechanism to aggregate/build a profile based on pubkey
+
  + a generic profile format (an extensible XML schema)
    where profiles have:
    + an anonymous/pseudonymous owner (e.g., a pubkey/credential)
@@ -30,8 +31,9 @@
    + a manifest of signed parts
    + an immutable MD5 (SHA1?) signature/checksum
    + a mutable profile/reputation accumulation mechanism
-
- + a profile storage mechanism
+ + examples in src/xml/prob*
+
+ + a profile storage mechanism (should become a default capability)
    + operated by an "agent"
      agent may have requirements like expire date, reputation, etc.
 

This archive was generated by hypermail 2b30 : Mon Jan 22 2001 - 15:52:14 PST