DB_Schema or the future of datastores in PEAR

Hi, I want to create a new mailinglist that addresses the area of how to best go about managing your datastores and related metadata. The idea is to have one config file that is converted via a package called DB_Schema [1][2] into different forms. This could either be other more specialized config files, SQL queries, other format of the same information, even php classes. DB_Schema would just consist of a number of extensible readers and writers along side with a number of extensible classes that help create an OO representation of common datastore structure elements. These OO representations would also allow creation and modifying of the datastore config within PHP. This would enable DB_Schema to be to connecting class between a general definition of a datastore and other classes such as: - Class to manipulate structure of a database - Class to manipulate contents of a database - Class to generate forms - Class to validate input Please tell me if you are interested to be on that mailinglist (probably best to just send a mail directly to me). I will also make sure that we have a wiki where we can collaborate. Regards, Lukas Smith PS: I have added a few people in the CC since I wasnt sure if these people read pear-dev. [1] http://marc.theaimsgroup.com/?l=pear-dev&m=105602183309324&w=2 [2] http://marc.theaimsgroup.com/?l=pear-dev&m=105879775921638&w=2