The Concept Modeler can specify equivalence between two classes, import equivalent classes from OWL, and export equivalent classes to OWL. Class equivalence expresses a generalization relationship stereotyped as «Equivalent Class». The Concept Modeler will draw this with a double-headed arrow.
Image RemovedImage Added
Two equivalent classes in Concept Modeler.
From the figure above, the equivalence class arrow relationship, identified by the «Equivalent Class» stereotype, defines that the two classes are semantically equivalent to each other. For more information on how to create equivalent classes, see Create Equivalent Classes.
If you would like to look at equivalent class relations which are identified by «Equivalent Class» stereotype, there are several possibilities of results depending on the types of classes. Consider the two related classes called Class 1 and Class 2. After perusing through all of these cases, please refer to the figure below the text to see a brief summary of some of these cases.
If both classes are Class but they
Note
title
Note
When there are two equivalent classes:
If classes do not share the same name,
then
one class will show
“Equivalent to”
Equivalent toand the
rest
other will show
“See.”
See.
Image Added Classes with different names in the Natural Language Glossary.
If both classes
are Class and they do
share the same name,
then
it will appear as one class with all the properties from both classes.
Image Added
Classes with the same name.
Image Added
Two equivalent classes appear as one class with all their properties displayed.
If Class is equivalent to a Union,
then
the Class will be shown with its properties and the subclasses of Union will be shown under Class.
Image AddedA class equivalent to a union.
If both classes are Unions
then
, both unions will be merged and follow the same pattern as the Class/Union combinations
explained above
.
Noteinfo
title
NoteInformation
Unions should not have names. If a Union has a name, it is a Class.
The following information explains more explicitly how to determine which Class will show “Equivalent to” and which will show “See.”shows Equivalent to or See.
If only one class has documentation:
This class will show ‘Equivalent to’ Equivalent toand list the rest of the classes it is equivalent to.
The rest of the classes will show ‘See’ Seewith the link going back to the class that shows ‘Equivalent to’shows Equivalent to.
More than one class has documentation:
First class with documentation in alphabetical order will show ‘Equivalent to’ show Equivalent toand list rest of the classes it is equivalent to.
The rest of the classes will show ‘See’ Seewith the link going back to the class that shows ‘Equivalent to’Equivalent to.
None of the classes have documentation:
First class in alphabetical order will show ‘Equivalent to’ show Equivalent toand list rest of the classes it is equivalent to.
The rest of the classes will show ‘See’ show Seewith the link going back to the class that shows ‘Equivalent to’Equivalent to.
Image Added
The merging of definitions of the equivalent classes when more than one class has documentation.
Note
title
Note
The class that shows ‘Equivalent to’, will list shows Equivalent to lists all properties and annotations from all the classes it is equivalent to.
The class that shows ‘See’, will shows See does not show any of the properties or annotations.
All same named classes will show ‘(from package{qualified class name})’ to differentiate each same named class.
Image Removed
Segmented shots of a report showing the merging of all the equivalent classes in the project
Image Added
Each different package name assigned to each class having the same name.
