From: cvs@openprivacy.orgCVS update: sierra/docs
Date: Thursday January 25, 19101 @ 11:06
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-serv7186/docs
Modified Files:
DOCUMENTATION_TODO TODO
Log Message:
...
*****************************************************************
File: sierra/docs/DOCUMENTATION_TODO
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/DOCUMENTATION_TODO?annotate=1.4
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/DOCUMENTATION_TODO?rev=1.4&content-type=text/x-cvsweb-markup
CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/DOCUMENTATION_TODO.diff?r1=1.4&r2=1.3
-----------------------------------
Index: sierra/docs/DOCUMENTATION_TODO
diff -u sierra/docs/DOCUMENTATION_TODO:1.3 sierra/docs/DOCUMENTATION_TODO:1.4
--- sierra/docs/DOCUMENTATION_TODO:1.3 Tue Jan 16 05:59:54 2001
+++ sierra/docs/DOCUMENTATION_TODO Thu Jan 25 11:06:10 2001
@@ -8,6 +8,34 @@
- Reputaton Calculation Engine
-- CVSROOT
+- CVSROOT??
- Mailing list.
+
+- How is everything tied together? UML?
+
+- Why are we using Talon??
+
+- describe the advantages that existing reputation based systems would get form
+ an open system like Sierra.
+
+ - standardized reputation framework
+ - reuse and nesting of existing Reputation Calculation Engines.
+ - remote query of RCEs
+ - ontological forwarding.
+ - different engine query.
+
+
+
+- Go over things that an RCE can do:
+ - get all reputation which point to a certain URI
+ - FILL IN OUR ADDITIONAL USE CASES.
+ - Give examples of Slashdot/etc using this.
+
+
+- Advantage: nym management
+ - identities can be portable across sites (slashdot and advogato can have the
+ same users).
+
+- Advangate: privacy
+ - privacy is always maintained for you users.
*****************************************************************
File: sierra/docs/TODO
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/TODO?annotate=1.36
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/TODO?rev=1.36&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.36&r2=1.35
-----------------------------------
Index: sierra/docs/TODO
diff -u sierra/docs/TODO:1.35 sierra/docs/TODO:1.36
--- sierra/docs/TODO:1.35 Wed Jan 24 12:52:38 2001
+++ sierra/docs/TODO Thu Jan 25 11:06:10 2001
@@ -1,46 +1,65 @@
********************************************************************************
-* Last-Modified: $Date: 2001/01/24 20:52:38 $
-* Version: $Id: TODO,v 1.35 2001/01/24 20:52:38 burton Exp $
+* Last-Modified: $Date: 2001/01/25 19:06:10 $
+* Version: $Id: TODO,v 1.36 2001/01/25 19:06:10 burton Exp $
* Author: Kevin A. Burton ( burton@openprivacy.org )
********************************************************************************
-
= ===============================================================================
= PRIORITY
= ===============================================================================
-
-- Should the SOAP Service just move under an rce.impl directory?
-- should it become SOAPServerRCE
-- Should we have a SOAPClientRCE
+- Should we have a SOAPClientRCE?
- should the SOAPServerRCE be pointed to another impl RCE which is local?
+
+
= ===============================================================================
+= COMPOSITE RCE NOTES
+= ===============================================================================
+
+Need to create a CompositeRCE component that held other RCEs and used each one
+intelligently.
+
+This could potentially be the default way that a Reputation server is used and
+it would be configured to use the correct RCE (remote or local).
+
+- determine the correct RCE by the type of URI requested.
+
+- if a getReputation is called on an object with a reputation:// URI where the
+ SERVER is specified... use a Remote object for this. IE:
+ reputation://www.slashdot.org/PUBKEY we would forward this to a SOAPClientRCE
+ which would have to point to slashdot.
+
+- Ability to offload certain ontological requests to specific engines.
+
+- specify cost of a RCE so that it isn't used as often??
+
+- is it possible to deploy a composite object which blends the responses from
+ multiple reputation servers??? (this might be something we need in the
+ future).
+
+- Example properties config:
+
+ talon.component.DEFAULT_RCE.classname=org.openprivacy.sierra.rce.CompositeRCE
+
+ talon.component.DEFAULT_RCE.property.
+
+= ===============================================================================
= REPUTATION CALCULATION ENGINE (RCE) REQUIREMENTS
= ===============================================================================
+
+
- 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 ReputationContext? getTargetRCE()???
- Should be able to pull this out of Talon
- - Should the also get an instance name???
-
-- 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.
+ - Should they also get an instance name???
- - specify cost of a RCE so that it isn't used as often
-
- - RCE Proxies that just run the request on a remote host. All this is done
- through remoting the interface.
-
- Need to meet a certain use cases. Should these go on the website??? These
should become arrowhead unit tests.
@@ -139,13 +158,6 @@
- Include support for ontology... use a default namespace. XSLT between
ontology. Come up with an Example of an XSLT between namespaces.
-
-- Need a mechanism to snap in Reputation Calculation Engines (RCEs)
- - Need a composite ReputationCalculationEngine which can contain multiple RCEs
- - http://pix.comedia.com/OpenPrivacy/20010112/DSCN5988.JPG
- - how do we blend multiple reputation responses with a composite engine?
- There is a lot we have to factor in here:
- - Ontological Reputation response per RCE?
- define reputation:// URI namespace so that reputations can have reputations..
reputation://<SERVER>/pubkey/hash
This archive was generated by hypermail 2b30 : Thu Jan 25 2001 - 11:06:11 PST
