The ORM Foundation

Now I see where my confusion came from. In the first ORM book, nested objects could only be made from spanning or 1-1 uniqueness constraints. The new book says "The second generation ORM...allows any fact type to be objectified...Although allowed for pragmatic reasons, such exceptions violate elementarity and require special treatment when ...

It is my understanding that a binary can only be objectified if it has a uniqueness constraint that spans both roles or if each role has a uniqueness constraint. I don't understand this limitation. Suppose I am modeling the process of assigning work to someone else. Here are the relevant facts:TaskRequest(id) is sent by [1] ...

My diagram has gotten way too big and I'm trying to reduce the complexity while I'm working. For example, suppose I've got an Entity called Person and a bunch of roles related to Contact Information and a bunch of roles related to Biographical Information. I might want to temporarily delete all the roles related to Contact Information ...