Difference between revisions of "Protege4Migration"
From Protege Wiki
Nickdrummond (talk | contribs) (Initial Page) |
Nickdrummond (talk | contribs) (screenshots added) |
||
| Line 18: | Line 18: | ||
! Protege 4.0 | ! Protege 4.0 | ||
|- | |- | ||
| − | | Frames | + | | align="center" | [[Image:p3.3.png]] |
| + | | align="center" | [[Image:p4.0.png]] | ||
| + | |- | ||
| + | | Frames editing | ||
| Frames editor not migrated yet | | Frames editor not migrated yet | ||
|- | |- | ||
Revision as of 04:52, October 5, 2007
Choosing between versions of Protege
This page contains an outline of the major feature differences between Protege 3.x and Protege 4.0.
Overview
There are a lot of differences between the current release version of Protege 3.x and the current Protege 4.0 alpha. This page is designed to show some of the major factors that would influence which of the two systems would be most appropriate for your project at this current time. It will also serve as a useful reference point for identifying major features that need priority migration from 3.x to 4.0. This is in no way a complete list, but is intended as an overview only.
Protege 3.x and 4.0 Side by Side
| Protege 3.x | Protege 4.0 |
|---|---|
|
|
| Frames editing | Frames editor not migrated yet |
| OWL 1.0 language support | OWL 1.1 language support |
| OWL and RDF(S) support | Purely OWL framework currently |
| Layered API of OWL over RDF over Frames | Uses clean, heavilly optimised, standard, open-source OWL API |
| SPARQL support | No SPARQL support |
| Meta-modelling support (allowing OWL-full) | no OWL-full |
| RDF/frames overheads in loading, reasoning and memory usage | Optimised OWL parser and model reduce memory usage and increase speed |
| Reasoner support through HTTP DIG interface allows connection to any DIG compliant reasoner | Direct connection to FaCT++ and Pellet for optimum speed of classifying |
| Project file based configuration | Global configuration - no project files |
| OWL imports through repositories mechanism | Simplified imports resolution from common folder (repositories also supported) |
| Large set of plugins available (incl SWRL support) | Increasing number of plugins available (SWRL support to be ported soon) |
| Protege plugin framework for Tabs, Slots, Backends, Projects, Import/Export | Built on Java Plugin Framework (soon to be switched to OSGi) - can define any type of plugin extension |
| Tabs and Slot Widgets make much of interface configurable | Plugins define all interface elements including tabs, views and menus making entire interface configurable |
| Access of meta model to configure interface | Menu and Drag and drop interface elements |
