Refining intentions

First, clients should be kept as light weight as possible and scripts interpreted on the client side is simply the wrong way to go. Scripts should be executed within a transactional context so we need to have the interpreter in the server itself. This will be called the RoleMagicInterpreter (RMI), an old term of Norm's.

Second, I've found it is best to take a layered approach rather than a monolithic one. Monolithic software is hard to learn, but a layered architecture can be learned in stages. The cost of a layered approach is having to deal with some coupling as well as some impedence mismatch, but then nothing is free. So the smart version of Browse and application modeling should be put in a separate layer, the Metadata OODBMS (MOODBMS, which seems to go well with CowDb), and we'll keep the scope of COODBMS tightly focused. (No web hits on a search for MOODBMS, for the obvious reasons I guess. So we've got a good name from 2 perspectives.)