Knowledge Modeling Process model

NeOn Methodology

Plans ontology projects as combinations of nine scenarios for specification, reuse, reengineering, and alignment.

NeOn treats ontologies as networks and provides nine scenarios rather than one linear process. A project selects scenarios, outputs, dependencies, and lifecycle to fit its context.

Core question

Which NeOn scenarios and activities lead from our sources to a maintainable ontology network?

Plan NeOn Methodology Method guide

Start comparison

Give feedbackIs this method useful to you?

Participants: 2-10
Time: Mehrere Wochen bis Monate

NeOn Methodology uses project-specific combination of the nine NeOn scenarios with explicit deliverables. Assessments remain justified and context-bound.

Paper illustration of NeOn Methodology with its method-specific working model.

Requirements
Requirements
Establish ontology requirements specification and network boundary.
Select scenarios
Select scenarios
Choose NeOn scenarios from sources and reuse needs.
Plan activities
Plan activities
Plan deliverables, dependencies, roles, and tests per scenario.
Govern lifecycle
Govern lifecycle
Govern modules, versions, alignments, and releases.

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

A good fit when

For larger ontology initiatives involving reuse, non-ontological sources, or multiple ontologies.

Ideal for

Larger ontology projects
Reuse of existing ontologies
Distributed modeling teams
Enterprise knowledge graphs

Not good for

Sehr kleine Ad-hoc-Ontologien
Pure explorative Skizzen ohne Reuse-Anspruch

Outputs

NeOn project route
NeOn project route with traceable sources, assumptions, and domain decisions.
Decision and review trail
Owners, dates, and next review for NeOn project route.

NeOn project route

Fictional worked example

project-specific combination of the nine NeOn scenarios with explicit deliverables as a precise working structure with a fictional example.

Need

CQ · scope · non-goal

Project actions, no finance ontology.

Scenario

Number · purpose · input

S2: reuse and re-engineer CSV; S3: reuse ORG.

Deliverable

Output · test · owner

Mapping tests; ontology lead.

Dependency

Module · version · alignment

Reuse W3C ORG; Person↔Member mapping.

The example demonstrates the domain logic of NeOn Methodology; worksheets remain blank.

NeOn Methodology for Building Ontology Networks

First step

Start with the core question: Which NeOn scenarios and activities lead from our sources to a maintainable ontology network?

Open the method guide

Good to do first

Knowledge Modeling

Competency Questions

Supplies scope and test questions that guide the choice of ontology scenarios.

Where to go next?

Knowledge Modeling

Ontology Design Patterns

Uses chosen design patterns within the planned ontology scenarios.

Knowledge Modeling

Linked Open Terms

Publishes the developed ontology as a linked, reusable vocabulary.

Deep dive

Purpose

The NeOn Methodology structures ontology work as a controlled process with reuse, scenarios, and reviews. It is useful when ontologies should not emerge ad hoc but modularly and reusably.

How it works

First, context, goals, and matching NeOn scenarios are set. The team then plans reuse of existing ontologies and works through iterative modeling and review steps. In the end, documented modules and clear maintenance paths remain for larger knowledge graph initiatives.

In detail

The NeOn Methodology works because it organizes ontology work as a reusable development process with scenarios, reuse, and reviews. Its benefit grows when decisions about sources, modules, and maintenance are treated not incidentally but as shapeable work packages. It gains substance through the living connection between domain goal, reused building blocks, and governance, so that the ontology can keep evolving consistently beyond the first draft.

Facilitation

A clear use case with a few modules and a review rhythm that brings together domain and technical feedback is suitable for getting started. It becomes a sensitive point when reuse looks more attractive than fit; then adoptions must be checked hard against the own domain. A good close anchors responsibilities, review criteria, and the next iteration step within the ongoing way of working.

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 Methodology Reuse Semantic Engineering

Sources

NeOn Methodology for Building Ontology Networksoeg.etsiinf.upm.esOntology Engineering Group page (UPM Madrid); describes the nine scenarios and activities of the NeOn methodology.

Artifact templates

NeOn Methodology: WorksheetPlan NeOn Methodology around its domain steps and the concrete decision question.

markdown

neon-methodology-working-template.md

Plan NeOn Methodology around its domain steps and the concrete decision question.

NeOn Methodology: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Full initiative Time: 2–4 hours planning; initiative over multiple iterations

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

Preparation for this scope

Method setup

Materials: Ontology requirements specification, source and ontology inventory, reuse and governance goals, shared workspace, source links, and decision log.
Roles: Ontology lead · domain experts · data stewards · integration owners
Advance information: Collect Ontology requirements specification, source and ontology inventory, reuse and governance goals in advance and mark open assumptions.
Overall time needed: 2–4 hours planning; initiative over multiple iterations
Setup: Prepare project-specific combination of the nine NeOn scenarios with explicit deliverables visibly and calibrate assessment terms before starting.