From: cvs@openprivacy.orgCVS update: sierra/docs
Date: Wednesday February 7, 19101 @ 16:44
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-serv12786
Modified Files:
TODO
Log Message:
...
*****************************************************************
File: sierra/docs/TODO
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/TODO?annotate=1.48
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/TODO?rev=1.48&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.48&r2=1.47
-----------------------------------
Index: sierra/docs/TODO
diff -u sierra/docs/TODO:1.47 sierra/docs/TODO:1.48
--- sierra/docs/TODO:1.47 Wed Feb 7 16:35:56 2001
+++ sierra/docs/TODO Wed Feb 7 16:44:28 2001
@@ -1,6 +1,6 @@
********************************************************************************
-*** Last-Modified: $Date: 2001/02/08 00:35:56 $
-*** Version: $Id: TODO,v 1.47 2001/02/08 00:35:56 burton Exp $
+*** Last-Modified: $Date: 2001/02/08 00:44:28 $
+*** Version: $Id: TODO,v 1.48 2001/02/08 00:44:28 burton Exp $
*** Author: Kevin A. Burton ( burton@apache.org | burton@openprivacy.org )
********************************************************************************
@@ -16,7 +16,10 @@
= BEGIN MILESTONES
= ===============================================================================
- - Use Case 1: http://pix.comedia.com/OpenPrivacy/20010116/DSCN6054.JPG
+ - ReputationCalculationEngine should throw Exceptions for every operation due to
+ the fact that a RemoteRCE may not be able to communicate.
+
+ - Use Case: http://pix.comedia.com/OpenPrivacy/20010116/DSCN6054.JPG
Standard JetSpeak SCDS stuff. A1 subscribes to multiple content
sources on a JetSpeek server. A2 then asks the JetSpeek server for the list
@@ -33,16 +36,16 @@
- the JetSpeek server should become an RCE which uses the Sierra stuff.
- - Use Case 2: http://pix.comedia.com/OpenPrivacy/20010115/DSCN6049.JPG
+ - Use Case: http://pix.comedia.com/OpenPrivacy/20010115/DSCN6049.JPG
- need to build hierarchies of URIs -> Reputations -> Reputations.
- - Use Case 3: should the "popularity" of a URL also be published? This could
+ - Use Case: should the "popularity" of a URL also be published? This could
be the total number of opinions cast... this might need to have a start and
end date.
- with reputations taken into account.
- - Use Case 4: Ability to calculate reputation sets (arrays) based on
+ - Use Case: Ability to calculate reputation sets (arrays) based on
threshold... "show me all Reputation objects for URI1 with a opinion > X..
- Needs to be based on an XPath query
@@ -98,15 +101,6 @@
getReputation will return the calculated reputation for this pointer and not
the actual value.
-
-
-= ===============================================================================
-= END MILESTONES
-= ===============================================================================
-
-
-
-
- determine the correct RCE by the type of URI requested. This should allow the
the administrator (and the object) to deploy the RCE and add some regexps
@@ -114,34 +108,19 @@
OCS you should be able to run queries on the original OCS Server if it happens
to be running Sierra or a reputation server. Maybe the OCS feed could contain
additional markup for pointing to a Reputation server.
-
-
-- Ability to offload certain ontological requests to specific engines.
+
+= ===============================================================================
+= END MILESTONES
+= ===============================================================================
- - FIXME: The ontology of a URL is NOT within the spec anywhere. We need to
- add this before this can be done.
-- When a getReputation is requested for a certain URI we need to be able to
- forward this to a more appropriate engine. This should be
-
+
= ===============================================================================
= GENERAL REQUIREMENTS
= ===============================================================================
-- 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.
-
- XML for adding an ontology:
<ontology>
@@ -184,63 +163,10 @@
- this should be a Talon component: OntologyRegistry which is a singleton.
This should have a persistence store so that when new Ontologies are
registered if the server stops we can just reload old ontologies.
-
-- Include support for ontology... use a default namespace. XSLT between
- ontology. Come up with an Example of an XSLT between namespaces.
-
-- define reputation:// URI namespace so that reputations can have reputations..
- reputation://<SERVER>/pubkey/hash
-
-- need to define how Gifts work... GiftRequiredException??? What does this data
- structure look like?? It is an array or URIs that the remote need more
- information about? The result should be put reputations... How does it
- specify what data it should have???
- Note. This is probably something we don't have to worry about for right now
- Should the reputation object just have a Result URL or object which has more
info??? URL,namespace which can then be parsed out and made polymorphic by the
reputation server???
-
-- Faults reported back from SOAP are now thrown as Exceptions... these actually
- have to be checked for :(... find out if there is a way these can use native
- Java stuff.
-
-- Provide a mechanism to store reputations on disk with the URI as the encode
- path. How should we handle the :// part?. This should be a dedicated object
- like
-
-- Talon should be used as the generic object factory.
-
-- decent logging mechanism. Use the Logger interface from Talon. Need a clean
- way to get a handle on a Talon component so the each works on a new VM.
-
-- how are agents resolved in the system???
-
-- Ontologies need to be versioned so that past Reputations that rely on an
- ontology don't break.
-
-
-**** Version 0.0.3 ****
-
-- (DONE) RCEs should become Talon components.
-
-- (DONE) Need to define RCE interface...
-
-- (DONE) All Reputations should be required to provide a Principal.
- - Need to parse out properties files when Sierra starts up so that it knows
- what principal the server is running under.
-
-- (DONE) before put-reputation is called... output what we are about to set.
-
-**** Version 0.0.2 ****
-
-- (DONE) setup Arrowhead as a testing framework. Need to see if there is an
- HTTP test to test various SOAP messages.
-
-**** Version 0.0.1 ****
-
-- (DONE) provide instructions for setting up SOAP in ./docs/SETUP
-
-- (DONE) get SOAP initially setup so that I can communicate with the server
This archive was generated by hypermail 2b30 : Wed Feb 07 2001 - 16:44:28 PST
