methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Method session1-3 h per patternWorkshop or asyncSelected Patterns

Session: Ontology Design Patterns

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with 1-6. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward Selected Patterns. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Isolate problem

    15-20 min

    Define the modeling problem in one sentence (for example "how do I model time-valid employee roles?"). Identify affected CQs. Sketch a solution-free problem fragment. Hint: If the problem splits into 2-3 sentences, multiple patterns are involved. Prefer one pattern session per pattern instead of mixing everything.

    FacilitatorSelected Patterns
  2. 2

    Phase 2: Search pattern catalog

    20-30 min

    Search for suitable candidates in the pattern catalog (keyword search, tags, similar problems). For each candidate, read description, inspect examples, and roughly check coverage against CQs. Hint: If three patterns seem equally strong, they are related. Choose the one with clearest documentation and strongest community, not the most exotic.

    FacilitatorAdapted Schema Fragments
  3. 3

    Phase 3: Adapt pattern

    30-60 min

    Adapt pattern to the domain: rename classes, specialize properties, add constraints. Document reuse relationship (pattern IRI, adaptation delta). Hint: If adaptation changes 80% of the pattern, it is no longer reuse. Document it clearly as a custom pattern or choose another pattern.

    FacilitatorPattern Documentation
  4. 4

    Phase 4: Validate

    20-30 min

    Populate the pattern in a sandbox with sample data. Run test queries for affected CQs. Check edge cases (empty values, time boundaries, multi-roles). Hint: If test query returns unexpected results, adaptation is too loose. Recheck pattern or tighten constraints, do not adapt test data.

    FacilitatorSelected Patterns
  5. 5

    Phase 5: Document and reference

    15-20 min

    Document pattern selection, source, adaptation, affected CQs, and test results in the model repo. Reference selected patterns as annotations in the model (for example dct:source) on pattern IRI. Hint: Without reference, the next modeler forgets why this pattern was selected. Reverse-engineering patterns is expensive.

    OwnerAdapted Schema Fragments
  6. 6

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerSelected Patterns
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: Ontology Design Patterns

Goal

Artifact: Selected Patterns

Working Question

Which modeling pattern solves the current problem so that it fits competency questions, the existing model, and reuse strategy?

Context

Modeling problem in one sentence; relevant competency questions; existing model fragments; list of known patterns (Part-Whole, Time-Indexed Situation, Roles, Provenance).

Setup

  • Format: Method session
  • Duration: 1-3 h per pattern
  • Mode: Workshop or async
  • Participants: One ontology engineer; one to two domain experts per pattern session; optional pattern reviewer with experience from other projects.
  • Owner: One ontology engineer
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Selected Patterns. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Pattern catalog (for example ODP wiki, NeOn pattern repository, or internal project catalog), modeling tool (Protégé, TopBraid), sketch surface, test query sandbox, sample data for pattern validation.

Preparation

Modeling problem and CQs visible. Pattern catalog at hand. Sandbox with mini sample data prepared so patterns can be tested immediately.

Agenda

  1. Phase 1: Isolate problem (15-20 min) Owner: Facilitator Action: Define the modeling problem in one sentence (for example "how do I model time-valid employee roles?"). Identify affected CQs. Sketch a solution-free problem fragment. Hint: If the problem splits into 2-3 sentences, multiple patterns are involved. Prefer one pattern session per pattern instead of mixing everything. Output: Selected Patterns

  2. Phase 2: Search pattern catalog (20-30 min) Owner: Facilitator Action: Search for suitable candidates in the pattern catalog (keyword search, tags, similar problems). For each candidate, read description, inspect examples, and roughly check coverage against CQs. Hint: If three patterns seem equally strong, they are related. Choose the one with clearest documentation and strongest community, not the most exotic. Output: Adapted Schema Fragments

  3. Phase 3: Adapt pattern (30-60 min) Owner: Facilitator Action: Adapt pattern to the domain: rename classes, specialize properties, add constraints. Document reuse relationship (pattern IRI, adaptation delta). Hint: If adaptation changes 80% of the pattern, it is no longer reuse. Document it clearly as a custom pattern or choose another pattern. Output: Pattern Documentation

  4. Phase 4: Validate (20-30 min) Owner: Facilitator Action: Populate the pattern in a sandbox with sample data. Run test queries for affected CQs. Check edge cases (empty values, time boundaries, multi-roles). Hint: If test query returns unexpected results, adaptation is too loose. Recheck pattern or tighten constraints, do not adapt test data. Output: Selected Patterns

  5. Phase 5: Document and reference (15-20 min) Owner: Owner Action: Document pattern selection, source, adaptation, affected CQs, and test results in the model repo. Reference selected patterns as annotations in the model (for example dct:source) on pattern IRI. Hint: Without reference, the next modeler forgets why this pattern was selected. Reverse-engineering patterns is expensive. Output: Adapted Schema Fragments

  6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Selected Patterns

Closeout

  • Update result artifact: Selected Patterns
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

Selected Patterns: Ontology Design Patterns

Working Question

Which modeling pattern solves the current problem so that it fits competency questions, the existing model, and reuse strategy?

Context

Modeling problem in one sentence; relevant competency questions; existing model fragments; list of known patterns (Part-Whole, Time-Indexed Situation, Roles, Provenance).

Participants

  • Owner: One ontology engineer
  • Participants: One ontology engineer; one to two domain experts per pattern session; optional pattern reviewer with experience from other projects.

Input

Pattern catalog (for example ODP wiki, NeOn pattern repository, or internal project catalog), modeling tool (Protégé, TopBraid), sketch surface, test query sandbox, sample data for pattern validation.

Template

Ontology Design Patterns Working Template

Goal

Reusable modeling patterns for recurring problems in ontologies and knowledge graphs.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Selected patterns:
  • Adapted schema fragments:
  • Pattern documentation:

Assumptions and open questions

  • ...

Decision / next step

Owner, date, and success signal.

Completion Check

  • Selected Patterns is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

Ontology Design Patterns Working Template

View templateCompact working template for Ontology Design Patterns with context, input, output artifacts, and next step.
markdown

ontology-design-patterns-working-template.md

Compact working template for Ontology Design Patterns with context, input, output artifacts, and next step.

Ontology Design Patterns Working Template

Goal

Reusable modeling patterns for recurring problems in ontologies and knowledge graphs.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Selected patterns:
  • Adapted schema fragments:
  • Pattern documentation:

Assumptions and open questions

  • ...

Decision / next step

Owner, date, and success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Selected Patterns.
  • Header with date, pattern version, and model version. Document delta for later pattern updates and keep previous version. Pin model annotation to exact pattern version, not a moving target.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet