From: cvs@openprivacy.orgCVS update: openprivacy/htdocs/notes
Date: Wednesday October 18, 19100 @ 17:02
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/cvsroot/openprivacy/htdocs/notes
In directory openprivacy.org:/home/fen/projects/openprivacy/htdocs/notes
Modified Files:
research.txt
Log Message:
expanded requirements
*****************************************************************
File: openprivacy/htdocs/notes/research.txt
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/research.txt?annotate=1.3
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/research.txt?rev=1.3&content-type=text/x-cvsweb-markup
CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/research.txt.diff?r1=1.3&r2=1.2
-----------------------------------
Index: openprivacy/htdocs/notes/research.txt
diff -u openprivacy/htdocs/notes/research.txt:1.2 openprivacy/htdocs/notes/research.txt:1.3
--- openprivacy/htdocs/notes/research.txt:1.2 Sat Sep 23 00:46:28 2000
+++ openprivacy/htdocs/notes/research.txt Wed Oct 18 17:02:10 2000
@@ -1,7 +1,7 @@
File: research.txt
Research questions that need answers
-$Id: research.txt,v 1.2 2000/09/23 07:46:28 fen Exp $
+$Id: research.txt,v 1.3 2000/10/19 00:02:10 fen Exp $
Contributors:
Fen Labalme <fen@openprivacy.org>
@@ -33,12 +33,25 @@
anonymous demographic profile data
Requirements:
- nym creation / maintenance
- authentication / verification mechanisms
- data format specification
- data store requirements
- data transport
- query / matching mechanisms (XQL/XPATH?)
+* nym creation / maintenance
+* authentication / verification mechanisms
+* communication encapsulation specification
+ contains:
+ capability you want to use (e.g., via a URI to a schema or DTD)
+ 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)
+* data format specification (XML)
+* data store requirements
+ data store API needed
+ resolve which data store to use according to reputation, including:
+ price(mojo)/KB, availability, speed, similar content types,
+ feature set, does it support query, etc.
+ censorship-resistant (e.g., Freenet, MojoNation, Publius)
+* query / matching mechanisms (XQL/XPATH?)
+* decentralized (e.g., Freenet, perhaps like an extendable DNS)
+* works with any message-based asynchronous data transport mechanism
+ (e.g., UDP, SMTP, ICQ, Carrier Pigeon, etc.)
---
@@ -52,7 +65,7 @@
2a) from users?
2b) from marketers?
3) how do users/marketers/agents find and contact other agents?
- A: some form of yellow pages lookup (architcture TBD - LDAP/Dynamic DNS?)
+ A: some form of yellow pages lookup (architecture TBD - LDAP/Dynamic DNS?)
Q: what is the format of a query? of an answer?
4) how do agents compare, match and trade anon profile data?
5) how is data authenticated? (blind signatures)
@@ -81,7 +94,7 @@
TBD: map all this to XML (needed for release 1? maybe not...)
-Once received, how does an agent authenitctae, verify, and store this data?
+Once received, how does an agent authenticate, verify, and store this data?
---
This archive was generated by hypermail 2b30 : Mon Jan 22 2001 - 15:52:14 PST