methodatlas
Method guideKnowledge Modeling

Ontology Design Patterns

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityMedium
Time1-3 h pro Pattern
Participants1-6
FormatWorkshop + async
MaturityEstablished
Plan Ontology Design Patterns
01

Prerequisite

What needs to be finished first

Complete firstBounded subject

The scope and purpose of Ontology Design Patterns are stated as a concrete question.

Without scope, ODP adoption record becomes arbitrary.
Complete firstAccess to relevant perspectives

Competency questions, local vocabulary, candidates from the ODP catalogue and domain decision makers are available.

Without these perspectives, central claims in ODP adoption record remain unsupported.
02

Preparation

What needs to be ready before start

Materials

Competency questions, local vocabulary, candidates from the ODP catalogue, shared workspace, source links, and decision log.

People / roles

Ontology engineer · domain expert · data consumer

Pre-read

Collect Competency questions, local vocabulary, candidates from the ODP catalogue in advance and mark open assumptions.

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.

03

Core question

The one question this method answers

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

04

Flow

Phases with goal, actions, output and pitfall

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

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
SubjectProblem/CQPatternConsequenceTest
ODP adoption recordWorked exampleRole-based participation over time.Participation Pattern.Participation as an instance.Approver A-17 found; outside interval excluded.

  1. 1. Problem/CQ

    ODP adoption record
    Role-based participation over time.

  2. 2. Pattern

    ODP adoption record
    Participation Pattern.

  3. 3. Consequence

    ODP adoption record
    Participation as an instance.

  4. 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

  1. 1

    Bound problem

    Bound problem

    Goal

    Produce problem profile so the core question “Which ontology design pattern satisfies the competency questions with suitable consequences?” can be answered with stronger support.

    Inputs for this step

    • Competency questions
    • local vocabulary
    • candidates from the ODP catalogue

    Actions

    • Bound the modelling problem and competency questions.
    • Record source, rationale, and open uncertainty directly in problem profile.

    Output

    problem profile

    problem profile · source · uncertainty · next decision

    Quality check

    Can the subproblem be tested independently?

    Pitfall

    A pattern is copied for its name without testing intent, CQs, and consequences. Match intent and CQs first, adopt minimal axioms, and run positive and negative queries.

    Timing: 10–20 minutes

  2. 2

    Compare patterns

    Compare patterns

    Goal

    Produce pattern comparison so the core question “Which ontology design pattern satisfies the competency questions with suitable consequences?” can be answered with stronger support.

    Inputs for this step

    • problem profile
    • local vocabulary
    • candidates from the ODP catalogue

    Actions

    • Compare intent, examples, consequences, and known uses.
    • Record source, rationale, and open uncertainty directly in pattern comparison.

    Output

    pattern comparison

    pattern comparison · source · uncertainty · next decision

    Quality check

    Does the ontological commitment fit?

    Pitfall

    A pattern is copied for its name without testing intent, CQs, and consequences. Match intent and CQs first, adopt minimal axioms, and run positive and negative queries.

    Timing: 10–20 minutes

  3. 3

    Specialise

    Specialise

    Goal

    Produce pattern module so the core question “Which ontology design pattern satisfies the competency questions with suitable consequences?” can be answered with stronger support.

    Inputs for this step

    • pattern comparison
    • local vocabulary
    • candidates from the ODP catalogue

    Actions

    • Minimally import or locally specialise the pattern.
    • Record source, rationale, and open uncertainty directly in pattern module.

    Output

    pattern module

    pattern module · source · uncertainty · next decision

    Quality check

    Are IRIs and provenance traceable?

    Pitfall

    A pattern is copied for its name without testing intent, CQs, and consequences. Match intent and CQs first, adopt minimal axioms, and run positive and negative queries.

    Timing: 10–20 minutes

  4. 4

    Test CQs

    Test CQs

    Goal

    Produce adoption record so the core question “Which ontology design pattern satisfies the competency questions with suitable consequences?” can be answered with stronger support.

    Inputs for this step

    • pattern module
    • local vocabulary
    • candidates from the ODP catalogue

    Actions

    • Run queries against positive, negative, and boundary cases.
    • Record source, rationale, and open uncertainty directly in adoption record.

    Output

    adoption record

    adoption record · source · uncertainty · next decision

    Quality check

    Does the module satisfy all relevant CQs?

    Pitfall

    A pattern is copied for its name without testing intent, CQs, and consequences. Match intent and CQs first, adopt minimal axioms, and run positive and negative queries.

    Timing: 10–20 minutes

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

Ontology Design Patterns · Modellierungsmuster wiederverwendenEin Modellierungsproblem mit Pattern-Katalogen abgleichen, ein Muster anpassen und über Competency Questions validieren
Ontology Design PatternsDas Visual zeigt ein Modellierungsproblem, einen Pattern-Katalog, ein adaptiertes Domain-Fragment und die Validierung über Competency Questions.Wiederkehrende Ontology-Probleme mit Mustern lösenPatterns machen Modellierungsentscheidungen wiederverwendbar, prüfbar und für Reviews erklärbar.Modellierungsproblemwiederkehrende Struktur isolierenPattern-KatalogPart-WholeTeil-GanzesRoleKontextrolleTime IntervalGültigkeitDescriptionKonzeptbeschreibungAdaptiertes FragmentPattern mit Domain-Begriffen belegenCQ-Validationbeantwortet das Pattern die Testfrage?passendes Musterwählenan Domain anpassenEntscheidungdokumentieren
Form

Versioned ODP adoption record with date, sources, owners, and next review.

Versioning / ownership

Retain date, source, assumption state, and decision for every version of ODP adoption record.

Tool alternatives
  • ODP adoption record as board or document
  • Source and evidence register
  • Decision and action log

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.

Prepare for the work steps

Bound problem: Bound problem

  • Competency questions
  • local vocabulary
  • candidates from the ODP catalogue

Compare patterns: Compare patterns

  • problem profile
  • local vocabulary
  • candidates from the ODP catalogue

Specialise: Specialise

  • pattern comparison
  • local vocabulary
  • candidates from the ODP catalogue

Test CQs: Test CQs

  • pattern module
  • local vocabulary
  • candidates from the ODP catalogue

ODP adoption record

SubjectProblem · question · boundaryName · intent · sourceAxiom · commitment · query impactPositive · negative · result
ODP adoption record
  • ODP adoption record: Worked example

Enter only real input, sources, and decisions.

OntologyDesignPatterns.org

Bound problem: Bound problem

Expected artifact: problem profile

problem profile · source · uncertainty · next decision

Entry:

...

  • Can the subproblem be tested independently?

Compare patterns: Compare patterns

Expected artifact: pattern comparison

pattern comparison · source · uncertainty · next decision

Entry:

...

  • Does the ontological commitment fit?

Specialise: Specialise

Expected artifact: pattern module

pattern module · source · uncertainty · next decision

Entry:

...

  • Are IRIs and provenance traceable?

Test CQs: Test CQs

Expected artifact: adoption record

adoption record · source · uncertainty · next decision

Entry:

...

  • Does the module satisfy all relevant CQs?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/ontology-design-patterns/run-sheet

06

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

ontology-design-patterns-beispiel.md

Concrete filled scenario, fictional example

Problem: n-ary participation among person, action, role, and interval. Candidate: Participation Pattern extended with Role and TimeInterval. CQ test: who participated as approver in A-17 between 1 and 15 May? Consequence: Participation becomes an instance; a simple direct edge is insufficient.

07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. Bound problemA pattern is copied for its name without testing intent, CQs, and consequences.View in phase
  2. Compare patternsA pattern is copied for its name without testing intent, CQs, and consequences.View in phase
  3. SpecialiseA pattern is copied for its name without testing intent, CQs, and consequences.View in phase
  4. Test CQsA pattern is copied for its name without testing intent, CQs, and consequences.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

ODP adoption record answers the core question with traceable evidence or explicitly marked uncertainty.
Owners, next actions, and review dates are named for open points.

Method after Ontology Design Patterns Community. Curated with 1 sources.

Sources: OntologyDesignPatterns.org

Flow, timeboxes, and pitfalls are editorially curated practice recommendations based on the listed sources.

Where to go next?

Paper illustration of Shape-first Modeling with its method-specific working model.
Knowledge Modeling
Shape-First Modeling

Turns the adopted patterns into testable SHACL or ShEx rules.

Paper illustration of Property Graph Schema Design with its method-specific working model.
Knowledge Modeling
Property Graph Schema Design

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

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profileMore methods