Powered by Zoomin Software. For more details please contactZoomin

Semaphore 5.13 Knowledge Model Management (KMM) How-To Articles

Work with OWL Axioms and Restrictions

  • Last Updated: November 20, 2026
  • 4 minute read
    • Semaphore
    • Version 5.13
    • Documentation

OWL axioms define relationships and constraints between ontology elements. For example, they can specify that two classes are equivalent, that a class must satisfy certain property conditions, or that two classes cannot share the same individuals.

In Knowledge Model Management (KMM), you can inspect these definitions to understand how classes are related and constrained. You can also add or edit supported disjointness relationships. Equivalent class definitions and subclass restrictions can be viewed but not edited.

Assumptions

Before you begin, ensure that:

  • You have access to Knowledge Model Management (KMM).
  • An OWL model has been created or imported.
  • The ontology contains classes with axioms or restrictions that you want to inspect, or classes for which you want to define disjointness.
  • You have the required permissions to modify ontology content if you intend to make changes.

Method

To work with OWL axioms and restrictions:

  1. Inspect class axioms.
  2. Review equivalent class definitions, if present.
  3. Review subclass restrictions, if present.
  4. Add or edit disjoint classes, if needed.

Inspect Class Axioms

  1. Open Knowledge Model Management and go to Models.
  2. Locate the OWL model and select Open Master.
  3. Select Ontology > Classes.
  4. Select the class you want to inspect.
  5. Open the Axioms tab.

The Axioms tab contains three sections:

Section What you can inspect
Equivalence Definitions Definitions that describe a class as equivalent to another class or class expression.
Subclass Restrictions Conditions that members of a class must satisfy.
Disjoint Classes Classes that cannot share the same individuals.

The content displayed depends on the definitions present in the ontology. If no axioms of a particular type are defined, the corresponding section displays a message indicating that none were found.

You can also select Hierarchy to inspect parent and child classes, or Raw Text to inspect the RDF representation of the selected class.

Review Equivalent Class Definitions

Equivalent class definitions describe classes or class expressions that represent the same set of individuals.

For example, an ontology can define Manager as equivalent to an Employee who works in at least one Department.

To review an equivalent class definition:

  1. Under Ontology > Classes, select the class you want to inspect.
  2. Open the Axioms tab.
  3. Under Equivalence Definitions, review the displayed expression.

For example:

Employee and (worksIn some Department)

This expression combines an intersection of class expressions with a property restriction. It describes individuals who belong to the Employee class and have at least one worksIn relationship to an individual belonging to the Department class.

Equivalent class definitions are read-only in KMM. You can inspect them, but you cannot create, modify, or remove them through the class editing interface.

Review Subclass Restrictions

Subclass restrictions define conditions that members of a class must satisfy.

For example, an ontology can define SeniorEmployee as a subclass of Employee with a restriction on the worksIn property.

To review subclass restrictions:

  1. Under Ontology > Classes, select the class you want to inspect.
  2. Open the Axioms tab.
  3. Under Subclass Restrictions, review the displayed expressions.

For example:

worksIn some Department

This expression means that every member of the class must have at least one worksIn relationship to an individual belonging to the Department class.

Subclass restrictions are read-only in KMM. They can be inspected but not edited through the class editing interface.

Simple subclass relationships between named classes are displayed in the class hierarchy. For example, Hierarchy can show Person > Employee > SeniorEmployee.

Add or Edit Disjoint Classes

Disjointness axioms specify that two classes cannot share the same individual. For example, an ontology can define Employee and Contractor as disjoint classes if no individual should belong to both.

To add or edit a disjointness relationship:

  1. Under Ontology > Classes, select the class you want to update.
  2. Open the Axioms tab.
  3. Under Disjoint Classes, click the + icon to add a relationship. To edit an existing relationship, click the pencil icon.
  4. In Select disjoint classes, start typing the name of the class you want to specify as disjoint.
  5. Select the class from the suggestions.
  6. Click the checkmark to save the relationship.
  7. Verify that the selected class appears under Disjoint Classes.

For example, adding Contractor under Disjoint Classes for Employee defines a direct owl:disjointWith relationship between the two classes.

Only binary owl:disjointWith axioms between named classes can be edited in KMM. If a class participates in an owl:AllDisjointClasses axiom, its disjointness relationships are displayed under Disjoint Classes, but the editing control is disabled. Hover over the disabled pencil icon to see why editing is unavailable.

Before adding a disjointness relationship, verify that the classes are intended to be mutually exclusive. For example, do not declare Employee disjoint with Person if Employee is a subclass of Person.

Outcome

You can inspect equivalent class definitions, subclass restrictions, and disjointness relationships to understand how classes are defined and constrained. You can also add or edit supported disjointness relationships through the Axioms tab.

For the next task, see Work with OWL Classes to manage class details and hierarchy, or Manage OWL Ontologies to explore other ontology elements and model operations.

Alert