28.11.2012 Views

Innovation and Ontologies

Innovation and Ontologies

Innovation and Ontologies

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

202 Multimethodological Background<br />

Once an ontology developed by the Cyc methodology is comprehensive enough, new common<br />

sense knowledge can be acquired either by using natural language or by delegation to machine<br />

learning tools (Gómez-Pérez, Fernández-López & Corcho, 2002; Guha & Lenat, 1990; Lenat &<br />

Guha, 1990). Validation of the ontology takes place by getting persons with common sense<br />

knowledge to use the system <strong>and</strong> feedback thereon (Lenat et al., 1990).<br />

1.1.1.2 Methods of Enterprise Ontology <strong>and</strong> TOVE<br />

�<br />

Uschold, King, Grueninger <strong>and</strong> Fox documented their experiences of the universityindustry<br />

cooperation of the Enterprise Ontology <strong>and</strong> TOVE. The resulting<br />

guidelines describe the activities necessary for establishment of a formal ontology as<br />

an intelligent way of enterprise modeling.<br />

In 1996, Uschold, King <strong>and</strong> their colleagues came up with methodical outlines elaborated during<br />

development of the Enterprise Ontology (Uschold, 1996; Uschold & Grueninger, 1996; Uschold et<br />

al., 1998). They suggested the following procedure:<br />

Purpose & Scope<br />

Scope<br />

Building<br />

Guidelines for Ontology Building<br />

• Identification <strong>and</strong> characterization of intended users (e.g. managers, programmers)<br />

• Identification of the purpose(s)<br />

• Production of user requirements document<br />

• Motivating (detailed) scenarios<br />

• Informal competency questions that the ontology should be able to answer<br />

• Brainstorming session to collect all potentially relevant terms <strong>and</strong> phrases<br />

• Grouping of the collected terms<br />

Capture (by a middle out approach234): Identification of key concepts <strong>and</strong><br />

relationships; production of precise unambiguous text definitions for concepts <strong>and</strong><br />

relationships; identification of terms to refer to concepts <strong>and</strong> relationships; <strong>and</strong><br />

agreement on all above<br />

Coding: Commitment to basic terms (meta-ontology), selection of formal<br />

representation language, <strong>and</strong> writing of code<br />

Integration: Decision on how <strong>and</strong> how much existing ontologies are integrated<br />

Evaluation Review process includes endusers as usability judges<br />

Documentation Establishment of guidelines for documentation<br />

table 52 Guidelines for ontology building (based on Uschold & Grueninger, 1996; Uschold, 1996)<br />

234 Middle out combines the top down <strong>and</strong> the bottom up approach, for details cf. paragraph 2.2.2.2.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!