DOME vs' IODT

1
DOME vs. IODT

• Two Eclipse-based Ontology Editors

2

• Introduction
• Features
• Evaluation

3
Motivation

• They are both
• Eclipse-based
• Tree-based
• So what can we
• learn?
• reuse?

4
Origin / Home

• DOME
• Started as DERIs OMS in fall 2004
• OMWG
• DERI
• Ontotext
• Ontoprise

• IODT
• Started as Ontology Engineering Environment
  (ORIENT) at IBM China
• Now developed at alphaWorks development platform

5
Data Model

• DOME
• Metamodel
• None
• Language
• WSML

• IODT
• Metamodel
• Derived from ODM and implemented in EMF
• Language
• OWL

6

• Introduction
• Features
• Evaluation

7
Eclipse UI contributions

• DOME
• One view
• For NFPs
• Two editors
• WSML editor
• Mapping editor
• One perspective
• Ontologies
• Two wizards
• New WSML files
• New mapping files

• IODT
• Two views
• Class hierarchy
• Property hierarchy
• One editor
• UML-style ontology editor
• One perspective
• OWL
• Two wizards
• New OWL files
• New view files

8
Repository

• DOME
• ORDI
• WSML lt-gt Triple File
• WSML lt-gtTriple Repository
• Querying

• IODT
• Minerva
• Storage and query system based on relational data
  storage (DB2 or Derby)
• Supports a subset of the SPARQL language

9
Reasoning Support

• DOME
• Still to be done

• IODT
• Inference Module
• DIG-Interface
• DL Reasoner for T-Box inference
• Pellet
• Racer
• Structural T-Box Engine
• Set of logic rules for A-Box inference

10

• Introduction
• Features
• Evaluation

11
Usability
12
Availability
13
Legal issues

• DOME
• Open source
• MIT license

• IODT
• Non-open source
• Nonexclusive license

14
Conclusions

• We can learn
• To model language independent
• We can reuse
• The EMF -gt UML approach

15
DOME vs. IODT

• Thanks a lot