There have been several posts about a new old application architecture which uses RDF as the M of MVC. Mike Hogan articulated the concept very well (by way of Leigh Dodds).

Do not model your data as objects...

Its just too rigid, it slows you down, it depresses you when you have to refactor half the model due to some new requirement that does not fit. It feels like you are wading through treacle. Objects are not great for data. Source

btw, if you find that you start extending your object model to allow arbitrary property annotation, and some of those properties are actually pointers to other objects in your graph, then that's probably a sign that you may be better off using an RDF based model. And possibly Python too but I've not explored that angle yet. Source