Knowledge Modeling Analysis method

Ontology Design Patterns

Applies small reusable modelling solutions to bounded ontology problems.

Content ODPs solve recurring modelling problems with intent, competency questions, consequences, and example axioms. Selection and specialisation must fit local semantics.

Core question

Which ontology design pattern satisfies the competency questions with suitable consequences?

Plan Ontology Design Patterns Method guide

Start comparison

Give feedbackIs this method useful to you?

Participants: 1-6
Time: 1-3 h pro Pattern

Ontology Design Patterns uses test a local modelling problem against an ODP's intent, CQs, axioms, and consequences. Assessments remain justified and context-bound.

Paper illustration of Ontology Design Patterns with its method-specific working model.

Bound problem
Bound problem
Bound the modelling problem and competency questions.
Compare patterns
Compare patterns
Compare intent, examples, consequences, and known uses.
Specialise
Specialise
Minimally import or locally specialise the pattern.
Test CQs
Test CQs
Run queries against positive, negative, and boundary cases.

Update after new evidence or a material context change and retain the previous version.

A good fit when

For recurring subproblems such as participation, situation, time interval, or n-ary relation.

Ideal for

Consistent ontology modeling
Knowledge graph schemas
Cross-domain reuse
Onboarding new modelers

Not good for

Sehr einmalige Domain-Strukturen
Schnelle Prototyping-Skizzen ohne Reuse-Ziel

Outputs

ODP adoption record
ODP adoption record with traceable sources, assumptions, and domain decisions.
Decision and review trail
Owners, dates, and next review for ODP adoption record.

ODP adoption record

Fictional worked example

test a local modelling problem against an ODP's intent, CQs, axioms, and consequences as a precise working structure with a fictional example.

ODP adoption record
Subject	Problem/CQ	Pattern	Consequence	Test
ODP adoption recordWorked example	Role-based participation over time.	Participation Pattern.	Participation as an instance.	Approver A-17 found; outside interval excluded.

1. Problem/CQ
ODP adoption record
Role-based participation over time.
2. Pattern
ODP adoption record
Participation Pattern.
3. Consequence
ODP adoption record
Participation as an instance.
4. Test
ODP adoption record
Approver A-17 found; outside interval excluded.

The example demonstrates the domain logic of Ontology Design Patterns; worksheets remain blank.

OntologyDesignPatterns.org

First step

Start with the core question: Which ontology design pattern satisfies the competency questions with suitable consequences?

Open the method guide

Good to do first

Knowledge Modeling

Competency Questions

Supplies the competency questions against which fitting design patterns are selected.

Where to go next?

Knowledge Modeling

Shape-First Modeling

Turns the adopted patterns into testable SHACL or ShEx rules.

Knowledge Modeling

Property Graph Schema Design

Carries adopted patterns into a property graph schema for graph databases.

Deep dive

Purpose

Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles.

How it works

First, the problem or modeling context is described precisely. The team then selects matching patterns, adapts them, and checks whether they correctly capture the domain meaning. This produces a model that stays consistent and does not need to be reinvented with every extension.

In detail

Ontology Design Patterns help because they translate recurring modeling problems into proven solution forms. The method works strongly when a pattern serves as a thinking aid and its assumptions are deliberately checked against the own domain. Good use pays attention to semantic fit, later extensibility, and clean documentation of adaptations, so that consistency grows without smoothing away domain-specific particularities.

Facilitation

Prepare a small set of matching patterns and briefly state for each which problem it is meant to solve. The tipping point often lies where a pattern looks elegant but hides important roles or temporal aspects of the domain. Close with a justified selection, documented adaptations, and an example that immediately tests the new structure.

The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.

Open method guide

Your perspective

Does this method help with your work?

Your feedback helps shape the next improvements to methodatlas.

Sources and topics

Topics

Ontology Patterns Reuse Semantic Modeling

Sources

OntologyDesignPatterns.orgontologydesignpatterns.orgCommunity wiki ontologydesignpatterns.org; collects reusable ontology design patterns with examples.

Artifact templates

Ontology Design Patterns: WorksheetPlan Ontology Design Patterns around its domain steps and the concrete decision question.

markdown

ontology-design-patterns-working-template.md

Plan Ontology Design Patterns around its domain steps and the concrete decision question.

Ontology Design Patterns: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Full workshop Time: 60–90 minutes per pattern

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

Materials: Competency questions, local vocabulary, candidates from the ODP catalogue, shared workspace, source links, and decision log.
Roles: Ontology engineer · domain expert · data consumer
Advance information: Collect Competency questions, local vocabulary, candidates from the ODP catalogue in advance and mark open assumptions.
Overall time needed: 60–90 minutes per pattern
Setup: Prepare test a local modelling problem against an ODP's intent, CQs, axioms, and consequences visibly and calibrate assessment terms before starting.