Search Mailing List Archives
[protege-owl] Using ObjectHasSelf in Protege 4.0
j.m.wright at massey.ac.nz
Mon Aug 3 17:36:01 PDT 2009
Thanks for the help! Using ObjectExistsSelf worked fine, but it looks like I
didn't require it.
For the interested I managed to define Edge.source != Edge.target as
follows. I'm not sure if it's semantically correct, but it seems to work
fine in Protege.
On Tue, Aug 4, 2009 at 12:40 AM, Timothy Redmond <tredmond at stanford.edu>wrote:
> You have run into one of the differences between owl 1.1 and owl 2.0.
> Protege 4.0 has not quite incorporated all the latest owl 2.0 changes. If
> you look at the owl 1.1  and owl 2.0  specifications, you will see
> that in owl 1.1 hasSelf is represented as ObjectExistsSelf and in owl 2.0
> hasSelf is represented as ObjectHasSelf.
> In addition, in Protege 4, a hasSelf restriction can be added from the user
> interface using the manchester owl syntax:
> hasTopping some Self
> There is a bleeding edge version of Protege 4.1 in svn which has
> incorporated many of the owl 2.0 changes.
>  http://www.webont.org/owl/1.1/owl_specification.html
>  http://www.w3.org/TR/2009/CR-owl2-syntax-20090611/#Self-Restriction
> On Aug 2, 2009, at 11:26 PM, Jevon Wright wrote:
>> I am trying to define an OWL ontology as follows: I have an Edge, that
>> connects two nodes. I would like to add the restriction that Edge cannot
>> connect the same Node together, i.e. Edge.source != Edge.target.
>> From the OWL mailing list it was suggested I use the ObjectHasSelf axiom.
>> SubClassOf(MyNode ObjectComplementOf(ObjectHasSelf(connectedTo)))
>> However when I load this up in Protege 4.0 build 113, I get the following
>> parsing error:
>> org.coode.owl.functionalparser.ParseException: Encountered "(" at line 16,
>> column 51.
>> Was expecting one of:
>> ")" ...
>> ":" ...
>> (Line 16)
>> Replacing ObjectHasSelf with another term resolves this error. Could it be
>> that the functional syntax parser does not have ObjectHaveSelf (from OWL
>> 2.0) defined? "OWLFunctionalSyntaxParser.jj" does not have it defined.
>> If the functional syntax parser cannot load this file, how else could I
>> define this using Protege? Am I using the ObjectHasSelf axiom correctly?
>> protege-owl mailing list
>> protege-owl at lists.stanford.edu
>> Instructions for unsubscribing:
> protege-owl mailing list
> protege-owl at lists.stanford.edu
> Instructions for unsubscribing:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the protege-owl