![]() ![]() Fixed a typo in the DL metrics view ( #20).Fixed a bug in the auto-update functionality that caused exceptions when encountering plug-ins with invalid version numbers ( #18).Previously, Protege requested both direct and indirect inferred individuals, which caused performance issues with larger ontologies ( #15). Selecting classes in the class hierarchy will only request directly inferred individuals from the reasoner.The inferred object property hierarchy no longer displays owl:bottomObjectProperty as a leaf of every node ( #9).Added an option to toggle rendering of annotation datatypes in the Annotations view (accessible via View -> Display datatypes on annotation values).Previously, it was necessary to click the symbol to bring up a separate dialog for viewing inline axiom annotations ( #50). Added the ability to view axiom annotations inline (accessible via View -> Display axiom annotations inline).Definition annotation properties are now listed after label annotation properties, making the Annotations view more user-friendly for the bio-ontology community ( #47).Renamed labels in the DL Query tab plug-in to be clearer and more standard ( #1).The Active Ontology tab now shows ontology metrics by default ( #46).Auto-update only checks for updates once per day, rather than checking for updates every time Protege launches ( #45).Exporting DisjointClasses axioms is no longer enabled by default, as this can be an expensive operation ( #43).Entering a number into the OWLConstantEditor now parses the value and chooses the correct datatype if no datatype was specified ( #42).The UI no longer allows specification of owl:real as the type for a literal ( #37).The Individuals tab now filters the list of individuals displayed based on the selected class in the class hierarchy ( #1).The search functionality has been significantly improved to search annotation values, display names, entity IRIs, and logical axioms (previously only display name was searched).Upgraded to the latest version of the OWL API (v3.5.0).Moved the Protege Desktop build system to Maven to standardize the build process.Moved the Protege Desktop source code to GitHub to allow for easier collaboration with developers outside of Stanford.This option caused the run scripts to fail on systems that only have a JRE installed vs. Removed the Java "-server" option from the Protege run scripts.Release notes for this build are available on github The contents of the release notes section describe changes relative to Protege 4.3. Sign up for the list at the Protege website. Contact us with your questions on the Protege Developer Support mailing list.View example code for developing tab, view, and menu plug-ins.Learn how to build a distribution from source.Access the source code, file issues, and submit pull requests on GitHub.Join the Protege community on Facebook and Twitter.Submit feedback, questions, and/or bug reports on the Protege User Support mailing list.Download and installation instructions.All newer Protege release notes have been moved to github. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |