The term "data modeling" may be a bit inaccurate. Generally, I'm trying to think about common themes in software design.
We would like to be able to define some sort of model, possibly hierarchical, with some of the following properties:
However, this seems prone to over-engineering, ending up with something "enterprisey", and/or something that works for a few cases but breaks down when you need to do anything complex.
See also Code Generation
Tableobjects accept an
infoargument, which is an arbitrary dictionary of user-defined data