From: cvs@openprivacy.orgCVS update: openprivacy/htdocs/notes/reputations
Date: Tuesday December 12, 19100 @ 18:38
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/reputations
-----------------------------------
Update of /usr/local/cvsroot/openprivacy/htdocs/notes/reputations
In directory openprivacy.org:/home/fen/projects/openprivacy/htdocs/notes/reputations
Modified Files:
requirements.txt
Log Message:
updated data store facility
*****************************************************************
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.20
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/requirements.txt?rev=1.20&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.20&r2=1.19
-----------------------------------
Index: openprivacy/htdocs/notes/reputations/requirements.txt
diff -u openprivacy/htdocs/notes/reputations/requirements.txt:1.19 openprivacy/htdocs/notes/reputations/requirements.txt:1.20
--- openprivacy/htdocs/notes/reputations/requirements.txt:1.19 Tue Dec 12 12:43:47 2000
+++ openprivacy/htdocs/notes/reputations/requirements.txt Tue Dec 12 18:38:48 2000
@@ -1,4 +1,4 @@
-$Id: requirements.txt,v 1.19 2000/12/12 20:43:47 fen Exp $
+$Id: requirements.txt,v 1.20 2000/12/13 02:38:48 fen Exp $
Reputation Server Requirements: top level feature list
@@ -14,7 +14,7 @@
can receive requests and return responses
has an internal state and possibly access to an internal datastore
can examine its state
- can initiate communications when programmed conditions are met
+ can initiate communications with peers when programmed conditions are met
A reputation server is an agent that can
respond to reputation requests
@@ -69,19 +69,35 @@
Note: Getting data in and out of the system securely is not part of this spec
-C. === Data storage ===
+C. === Data store facility ===
-Database features (insert, select, delete)
- define selection criteria (query) constraints
- provide query/matching mechanisms (XQL/XPATH?)
- that support standard data mining interfaces
- when and how does this calculation span peer reputation servers?
- define retrieval set format
- define exceptions
- define admin features, such as size, number of objects, etc.
+0. Data store features to support:
+ a. insert(URL = reputation)
+ b. reputationSet = select(querySet = ???)
+ i. define selection criteria (query) constraints (XML...)
+ ii. provide query/matching mechanisms (XQL/XPATH?)
+ that support standard data mining interfaces
+ iii. when and how does this calculation span peer reputation servers?
+ iv. define retrieval set format
+ c. delete(URL = reputation)
+ d. define exceptions
+ i. reputation_does_not_exist
+ ii. insufficient_permissions_for_operation
+ iii. timeout
+ iv. (what else?)
+ e. define admin features
+ i. size of database (Kb)
+ ii. number of objects
+ iii. (what else?)
+
+1. Standardized data format specification
+ a. based on the xmldsig namespace (xmlns="http://www.w3.org/2000/09/xmldsig#")
+ b. extended by:
+ i. reputation:xmlns="http://www.openprivacy.org/2000/12/reputation-metainfo"
+ ii. payload:xmlns="http://www.openprivacy.org/2000/12/reputation-opinion"
-Standardized data format specification
- and standardized data store API
+2. Standardized data store API
+ a. (XML...)
D. === sorting, ranking, calculating ===
This archive was generated by hypermail 2b30 : Mon Jan 22 2001 - 15:52:14 PST