Hi Martin,
Thank you for the response.
What I would actually like to do (given my simplified example) is
after using Pellet to reason over the KB and classify the instances
from 'Town' to also belong to the class 'Fast-Community' (based on the
property of class'Person'), which it does, I wish to then infer
something using the SWRLtab.
I would like to set SWRL inference rules using the 'Fast-Community'
class. However, the SWRL/Jess does not seem to see the inferred
instances under the new class. If I change the rule to use the 'Town'
class it works (as the instances are asserted there).
Is this because the Jess back end doesn't recognise OWL axioms (e.g. hasValue)?
Regards
Jedda
On Thu, Jul 2, 2009 at 12:02 PM, Jedda Miles<
[hidden email]> wrote:
> Hello
>
> I have a question that is a follow-on from my previous (below). Now
> that the individuals are correctly inferred I have tried to run SWRL
> rules over the knowledge base and they don't acknowledge the inferred
> instances.
>
> The axioms used by the reasoning engine were suggested by Thomas in my
> recent cry for help:
> Class Fast-Community <=> Town and (homeOf someValuesFrom (Person and
> (dtP-speed hasValue fast)))
>
> I have been over previous posts and some mention the problem and that
> it was in future works to be able to use inferred knowledge in SWRL
> rules or SQWRL queries. Is this going to be possible in Protege 3.4? I
> ask as I would like to be able to classify instances to various
> classes and then extract the inferred instances
>
> There was also a post from Martin referring to the Jess back end and
> not recognising OWL axioms (e.g. hasValue):
>
> [1]
http://protege.cim3.net/cgi-bin/wiki.pl?SWRLRuleEngineBridgeFAQ#nid6QL>
> Is there any way to use SWRL rules to recognise inferred instances
> after reasoning?
>
> Thank you
> Jedda
>
_______________________________________________
protege-owl mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-owlInstructions for unsubscribing:
http://protege.stanford.edu/doc/faq.html#01a.03
