I have a meta-description language - custom format - that describes any set of Domain Specific Languages (I have languages of objects, properties, relationships, data types, value lists, features, actions, screens, etc.) and auto-generates the db tables to store essential, optional and custom statements in each DSL and the service methods to access them. I then have a set of templates and a set of database described generators that generate each cms based on the metadata relevant to that project. Everything is done using convention by default with a number of overload points and is designed for easy reuse of declaritive metadata across hundreds or thousands of custom applications - quickly and cost effectively using packages for essential metadata, a decision support system for helping non-technical users to select optional metadata based on business requirements and a set of netadata constraints to ensure you can't (for instance) select UPS shipping without having a Product.Weight property.
Well, you asked :-> Best Wishes, Peter On 3/26/07 10:35 AM, "Tom Chiverton" <[EMAIL PROTECTED]> wrote: > On Monday 26 Mar 2007, Peter Bell wrote: >> I guess one of the reasons XML never worked for me is that I see >> configuration as a type of content which (like any type of content) can be >> managed using a cms > > How do you configure the CMS ? -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
