Difference between revisions of "ProtegeDesktopUserDocs"

Revision as of 16:11, April 17, 2008

General

Protege 4 "to do" list

Below is a "to-do" list of things that we are working on integrating into Protege 4. Please note that these items are not listed in any particular order of priority. If you have a question about the status of any line item, please post a message on the Protege 4 mailing list.

• Protege-Frames editor (currently we only have the OWL editor)
• Protege Web client
• Protege Services
• Client-server support
• Better SWRL support in the Protege-OWL editor
• Better modularization support
• Support for collaborative ontology development
• Forms and browser slot patterns in the Protege-OWL editor
• A database back-end

User Interface

Protege-OWL

• Getting started with the Protege-OWL editor
• Overview of new features in the Protege-OWL editor
• A Practical Guide to Building OWL Ontologies using Protege 4 and CO-ODE Tools (errata page)
• Menu and keyboard shortcuts
• DL Query tab
• Manchester OWL Syntax

Plug-ins

Protege-OWL

Viewing Plugins

To see a listing of plug-ins specific to the Protege-OWL editor, go to the Wiki article for the 4.x version of the Protege-OWL editor. The list of "Compatible Plugins" on this page is the result of a semantic query that gathers all plug-ins that have declared themselves compatible with the 4.x version of the Protege-OWL editor.

The CO-ODE group at the University of Manchester is the biggest contributor of plug-ins to the Protege-OWL editor. As such, users may be interested to look at the Protege 4 Plugins page on the CO-ODE Web site, which a listing of only those plug-ins developed at the University of Manchester. This is a good place to go to download the source code for CO-ODE developed plug-ins.

Adding Plugins

If you have developed a plug-in for Protege-OWL 4.0 and you would like to contribute it to the community, follow the following steps:

• Click the New Plugin Link. You may want to right click and choose a new window.
• Choose a name for the page that discusses the new plugin (e.g. "Sub Ontology Tab").
• Click "Add or Edit"
• Be sure to add "Protege-OWL" (exactly like so without the quotes) in the Works with field. Also give the plugin a type (commonly "Tab Widget").
• Fill in the other fields and save.
• Click the create new version and use the naming convention described. Without this step the plugin will not show up in the plugin list below.
• Make the plugin compatible with "Protege-OWL 4.0".
• When you are done save the page and make sure that your plugin shows up on the 4.x version of the Protege-OWL editor page. It seems for some reason this page often does not update for a while so you may need to come back later.

Handling Problems with FaCT++ not Finding Libraries

On some occasions FaCT++ will have problems

First checkout FaCT++ with the command line call:

svn checkout http://factplusplus.googlecode.com/svn/trunk/ factplusplus.

We now need to edit the Makefile.include to use the options associated with the correct version of gcc. First we find the version of gcc with the command line

gcc -v

On my linux machine the result was

Reading specs from /usr/lib/gcc/i386-redhat-linux/3.4.6/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-java-awt=gtk --host=i386-redhat-linux
Thread model: posix
gcc version 3.4.6 20060404 (Red Hat 3.4.6-9)

So I modified the Makefile.include so that the GENERAL_DEFINES were

GENERAL_DEFINES = $(GCC_OPT_OPT) $(GCC_34_OPT) $(ALL_DEF)

Wish list

To follow is list of considerations for improving Protege 4, its documentation, and/or this Wiki.

• Convert A Practical Guide Guide to Building Ontologies... to a collection of Wiki pages so that the guide can be more easily shared, searched, modified, commented on, referenced by section, extended, etc.
• Consider an "Add Tab" feature in the Tabs menu that would allow users to add an empty tab (e.g., "My Tab"), and thus have a place to assemble personal layouts from a clean starting point. Perhaps provide a minimum of one empty "My Tab" in the user interface.