From: cvs@openprivacy.orgCVS update: sierra/docs
Date: Wednesday January 24, 19101 @ 3:10
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/sierra/docs
-----------------------------------
Update of /usr/local/cvs/public/sierra/docs
In directory giga:/tmp/cvs-serv2935/docs
Modified Files:
TODO
Added Files:
LICENSE
Removed Files:
RCE_REQUIREMENTS
Log Message:
...
*****************************************************************
File: sierra/docs/LICENSE
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/LICENSE?annotate=1.1
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/LICENSE?rev=1.1&content-type=text/x-cvsweb-markup
-----------------------------------
*****************************************************************
File: sierra/docs/TODO
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/TODO?annotate=1.31
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/TODO?rev=1.31&content-type=text/x-cvsweb-markup
CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/TODO.diff?r1=1.31&r2=1.30
-----------------------------------
Index: sierra/docs/TODO
diff -u sierra/docs/TODO:1.30 sierra/docs/TODO:1.31
--- sierra/docs/TODO:1.30 Tue Jan 16 14:25:38 2001
+++ sierra/docs/TODO Wed Jan 24 03:10:40 2001
@@ -1,23 +1,56 @@
********************************************************************************
-* Last-Modified: $Date: 2001/01/16 22:25:38 $
-* Version: $Id: TODO,v 1.30 2001/01/16 22:25:38 burton Exp $
+* Last-Modified: $Date: 2001/01/24 11:10:40 $
+* Version: $Id: TODO,v 1.31 2001/01/24 11:10:40 burton Exp $
* Author: Kevin A. Burton ( burton@openprivacy.org )
********************************************************************************
-- Right now...
- - (DONE) RCEs need Principals
- -
+= ===============================================================================
+= REPUTATION CALCULATION ENGINE (RCE) REQUIREMENTS
+= ===============================================================================
-- Reputation class should become an interface (Talon component???). There
- should be multiple versions of this I think.
+- All RCEs are registered with their own namespace. This way a getReputation
+ request can specify a specific RCE namespace (or instance). Should this be
+ included in a RCEContext? getTargetSpace()???
+
+
+- Build a CompositeRCE which takes parameters used to build an overall
+ reputation.
+
+ - Supports nested Reputation Calculation Engines...
+
+ - Ability to offload certain ontological requests to specific engines.
+ - specify cost of a RCE so that it isn't used as often
+
+ - RCE Proxies that just run the request on a remote host.
+
- Need to meet a certain use cases. Should these go on the website??? These
should become arrowhead unit tests.
Use Case 2: http://pix.comedia.com/OpenPrivacy/20010115/DSCN6049.JPG
+- How should we define the query() mechanism which is provide within the RCE
+ interface? This would take a XPath query as a param and query a virtual XML
+ document which could be mapped to SQL/flat files/etc within the infomediary layer
+
+= ===============================================================================
+= GENERAL REQUIREMENTS
+= ===============================================================================
+
+- write a MeanRCE ReputationCalculationEngine. This should be the default which
+ ships with Sierra.
+
+- Example Virtual XML document... this should be just like the Reputation,
+ Ontology, Value APIs.
+
+ <reputations>
+ <entry pubkey="URI">
+
+- Reputation class should become an interface (Talon component???). There
+ should be multiple versions of this I think.
+
- ReputationCalculationEngine should throw Exceptions for every operation due to
the fact that a RemoteRCE may not be able to communicate.
@@ -64,9 +97,6 @@
- Need a mechanism to register ontological namespaces. This may also need to be
done via SOAP so that remote objects can install their namespaces.
-- write a MeanRCE ReputationCalculationEngine. This should be the default which
- ships with Sierra.
-
- Include support for ontology... use a default namespace. XSLT between
ontology. Come up with an Example of an XSLT between namespaces.
@@ -91,7 +121,7 @@
info??? URL,namespace which can then be parsed out and made polymorphic by the
reputation server???
-- Need a mechanism (factory) to abstract pubkeys... Avalon. The mechanism
+- Need a mechanism (factory) to abstract pubkeys... Talon. The mechanism
should support any mechanism... psuedonyms (with a key), PGP public keys, RSA,
etc. The object implementation should just have an impl of equals() so that
key comparison is up to the implementation. Is this in the Java Security
*****************************************************************
File: sierra/docs/RCE_REQUIREMENTS
This archive was generated by hypermail 2b30 : Wed Jan 24 2001 - 03:10:41 PST
