The more I look at this project the more I have to remind myself that the goal or the persistence layer is simply to persist our object model and not create expose a database schema through and object oriented API. 

The following task are left on the Peristence layer portion of this project. If you seen anything left out of these tasks let me know:

• Query Templates
  • We need a consistent way to query objects across providers.
  • Initial thoughts are to define a query template class for each domain class that can query classes from a strongly typed collection, an SQL compliant provider and a simple Xml provider
  • Why?  We need a very consistent way to query classes from the domain layer.  Creating classes that are responsible for creating queries seems like an easy and straight forward way to perform this task 
• Xml Persistence Provider
  • Writes serialized object XML files to a local disk.
  • Initial Iteration in GotDotNet Source Control
  • Remaining Tasks:
    • Create a schema to index the XML files to increase retrieval speed
    • Store references to contained objects that implement the IPersistable interface and provide for the option of lazy loading
• RDBMS Persistence Provider
  • Provider that stores objects in a relational database
  • Created an RDBMS provider using Wilson ORMapper.  Works but has a few problems:
    • External mapping file is required for every object that needs to be persisted
    • All persisted object must implement ORMapper interfaces for best perfrormance
    • Utility to help create xml mapping file isn't always correct out of the box
    • Initial uses seem to require a 'database centric' design as opposed to an object centric design
    • During initial test existing class files had to be modified in order to get them to persist correctly.
  • Remaing Tasks
    • Evaluate effectivness of current ORMapper implementation and document why or why not we should use this
    • Determine next steps of action for RDBMS provider
• Remote Persistence Provider
  • Remote persistence should simply be a Web Services wrapper over an existing Persistence Provider (XML or RDBMS).  We'll wait to have an implementation of the RDBMS provider first.