owl imports issues

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

owl imports issues

Emilio
I'm working with modular OWL ontologies and I'm experiencing some problems
with owl:imports on Protégé (5.5.0). For instance, consider that I have an
ontology O1 which imports ontology O2. When I import O1 into a new owl file,
O2 is sometimes automatically imported, and sometimes it is not (btw, when I
manually fix the import, all binding axioms between O1 and O2 are still
there).

I don't understand where this problem comes from.

Are there documented issues with owl:imports, especially when using Protégé?
Is there any specific documentation/paper on the advantages/drawbacks of
owl:imports?

Thanks for any comment.

Best,

Emilio



--
Sent from: http://protege-project.136.n4.nabble.com/Protege-User-f4659818.html
_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user
Reply | Threaded
Open this post in threaded view
|

Re: owl imports issues

marksem
Are your files in Turtle format?  I discovered that multi-level import works if the Turtle ontologies are already in the workspace, but not if importing from files.    I don't see this problem if the files are RDF/XML format.

The full thread (including a work-around) are in this mailing list's archives, dated Oct 10, 2019.  

 -Mark  

-----Original Message-----
From: protege-user <[hidden email]> On Behalf Of Emilio
Sent: Wednesday, March 11, 2020 12:30 PM
To: [hidden email]
Subject: [protege-user] owl imports issues

I'm working with modular OWL ontologies and I'm experiencing some problems with owl:imports on Protégé (5.5.0). For instance, consider that I have an ontology O1 which imports ontology O2. When I import O1 into a new owl file,
O2 is sometimes automatically imported, and sometimes it is not (btw, when I manually fix the import, all binding axioms between O1 and O2 are still there).

I don't understand where this problem comes from.

Are there documented issues with owl:imports, especially when using Protégé?
Is there any specific documentation/paper on the advantages/drawbacks of owl:imports?

Thanks for any comment.

Best,

Emilio



--
Sent from: http://protege-project.136.n4.nabble.com/Protege-User-f4659818.html
_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user
_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user
Reply | Threaded
Open this post in threaded view
|

Re: owl imports issues

Emilio
Thanks Mark for your reply.

I had a look at the workaround mentioned on that thread but it doesn't work
for my scenario. As said, I'm working on multiple imports (btw, all
ontologies are in RDF/XML): O1 imports O2; then, I need a new ontology O3 --
with a new IRI -- importing O1 and therefore O2.

The workaround proposed in the thread would overwrite the new IRI, which I
don't want to.

Best,

Emilio



--
Sent from: http://protege-project.136.n4.nabble.com/Protege-User-f4659818.html
_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user
Reply | Threaded
Open this post in threaded view
|

Re: owl imports issues

marksem
Ah, Ok.  Next thing to suspect is the catalog-001.xml file(s).   
Have you tried closing Protege, deleting them, and then re-doing the import?  
Sometimes if the catalog-001.xml files are incorrect, Protege can't properly resolve things, and then an import doesn't work. 

Also, attaching example files to your posts definitely helps others to help you. :)  

From: protege-user <[hidden email]> on behalf of Emilio <[hidden email]>
Sent: Friday, March 13, 2020 6:09 AM
To: [hidden email] <[hidden email]>
Subject: Re: [protege-user] owl imports issues
 
Thanks Mark for your reply.

I had a look at the workaround mentioned on that thread but it doesn't work
for my scenario. As said, I'm working on multiple imports (btw, all
ontologies are in RDF/XML): O1 imports O2; then, I need a new ontology O3 --
with a new IRI -- importing O1 and therefore O2.

The workaround proposed in the thread would overwrite the new IRI, which I
don't want to.

Best,

Emilio



--
Sent from: http://protege-project.136.n4.nabble.com/Protege-User-f4659818.html
_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user

_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user