I second the restriction recommendation. Restrictions are local to a class as opposed to being global - as domains and ranges are.
They are also open ended. You can keep on adding new restrictions without impacting what was stated before. With unions, you can't simply add new statements, you have to retract the existing one. This means they impact modularity and you are likely to have problems merging two models which are using the same property. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Holger Knublauch Sent: Thursday, January 07, 2010 3:44 AM To: [email protected] Cc: Bonsma, P. (Peter) Subject: Re: [tbc-users] multiple domains? On Jan 6, 2010, at 11:53 PM, Bohms, H.M. (Michel) wrote: > Ok, what we will do in our owl-generation: > - if range is different: change propertyname (make it globally unique) > - if range is the same: merge domains via union > > Guess this is the way to handle it? > (we are coming from languages that define properties as secondary concept not as prime concepts on the same level as classes so we have to adapt a bit...) Yes this should work. We had the same problems several times when attempting to convert UML or XML models to RDF/OWL. An alternative to using rdfs:domains, is to define owl:allValuesFrom restrictions (or cardinality restrictions + range). This may make your data structures easier to manage, and is another way of "attaching" a property to a class. Holger
-- 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.
