OWL Capabilities and Limitations
- Last Updated: November 20, 2026
- 4 minute read
- Semaphore
- Version 5.13
- Documentation
OWL ontologies support classes, properties, individuals, and logical relationships that describe a domain. Knowledge Model Management (KMM) provides tools for working with these elements, but some OWL definitions can be viewed without being edited directly.
This article outlines the main limitations to consider when editing, importing, linking, or deriving content from OWL ontologies.
For instructions on navigating an ontology and managing its content, see Manage OWL Ontologies.
Editing Limitations
The editing options available in KMM depend on the type of OWL element and the complexity of its definition.
| Element or feature | Editing capabilities | Limitations |
|---|---|---|
| OWL classes | Create classes and edit supported labels, descriptions, and annotations. | Complex class expressions are read-only. Classes with subclasses cannot be deleted. |
| Class disjointness | Edit simple owl:disjointWith axioms. |
Complex disjointness expressions are read-only. |
| Equivalent class definitions | View equivalent class definitions. | Equivalent class definitions are read-only. |
| Subclass restrictions | Inspect subclass restrictions and navigate simple subclass relationships through the class hierarchy. | Subclass restrictions are read-only. |
| Object properties | Edit supported labels, descriptions, characteristics, domain, and range values. | Complex property expressions are read-only. |
| Data properties | Edit supported labels, descriptions, characteristics, domain, and range values. | Complex property expressions are read-only. |
| Annotation properties | Create annotation properties and edit supported property information. | Editing options depend on the property definition. |
| Datatypes | Inspect datatype information. | Datatypes are read-only and cannot be created directly in KMM. |
| Individuals | Inspect individuals associated with OWL classes. | Individuals are read-only and cannot be edited directly in KMM. |
Class Axioms and Restrictions
KMM supports editing simple owl:disjointWith axioms. More complex disjointness expressions, equivalent class definitions, and subclass restrictions can be inspected but not edited directly.
Simple subclass relationships are represented in the class hierarchy.
For more information, see Work with OWL Axioms and Restrictions.
Property Domain and Range
Domain and range values can be edited when they use direct IRI or datatype references supported by the property type.
Complex domain and range expressions can be inspected but are read-only.
For instructions on editing properties, see:
Import Limitations
OWL ontologies can be imported using supported RDF serialization formats.
| File extension | Import support |
|---|---|
.ttl |
Supported |
.rdf |
Supported |
.xml |
Supported |
.owl |
Not supported |
.xls |
Not supported |
The imported file must contain RDF data in a compatible serialization format. Renaming a file extension does not convert its contents.
Importing an OWL ontology does not automatically create SKOS concepts or model structure. Use a derivation workflow when you want to generate SKOS content from an OWL ontology.
For instructions, see Create and Import OWL Ontologies.
Model Linking Limitations
An OWL model can be linked to other OWL models through Linking > Model Links.
OWL-to-SKOS derivation uses a different relationship: the destination SKOS model must have access to the source OWL model.
- When you create a destination SKOS model through the Derive workflow, KMM automatically establishes the required link.
- When you select an existing destination SKOS model, the required link must already be configured.
For instructions on managing links, see Manage OWL Ontologies.
Derivation Limitations
KMM provides two profiles for deriving SKOS content from an OWL ontology. The profiles produce different results and do not preserve every OWL construct as an equivalent SKOS representation.
| Profile | Derived content | Limitations |
|---|---|---|
| Concepts | SKOS concepts derived from OWL classes, including supported terminology relationships. | Complex OWL semantics and expressions are not fully represented in the resulting SKOS concepts. |
| Structure | Model structure derived from OWL classes and SKOS concepts derived from OWL individuals. | Not supported when the source ontology contains more than 1,000 OWL classes. |
Concepts Derivation
The Concepts profile derives SKOS concepts from named OWL classes. Supported class relationships can be used to establish relationships between the resulting concepts.
Because SKOS and OWL represent different types of knowledge, the derived concepts do not preserve the complete logical semantics of the source ontology.
For more information, see Derive SKOS Concepts from an OWL Ontology.
Structure Derivation
The Structure profile derives model structure from OWL classes and SKOS concepts from OWL individuals.
- OWL classes are converted into subclasses of
skos:Concept. - OWL individuals are converted into SKOS concepts.
Structure derivation supports source ontologies containing up to 1,000 OWL classes. If the source ontology exceeds this limit, use the Concepts profile if its output meets your requirements.
For more information, see Derive Model Structure from an OWL Ontology.
Outcome
You can identify which OWL elements can be edited in KMM, recognize restrictions that affect imports and model links, and select a derivation profile based on the content you want to generate.
For the next task, see Work with OWL Classes to edit supported class details, or Derive SKOS Concepts from an OWL Ontology to create SKOS concepts from OWL classes.