Protege 3.3 Beta update (build 408)

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Protege 3.3 Beta update (build 408)

Jennifer Vendetti
There is a new beta build available on our Web site:

IMPORTANT: We have introduced many *major* changes in this beta release. These changes were developed over a relatively long period of time to support dramatic performance improvements when Protege is being used in client-server mode with OWL ontologies and the database back-end. As a result of having introduced these changes, there are two essential things to note before upgrading to this release:

* If you have a project in database format and you want to upgrade to this build, you must first convert your project to a file-based one in Protege, and then regenerate the database project using build 408.

* If you use Protege in client-server mode, you should be aware that we have changed the format of the metaproject ontology. You will have to migrate your data from the old metaproject ontology to the new format, an example of which can be found in the following location:


Changes & Bug Fixes in Protege
1. Made many changes to client-server Protege:

a). Dramatic performance improvements, specifically for the case where Protege is being used in client-server mode with OWL ontologies and the database back-end.

b). Added the ability to control access to the Protege server through an access control policy. The policy is defined in the metaproject ontology and identifies collections of users (groups) that have rights to perform particular operations. This mechanism is extensible and can be used by plug-in developers.

c). There are several new client-server configuration options that are documented in the Protege multi-user tutorial on our Wiki (

d). Fixed several bugs involving incorrect processing of transactions (mainly effecting the client-server code).

e). Made several updates that may be of special interest to developers including the ProtegeJob class ( that allows a client to specify a job that must be run on the server and greater access to the details of transactions with the transaction monitor.

2. Added an option in the Project -> Configure... -> Options panel that allows users to enable/disable the Undo/Redo functionality.

3. Added better support for annotation properties in Protege-OWL. Simple annotation properties will not be automatically converted into datatype annotation properties as they were in previous versions.

4. There is a new directory under <protege-install-dir>/examples called "collaborativeNewspaper" that contains a version of the newspaper project configured to work with Collaborative Protege ( If you use Protege in client-server mode, the metaproject ontology has been modified to include the collaborative newspaper ontology. If you start the Protege server with the example metaproject, you will be able to test Collaborative Protege in client-server mode.

Changes to Bundled Plug-ins
1. We are now bundling an updated version of the Jambalaya plug-in (version 2.6.0). To read about all the new features, please visit the following Web page:

2. Removed the DataGenie plug-in (, which is no longer being maintained and replaced it with the DataMaster plug-in ( DataMaster allows users to import schema structure and data from relational databases into Protege.

3. The XMLTab ( was updated to work with the Protege-OWL editing environment. Previously it only worked with frame-based ontologies.

As always, a web-based version of the release notes is available on our website:

The Protege Team

protege-beta mailing list
[hidden email]

Instructions for unsubscribing: