Owlready

handling of imported ontology

Classic

List

Threaded

15 messages Options

gp handling of imported ontology – Hello, I am having difficulties working with imported ontologies. Specifically I used Protege to define some ontology which imports other ontol...

Jiba Hello, There was a bug on imported ontologies, in particular when the ontology is loaded from its filename (instead of its IRI), or when it int...

gp Bonjour Jean-Baptiste, Somehow I could not get it to work. After removing the existing installed version and installing the one I cloned from B...

Jiba Bonjour, > Would you need the ontology file for reference? Yes please. I would like to remove all bugs from Owlready! Your workaround ...

gp Hello, I had tried to contact you via email (using the Nabble forum interface) but I guess this did not work out. Anyway, using the developmen...

gp Ok my bad, I was experiencing a version conflict: somehow pip uninstall owlready2 did not do the work completely and the egg coming from the setup...

gp Hello, Time for me to revive this thread as I seem to experience the very same problem with the last version of owlready2 (0.12). After impor...

Jiba Hello, Many things have changed in 0.12 with the new quadstore; so it is possible that some old bugs are back. I tested importation on a sin...

gp Hi, You might give a try with the ontology placed in the following repo: https://github.com/Definiens/TissuePhenomicsOntology I could rep...

Avraheem Thank you. Finally works for me too.

jos lehmann Hi there is there an owlready2 web-page explaining the steps for loading/getting/writing imported ontologies? From this thread I gather th...

Jiba Hi, I would rather suggest to put all ontologies in the same directory (such as ./ontology), and then to add this directory to onto_path. If yo...

Jiba Hi, I investigated the problem. It was caused by the fact that your ontologies use "TissuePhenomicsOntology" both as a path element (...

gp Hello, I tried the dev version in different scenarios and so far I did not have any glitch w.r.t the imported ontologies. Thanks for the ver...

gp Ok I figured that, fairly weirdly, the first call to . load() results in the above mentioned error, but a successive call to the same method works...