********************************************************************************
*** Last-Modified: $Date: 2001/04/13 04:05:53 $ 
*** Version: $Id: CHANGELOG,v 1.1 2001/04/13 04:05:53 burton Exp $
*** Author: Kevin A. Burton ( burton@apache.org | burton@openprivacy.org )
********************************************************************************

- Wed Feb 28 18:42:27 2001 (burton@relativity.yi.org): (DONE) need to build a
  static class that can take a SignatureValue and build it into a URI and a
  URI and turn it into a SignatureValue...

- Mon Feb 26 21:17:23 2001 (burton@relativity.yi.org): (DONE) How do I ascii
  armor my Reputation URIs?  Is this Base64?

- Sat Feb 24 21:45:00 2001 (burton@relativity.yi.org): (DONE) write a test to
  make sure that all Components under SierraResources are available.

  - Sat Feb 24 21:44:22 2001 (burton@relativity.yi.org): (DONE) should I move the
    'rce' package around to reflect the talon/ hierarchy which I am using
    elsewhere????

  - Tue Feb 20 14:21:34 2001 (burton@relativity.yi.org): remove Concept,
    Opinion, Value, Reputation from the top-level package.

  - Sun Feb 11 17:21:55 2001 (burton@relativity.yi.org): (DONE) not every
    component within Sierra needs or should be under the 'talon' package.
    Instead we should move these to their own package... Example.  The basic nym
    package should be under org.openprivacy.sierra.nym.talon.  The reputation
    interfaces should go under org.openprivacy.sierra.reputation.talon.

  - Sun Feb 11 16:39:52 2001 (burton@relativity.yi.org): (DONE) Need an
    abstraction of how to create and manage nyms.  The facility needs a way to
    get the private and public keys for the nym and also determine a new nym
    based on another nym.  This "new" nym could be used temporarily but could
    also stay with the user for a long period of time with support for the
    parent nym proving that it created this sub-nym.  The system should support
    basic nyms which are simple to implement but scales to PGP, RSA, etc.  When
    it comes time to rewrite this Sierra to support PGP/RSA we shouldn't have to
    modify any of Sierra to support this.

      - need to provide an equals() method so that we can determine if two Ns are
        the same. 

     - Nym implements Principal -> Talon interface
       +init() do whatever it takes to build this Num
       +getPrivateKey
       +getPublicKey
       +getNym() get a child nym... based on this nym

     - KeyBuilder -> Talon interface... need to build more impls... 
       +getNym()
       +getPropertyManager()
      
- Thu Feb 8 18:36:54 2001 (burton): (DONE) ReputationCalculationEngine should
  throw Exceptions for every operation due to the fact that a RemoteRCE may not
  be able to communicate.


- Wed Feb 7 15:02:37 2001 (burton): (DONE) Reputation should become an
  component.  It should be served by talon.

**** 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

