Search Mailing List Archives
[protege-owl] Different behavior in Protege 3x and 4x
tredmond at stanford.edu
Tue Jan 26 11:50:06 PST 2010
I had to do a little digging to remember the status on this. This is a
known bug in the OWL api and in fact there is currently a query on the
OWL api mailing list about this very issue. The problem is not fixed
in the latest v2 version of the OWL API.
I believe that this is fixed in Protege 4.1 and in the v3 version of the
OWL API but there is a bit of work to do in that arena with editing
rules. I was planning on putting some time in today to fix the Protege
4.1 editing of rules.
Things are a bit awkward at the moment because we are between versions
of Protege. I am working on fixing this soon.
On Sun, 2010-01-24 at 17:12 +0530, swamy wrote:
> Hi All,
> I have sample ontology to find near by restaurants.
> I have made this ontology using Protege 3x and applied the following
> rule too.
> Place(?p) ∧ Category(Chinese_Restaurants) ∧ hasCategory(?p,
> Chinese_Restaurants) ∧ Selected(?s) → hasSelected(?s, ?p)
> And when I am trying the same in Protege 4 or (Pellet + OWL API), I am
> getting the following error in the rule part.
> In Protege 4x - IllegalStateException: Node is null. Attempting to get
> node for Chinese_Restaurants
> In Pellet & OWL API - Error: Node is null. Attempting to get node for
> Here Chinese_Restaurants is individual of Category class.
> Please help me in explain this difference.
> Thank you in advance.
> protege-owl mailing list
> protege-owl at lists.stanford.edu
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
More information about the protege-owl