>>Jim, before getting really sad overhere, could you explain "domain definition" please ? I can translate it but just can't place it to the subject.
>
>Peter,
>
>The domain refers to the real world environment that the database is trying to model. For example, if a university has a rule that says one advisor works with one member on one project then that is part of the definition of the database domain for that university. Whether the database designer decides to enforce that rule in the database design or to relegate it to business rules enforcement is a design decision but it does not alter the domain definition for that university. In other words, databases are not designed in a vacuum, they are designed for a specific purpose.
>
>This means that before we can discusss a certain design we need to agree to the domain rules for the database. Otherwise you are speaking Dutch and I am speaking Chinese and we will never understand what the other is trying to say.

Jim,

I can't recall that I changed the domain in any way, but I do recall being Dutch. If you're an American it might be better for me than Chinese, but the problems are sufficiently there I suppose.

Really, I didn't try to change one bit. Oh yes, I had some lines about real world and stuff and I talked about the N:N for Members and Advisors in time, and made the relation 1:1 (for one project) again by having the time period in the key ("solved by processing").

If it is this what you mean, it is my opinion that this is not wrong at all and exactly what you meant. Maybe to discuss.
But since you stated that I kept on changing each other example (similar), there is more I guess, and I can't recognize it.