|
View:
New views
10 Messages
—
Rating Filter:
Alert me
|
|
|
swrlb:notEqualHi, Is there a way to string-wise compare an owl individual with
a datatype value using SWRL rules? I have an individual, say ind1, and I have a
datatype value, say So, I wrote the following rule, where hasID and hasName are
datatype properties Car(?x) ^ Manufacturer(?y) ^ hasManufacturer(?x, ?y) ^ hasID(?x,
?z) ^ swrlb:notEqual(?y, ?z) → hasName(?x, ?z) But I get a problem with the swrlb:notEqual builtin… the
following is the error I get… Exception importing SWRL rules and OWL
knowledge:
edu.stanford.smi.protegex.owl.swrl.bridge.jess.exceptions.SWRLJessBridgeException:
Jess reported an error in routine invokeSWRLBuiltIn while
executing (invokeSWRLBuiltIn "Rule-2" "swrlb:notEqual" 0 ?y
?z) while
executing rule LHS (Node2) while
executing rule LHS (Node2) while
executing rule LHS (Node2) while
executing rule LHS (Node2) while
executing rule LHS (MTELN) while
executing rule LHS (TECT) while
executing (assert (MAIN::hasActualTagID_String Tag_2
"urn-epc-tag-gid-96-1.2.45678")). Message: error invoking built-in
from Jess: exception thrown by built-in Program text: ( assert (
hasActualTagID_String Tag_2 "urn-epc-tag-gid-96-1.2.45678" ) )
at line 1. What could be the reason? I’m using Protégé 3.4 beta build
110… I know it’s an old build, but the latest builds are always giving some
problem or the other, so I thought it’s better to use a stable one as long as I
don’t get into troubles… can someone suggest the latest stable build, along with
swrl updates! Cheers, Raj _______________________________________________ protege-owl mailing list protege-owl@... https://mailman.stanford.edu/mailman/listinfo/protege-owl Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 |
|
|
Re: swrlb:notEqualThis type of reasoning is outside both OWL and SWRL. swrlb:notEqual applies to datatype values only. SWRL's sameAs and different from atoms can be used to compare individuals. However, comparing individuals or classes or properties with datatype values is beyond SWRL's semantics. You can use the custom abox:hasURI built-in in association with core string built-ins to perform the types of comparisons but should not be used to make deductions. Martin Quoting "Mudunuri, Vekata Rajashekar Varma" <Raj.Mudunuri@...>: > Hi, > > > > Is there a way to string-wise compare an owl individual with a > datatype value using SWRL rules? I have an individual, say ind1, and > I have a datatype value, say ind:1, and I want to compare using > swrl rules whether the individual of a class and the datatype value > associated to this class via a datatype property, are literally the > same? > > > > So, I wrote the following rule, where hasID and hasName are datatype > properties > > > > Car(?x) ^ Manufacturer(?y) ^ hasManufacturer(?x, ?y) ^ hasID(?x, ?z) > ^ swrlb:notEqual(?y, ?z) ? hasName(?x, ?z) > > > > But I get a problem with the swrlb:notEqual builtin? the following > is the error I get? > > > > Exception importing SWRL rules and OWL knowledge: > edu.stanford.smi.protegex.owl.swrl.bridge.jess.exceptions.SWRLJessBridgeException: Jess reported an error in routine > invokeSWRLBuiltIn > > while executing (invokeSWRLBuiltIn "Rule-2" > "swrlb:notEqual" 0 ?y ?z) > > while executing rule LHS (Node2) > > while executing rule LHS (Node2) > > while executing rule LHS (Node2) > > while executing rule LHS (Node2) > > while executing rule LHS (MTELN) > > while executing rule LHS (TECT) > > while executing (assert (MAIN::hasActualTagID_String > Tag_2 "urn-epc-tag-gid-96-1.2.45678")). > > Message: error invoking built-in from Jess: exception thrown by > built-in 'swrlb:notEqual' in rule 'Rule-2': expecting ordered type, > got individual with name 'urn-epc-tag-gid-96-1.2.98765' for > (0-offset) argument #0. > > Program text: ( assert ( hasActualTagID_String Tag_2 > "urn-epc-tag-gid-96-1.2.45678" ) ) at line 1. > > > > > > What could be the reason? I?m using Protégé 3.4 beta build 110? I > know it?s an old build, but the latest builds are always giving some > problem or the other, so I thought it?s better to use a stable one > as long as I don?t get into troubles? can someone suggest the latest > stable build, along with swrl updates! > > > > Cheers, > > Raj > > > > _______________________________________________ protege-owl mailing list protege-owl@... https://mailman.stanford.edu/mailman/listinfo/protege-owl Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 |
|
|
Re: swrlb:notEqualThanks Martin...
my problem would be solved if Protégé allows characters like : and ; for the names of individuals... I have individuals where they should be named for example like urn:epc:tag:gid-96:1.2.98765 but the problem is that Protégé does not accept the character : while naming the individuals... it is important for us to name them as such so that further processing is done based on these individuals... Btw, I tried to use swrlb:sameAs but the SWRL editor does not allow it... neither swrl:sameAs... how do we use (syntax) these swrl sameAs and differentFrom atoms, to do the owl individuals comparasion? Cheers, Raj -----Original Message----- From: protege-owl-bounces@... [mailto:protege-owl-bounces@...] On Behalf Of Martin O'Connor Sent: Mittwoch, 9. Juli 2008 20:47 To: protege-owl@... Subject: Re: [protege-owl] swrlb:notEqual This type of reasoning is outside both OWL and SWRL. swrlb:notEqual applies to datatype values only. SWRL's sameAs and different from atoms can be used to compare individuals. However, comparing individuals or classes or properties with datatype values is beyond SWRL's semantics. You can use the custom abox:hasURI built-in in association with core string built-ins to perform the types of comparisons but should not be used to make deductions. Martin Quoting "Mudunuri, Vekata Rajashekar Varma" <Raj.Mudunuri@...>: > Hi, > > > > Is there a way to string-wise compare an owl individual with a > datatype value using SWRL rules? I have an individual, say ind1, and > I have a datatype value, say ind:1, and I want to compare using > swrl rules whether the individual of a class and the datatype value > associated to this class via a datatype property, are literally the > same? > > > > So, I wrote the following rule, where hasID and hasName are datatype > properties > > > > Car(?x) ^ Manufacturer(?y) ^ hasManufacturer(?x, ?y) ^ hasID(?x, ?z) > ^ swrlb:notEqual(?y, ?z) ? hasName(?x, ?z) > > > > But I get a problem with the swrlb:notEqual builtin? the following > is the error I get? > > > > Exception importing SWRL rules and OWL knowledge: > edu.stanford.smi.protegex.owl.swrl.bridge.jess.exceptions.SWRLJessBridgeException: Jess reported an error in routine > invokeSWRLBuiltIn > > while executing (invokeSWRLBuiltIn "Rule-2" > "swrlb:notEqual" 0 ?y ?z) > > while executing rule LHS (Node2) > > while executing rule LHS (Node2) > > while executing rule LHS (Node2) > > while executing rule LHS (Node2) > > while executing rule LHS (MTELN) > > while executing rule LHS (TECT) > > while executing (assert (MAIN::hasActualTagID_String > Tag_2 "urn-epc-tag-gid-96-1.2.45678")). > > Message: error invoking built-in from Jess: exception thrown by > built-in 'swrlb:notEqual' in rule 'Rule-2': expecting ordered type, > got individual with name 'urn-epc-tag-gid-96-1.2.98765' for > (0-offset) argument #0. > > Program text: ( assert ( hasActualTagID_String Tag_2 > "urn-epc-tag-gid-96-1.2.45678" ) ) at line 1. > > > > > > What could be the reason? I?m using Protégé 3.4 beta build 110? I > know it?s an old build, but the latest builds are always giving some > problem or the other, so I thought it?s better to use a stable one > as long as I don?t get into troubles? can someone suggest the latest > stable build, along with swrl updates! > > > > Cheers, > > Raj > > > > _______________________________________________ protege-owl mailing list protege-owl@... https://mailman.stanford.edu/mailman/listinfo/protege-owl Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 _______________________________________________ protege-owl mailing list protege-owl@... https://mailman.stanford.edu/mailman/listinfo/protege-owl Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 |
|
|
Re: swrlb:notEqualRaj,
I'm only replying to the individuals name part. Protege 3.4 b504 allows you to have inviduals names such as "urn:epc:tag:gid-96:1.2.98765". And the default parser for restrictions works with the urn-s. I am not sure whether the SWRL parser allows urn-s. If it doesn't, it shouldn't be hard to fix. I suggest that you upgrade to the latest 3.4 beta. Tania Mudunuri, Vekata Rajashekar Varma wrote: > Thanks Martin... > > my problem would be solved if Protégé allows characters like : and ; for the names of individuals... I have individuals where they should be named for example like urn:epc:tag:gid-96:1.2.98765 but the problem is that Protégé does not accept the character : while naming the individuals... it is important for us to name them as such so that further processing is done based on these individuals... > > Btw, I tried to use swrlb:sameAs but the SWRL editor does not allow it... neither swrl:sameAs... how do we use (syntax) these swrl sameAs and differentFrom atoms, to do the owl individuals comparasion? > > Cheers, > Raj > > > > -----Original Message----- > From: protege-owl-bounces@... [mailto:protege-owl-bounces@...] On Behalf Of Martin O'Connor > Sent: Mittwoch, 9. Juli 2008 20:47 > To: protege-owl@... > Subject: Re: [protege-owl] swrlb:notEqual > > > > This type of reasoning is outside both OWL and SWRL. swrlb:notEqual > applies to datatype values only. SWRL's sameAs and different from > atoms can be used to compare individuals. However, comparing > individuals or classes or properties with datatype values is beyond > SWRL's semantics. You can use the custom abox:hasURI built-in in > association with core string built-ins to perform the types of > comparisons but should not be used to make deductions. > > Martin > > Quoting "Mudunuri, Vekata Rajashekar Varma" > <Raj.Mudunuri@...>: > > >> Hi, >> >> >> >> Is there a way to string-wise compare an owl individual with a >> datatype value using SWRL rules? I have an individual, say ind1, and >> I have a datatype value, say ind:1, and I want to compare using >> swrl rules whether the individual of a class and the datatype value >> associated to this class via a datatype property, are literally the >> same? >> >> >> >> So, I wrote the following rule, where hasID and hasName are datatype >> properties >> >> >> >> Car(?x) ^ Manufacturer(?y) ^ hasManufacturer(?x, ?y) ^ hasID(?x, ?z) >> ^ swrlb:notEqual(?y, ?z) ? hasName(?x, ?z) >> >> >> >> But I get a problem with the swrlb:notEqual builtin? the following >> is the error I get? >> >> >> >> Exception importing SWRL rules and OWL knowledge: >> edu.stanford.smi.protegex.owl.swrl.bridge.jess.exceptions.SWRLJessBridgeException: Jess reported an error in routine >> invokeSWRLBuiltIn >> >> while executing (invokeSWRLBuiltIn "Rule-2" >> "swrlb:notEqual" 0 ?y ?z) >> >> while executing rule LHS (Node2) >> >> while executing rule LHS (Node2) >> >> while executing rule LHS (Node2) >> >> while executing rule LHS (Node2) >> >> while executing rule LHS (MTELN) >> >> while executing rule LHS (TECT) >> >> while executing (assert (MAIN::hasActualTagID_String >> Tag_2 "urn-epc-tag-gid-96-1.2.45678")). >> >> Message: error invoking built-in from Jess: exception thrown by >> built-in 'swrlb:notEqual' in rule 'Rule-2': expecting ordered type, >> got individual with name 'urn-epc-tag-gid-96-1.2.98765' for >> (0-offset) argument #0. >> >> Program text: ( assert ( hasActualTagID_String Tag_2 >> "urn-epc-tag-gid-96-1.2.45678" ) ) at line 1. >> >> >> >> >> >> What could be the reason? I?m using Protégé 3.4 beta build 110? I >> know it?s an old build, but the latest builds are always giving some >> problem or the other, so I thought it?s better to use a stable one >> as long as I don?t get into troubles? can someone suggest the latest >> stable build, along with swrl updates! >> >> >> >> Cheers, >> >> Raj >> >> >> >> >> > > > _______________________________________________ > protege-owl mailing list > protege-owl@... > https://mailman.stanford.edu/mailman/listinfo/protege-owl > > Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 > _______________________________________________ > protege-owl mailing list > protege-owl@... > https://mailman.stanford.edu/mailman/listinfo/protege-owl > > Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 > > _______________________________________________ protege-owl mailing list protege-owl@... https://mailman.stanford.edu/mailman/listinfo/protege-owl Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 |
|
|
Re: swrlb:notEqualsameAs and differentFrom are not built-ins - they are part of the SWRL
language: protege.cim3.net/cgi-bin/wiki.pl?*SWRL**Language*FAQ Martin Tania Tudorache wrote: >Raj, > >I'm only replying to the individuals name part. Protege 3.4 b504 allows >you to have inviduals names such as "urn:epc:tag:gid-96:1.2.98765". >And the default parser for restrictions works with the urn-s. > >I am not sure whether the SWRL parser allows urn-s. If it doesn't, it >shouldn't be hard to fix. > >I suggest that you upgrade to the latest 3.4 beta. > >Tania > > >Mudunuri, Vekata Rajashekar Varma wrote: > > >>Thanks Martin... >> >>my problem would be solved if Protégé allows characters like : and ; for the names of individuals... I have individuals where they should be named for example like urn:epc:tag:gid-96:1.2.98765 but the problem is that Protégé does not accept the character : while naming the individuals... it is important for us to name them as such so that further processing is done based on these individuals... >> >>Btw, I tried to use swrlb:sameAs but the SWRL editor does not allow it... neither swrl:sameAs... how do we use (syntax) these swrl sameAs and differentFrom atoms, to do the owl individuals comparasion? >> >>Cheers, >>Raj >> >> >> >>-----Original Message----- >>From: protege-owl-bounces@... [mailto:protege-owl-bounces@...] On Behalf Of Martin O'Connor >>Sent: Mittwoch, 9. Juli 2008 20:47 >>To: protege-owl@... >>Subject: Re: [protege-owl] swrlb:notEqual >> >> >> >>This type of reasoning is outside both OWL and SWRL. swrlb:notEqual >>applies to datatype values only. SWRL's sameAs and different from >>atoms can be used to compare individuals. However, comparing >>individuals or classes or properties with datatype values is beyond >>SWRL's semantics. You can use the custom abox:hasURI built-in in >>association with core string built-ins to perform the types of >>comparisons but should not be used to make deductions. >> >>Martin >> >>Quoting "Mudunuri, Vekata Rajashekar Varma" >><Raj.Mudunuri@...>: >> >> >> >> >>>Hi, >>> >>> >>> >>>Is there a way to string-wise compare an owl individual with a >>>datatype value using SWRL rules? I have an individual, say ind1, and >>> I have a datatype value, say ind:1, and I want to compare using >>>swrl rules whether the individual of a class and the datatype value >>> associated to this class via a datatype property, are literally the >>> same? >>> >>> >>> >>>So, I wrote the following rule, where hasID and hasName are datatype >>> properties >>> >>> >>> >>>Car(?x) ^ Manufacturer(?y) ^ hasManufacturer(?x, ?y) ^ hasID(?x, ?z) >>> ^ swrlb:notEqual(?y, ?z) ? hasName(?x, ?z) >>> >>> >>> >>>But I get a problem with the swrlb:notEqual builtin? the following >>>is the error I get? >>> >>> >>> >>>Exception importing SWRL rules and OWL knowledge: >>>edu.stanford.smi.protegex.owl.swrl.bridge.jess.exceptions.SWRLJessBridgeException: Jess reported an error in routine >>>invokeSWRLBuiltIn >>> >>> while executing (invokeSWRLBuiltIn "Rule-2" >>>"swrlb:notEqual" 0 ?y ?z) >>> >>> while executing rule LHS (Node2) >>> >>> while executing rule LHS (Node2) >>> >>> while executing rule LHS (Node2) >>> >>> while executing rule LHS (Node2) >>> >>> while executing rule LHS (MTELN) >>> >>> while executing rule LHS (TECT) >>> >>> while executing (assert (MAIN::hasActualTagID_String >>>Tag_2 "urn-epc-tag-gid-96-1.2.45678")). >>> >>> Message: error invoking built-in from Jess: exception thrown by >>>built-in 'swrlb:notEqual' in rule 'Rule-2': expecting ordered type, >>>got individual with name 'urn-epc-tag-gid-96-1.2.98765' for >>>(0-offset) argument #0. >>> >>> Program text: ( assert ( hasActualTagID_String Tag_2 >>>"urn-epc-tag-gid-96-1.2.45678" ) ) at line 1. >>> >>> >>> >>> >>> >>>What could be the reason? I?m using Protégé 3.4 beta build 110? I >>>know it?s an old build, but the latest builds are always giving some >>> problem or the other, so I thought it?s better to use a stable one >>>as long as I don?t get into troubles? can someone suggest the latest >>> stable build, along with swrl updates! >>> >>> >>> >>>Cheers, >>> >>>Raj >>> >>> >>> >>> >>> >>> >>> >>_______________________________________________ >>protege-owl mailing list >>protege-owl@... >>https://mailman.stanford.edu/mailman/listinfo/protege-owl >> >>Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 >>_______________________________________________ >>protege-owl mailing list >>protege-owl@... >>https://mailman.stanford.edu/mailman/listinfo/protege-owl >> >>Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 >> >> >> >> > >_______________________________________________ >protege-owl mailing list >protege-owl@... >https://mailman.stanford.edu/mailman/listinfo/protege-owl > >Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 > > > _______________________________________________ protege-owl mailing list protege-owl@... https://mailman.stanford.edu/mailman/listinfo/protege-owl Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 |
|
|
Re: swrlb:notEqualCorrected URL:
protege.cim3.net/cgi-bin/wiki.pl?SWRLLanguageFAQ Martin Martin O'Connor wrote: >sameAs and differentFrom are not built-ins - they are part of the SWRL >language: > >protege.cim3.net/cgi-bin/wiki.pl?*SWRL**Language*FAQ > >Martin > >Tania Tudorache wrote: > > > >>Raj, >> >>I'm only replying to the individuals name part. Protege 3.4 b504 allows >>you to have inviduals names such as "urn:epc:tag:gid-96:1.2.98765". >>And the default parser for restrictions works with the urn-s. >> >>I am not sure whether the SWRL parser allows urn-s. If it doesn't, it >>shouldn't be hard to fix. >> >>I suggest that you upgrade to the latest 3.4 beta. >> >>Tania >> >> >>Mudunuri, Vekata Rajashekar Varma wrote: >> >> >> >> >>>Thanks Martin... >>> >>>my problem would be solved if Protégé allows characters like : and ; for the names of individuals... I have individuals where they should be named for example like urn:epc:tag:gid-96:1.2.98765 but the problem is that Protégé does not accept the character : while naming the individuals... it is important for us to name them as such so that further processing is done based on these individuals... >>> >>>Btw, I tried to use swrlb:sameAs but the SWRL editor does not allow it... neither swrl:sameAs... how do we use (syntax) these swrl sameAs and differentFrom atoms, to do the owl individuals comparasion? >>> >>>Cheers, >>>Raj >>> >>> >>> >>>-----Original Message----- >>>From: protege-owl-bounces@... [mailto:protege-owl-bounces@...] On Behalf Of Martin O'Connor >>>Sent: Mittwoch, 9. Juli 2008 20:47 >>>To: protege-owl@... >>>Subject: Re: [protege-owl] swrlb:notEqual >>> >>> >>> >>>This type of reasoning is outside both OWL and SWRL. swrlb:notEqual >>>applies to datatype values only. SWRL's sameAs and different from >>>atoms can be used to compare individuals. However, comparing >>>individuals or classes or properties with datatype values is beyond >>>SWRL's semantics. You can use the custom abox:hasURI built-in in >>>association with core string built-ins to perform the types of >>>comparisons but should not be used to make deductions. >>> >>>Martin >>> >>>Quoting "Mudunuri, Vekata Rajashekar Varma" >>><Raj.Mudunuri@...>: >>> >>> >>> >>> >>> >>> >>>>Hi, >>>> >>>> >>>> >>>>Is there a way to string-wise compare an owl individual with a >>>>datatype value using SWRL rules? I have an individual, say ind1, and >>>>I have a datatype value, say ind:1, and I want to compare using >>>>swrl rules whether the individual of a class and the datatype value >>>>associated to this class via a datatype property, are literally the >>>>same? >>>> >>>> >>>> >>>>So, I wrote the following rule, where hasID and hasName are datatype >>>>properties >>>> >>>> >>>> >>>>Car(?x) ^ Manufacturer(?y) ^ hasManufacturer(?x, ?y) ^ hasID(?x, ?z) >>>>^ swrlb:notEqual(?y, ?z) ? hasName(?x, ?z) >>>> >>>> >>>> >>>>But I get a problem with the swrlb:notEqual builtin? the following >>>>is the error I get? >>>> >>>> >>>> >>>>Exception importing SWRL rules and OWL knowledge: >>>>edu.stanford.smi.protegex.owl.swrl.bridge.jess.exceptions.SWRLJessBridgeException: Jess reported an error in routine >>>>invokeSWRLBuiltIn >>>> >>>> while executing (invokeSWRLBuiltIn "Rule-2" >>>>"swrlb:notEqual" 0 ?y ?z) >>>> >>>> while executing rule LHS (Node2) >>>> >>>> while executing rule LHS (Node2) >>>> >>>> while executing rule LHS (Node2) >>>> >>>> while executing rule LHS (Node2) >>>> >>>> while executing rule LHS (MTELN) >>>> >>>> while executing rule LHS (TECT) >>>> >>>> while executing (assert (MAIN::hasActualTagID_String >>>>Tag_2 "urn-epc-tag-gid-96-1.2.45678")). >>>> >>>> Message: error invoking built-in from Jess: exception thrown by >>>>built-in 'swrlb:notEqual' in rule 'Rule-2': expecting ordered type, >>>>got individual with name 'urn-epc-tag-gid-96-1.2.98765' for >>>>(0-offset) argument #0. >>>> >>>> Program text: ( assert ( hasActualTagID_String Tag_2 >>>>"urn-epc-tag-gid-96-1.2.45678" ) ) at line 1. >>>> >>>> >>>> >>>> >>>> >>>>What could be the reason? I?m using Protégé 3.4 beta build 110? I >>>>know it?s an old build, but the latest builds are always giving some >>>>problem or the other, so I thought it?s better to use a stable one >>>>as long as I don?t get into troubles? can someone suggest the latest >>>>stable build, along with swrl updates! >>>> >>>> >>>> >>>>Cheers, >>>> >>>>Raj >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>_______________________________________________ >>>protege-owl mailing list >>>protege-owl@... >>>https://mailman.stanford.edu/mailman/listinfo/protege-owl >>> >>>Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 >>>_______________________________________________ >>>protege-owl mailing list >>>protege-owl@... >>>https://mailman.stanford.edu/mailman/listinfo/protege-owl >>> >>>Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 >>> >>> >>> >>> >>> >>> >>_______________________________________________ >>protege-owl mailing list >>protege-owl@... >>https://mailman.stanford.edu/mailman/listinfo/protege-owl >> >>Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 >> >> >> >> >> > >_______________________________________________ >protege-owl mailing list >protege-owl@... >https://mailman.stanford.edu/mailman/listinfo/protege-owl > >Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 > > > _______________________________________________ protege-owl mailing list protege-owl@... https://mailman.stanford.edu/mailman/listinfo/protege-owl Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 |
|
|
Re: swrlb:notEqualHi Tania,
Thanks for the suggestion... there is still a glitch though... I noticed that in this now (504 beta) version, there is this extra namespace for the individuals while naming them... however, only the real individual name is showed in the individuals list after naming them... so far so good... But, when I use a : while naming the individual and entering it, then the real individual name in the list of individuals changes to the entire string with the whole namespace... so, it seems there is still a problem with using : in the names... (btw, same problem with the class names too) Cheers Raj -----Original Message----- From: protege-owl-bounces@... [mailto:protege-owl-bounces@...] On Behalf Of Tania Tudorache Sent: Donnerstag, 10. Juli 2008 19:18 To: User support for the Protege-OWL editor Subject: Re: [protege-owl] swrlb:notEqual Raj, I'm only replying to the individuals name part. Protege 3.4 b504 allows you to have inviduals names such as "urn:epc:tag:gid-96:1.2.98765". And the default parser for restrictions works with the urn-s. I am not sure whether the SWRL parser allows urn-s. If it doesn't, it shouldn't be hard to fix. I suggest that you upgrade to the latest 3.4 beta. Tania Mudunuri, Vekata Rajashekar Varma wrote: > Thanks Martin... > > my problem would be solved if Protégé allows characters like : and ; for the names of individuals... I have individuals where they should be named for example like urn:epc:tag:gid-96:1.2.98765 but the problem is that Protégé does not accept the character : while naming the individuals... it is important for us to name them as such so that further processing is done based on these individuals... > > Btw, I tried to use swrlb:sameAs but the SWRL editor does not allow it... neither swrl:sameAs... how do we use (syntax) these swrl sameAs and differentFrom atoms, to do the owl individuals comparasion? > > Cheers, > Raj > > > > -----Original Message----- > From: protege-owl-bounces@... [mailto:protege-owl-bounces@...] On Behalf Of Martin O'Connor > Sent: Mittwoch, 9. Juli 2008 20:47 > To: protege-owl@... > Subject: Re: [protege-owl] swrlb:notEqual > > > > This type of reasoning is outside both OWL and SWRL. swrlb:notEqual > applies to datatype values only. SWRL's sameAs and different from > atoms can be used to compare individuals. However, comparing > individuals or classes or properties with datatype values is beyond > SWRL's semantics. You can use the custom abox:hasURI built-in in > association with core string built-ins to perform the types of > comparisons but should not be used to make deductions. > > Martin > > Quoting "Mudunuri, Vekata Rajashekar Varma" > <Raj.Mudunuri@...>: > > >> Hi, >> >> >> >> Is there a way to string-wise compare an owl individual with a >> datatype value using SWRL rules? I have an individual, say ind1, and >> I have a datatype value, say ind:1, and I want to compare using >> swrl rules whether the individual of a class and the datatype value >> associated to this class via a datatype property, are literally the >> same? >> >> >> >> So, I wrote the following rule, where hasID and hasName are datatype >> properties >> >> >> >> Car(?x) ^ Manufacturer(?y) ^ hasManufacturer(?x, ?y) ^ hasID(?x, ?z) >> ^ swrlb:notEqual(?y, ?z) ? hasName(?x, ?z) >> >> >> >> But I get a problem with the swrlb:notEqual builtin? the following >> is the error I get? >> >> >> >> Exception importing SWRL rules and OWL knowledge: >> edu.stanford.smi.protegex.owl.swrl.bridge.jess.exceptions.SWRLJessBridgeException: Jess reported an error in routine >> invokeSWRLBuiltIn >> >> while executing (invokeSWRLBuiltIn "Rule-2" >> "swrlb:notEqual" 0 ?y ?z) >> >> while executing rule LHS (Node2) >> >> while executing rule LHS (Node2) >> >> while executing rule LHS (Node2) >> >> while executing rule LHS (Node2) >> >> while executing rule LHS (MTELN) >> >> while executing rule LHS (TECT) >> >> while executing (assert (MAIN::hasActualTagID_String >> Tag_2 "urn-epc-tag-gid-96-1.2.45678")). >> >> Message: error invoking built-in from Jess: exception thrown by >> built-in 'swrlb:notEqual' in rule 'Rule-2': expecting ordered type, >> got individual with name 'urn-epc-tag-gid-96-1.2.98765' for >> (0-offset) argument #0. >> >> Program text: ( assert ( hasActualTagID_String Tag_2 >> "urn-epc-tag-gid-96-1.2.45678" ) ) at line 1. >> >> >> >> >> >> What could be the reason? I?m using Protégé 3.4 beta build 110? I >> know it?s an old build, but the latest builds are always giving some >> problem or the other, so I thought it?s better to use a stable one >> as long as I don?t get into troubles? can someone suggest the latest >> stable build, along with swrl updates! >> >> >> >> Cheers, >> >> Raj >> >> >> >> >> > > > _______________________________________________ > protege-owl mailing list > protege-owl@... > https://mailman.stanford.edu/mailman/listinfo/protege-owl > > Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 > _______________________________________________ > protege-owl mailing list > protege-owl@... > https://mailman.stanford.edu/mailman/listinfo/protege-owl > > Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 > > _______________________________________________ protege-owl mailing list protege-owl@... https://mailman.stanford.edu/mailman/listinfo/protege-owl Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 _______________________________________________ protege-owl mailing list protege-owl@... https://mailman.stanford.edu/mailman/listinfo/protege-owl Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 |
|
|
Re: swrlb:notEqualHi Raj,
I do not understand. Can you give me an example? If there is a problem, it is only at the UI level. Internally, there is no problem in dealing with URNs or other URIs. Thanks, Tania Mudunuri, Vekata Rajashekar Varma wrote: > Hi Tania, > > Thanks for the suggestion... there is still a glitch though... I noticed that in this now (504 beta) version, there is this extra namespace for the individuals while naming them... however, only the real individual name is showed in the individuals list after naming them... so far so good... > > But, when I use a : while naming the individual and entering it, then the real individual name in the list of individuals changes to the entire string with the whole namespace... so, it seems there is still a problem with using : in the names... (btw, same problem with the class names too) > > Cheers > Raj > > > > > -----Original Message----- > From: protege-owl-bounces@... [mailto:protege-owl-bounces@...] On Behalf Of Tania Tudorache > Sent: Donnerstag, 10. Juli 2008 19:18 > To: User support for the Protege-OWL editor > Subject: Re: [protege-owl] swrlb:notEqual > > Raj, > > I'm only replying to the individuals name part. Protege 3.4 b504 allows > you to have inviduals names such as "urn:epc:tag:gid-96:1.2.98765". > And the default parser for restrictions works with the urn-s. > > I am not sure whether the SWRL parser allows urn-s. If it doesn't, it > shouldn't be hard to fix. > > I suggest that you upgrade to the latest 3.4 beta. > > Tania > > > Mudunuri, Vekata Rajashekar Varma wrote: > >> Thanks Martin... >> >> my problem would be solved if Protégé allows characters like : and ; for the names of individuals... I have individuals where they should be named for example like urn:epc:tag:gid-96:1.2.98765 but the problem is that Protégé does not accept the character : while naming the individuals... it is important for us to name them as such so that further processing is done based on these individuals... >> >> Btw, I tried to use swrlb:sameAs but the SWRL editor does not allow it... neither swrl:sameAs... how do we use (syntax) these swrl sameAs and differentFrom atoms, to do the owl individuals comparasion? >> >> Cheers, >> Raj >> >> >> >> -----Original Message----- >> From: protege-owl-bounces@... [mailto:protege-owl-bounces@...] On Behalf Of Martin O'Connor >> Sent: Mittwoch, 9. Juli 2008 20:47 >> To: protege-owl@... >> Subject: Re: [protege-owl] swrlb:notEqual >> >> >> >> This type of reasoning is outside both OWL and SWRL. swrlb:notEqual >> applies to datatype values only. SWRL's sameAs and different from >> atoms can be used to compare individuals. However, comparing >> individuals or classes or properties with datatype values is beyond >> SWRL's semantics. You can use the custom abox:hasURI built-in in >> association with core string built-ins to perform the types of >> comparisons but should not be used to make deductions. >> >> Martin >> >> Quoting "Mudunuri, Vekata Rajashekar Varma" >> <Raj.Mudunuri@...>: >> >> >> >>> Hi, >>> >>> >>> >>> Is there a way to string-wise compare an owl individual with a >>> datatype value using SWRL rules? I have an individual, say ind1, and >>> I have a datatype value, say ind:1, and I want to compare using >>> swrl rules whether the individual of a class and the datatype value >>> associated to this class via a datatype property, are literally the >>> same? >>> >>> >>> >>> So, I wrote the following rule, where hasID and hasName are datatype >>> properties >>> >>> >>> >>> Car(?x) ^ Manufacturer(?y) ^ hasManufacturer(?x, ?y) ^ hasID(?x, ?z) >>> ^ swrlb:notEqual(?y, ?z) ? hasName(?x, ?z) >>> >>> >>> >>> But I get a problem with the swrlb:notEqual builtin? the following >>> is the error I get? >>> >>> >>> >>> Exception importing SWRL rules and OWL knowledge: >>> edu.stanford.smi.protegex.owl.swrl.bridge.jess.exceptions.SWRLJessBridgeException: Jess reported an error in routine >>> invokeSWRLBuiltIn >>> >>> while executing (invokeSWRLBuiltIn "Rule-2" >>> "swrlb:notEqual" 0 ?y ?z) >>> >>> while executing rule LHS (Node2) >>> >>> while executing rule LHS (Node2) >>> >>> while executing rule LHS (Node2) >>> >>> while executing rule LHS (Node2) >>> >>> while executing rule LHS (MTELN) >>> >>> while executing rule LHS (TECT) >>> >>> while executing (assert (MAIN::hasActualTagID_String >>> Tag_2 "urn-epc-tag-gid-96-1.2.45678")). >>> >>> Message: error invoking built-in from Jess: exception thrown by >>> built-in 'swrlb:notEqual' in rule 'Rule-2': expecting ordered type, >>> got individual with name 'urn-epc-tag-gid-96-1.2.98765' for >>> (0-offset) argument #0. >>> >>> Program text: ( assert ( hasActualTagID_String Tag_2 >>> "urn-epc-tag-gid-96-1.2.45678" ) ) at line 1. >>> >>> >>> >>> >>> >>> What could be the reason? I?m using Protégé 3.4 beta build 110? I >>> know it?s an old build, but the latest builds are always giving some >>> problem or the other, so I thought it?s better to use a stable one >>> as long as I don?t get into troubles? can someone suggest the latest >>> stable build, along with swrl updates! >>> >>> >>> >>> Cheers, >>> >>> Raj >>> >>> >>> >>> >>> >>> >> _______________________________________________ >> protege-owl mailing list >> protege-owl@... >> https://mailman.stanford.edu/mailman/listinfo/protege-owl >> >> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 >> _______________________________________________ >> protege-owl mailing list >> protege-owl@... >> https://mailman.stanford.edu/mailman/listinfo/protege-owl >> >> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 >> >> >> > > _______________________________________________ > protege-owl mailing list > protege-owl@... > https://mailman.stanford.edu/mailman/listinfo/protege-owl > > Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 > _______________________________________________ > protege-owl mailing list > protege-owl@... > https://mailman.stanford.edu/mailman/listinfo/protege-owl > > Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 > > _______________________________________________ protege-owl mailing list protege-owl@... https://mailman.stanford.edu/mailman/listinfo/protege-owl Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 |
|
|
Re: swrlb:notEqualHi Tania,
It seems like it is an UI problem... Suppose I have a class Student... when I try to create an individual to this class I go to the individuals tab and press the create-individual button... it creates a new individual in the instance browser with the name Student_1, but the URN in the individual editor is http://www.owl-ontologies.com/Example.owl#Student_1 That is fine... but when I change this URN to http://www.owl-ontologies.com/Example.owl#Student:1 (by replacing _ with :) then the string in the instance browser changes from Student_1 to http://www.owl-ontologies.com/Example.owl#Student:1 and when I remove this : it again gets back to normal naming... So, that means, the UI is having some problems... the owl file is normal... but when I use SPARQL panel in the protégé UI it gives this long URN when I query for individuals of this Student class... perhaps SPARQL doesn't even bother to look at the owl file and takes directly from the values stored in the current UI!! Cheers, Raj -----Original Message----- From: protege-owl-bounces@... [mailto:protege-owl-bounces@...] On Behalf Of Tania Tudorache Sent: Samstag, 19. Juli 2008 03:20 To: User support for the Protege-OWL editor Subject: Re: [protege-owl] swrlb:notEqual Hi Raj, I do not understand. Can you give me an example? If there is a problem, it is only at the UI level. Internally, there is no problem in dealing with URNs or other URIs. Thanks, Tania Mudunuri, Vekata Rajashekar Varma wrote: > Hi Tania, > > Thanks for the suggestion... there is still a glitch though... I noticed that in this now (504 beta) version, there is this extra namespace for the individuals while naming them... however, only the real individual name is showed in the individuals list after naming them... so far so good... > > But, when I use a : while naming the individual and entering it, then the real individual name in the list of individuals changes to the entire string with the whole namespace... so, it seems there is still a problem with using : in the names... (btw, same problem with the class names too) > > Cheers > Raj > > > > > -----Original Message----- > From: protege-owl-bounces@... [mailto:protege-owl-bounces@...] On Behalf Of Tania Tudorache > Sent: Donnerstag, 10. Juli 2008 19:18 > To: User support for the Protege-OWL editor > Subject: Re: [protege-owl] swrlb:notEqual > > Raj, > > I'm only replying to the individuals name part. Protege 3.4 b504 allows > you to have inviduals names such as "urn:epc:tag:gid-96:1.2.98765". > And the default parser for restrictions works with the urn-s. > > I am not sure whether the SWRL parser allows urn-s. If it doesn't, it > shouldn't be hard to fix. > > I suggest that you upgrade to the latest 3.4 beta. > > Tania > > > Mudunuri, Vekata Rajashekar Varma wrote: > >> Thanks Martin... >> >> my problem would be solved if Protégé allows characters like : and ; for the names of individuals... I have individuals where they should be named for example like urn:epc:tag:gid-96:1.2.98765 but the problem is that Protégé does not accept the character : while naming the individuals... it is important for us to name them as such so that further processing is done based on these individuals... >> >> Btw, I tried to use swrlb:sameAs but the SWRL editor does not allow it... neither swrl:sameAs... how do we use (syntax) these swrl sameAs and differentFrom atoms, to do the owl individuals comparasion? >> >> Cheers, >> Raj >> >> >> >> -----Original Message----- >> From: protege-owl-bounces@... [mailto:protege-owl-bounces@...] On Behalf Of Martin O'Connor >> Sent: Mittwoch, 9. Juli 2008 20:47 >> To: protege-owl@... >> Subject: Re: [protege-owl] swrlb:notEqual >> >> >> >> This type of reasoning is outside both OWL and SWRL. swrlb:notEqual >> applies to datatype values only. SWRL's sameAs and different from >> atoms can be used to compare individuals. However, comparing >> individuals or classes or properties with datatype values is beyond >> SWRL's semantics. You can use the custom abox:hasURI built-in in >> association with core string built-ins to perform the types of >> comparisons but should not be used to make deductions. >> >> Martin >> >> Quoting "Mudunuri, Vekata Rajashekar Varma" >> <Raj.Mudunuri@...>: >> >> >> >>> Hi, >>> >>> >>> >>> Is there a way to string-wise compare an owl individual with a >>> datatype value using SWRL rules? I have an individual, say ind1, and >>> I have a datatype value, say ind:1, and I want to compare using >>> swrl rules whether the individual of a class and the datatype value >>> associated to this class via a datatype property, are literally the >>> same? >>> >>> >>> >>> So, I wrote the following rule, where hasID and hasName are datatype >>> properties >>> >>> >>> >>> Car(?x) ^ Manufacturer(?y) ^ hasManufacturer(?x, ?y) ^ hasID(?x, ?z) >>> ^ swrlb:notEqual(?y, ?z) ? hasName(?x, ?z) >>> >>> >>> >>> But I get a problem with the swrlb:notEqual builtin? the following >>> is the error I get? >>> >>> >>> >>> Exception importing SWRL rules and OWL knowledge: >>> edu.stanford.smi.protegex.owl.swrl.bridge.jess.exceptions.SWRLJessBridgeException: Jess reported an error in routine >>> invokeSWRLBuiltIn >>> >>> while executing (invokeSWRLBuiltIn "Rule-2" >>> "swrlb:notEqual" 0 ?y ?z) >>> >>> while executing rule LHS (Node2) >>> >>> while executing rule LHS (Node2) >>> >>> while executing rule LHS (Node2) >>> >>> while executing rule LHS (Node2) >>> >>> while executing rule LHS (MTELN) >>> >>> while executing rule LHS (TECT) >>> >>> while executing (assert (MAIN::hasActualTagID_String >>> Tag_2 "urn-epc-tag-gid-96-1.2.45678")). >>> >>> Message: error invoking built-in from Jess: exception thr |