CVS update: sierra/docs

From: cvs@openprivacy.org
Date: Sun Feb 18 2001 - 22:50:28 PST

  • Next message: cvs@openprivacy.org: "CVS update: sierra/src/java/org/openprivacy/sierra/nym/talon/implementations"

    Date: Sunday February 18, 19101 @ 22:50
    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-serv25618/docs

    Modified Files:
            TODO
    Log Message:
    update from over weekend. clean up copyright... more work on store

    *****************************************************************
    File: sierra/docs/TODO

    CVSWEB Options: -------------------

    CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/TODO?annotate=1.53

    CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/TODO?rev=1.53&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.53&r2=1.52

    -----------------------------------

    Index: sierra/docs/TODO
    diff -u sierra/docs/TODO:1.52 sierra/docs/TODO:1.53
    --- sierra/docs/TODO:1.52 Mon Feb 12 00:11:19 2001
    +++ sierra/docs/TODO Sun Feb 18 22:50:27 2001
    @@ -1,6 +1,6 @@
     ********************************************************************************
    -*** Last-Modified: $Date: 2001/02/12 08:11:19 $
    -*** Version: $Id: TODO,v 1.52 2001/02/12 08:11:19 burton Exp $
    +*** Last-Modified: $Date: 2001/02/19 06:50:27 $
    +*** Version: $Id: TODO,v 1.53 2001/02/19 06:50:27 burton Exp $
     *** Author: Kevin A. Burton ( burton@apache.org | burton@openprivacy.org )
     ********************************************************************************
       
    @@ -9,11 +9,24 @@
     = ===============================================================================
     
     
    +
    +
     = ===============================================================================
     = BEGIN MILESTONES
     = ===============================================================================
     
     
    +- Need to define a few sample applications. This should include setup
    + instructions and an example app.
    +
    +
    +
    +
    +- should each RCE have a specific data store???
    +
    +
    +
    +
       - determine requirements for a data store... maybe this *should* be
         something like jewel.
     
    @@ -21,13 +34,12 @@
                  event based system so that an RCE can be a target but so can a
                  RCEStore.
     
    - - ... this should just add a listener and they we can call methods to
    - see if it is something we need to pay attention to.
    + - Method for Query resolution engines ... this should just add a
    + listener and then we can call methods to see if it is something we
    + need to pay attention to.
     
       - need to build a Query type used to fetch an actual reputation value (not
         getReputation). This should use the Hashcode of current objects.
    -
    -
             
     TODO:
     
    @@ -51,12 +63,6 @@
       - Use Case: http://pix.comedia.com/OpenPrivacy/20010115/DSCN6049.JPG
     
         - need to build hierarchies of URIs -> Reputations -> Reputations.
    -
    - - 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.
    - - this could become just a query...
     
       - Use Case: Ability to calculate reputation sets (arrays) based on
         threshold... "show me all Reputation objects for URI1 with a opinion > X..
    @@ -125,8 +131,12 @@
       events from an RCE.putReputation. It should also be able to restore an RCEs
       state after shutdown/restart. We need a strong object hierarchy/factory for
       handling this.
    -
    -
    +
    + - 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.
    + - this could become just a query...
     
            
     = ===============================================================================

    This archive was generated by hypermail 2b30 : Sun Feb 18 2001 - 22:51:00 PST