Page History

This section is dedicated to explaining exactly what the modeling tool imports.

Complex, nested class expressions

Importing or exporting complex, nested class expressions involving unions, intersections, complements, and restrictions no longer results in a loss of fidelity.

Constructs

The Concept Modeler supports importing the following constructs: Class, Datatype, Datatype Property, Object Property, Object Property Chains, Class Generalization, Class Equivalence, Class Disjoint Relation, Annotation Property, Object Property Generalization, Object Property Equivalence, Datatype Property Generalization, Class Restriction, Named Individual, Named Individual Property, and Annotations.

Superclass Intersections

OWL Classes that have no superclasses and are equivalent to intersections of Classes will be stereotyped as «Superclass Intersection». More about the stereotype can be found here: Working with superclass intersection.

If you would like to learn about the applications of Superclass Intersections, please peruse Working with intersection and Intersection.

Aristotelian Definitions

The Concept Modeler supports importing Aristotelian definitions. More information about this is found here: [Insert link here...]in the Conditions page.

IRI/URI

When you import an OWL ontology file, the Concept Modeler preserves the URI/IRI for every OWL class and property and imports it as a tagged value of the corresponding UML class or property. The tagged value, called IRI, is part of a «Resource» stereotype applied to each UML element.

...