Open amedranogil opened 7 years ago
As long as it is not an editor, just a "viewer" or a "browser", then I'm pretty sure there are already third party tools. Let me come back with some links next week. (bump if I forgot in a while...)
The LogMonitor contains a (very basic) viewer of registered ontologies.
For an external repository (website), we once used a modified version of bioportal.
And there was the coding assistant tool (eclipse plugin) that connected to our bioportal and helped the developer to browse onts and include URIs in their code (but IIRC it downloaded the whole repo from bioportal, had a hierarchical text-based view and a copy-paste function for URIs).
I just wanted to mention the ideas/tools that we have/had. Obviously, much more can be done here and I'm very much open to any improvement.
some time ago I came across webvowl, which might be a replacement for the bioportal alternative, well as a solution for the ont wikis. It needs a Node.js server and apparently also some transformation of the owl file; all this could happen if we had a proper development server (including all this in the CI). This will also "force" us to better complete our ontologies with the human readable info (labels and comments) for automatic generation.
I just tested webvowl and it works quite well in a JFrame (with JavaFX WebView), so it could even be integrated in LogMonitor. JSON transformation needs to be done though. Does it really need node.js server? I'm not sure how it works if you have many ontologies. Looks like they all are shown in a drop-down menu, which works well for small numbers of ontologies..
This tool will esentially run the ontologies and make all the semantics described in java more easily available. It will enable developers to browse the concepts, each property, the restrictions of the properties, etc... of imported ontologies in their proyect, maybe even in graphical form. This tool may make it easier for us also, since this will "eliminate" the need to maintain the ontologies wiki, and have developers access the actual used semantics (it will adapt automatically to the used version) directly from the IDE.
Other desired functions would be other helper methods (like copying URIs) for aiding coding when operating with ontologies. Searching.
As another functionality (extending this plugin or a new plugin) would be good to navigate between ontologies, not just imported, but available, helping developers decide which ontologies are useful for them.
This is NOT an editor of ontologies, nor it is a substitude for the old ontology transformation tools.