Bernard; Note that owl:InverseFunctionalProperty is a subproperty of owl:ObjectProperty. Hence Composer will assume that values are resources, not literals.
The workaround is as you have stated, define the datatype property values before asserting that the property is inverse functional. -- Scott On Oct 23, 4:32 am, Bernard Chabot <[email protected]> wrote: > Hello, > > I'm want to build a ontology using the property "email" as a owl > :InverseFunctionalProperty > > If I first define "email" as owl:DatatypeProperty, > I can set a property "email" to instances of class "Person" using a single > string > > Then If a also define as a owl:InverseFunctionalProperty > the reasonner works fine and state that instances of "Person" with the same > email are the same Person > > But If a define at the very beginning "email" is both a owl:DatatypeProperty > and a owl:InverseFunctionalProperty > I can not add email as a string ... the system is waiting for a instance > > How can I solve this limitation ? > (In theorie this could be possible using a OWL Full ontology) > > Regards, > > Bernard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
