Actually, the Zend Framework has adapters (currently for XML and "INI" style config files), which could prove an alternative.
However, before we can start saying that we are "applying UML" we need to see how the evolution of dividing the data persistence of the entities from the business objects controlled by the system will evolve. CCK in itself tends to tie together the form binding, the business objects and the database persistence all together, which doesn't really allow much more than a ERD to CCK translation; I wouldn't call that UML.
However, I have had ERD semi-complex diagrams which needed to be implemented in CCK, and had to do the whole thing by hand, of course, so in that sense this would be a boon.
And I thoroughly agree against the idea of a parser; go YAML or XML or both. Arrays are "the Drupal Way" for ojects in memory, but not the configuration language, necessarily.
Zend Framework... UML buzzword thoughts
Actually, the Zend Framework has adapters (currently for XML and "INI" style config files), which could prove an alternative.
However, before we can start saying that we are "applying UML" we need to see how the evolution of dividing the data persistence of the entities from the business objects controlled by the system will evolve. CCK in itself tends to tie together the form binding, the business objects and the database persistence all together, which doesn't really allow much more than a ERD to CCK translation; I wouldn't call that UML.
However, I have had ERD semi-complex diagrams which needed to be implemented in CCK, and had to do the whole thing by hand, of course, so in that sense this would be a boon.
And I thoroughly agree against the idea of a parser; go YAML or XML or both. Arrays are "the Drupal Way" for ojects in memory, but not the configuration language, necessarily.
Victor Kane
http://awebfactory.com.ar