Importing the classes-only variant causes an import of the full version

[GoogleCodeExporter]

Steps to reproduce:

1. Create a new ontology in Protege (4.3.0 b304)
2. Add a "Direct Import" selecting "Import an ontology contained in a document 
located on the web" with this IRI:

http://purl.obolibrary.org/obo/bfo/2014-05-03/classes-only.owl

3. Verify that there are no Object Properties
4. Save the file (RDF/XML) and close the Protege window
5. Open the ontology file again in Protege: there are many Object Properties

Cause:

In the saved file I see the following line:

<owl:imports rdf:resource="http://purl.obolibrary.org/obo/bfo.owl"/>

This is the Ontology IRI of the classes-only variant, but also of the full 
version. It seems that Protege ignores the Ontology Version IRI, stores only 
the Ontology IRI, and when the file is reopened Protege loads the main version 
instead of the variant.

Solution:

The classes only variant should have have its own Ontology IRI.

Original issue reported on code.google.com by ja...@overton.ca on 12 Jun 2014 at 3:45

[GoogleCodeExporter]

Workaround: Edit the OWL file and replace this line

<owl:imports rdf:resource="http://purl.obolibrary.org/obo/bfo.owl"/>

with this line

<owl:imports 
rdf:resource="http://purl.obolibrary.org/obo/bfo/2014-05-03/classes-only.owl"/>

In my tests, the revised import statement is maintained across Protege sessions 
and save/load operations.

Original comment by ja...@overton.ca on 12 Jun 2014 at 6:14

[GoogleCodeExporter]

The problem seems to be Protege's import wizard. Please refer to this new 
Protege tracker item:

https://github.com/protegeproject/protege/issues/57

Manually specifying the IRI is a sufficient workaround. I'm downgrading the 
priority of this BFO tracker item and closing it as "wontfix".

Original comment by ja...@overton.ca on 12 Jun 2014 at 6:49

• Changed state: WontFix
• Added labels: Priority-Medium
• Removed labels: Priority-Critical