Search Mailing List Archives
[protege-owl] Bug in DefaultSWRLImp RuleGroup-mechanism
milo at informatik.uni-kiel.de
Mon Feb 2 04:09:20 PST 2009
thank you again for the hint. It helped me a lot. And after finding an
earlier post of you about this topic containing some snippets of code, I
was able to resolve the problem.
DefaultSWRLImp rule = (DefaultSWRLImp) iter.next();
OWLNamedClass ruleGroupClass =
OWLIndividual ruleGroupIndividual = (OWLIndividual)
System.err.println("getRuleGroupNames: "+ rule.getRuleGroupNames());
Martin O'Connor schrieb:
> I have not documented the rule group functionality on the Wiki because
> it was developed for internal use and is not all that elegant. The name
> of the rule group has to be the name of an individual of type
> I hope to clean this up in the next few months.
> Michael Lodemann wrote:
>> perhaps not a bug ... the boolean return code of
>> addRuleGroup("testGroup") is "false", but why can a rule-object decide
>> to reject a group assignment?
>> Is there a further documentation / example about rule-grouping-mechanism?
>> Michael Lodemann schrieb:
>>> Hmm .. no screenshot? But now!
>>> Michael Lodemann schrieb:
>>>> I possibly found a bug in the DefaultSWRLImp-implementation:
>>>> When adding a RuleGroup with addRuleGroup("testGroup") to a rule the
>>>> method getRuleGroupNames().size() is 0.
>>>> Take a look at the self-explaining screenshot. Can someone verify
>>>> this, or do I have an error in my code and thoughts?
More information about the protege-owl