********************************************************************************
*** Last-Modified: $Date: 2001/03/24 20:41:54 $ 
*** Version: $Id: DOCUMENTATION_TODO,v 1.17 2001/03/24 20:41:54 burton Exp $
*** Author: Kevin A. Burton ( burton@openprivacy.org )
********************************************************************************
                
    
- document the requiremment for crypto with parent child relationships.

- document why we are using *Manager classes (RCEManager, QueryManager,
  StoreManager).  These are basically just so we can progmatically (maybe with
  reputations) determine the best RCE, Query or Store to use. 

- An RCE should be the central interface into Sierra.  All interaction should be
  exposed through this mechanism.

- need to document how reputation systems are transparently peer-to-peer.
  Should this be in the whitepaper?
   - one part should be in the whitepaper and then we can talk about
  implementation specific protocol bridges.

- document how all interfaces work within Sierra.  This should document all
  packages and how they work as components.  

  - merge this over from javadoc?
  
- Talk about how Sierra is both a client and a server in a P2P network.  Server
  components are registered as RCEs and are connected with client RCEs which
  talk the same protocol. 

  
- Reputaton Calculation Engine.
  - Define it
  - provide examples
  - it is a plugin
  - A specific RCE can have reputation.
  - All queries should return a Result which is basically an array or Reputation
    URIs. 
  - What are the requirements for a basic RCE
    - support the ReferenceRCEQuery
    - support the PropertyManagerPayload
  
- How is everything tied together? UML?

- Why are we using Talon??
  - describe why RCEs are just components...
  - reputation object and payloads are just basic components...

- standardized reputation framework

- reuse and nesting of existing Reputation Calculation Engines to build advanced logic.

- remote query of RCEs

- Advantage: nym management
  - identities can be portable across sites (slashdot and advogato can have the
  same users).

- Advangage: privacy
  - privacy is always maintained for you users.  
