Protege 3.4 Release Candidate 2 (build 529)

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

Protege 3.4 Release Candidate 2 (build 529)

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

**PLEASE NOTE - This is a candidate build for the 3.4 release.  We
encourage you to try this build and report any bugs before they become
part of an official release.

Bug Fixes in Core Protege
- Fixed a problem where users ran out of Java PermGen space.

- Fixed a problem in the installer that caused Protege to get installed
with an empty program group on the Windows Vista operating system.

Changes in Protege Client-Sever
- The read-only policy is now enforced in client-server mode. Users
without write access to an ontology will not be able to perform edits.
Note that the read-only policy is only enforced if there is a "Write"
operation defined in the metaproject.

- The server now logs Protege information to the console, e.g., build
number, heap size, character encoding, etc.

- The Administer Protege Server panel now supports multiple selection
for project shutdown and killing user sessions.

- The server now saves server projects before shutdown, i.e., through
the Administer Protege Server panel.

Changes & Bug Fixes in Protege-OWL
- Fixed domain and range widgets that prevented a domain and range from
being added to an imported property.

- Fixed the range widget that sometimes prevented the addition of a new
data range value because the add icon was disabled.

- The triples table, which is accessible by a switch icon in the
Annotations widget, shows all triples that have the selected resource as
a subject. In previous versions, the triples were filtered.

- Fixed a problem where a clone operation rearranged the imports tree.

- The Protege native writer can now be invoked when converting database
projects to file-based projects.

- Added a mechanism to disable automatic importing of several ancillary
ontologies by the SWRLTab [1].

Changes in Collaboration & Change Tracking
- The language of change descriptions in the Changes Tab has been
improved so that users can more easily understand the change history of
a particular resource.

- More checks are made in client-server mode for an improperly
configured changes and annotations ontology (ChAO) in the metaproject.

As always, a web-based version of the release notes is available on our
site [2].

Best Regards,
The Protege Team


protege-beta mailing list
[hidden email]

Instructions for unsubscribing: