Suppose two definitions have the same name but specify different superior classes. If those superior classes have different foundation classes, and each of the conflicting classes has at least one instance, the conflict between the two definitions cannot be resolved.
To illustrate, assume that different G2 developers have created two different but related KBs. One KB contains an object definition named
TRUE-FALSE-LIST, whose superior class is the system-defined class ITEM-LIST. The other KB contains a TRUE-FALSE-LIST object definition whose superior class is the system-defined class TRUTH-VALUE-LIST. Finally, assume that each KB has at least one item that is an instance of the TRUE-FALSE-LIST class. These two Inspect workspaces show the class hierarchies for the two
TRUE-FALSE-LIST definition items:
|
After merging the KBs with the
automatically resolve conflicts option selected, G2 displays the following conflict workspace:
 |
The conflict workspace shows that only the
Direct-superior-classes attribute differs in the two versions of TRUE-FALSE-LIST. The conflict between these two definitions cannot be resolved, because G2 does not allow you to change the class of an instance whose foundation class is ITEM-LIST, into an instance whose foundation class is not ITEM-LIST, or one of its system-defined subclasses.