Difference between revisions of "Protege4Migration"
From Protege Wiki
Nickdrummond (talk | contribs) (screenshots added) |
|||
| Line 1: | Line 1: | ||
<div class="orangeBox"> | <div class="orangeBox"> | ||
<span class="orangeBoxTitle">Choosing between versions of Protege</span><br /><br /> | <span class="orangeBoxTitle">Choosing between versions of Protege</span><br /><br /> | ||
| − | This page contains | + | This page contains a high level outline of the major differences in features between Protege 3.x and Protege 4.0. |
</div><br /> | </div><br /> | ||
| Line 8: | Line 8: | ||
== Overview == | == Overview == | ||
| − | There are a | + | There are a number of differences between the Protege 3 series (Protege 3.3.1, Protege 3.4 beta) and the alpha version of Protege 4.0. This page is designed to highlight some of the major factors that may influence which of the two systems would be most appropriate for your project at present. It will also serve as a useful reference point for identifying major features that need priority migration from 3.x to 4.0. This list is by no means exhaustive and is intended as an overview only.<br /><br /> |
| − | This page is designed to | ||
| − | 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 | ||
| − | == | + | == Side by Side Comparison == |
| + | <br /> | ||
| − | {| | + | {| cellpadding="5" cellspacing="1" style="border:1px dashed #BC8F8F;" |
| − | ! Protege 3.x | + | ! align="left" | Protege 3.x |
| − | ! Protege 4.0 | + | ! align="left" | Protege 4.0 |
|- | |- | ||
| − | + | | [[Image:p3.3.png]] | |
| − | + | | [[Image:p4.0.png]] | |
|- | |- | ||
| Frames editing | | Frames editing | ||
| Frames editor not migrated yet | | Frames editor not migrated yet | ||
|- | |- | ||
| − | | '''OWL 1.0''' language support | + | | '''OWL 1.0''' language support || '''OWL 1.1''' language support |
| − | | '''OWL 1.1''' language support | ||
|- | |- | ||
| OWL and RDF(S) support | | OWL and RDF(S) support | ||
Revision as of 14:50, October 5, 2007
Choosing between versions of Protege
This page contains a high level outline of the major differences in features between Protege 3.x and Protege 4.0.
Contents
[hide]Overview
There are a number of differences between the Protege 3 series (Protege 3.3.1, Protege 3.4 beta) and the alpha version of Protege 4.0. This page is designed to highlight some of the major factors that may influence which of the two systems would be most appropriate for your project at present. It will also serve as a useful reference point for identifying major features that need priority migration from 3.x to 4.0. This list is by no means exhaustive and is intended as an overview only.
Side by Side Comparison
| 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 |
