[protege-releases] Protege 3.4.5 Patch Release

Jennifer Vendetti <[email protected]> Sat, 12 Mar 2011 10:46:14 -0800
Newsgroups gmane.comp.misc.ontology.protege.beta
Message-ID <[email protected]>
We've posted an update to the 3.4 release (version number 3.4.5, build 608).

Download URL: http://bit.ly/Protege345

If you haven't registered to use Protege, please do so before 
downloading this patch release.

Registration URL: http://protege.stanford.edu/download/register.html


Core Protege
-------------------
- Fixed a database connection leak.

- Removed unicode_panel.jar from the classpath of Protege server's 
startup script because it threw headless exceptions if Protege-OWL used 
Forms.

- Made some updates to the Metaproject API. The Metaproject API 
facilitates programmatic access to Protege's Metaproject [1], which is 
used by the client-server version of Protege.

Change Management
-------------------------------
- Added new options to the Change menu (under Change | Clean Up Changes 
Ontology...):

a) Delete sub-changes (keep only top-level changes)

b) Wipe out changes and annotations (replace ChAO with an empty one)

- The Change menu will now only appear if change tracking is enabled.

- Added a "View Change Analysis" menu item in the Change menu that will 
start the Change Analysis plug-in [2].

- Implemented a fix for storing timestamps with different locales in the 
ChAO.

- Added a watchedBranch property to the ChAO.

- Significantly improved performance of the initial change caching for 
database mode.

- Added a column in the Change History table to display the ontology 
entity on which the change occurred.

Lucene Query
-------------------
- It's now possible to configure which entities, i.e., classes, 
properties, or individuals, should be indexed.

- The query result list can now be filtered by entity type, i.e, class, 
property, individual, using check-boxes at the bottom of the result list.

- It's now possible to index the browser text for entities by indexing 
the :NAME slot. A current limitation is that you also need to index the 
properties/slots that are part of browser slot patterns to ensure that 
the browser text index will be correctly updated. We're working on a 
better solution for this.

- Implemented support for expanded queries for browser text, e.g., "mal 
mel" will retrieve results for "malignant melanoma".

MappingMaster
----------------------
- Implemented significant extensions to the MappingMaster 
spreadsheet-to-OWL mapping language [3].

BioPortal Reference
----------------------------
- Updated the BioPortal Reference plug-in [4] to work with the latest 
version of BioPortal (2.6.4) [5].


Best Regards,
The Protege Team

[1] 
http://protegewiki.stanford.edu/wiki/Protege_Client_Server_Tutorial_Configuration#The_Metaproject
[2] http://protegewiki.stanford.edu/wiki/ChangeAnalysisTab
[3] http://protege.cim3.net/cgi-bin/wiki.pl?MappingMasterDSL
[4] http://protegewiki.stanford.edu/wiki/BioPortal_Reference_Plugin
[5] http://bioportal.bioontology.org/

_______________________________________________
protege-releases mailing list
[email protected]
https://mailman.stanford.edu/mailman/listinfo/protege-releases

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03