The webprotege code base
This is a bug fix release. It is backwards compatible with the WebProtégé 4.0.0 release only and should not be installed on top of any earlier or later releases.
Please note that this is a release for system administrators who are in charge of maintaining a local installation of WebProtégé. In general, end-users should use WebProtégé at https://webprotege.stanford.edu.
This is a bug fix release. It is backwards compatible with the WebProtégé 4.0.0 release only and should not be installed on top of any earlier or later releases.
Please note that this is a release for system administrators who are in charge of maintaining a local installation of WebProtégé. In general, end-users should use WebProtégé at https://webprotege.stanford.edu.
This release is a major release of WebProtégé. It contains many improvements, new features and enhancements beyond the 3.0.0 release.
Please note that this is a release for system administrators who are in charge of maintaining a local installation of WebProtégé. In general, end-users should use WebProtégé at https://webprotege.stanford.edu.
This release is not compatible with previous releases. It is not compatible with data generated by previous releases. Once you have upgraded to this release you cannot return to a previous WebProtege release. This release is NOT a drop in replacement for WebProtege 3.0.0. If you have an earlier existing installation, you MUST upgrade it by following the migration instructions. What ever you do, please back up your existing data directory first.
Please see the wiki for installation instructions.
Entities can now be tagged with colorful custom tags. Tags are set up on the settings page for a project and can be assigned automatically, based on ontology content, or manually.
Tags can be assigned based on ontology content by using complex matching criteria
Tags are displayed in the various hierarchy views. It is also possible to search for entities that have a given tag.
We have added a simple structural query capability to WebProtege. There is a new "Query" tab for this that exposes a query view. Queries can be built up using a form, and entities can be queried by the presence or absence of annotation values, hierarchical position, etc. We plan to add more querying capabilities in the future.
Simple existential graph visualization that displays a visualization of hierarchical information and relationships for the currently selected entity.
Inline display of images for annotation values that are URLs pointing to images.
Inline display of change history that is integrated into the simple entity view. There is no need for a separate Entity Changes tab anymore.
It is now possible to edit multiple annotation values at once. Editing is accomplished through specifying matching criteria and matched annotations can either be deleted, be augmented or be replaced based upon the matched values. It is possible to match values using regular expressions and then use the capturing groups from the regular expression to generate fresh or replacement values.
It is now possible to specify a default language for a project. When creating entities, they are labeled with the default language tag, which can be overridden at entity creation time. It is now possible to specify annotation property/language tag pairs that should be used for generating display names.
It is also possible to set up a secondary display language and override the primary and secondary display languages on a per-user/browser basis. Secondary display languages are shown in the various hierarchies and listed alongside the primary display name.
We have improved individual navigation and filtering capabilities. Individuals can be filtered by type, and it is possible to jump up or move down their class hierarchy to change the filter to related more general or more specific types. It is also now possible to display direct and indirect instances of the filter type.
For those that like this sort of thing, and for operating systems and browsers that support it and have it enabled then dark mode is available. For example, if macOS is set to use dark mode (macOS 10.14.4 or later) and the browser is Safari then WebProtégé will be displayed in a dark mode theme.
Simplified WebProtege installation using the Docker container solution. We have dockerized WebProtégé and distributed the image through Docker Hub. Please refer to the wiki page for more detail instruction of the installation. We'd like to thank @Azolo for his valuable contribution and previous contributions by @hammar.
This release is a major release of WebProtégé. It contains many improvements, new features and enhancements beyond the 3.0.0 release.
Please note that this is a release for system administrators who are in charge of maintaining a local installation of WebProtégé. In general, end-users should use WebProtégé at https://webprotege.stanford.edu.
This release is not compatible with previous releases. It is not compatible with data generated by previous releases. Once you have upgraded to this release you cannot return to a previous WebProtege release.
This release is not a drop in replacement for WebProtege 3.0.0. If you have an earlier existing installation, you MUST upgrade it by following the migration instructions. What ever you do, please back up your existing data directory first.
Please see the wiki for installation instructions.
Simplified WebProtege installation using the Docker container solution. We have dockerized WebProtégé and distributed the image through Docker Hub. Please refer to the wiki page for more detail instruction of the installation. We'd like to thank @Azolo for his valuable contribution and previous contributions by @hammar.
This release is a major release of WebProtégé. It contains many improvements, new features and enhancements beyond the 3.0.0 release.
Please note that this is a release for system administrators who are in charge of maintaining a local installation of WebProtégé. In general, end-users should use WebProtégé at https://webprotege.stanford.edu.
This release is not compatible with previous releases. It is not compatible with data generated by previous releases. Once you have upgraded to this release you cannot return to a previous WebProtege release. This release is a drop in replacement for WebProtege 3.0.0. If you have an earlier existing installation, you MUST upgrade it by following the migration instructions. What ever you do, please back up your existing data directory first.
Please see the wiki for installation instructions.
Entities can now be tagged with colorful custom tags. Tags are set up on the settings page for a project and can be assigned automatically, based on ontology content, or manually.
Tags can be assigned based on ontology content by using complex matching criteria
Tags are displayed in the various hierarchy views. It is also possible to search for entities that have a given tag.
We have added a simple structural query capability to WebProtege. There is a new "Query" tab for this that exposes a query view. Queries can be built up using a form, and entities can be queried by the presence or absence of annotation values, hierarchical position, etc. We plan to add more querying capabilities in the future.
Simple existential graph visualization that displays a visualization of hierarchical information and relationships for the currently selected entity.
Inline display of images for annotation values that are URLs pointing to images.
Inline display of change history that is integrated into the simple entity view. There is no need for a separate Entity Changes tab anymore.
It is now possible to edit multiple annotation values at once. Editing is accomplished through specifying matching criteria and matched annotations can either be deleted, be augmented or be replaced based upon the matched values. It is possible to match values using regular expressions and then use the capturing groups from the regular expression to generate fresh or replacement values.
It is now possible to specify a default language for a project. When creating entities, they are labeled with the default language tag, which can be overridden at entity creation time. It is now possible to specify annotation property/language tag pairs that should be used for generating display names.
It is also possible to set up a secondary display language and override the primary and secondary display languages on a per-user/browser basis. Secondary display languages are shown in the various hierarchies and listed alongside the primary display name.
We have improved individual navigation and filtering capabilities. Individuals can be filtered by type, and it is possible to jump up or move down their class hierarchy to change the filter to related more general or more specific types. It is also now possible to display direct and indirect instances of the filter type.
For those that like this sort of thing, and for operating systems and browsers that support it and have it enabled then dark mode is available. For example, if macOS is set to use dark mode (macOS 10.14.4 or later) and the browser is Safari then WebProtégé will be displayed in a dark mode theme.
This release is a major release of WebProtégé. It contains many improvements, new features and enhancements.
Please note that this is a release for system administrators who are in change of maintaining a local installation of WebProtégé. In general, end-users should use WebProtégé at https://webprotege.stanford.edu.
This release is not compatible with previous releases. It is not compatible with data generated by previous releases. If you have an existing installation, you MUST upgrade it by following the migration instructions. What ever you do, please back up your existing data directory first.
Please see the wiki for installation instructions.
Most of the WebProtégé user interface has been reimplemented from the ground up. This has enabled us to provide a cleaner, more modern look & feel and more flexible user-interface for WebProtégé.
Replaced the class, object, data and annotation property hierarchy displays so that they are more reliable, robust and more uniform over the different types of hierarchy.
Split the object, data and annotation property hierarchies out into separate trees that can be reached by tabs.
Added context menus on the class, object property, data property and annotation hierarchy displays with short cuts for creating entities and actions to prune (see below) the displayed hierarchies.
Added new entity search functionality. In addition to the class hierarchy, the object property, data property and annotation property hierarchies can now be search.
Added "watch" functionality to the object, data and annotation property hierarchies.
Added the ability to temporarily prune branches from the view in the various hierarchies (see screenshot below). This makes it easier to focus on a specific entity at a specific place in the hierarchy and view/edit its children.
Improved the default style for email messages that are sent out to users for notifications of project changes and posted comments (see below).
Notification emails now contain links to the relevant project, subject entity and any mentioned entities (see example below).
Notification emails for posted comments are now threaded for email clients that support this.
/etc/webprotege/webprotege.properties
and /etc/webprotege/mail.properties
.This release updates parts of the WebProtege UI and fixes numerous bugs.
Please note that this is a release for system administrators who are in change of maintaining a local installation of WebProtege.
It also includes a huge number of under the hood changes and code improvements that are too numerous to mention - see https://github.com/protegeproject/webprotege/compare/v2.5.0...v2.6.0 for a complete description of these.
This release adds several new features and fixes various bugs.
foaf:Person
when creating a class and the foaf:
prefix name will be expanded to the foaf prefix. (#131)<http://semanticweb.org/ontologies/A>
when creating a class with cause the class to have the IRI http://semanticweb.org/ontologies/A
. (#100)This is a maintenance release which fixes a number of bugs:
The main new feature in this release is the ability to customize IRI prefixes and suffixes for new entities (#1 #7). There are three built in options:
In addition to this, the following issues have been fixed: