Search Mailing List Archives
[protege-owl] Support to remaining restrictions
martin.oconnor at stanford.edu
Thu Aug 9 09:15:31 PDT 2007
This has nothing to do with OWL restrictions - all your strings have
leading and trailing quotes.
Quoting Hrishikesh Sharma <hrishikesh.sharma at gmail.com>:
> As mentioned, I am using oneOf *in conjunction with* DataRange construct.
> Details can be seen in section 6.2 of
> I am attaching the OWL file I am using. In the 2nd SWRL rule(rule-2), adding
> the atom(right now not there)
> ... ^ hasName(?b, "Travel") ^ ...
> in the antecedent makes the rule stop firing, while corresponding knowledge
> instances/RDF data is ther in the file. My guess is it is because of missing
> support to some constraints in the bridge.
> On 8/9/07, Martin O'Connor <martin.oconnor at stanford.edu> wrote:
>> I don't understand how you are using oneOf - it takes a list of OWL
>> individuals, not a data range.
>> Quoting Hrishikesh Sharma <hrishikesh.sharma at gmail.com>:
>> > I have been using oneOf construct of OWL in conjunction with DataRange
>> > specification. However, if I use a literal which is "one of" the data
>> > ranges, the SWRL rule does not fire. E.g., the use of string literal in
>> > following gives problem in firing of rule, until that clause is removed:
>> > Employee(?a) ? hasWorkPlan(?a, ?b) ? *hasName(?b, "Travel") * ? ... ->
>> > Presumably this is happening because the SWRL Jess Bridge right now
>> > not export all restrictions to JESS. The last question in SWRL Rule
>> > Bridge FAQ refers to that. Such limitation makes my work a bit crude.
>> May I
>> > know what is the priority of fixing this limitation?
>> > Regards
>> > Hrishikesh.
More information about the protege-owl