[protege-releases] Protege 4.1 beta update (build 217)
Jennifer Vendetti <[email protected]> Fri, 18 Feb 2011 16:00:28 -0800
| Newsgroups | gmane.comp.misc.ontology.protege.beta |
|---|---|
| Message-ID | <[email protected]> |
There's a new Protege 4.1 beta build available on our website: http://bit.ly/Protege41Beta Please note that the Manchester OWL Syntax is now discouraged as a format for saving the entire ontology as certain axioms cannot be represented in this format and are lost during save operations. Enhancements --------------------- - Upgraded Protege to use version 3.2.2 of the OWL API [1]. - Added support to the OntoGraf visualization plug-in [2] to export the current visible graph into a DOT language format file. Thanks go to Sean Falconer for this contribution. - Simplified and consolidated some of the menu items in the main menu bar. - Made rendering preferences much quicker to access via the new "View" menu, e.g., View | Render by name, View | Render by label. - Axiom annotations are now displayed in axiom tooltips. - Added support for the disjoint union axiom. - Dublin Core annotation properties are no longer included by default in new ontologies. If users want Dublin Core annotation properties, we recommend you import protege-dc.owl [3]. - Modified the user interface of the dialog for creating/editing annotations to disable the "Lang" combo box if a type other than plain literal is selected. - Users can now enter inverse object properties when adding object property disjoint or equivalent axioms. - After a user runs a reasoner, Protege will now display inferred same individuals and disjoint classes. The display of inferred disjoint classes is turned off by default. - Added an explanation facility for why classes are disjoint. - In previous builds, if a user edited a general class axiom (GCI) in the "General class axioms" view in such a way that it became a regular class axiom, the resulting regular class axiom disappeared from the GCIs view. This mistakenly gave the impression that the edit to the GCI was unsuccessful. Going forward, Protege will present a dialog after completion of an edit to notify the user that the GCI is now a regular class axiom and will be displayed in the appropriate view (not the GCIs view). Bug Fixes ------------- - Axiom annotations are no longer lost when an axiom is changed. - Fixed a problem where the create class hierarchy tool (Tools | Create class hierarchy...) did not respect the preference that new entities should be created with a particular URI. - Made qualified name rendering consistent when a user moves between ontologies in a workspace. This is done by calculating a merged prefix name to prefix map for the entire workspace that doesn't change when switching active ontologies. - Declarations are no longer copied from imported ontologies to importing ontologies on save. - Fixed a bug that allowed Protege to create empty disjoint/equivalent axioms. These axioms asserted that a class, object property, or data property was disjoint or equivalent to something, but no other entity was mentioned. A similar problem existed for same and distinct individuals. - Fixed the ontology reload feature. - Fixed a problem with the OS X application bundle format, which prevented it from loading on some platforms. A web-based version of the release notes is available on the Protege Wiki [4]. Best Regards, The Protege Team [1] http://owlapi.sourceforge.net/index.html [2] http://protegewiki.stanford.edu/wiki/OntoGraf [3] http://protege.stanford.edu/plugins/owl/dc/protege-dc.owl [4] http://protegewiki.stanford.edu/wiki/Protege_4.1_Beta_Release_Notes#Build_217_--_February_18.2C_2011 _______________________________________________ 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