The ORM Foundation

Hi, The 2/6/2007 release corrects the @ variable not declarred error - a huge help. There are other issues in the DDL generation that are new or still present. I'll put these in another thread and bug report. BRN..

I still think there is a problem here with the recent release. It is my understanding that there is an implied subset constraint from every role an object plays to every mandatory role that same object plays. In some cases these implied subset constraints can be ignored when mapped to a SQL database because the roles map to the same table and ...

Hi, Thanks to all the NORMA team for the latest release. While incremental and intermediate, the fixes should make it much easier to test through physical implementation. Good luck with the next phase of the project; as it sounds like you'll be addressing some fundemental issues with the framework. Please remember to keep the forum ...

Terry, Nice to see you here and thanks for the comment on mandatory constraints being orthogonal. I wasn't sure I hadn't missed something there, but I do recall this issue (mentioned in the book) now. I'll add mandatory constraints back in, in the form of a boolean on a FrequencyConstraint (min and max are both nullable). I'll email you ...

Hi Matt, I like the proposed name changes; they add clarity. The last one ObjectifiedType --> ObjectificationObjectType, though I see the correctness of it, seems too cumbersome. I'm afraid it will be abreviated in use and documantation, and the effectiveness will be lost. Symantically, Objectification implies object creation, so ...

Hi Clifford Your claim that ''unique and mandatory constraints are just instances of frequency constraint'' is only party true. You may treat a uniqueness constraint as a frequency constraint of 1, but a mandatory constraint cannot be reduced to a frequency constraint. A frequency constraint of n on a role says that any instance playing that ...

Absolutely. There's a big difference between the core model and the xml file. The .orm files have a dummy root element (ormRoot:ORM2) that is a container for the 'real' information. The only special thing we do with this root element is provide an xml namespace mapping for all loaded domain models. Two of these are mapped automatically (ORMCore, ...

Sten, I don't really disagree about isExternal - but to me, it's a pity that we have to declare the degree of open-ness of our open world assumption. In other words, I'd rather that tools make an assumption that the world is open unless declared otherwise. The RMap procedure doesn't necessarily allow this, as Matthew alluded to when ...

I believe there is a conceptual quality in the isExternal property. One of the great things about Service-Oriented Architecture is the way it allows you to build an infrastructure of shareable information. Such an infrastructure technically consists of a number of entity services, where the mission of each entity service is to be the only ...

> It is not a conceptual setting so does not really belong in the core model Well, the diagrams aren't either, and neither really is the ''isExternal'' boolean, yet they find a place in the file - just not in the model itself. Perhaps it would be best to have the generator settings in a third section of the file, rather than stored inside ...