Ontograf protege is not showing individuals in case of joined ontology

0
votes

First of all, it has been working for the last 4 months, but now when I need to write the report it stopped.

When i have one ontology with instances, the Ontograf shows the individuals, but when i create a new ontology and load another ontology, the ontograf doesn't show the individuals from the other ontology.

i tried repeating everything from scratch, i tried to make each ontology just one class and one individuals, but i sitll have the problem, i installed protege Protege-5.0.0-beta-24 and Protege-5.0.0-beta-23 and Protege-5.0.0-beta-21 and Protege-5.0.0-beta-17 but still have the same problem (in the past i was working with Protege-5.0.0-beta-23 and it was working)

just yesterday everythign was fine, today nothing is working,

Update

I uploaded a minimum example to show you the problem:

the file contains three ontologies, the first.ttl has one class and one instances, the second.ttl has one class, the third join them together and make the class of the first as a sub class of the second. in this joined ontology i can't see the instances that is in first.ttl using ontograf

http://www.mediafire.com/download/6rr3xwb196mxab1/StackoverflowMinimumExample.zip

1
javasparqlsemantic-webowlprotege
please help, i worked hard for the problem and now i am writing the report, if this doesn't work, it is like i didn't work. appreciate it guys - Ania David
This is funny, nobody helped you after 1h on Friday evening...and moreover, do you know that there is a Protege mailing list? - UninformedUser
Maybe Ontograf does not consider imported axioms? It's also not clear how you import the other ontology. Is it shown correctly in Protege? - UninformedUser
Moreover, this is definitely the wrong platform as you're asking nothing code related but a tool specific question. And last but not least, why do you tag all your questions with sparql? I don't see here any relationship to nor usage of SPARQL. - UninformedUser
So what did change between the time it was working and now? Can't you just roll back to the older version? - Joshua Taylor

1 Answers

0
votes

It is a bug in protege and this is the ticket to try to solve it

https://github.com/protegeproject/ontograf/issues/13