You don't need to apologise. The only kinds of discussion worth having are the "explicit" type so thanks for the clarity
If its OK with you - I'll skip the general debate on "free software".
The perspective I prefer to take is that of the businessman who has a "business problem" to solve and needs help in solving it.
So for me, statements such as "We can't solve your problem because we have chosen to use an open source technology platform prevents us from deploying the most appropriate tool" are likley to get a business response of "OK - so change your platform"
I guess that is one reason why ORM is much less used than EER and UML
Wow! That's quite a leap ! You must be an expert in creative marketing spin
It seems to me that the reason that ER and UML are used rather than ORM is down to one main thing: "marketing muscle".
For on overview of data modeling practise see Graeme Simsion (2007): "Data Modeling Theory and Practise". Is there a similar study on ORM usage by the way?
Thanks for the tip. You might be interested to know that used Graeme's work in my Masters dissertation and (with his agreement) defined and conducted a survey that re-used parts of his PhD thesis - very similar to his book - which I have referenced on the "Research" page of this website. You will also see that I posted an interim report of my "Design or description" survey in the Library on 24 May 2008.
Anyway, his main focus was to discover whether data modeling is about "Describing the world" or "Designing the world". Graeme concluded that data modelers actually "invent" the data model and my survey supported his findings.
I'd strongly bet that most features of ORM are rarely used in real world applications at all.
Well - I think you would win your bet.
However, the real question is "why".
My answer is that ORM can do a lot more than UML and ER and "business people" have not yet woken up to the need for the features of ORM.
With an exchange format you could automatically check ORM models to find out what features are used and you may even detect common mistakes and pitfalls in ORM modeling
Now I must confess some confusion in what you are trying to say here.
It seems that you are asserting that
1: There is a need to check ORM models to find out what ORM features are used"
It is my understanding that "the ORM features that are used an a model" are those features that are needed to adequately define the elementary facts in the universe of discourse". I'm curious to know what other purpose there might be in finding and answer to this question.
2: ORM models contain "common mistakes and pitfalls" that could be detected by some external algorithm.
I don't doubt the facts that "some ORM models contain mistakes" and that "there are pitfalls in using ORM".
However, I'm curious to know how the "external algorithm" could uncover the "mistakes" and "pitfalls" without knowing about them in the first place.
And if you know about the "common mistakes" and "pitfalls" surely the best use for such knowledge is to use it to avoid making the common mistakes and to avoid the pitfalls in the first place.
Or have I misunderstood something here?