- From: Stephen Rhoads <rhoadsnyc@mac.com>
- Date: Thu, 23 Sep 2004 14:12:23 -0400
- To: kurt.godden@GM.com
- Cc: www-rdf-interest@w3.org
Only use domain and range constraints when you truly want to restrict a property on a global basis. A better way to model is to use DLs: Class(Brakepad partial restriction(isPartOf someValuesFrom(BrakeAssembly))) Class(BrakeAssembly partial restriction(isPartOf someValuesFrom(Vehicle)) restriction(hasPart someValuesFrom(BrakePad))) Class(Vehicle partial restriction(hasPart someValuesFrom(BrakeAssembly))) ObjectProperty(isPartOf Transitive inverseOf(hasPart)) ObjectProperty(hasPart Transitive inverseOf(isPartOf)) --- Stephen On Thursday, September 23, 2004, at 09:22AM, <kurt.godden@GM.com> wrote: > >Oops, I accidentally sent that before I was done. Just a wee bit more: > >So it seems to me that I should simply omit specifying any ranges for >isPartOf. Then I can attach it to any domain that I need. Does that sound >reasonable to others? > >-KG > >----- Forwarded by Kurt S Godden/US/GM/GMC on 09/23/2004 09:18 AM ----- > > kurt.godden@gm.com > Sent by: To: www-rdf-interest@w3.org > www-rdf-interest-req cc: > uest@w3.org Subject: rdfs:range with dcterms:isPartOf > > > 09/23/2004 09:10 AM > > > > > > > >Suppose >Brakepad isPartOf BrakeAssembly. >and >BrakeAssembly isPartOf Vehicle. > >It seems like I can NOT specify that there is an rdfs:range on >dcterms:isPartOf for the class Vehicle as well as the class BrakeAssembly. >The reason is because the RDF Schema spec says "Where P has more than one >rdfs:range, then the resources denoted by the objects...are instances of >*all* the classes..." [emphasis added]. > >Kurt Godden >GM Technical Fellow >GM R&D, Warren, MI >ph: 586-986-0445; em: kurt.godden@gm.com > >"I distrust a research person who is always obviously busy on a task." > ---Robert A. Frosch, VP (retired), GM Research > > > > > > > > > > >
Received on Thursday, 23 September 2004 18:12:30 UTC