Protege 4.2 Beta Release Notes
From Protege Wiki
Revision as of 16:02, March 21, 2012 by JenniferVendetti (talk | contribs) (added notes for build 269)
Protege 4.2 Beta
We are pleased to announce Protege 4.2 beta! The main thrust of the 4.2 series will be the roll out of several new plug-ins, including an ontology difference tool, enhanced explanation support, client-server capabilities, support for code generation, and a database back-end. Please contact us via the Protege 4 mailing list with questions, feedback, and bug reports.
Download Protege 4.2 beta from the main Protege website (new users, please register first).
Release Notes
The contents of the release notes section describe changes relative to Protege 4.1 and Protege 4.2 alpha.
Build 269 -- March 21, 2012
- Introduced a new explanation plug-in in addition to the existing basic explanation plug-in provided in previous releases. The new explanation plug-in, referred to as "Justification Based Explanation", will generate multiple explanations for a single inference, will sort the explanation to be more readable, and can generate laconic explanations (laconic justifications). The plug-in can also generate explanations for inconsistent ontologies (previous releases only included an ad-hoc tool, which in some cases was unable to find any explanation for a problem).
- Fixed a bug that could cause Protege to crash during start-up.
Build 265 -- March 14, 2012
- Improved the user interface for the Active Ontology tab so that the ontology name and version are much more prominent, thereby encouraging users to set versions when appropriate.
- Launching the Protege application now opens an empty ontology instead of a welcome screen. This is part of a broader effort to align Protege's behavior with common document editing tools, e.g., opening Microsoft Word presents users with a blank document.
- Added support for Java code generation. Available from Tools | Generate Protege-OWL Java Code.
- Protege no longer requires administrative privileges to run on Windows machines. Please note the exception that downloading new plug-ins will still require Protege to be run in administrative mode.
