We should implement a way of creating a project from an OWL file, using the imported ontology metadata as the project metadata and starting the import process right away.
Motivation
There are typically two use cases for the ontology importer:
1) The user wants to graphically represent part of another ontology as graphol into an existing ontology represented in a graphol project. This is similar to the import assertion in OWL, except that we want to import (possibly a subset of) the axioms in the imported ontology transforming them to graphol.
2) The user wants to migrate an existing ontology from any of the OWL formats to graphol. In this case the resulting project is a graphol representation of (possibly a subset of) the imported ontology, and all the project metadata could be derived from that.
The second scenario is not immediately supported in the current implementation.
Example Use Cases
One possible solution is to split the import into two steps, one (optional) that given an owl file creates a new project using the ontology metadata, and another that given an existing project and an owl file starts the interactive import procedure.
With this separation the first scenario can be carried out by the second step only, while the second scenario can be carried out by chaining the first and second step.
Description
We should implement a way of creating a project from an OWL file, using the imported ontology metadata as the project metadata and starting the import process right away.
Motivation
There are typically two use cases for the ontology importer: 1) The user wants to graphically represent part of another ontology as graphol into an existing ontology represented in a graphol project. This is similar to the import assertion in OWL, except that we want to import (possibly a subset of) the axioms in the imported ontology transforming them to graphol. 2) The user wants to migrate an existing ontology from any of the OWL formats to graphol. In this case the resulting project is a graphol representation of (possibly a subset of) the imported ontology, and all the project metadata could be derived from that.
The second scenario is not immediately supported in the current implementation.
Example Use Cases
One possible solution is to split the import into two steps, one (optional) that given an owl file creates a new project using the ontology metadata, and another that given an existing project and an owl file starts the interactive import procedure. With this separation the first scenario can be carried out by the second step only, while the second scenario can be carried out by chaining the first and second step.