Search Mailing List Archives

Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-owl] Import Problem and Active Ontology

Martin O'Connor martin.oconnor at
Sat Aug 4 09:58:05 PDT 2007

The Protégé 3.3 release has broken import functionality:

Protégé 3.3

Attention Protégé-OWL Users: We have discovered a serious regression in the
import functionality in the 3.3 release. We are planning to do a 3.3.1 patch
release in early August (after we are back from the Protégé Conference).
Until then, we are recommending that you revert to the last Protégé 3.3 beta
build (Protégé 3.3 beta, build 414), or the last major release of Protégé
(Protégé 3.2.1).


-----Original Message-----
From: protege-owl-bounces at
[mailto:protege-owl-bounces at] On Behalf Of Jean-Paul
Sent: Saturday, August 04, 2007 9:53 AM
To: protege-owl at
Subject: [protege-owl] Import Problem and Active Ontology

I have tried to build an ontology on top of an existing one. I use Protégé
3.3 and OWL.
My ontology is called ESOA and the imported one SOA.

Whenever I tried to import SOA, Protégé would dim the buttons on the
Ontology Browser of the Metadata tab and switch to the imported ESOA

When saving, this lead systematically to a Protege2Jena error - maybe
because the base tag points to ESOA while the default namespace is still

Eventually, I used an editor to insert the line
    <owl:imports rdf:resource=""/>
which displayed as I was expecting it in Protégé, namely in a SOA followed
by ESOA hierarchy managed by the entries (read-only) in the repository

Why was it not possible through a simple import?

- JP

More information about the protege-owl mailing list