Search Mailing List Archives
[protege-discussion] inconsistent ontology error
jiezheng at pcbi.upenn.edu
Mon Jun 27 18:52:11 PDT 2011
I check the detailed error by clicking "see Explain inconsistent
ontology" but it did not give me much information. It said the ontology
is inconsistent. OWL reasoner cannot give correct inference even it
I got import error when I ran Pellet using command line. However, I
still got ontology consistent message. I will try again tomorrow to see
whether I can reproduce the errors.
Thanks for your help.
On 6/27/2011 7:38 PM, Tania Tudorache wrote:
> Hi Jie,
> I just tried out in the latest Protege 4.1 release candidate (build
> 231) the ontology you sent with Pellet 2.1.2, and it classified
> without any problem. It took a little bit of time, though.
> I noticed that some of the imports are not always available online. I
> wonder if the inconsistent ontology error is somehow caused by this
> (although you would not expect it).
> In case you do get the inconsistent ontology error again, please go to
> the Reasoner menu -> Explain inconsistent ontology and see which
> statements are likely to cause this error.
> On 06/27/2011 04:05 PM, Jie Zheng wrote:
>> I worked on an ontology. When I ran reasoners (HermiT 1.3.4 and
>> Pellet 2.2.1) in Protege 4.1, both gave me inconsistent ontology
>> error. However, I ran Pellet 2.2.1 from command line . The result
>> shows ontology is consistent. I also tried to use latest stable
>> HermiT (jar downloaded on June 7, 2011) call from OWL API. It also
>> show no unsatisfied classes and can display the classes in the
>> inferred hierarchy. I cannot figure out why. I attached the owl for
>> Any help would be appreciated.
>> protege-discussion mailing list
>> protege-discussion at lists.stanford.edu
>> Instructions for unsubscribing:http://protege.stanford.edu/doc/faq.html#01a.03
> protege-discussion mailing list
> protege-discussion at lists.stanford.edu
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the protege-discussion