Powered by Zoomin Software. For more details please contactZoomin

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

Derive Model Structure from an OWL Ontology

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

Structure derivation uses OWL ontology content to create structural definitions and concepts in a destination SKOS model. This allows you to reuse an existing ontology when defining how concepts are organized in Semaphore.

This article describes how to derive model structure using the Structure profile. To derive SKOS concepts instead, see Derive SKOS Concepts from an OWL Ontology.

Understanding Structure Derivation

Structure derivation converts supported OWL ontology elements into content used by the destination SKOS model.

The following conversions apply:

Source OWL element Result in the destination model
OWL classes Subclasses of skos:Concept
OWL individuals SKOS concepts

OWL classes provide the structural definitions used to classify concepts. OWL individuals become concepts that can use those definitions.

For example, consider an ontology containing:

  • A class named Dataset.
  • A subclass named ResearchDataset.
  • An individual named Dataset001 belonging to ResearchDataset.

When you derive model structure, the OWL classes provide the basis for the destination's concept class structure, while the individual provides the basis for an actual concept.

The derived content does not reproduce every OWL construct or its formal semantics. Review the derived concept classes, their hierarchy, and the resulting concepts before using the model.

Class Limit

Structure derivation supports OWL ontologies containing up to 1,000 classes.

If the source ontology contains more than 1,000 classes, Semaphore does not support deriving model structure from it.

This limit applies specifically to Structure derivation. You can still use the Concepts derivation profile for an ontology containing more than 1,000 classes.

Assumptions

Before you begin, ensure that:

  • You have access to Knowledge Model Management (KMM).
  • The source OWL ontology exists in Semaphore.
  • You have the permissions required to access the source ontology and create or update the destination SKOS model.
  • A suitable destination SKOS model exists, or you have permission to create one.

Understanding the Source and Destination Models

Structure derivation involves two models:

Model Role
Source OWL model Contains the classes, individuals, and other ontology information used for derivation.
Destination SKOS model Receives the derived model structure and concepts.

The destination SKOS model must be linked to the source OWL model. If you create a new destination model through the Derive model dialog, Semaphore automatically establishes the required link. If you use an existing destination SKOS model, ensure that the link to the source OWL model is already configured.

Method

Follow these steps to derive model structure from an OWL ontology:

  1. Open the Derive dialog.
  2. Configure Structure derivation.
  3. Run the derivation.
  4. Review the derived structure.

Important: Structure derivation supports source OWL ontologies containing up to 1,000 classes. See Class Limit for details.

Open the Derive Dialog

  1. In Knowledge Model Management, open Models.
  2. Open the OWL model you want to use as the source.
  3. Click Derive on the model toolbar.

The Derive model dialog opens.

Configure Structure Derivation

  1. Under Derivation profile, select Structure.
  2. Under Target SKOS model, select Use existing to choose an existing SKOS model, or Create new to create a destination model.
  3. Under Target task, select Use existing to choose an existing task, or Create new to create one.
  4. Under Target concept scheme, select Use existing to choose an existing concept scheme, or Create new to create one.
  5. Review the What will happen summary to confirm the selected derivation profile, destination model, target task, and concept scheme. If you are creating a new destination model, the summary also lists the model, concept scheme, and source link that Semaphore will create.

Run the Derivation

  1. Click Derive to start the operation.
  2. Wait for the Derivation complete confirmation dialog.
  3. Click View Model Structure to open the derived structure in the destination SKOS model.

Review the Derived Structure

After derivation, review the destination SKOS model to verify that the expected structure was created.

  1. Expand Concept Classes and verify that the expected OWL classes appear in the derived hierarchy.
  2. Review the parent-child relationships to confirm that the hierarchy reflects the class relationships in the source OWL ontology.
  3. Expand Resource Metadata to inspect derived data properties. Select a property to review its URI, attribute type, domain, and range.
  4. Review Concept-to-Concept Relationships and other relevant sections of the model structure to identify additional derived properties and relationships.
  5. Open Concepts and review the concepts derived from OWL individuals. Verify that the expected concepts are present and classified appropriately.

Some OWL properties may be present in the destination model's RDF data without appearing in the Structure tree. To inspect these properties, use Querying > SPARQL Editor.

Not all OWL axioms, restrictions, or complex expressions are necessarily represented in the derived model structure. Compare the derived structure with the source OWL ontology, particularly classes that use restrictions or complex expressions. If required definitions are missing, review the source ontology and the corresponding derived elements before using the destination model.

Outcome

You have derived model structure from an OWL ontology into a destination SKOS model.

The resulting model contains structural definitions based on the source OWL classes and concepts derived from OWL individuals.

You can now review the derived concept classes and properties under Structure, and work with the resulting concepts under Concepts.

Alert