From: cvs@openprivacy.orgCVS update: openprivacy/htdocs/notes/reputations
Date: Monday December 11, 19100 @ 17:17
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/reputations
-----------------------------------
Update of /usr/local/cvsroot/openprivacy/htdocs/notes/reputations
In directory openprivacy.org:/tmp/cvs-serv16835
Modified Files:
requirements.txt
Log Message:
....
*****************************************************************
File: openprivacy/htdocs/notes/reputations/requirements.txt
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/requirements.txt?annotate=1.15
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/requirements.txt?rev=1.15&content-type=text/x-cvsweb-markup
CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/requirements.txt.diff?r1=1.15&r2=1.14
-----------------------------------
Index: openprivacy/htdocs/notes/reputations/requirements.txt
diff -u openprivacy/htdocs/notes/reputations/requirements.txt:1.14 openprivacy/htdocs/notes/reputations/requirements.txt:1.15
--- openprivacy/htdocs/notes/reputations/requirements.txt:1.14 Mon Dec 11 17:00:59 2000
+++ openprivacy/htdocs/notes/reputations/requirements.txt Mon Dec 11 17:17:46 2000
@@ -1,4 +1,4 @@
-$Id: requirements.txt,v 1.14 2000/12/12 01:00:59 burton Exp $
+$Id: requirements.txt,v 1.15 2000/12/12 01:17:46 burton Exp $
Reputation Server Requirements: top level feature list
@@ -98,8 +98,12 @@
payload (data conformant to the data format spec)
session key (e.g., a pseudo-random number)
some sort of TTL-like value (e.g., Freenet's hops-to-live)
+
(kab) session key will be the J
-
+
+ (kab) I think a lot of this is in 'primary-agent-protocol.txt'... should
+ we just migrate this document into requirements...? I think so.
+
works with any message-based asynchronous data transport mechanism
(e.g., UDP, SMTP, ICQ, Carrier Pigeon, etc.)
@@ -114,10 +118,14 @@
G. === Optional ===
-Support a reputation:// URI namespace based on pet names.
+Support a reputation:// URI namespace based on pet names (or another appropriate
+facility):
http://www.erights.org/elib/capability/pnml.html. This could provide a
facility to specify a way to lookup a reputation based on a human name and
- include this URI in another facility (XML, e-mail, etc).
+ include this URI in another facility (XML, e-mail, etc). A client
+ application could then use this URI namespace as a pointer to determine a
+ reputation for an object which is not currently part of the Sierra
+ reputation system.
H. === Wish list ===
This archive was generated by hypermail 2b30 : Mon Jan 22 2001 - 15:52:14 PST