1. Ontology Engineering and Plugin Development with the NeOn Toolkit NeOn Toolkit Overview June 1st, 2008 Michael Erdmann, Peter Haase, Holger Lewen, Rudi Studer

2. Slide 2Agenda  Introduction to the NeOn Toolkit –Terminology –Languages –Components  Modeling with the NeOn Toolkit

3. Slide 3 A Little Terminology  We use Eclipse-Terminology  Workspace, projects, files, folders –Common place to organize & store development artifacts  Workbench, editors, views, perspectives –Common user presentation and UI paradigm

4. Slide 4 Menus, Views, Editors & Perspectives Tool bar Perspective and Fast View bar Resource Navigator view Stacked views Properties view Tasks view Outline view Bookmarks view Menu bar Message area Editor Status area Text editor

5. Slide 5 Perspective = Editors + Views Perspective Views Editor

6. Slide 6 NeOn Toolkit Entity Property View showing details Ontology Navigator Instances

7. Slide 7 NeOn Toolkit Ontology Navigator Instances Other views e.g. visualizer

8. Slide 8 Language Terminology  FLogic: –Concepts –Attributes and relations –Instances  OWL: –Classes –Data properties and object properties –Individuals  RDF(S): –Classes –Properties –Instance

9. Slide 9 Language Support of NeOn Toolkit  The NeOn Toolkit follows the dual language approach.  FLogic: –Native support for frame based language FLogic, which is declarative like Prolog, and object-oriented like Java; –Import and export of OWL and RDF(S) ontologies by translating to/from the frames-model.  OWL: –Native support for managing OWL ontologies. –API is finished –GUI level support is work-in-progress

10. Slide 10 Ontology Navigator  Workspace –Hosts all ontology projects  Ontology-Project is the main structuring means –Hosts ontologies in one language (OWL or FLogic) –Independent from other projects –Imported ontologies must be (are) in the same project  Ontology –Hosts classes, properties, rules, … –Depending on the ontology language  Folder metaphor –Each folder contains different kinds of entities –Sometimes hierarchical structure

11. Slide 11 Entity Property View  Each type of entity has its specific entity property view

12. Slide 12 Entity Property View  Each type of entity has its specific entity property view with sub tabs

13. Slide 13 Entity Property View  Each type of entity has its specific entity property view with sub tabs

14. Slide 14Individuals

15. Slide 15Agenda  Introduction to the NeOn Toolkit –Terminology –Languages –Components  Modeling with the NeOn Toolkit

16. Slide 16

17. Slide 17 [Demo Script]  Start NTK in FLO perspective –Load FLO onto –Browse/visualize the ontology –Query it –New OWL project –Transform FLO to OWL  Switch to OWL perspective –Load Dolce ontologies –New OWL project Load Pizza ontology –Browse visualize the ontology –modify the pizza ontology [see next page]

18. Slide 18 [Demo Script]  OWL modeling –Beverage subclassof Food –Beverage disjointWith Pizza –Texture subclassof ValuePartition –Liquid, Solid subclassof Texture –Soft, Medium, Hard subclassof Solid –ObjectProperty hasTexture Domain DomainConcept Range StateOfMatter –Beverage equivRestriction: All hasStateOfMatter Liquid