From: cvs@openprivacy.orgCVS update: openprivacy/htdocs/notes/reputations
Date: Tuesday December 12, 19100 @ 22:46
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:
integrated some lines from soc.txt
*****************************************************************
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.24
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/requirements.txt?rev=1.24&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.24&r2=1.23
-----------------------------------
Index: openprivacy/htdocs/notes/reputations/requirements.txt
diff -u openprivacy/htdocs/notes/reputations/requirements.txt:1.23 openprivacy/htdocs/notes/reputations/requirements.txt:1.24
--- openprivacy/htdocs/notes/reputations/requirements.txt:1.23 Tue Dec 12 19:06:06 2000
+++ openprivacy/htdocs/notes/reputations/requirements.txt Tue Dec 12 22:46:06 2000
@@ -1,15 +1,12 @@
-$Id: requirements.txt,v 1.23 2000/12/13 03:06:06 fen Exp $
+$Id: requirements.txt,v 1.24 2000/12/13 06:46:06 fen Exp $
Reputation Server Requirements: top level feature list
"The OpenPrivacy Platform enables a distributed, secure marketplace
for anonymous user demographic and profile information."
-A. === general ===
+A. === Definitions ===
-1. decentralized, peer-to-peer
- a. agent => reputation server [ => broker ]
-
An agent
can receive requests and return responses
has an internal state and possibly access to an internal datastore
@@ -24,8 +21,17 @@
Note that a broker may not serve reputation information to others,
but it needs to be capable of reputation operations to do its work
(brokers are generally outside the scope of these requirements)
+
+B. === General ===
+
+1. decentralized, peer-to-peer
+ a. agent => reputation server [ => broker ]
+
+2. a reputation can be attached (grafted) to any URI
+ a. all reputations are URL-addressable
+ i. all reputations can have reputations grafted to them
-B. === Security, Authentication, Privacy, Validation ===
+C. === Security, Authentication, Privacy, Validation ===
Key:
U user
@@ -69,17 +75,18 @@
Note: Getting data in and out of the system securely is not part of this spec
-C. === Data store facility ===
+D. === Data store facility ===
-0. Data store features to support:
- a. insert(URL = reputation)
- b. reputationSet = select(querySet = ???)
+1. Data store features to support:
+ a. putReputation(URI=object, XML=reputation) // insert
+ b. reputationSet = getReputation(querySet=???) // select
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)
+ iv. if signed object but no reputation, return reputation of signer
+ v. define retrieval set formats (set of grafts or merged value)
+ c. removeReputation(URI=object, XML=reputation) // delete
d. define exceptions
i. reputation_does_not_exist
ii. insufficient_permissions_for_operation
@@ -90,16 +97,16 @@
ii. number of objects
iii. (what else?)
-1. Standardized data format specification
+2. 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"
-2. Standardized data store API
+3. Standardized data store API
a. (XML...)
-D. === sorting, ranking, calculating ===
+E. === sorting, ranking, calculating ===
1. Sorting, ranking
a. results may be returned ranked according to local server rules
@@ -127,7 +134,7 @@
server reputation gain will occur when:
good results within some particular domain are regularly retrieved
-E. === Communications ===
+F. === Communications ===
1. Agent discovery (in a distributed, peer-to-peer network)
a. local directory maintenance
@@ -150,7 +157,7 @@
3. works with any message-based asynchronous data transport mechanism
a. e.g. UDP, SMTP, ICQ, Carrier Pigeon, etc.
-F. === Phase II ===
+G. === Phase II ===
1. Support reputation by ontology/semantics
@@ -171,7 +178,7 @@
determine a reputation for an object which is not currently part of the
Sierra reputation system.
-G. === Wish list ===
+H. === Wish list ===
1. Ability to verify calculated results by requesting the 'opinions' which were
used to determine a calculation and then compare the results of the calculation
This archive was generated by hypermail 2b30 : Mon Jan 22 2001 - 15:52:14 PST