Tested Protege 5.2 release candidate on Windows 7.
If you load two ontologies in the same Protégé window (in two different workspaces), OntoGraf lets you create a graph that contains classes from both ontologies. While, this could be used for some very cool diagram manipulation, for the unaware user it can be quite confusing to work with an ontology and see a graph that contains classes which are not even in that ontology. In most cases the interconnection of the different sub-graphs that belong to different ontologies happens through the owl:Thing class.
For example, in the screen shot below, we can see a graph with classes from three unrelated ontologies. When I switched from one workspace to another, OntoGraph did not reset or swapped its content (which I have expected to happen), but it kept the old content, end it let me edit it further.
The problem seems to be that OntoGraf doesn't have a workspace specific view, but rather a global view.
Could this behavior be due to a fix for #16 ? Even if that is the case, and let's say it would be desirable to let OntoGraf show classes from other workspaces, which contain ontologies that are imported in the current ontology, to me it still seems unnatural to let OntoGraf combine classes from different ontologies, loaded in separate workspaces, which do not have any owl:import relationship among themselves.
Tested Protege 5.2 release candidate on Windows 7.
If you load two ontologies in the same Protégé window (in two different workspaces), OntoGraf lets you create a graph that contains classes from both ontologies. While, this could be used for some very cool diagram manipulation, for the unaware user it can be quite confusing to work with an ontology and see a graph that contains classes which are not even in that ontology. In most cases the interconnection of the different sub-graphs that belong to different ontologies happens through the
owl:Thingclass.For example, in the screen shot below, we can see a graph with classes from three unrelated ontologies. When I switched from one workspace to another, OntoGraph did not reset or swapped its content (which I have expected to happen), but it kept the old content, end it let me edit it further.
The problem seems to be that OntoGraf doesn't have a workspace specific view, but rather a global view.
Could this behavior be due to a fix for #16 ? Even if that is the case, and let's say it would be desirable to let OntoGraf show classes from other workspaces, which contain ontologies that are imported in the current ontology, to me it still seems unnatural to let OntoGraf combine classes from different ontologies, loaded in separate workspaces, which do not have any owl:import relationship among themselves.