- From: Peter F. Patel-Schneider <pfps@research.bell-labs.com>
- Date: Tue, 17 Jan 2006 08:39:49 -0500 (EST)
- To: hans.teijgeler@quicknet.nl
- Cc: semantic-web@w3.org
From: "Hans Teijgeler" <hans.teijgeler@quicknet.nl> Subject: hasValue with more than one outcome Date: Tue, 17 Jan 2006 13:34:42 +0100 > Hi, > > In http://www.w3.org/TR/2004/REC-owl-ref-20040210/#hasValue-def > <http://www.w3.org/TR/2004/REC-owl-ref-20040210/#hasValue-def> > I find: > > <owl:Restriction> > <owl:onProperty rdf:resource="#hasParent" /> > <owl:hasValue rdf:resource="#Clinton" /> > </owl:Restriction> > > In order to make this complete can I state: > > <owl:Restriction> > <owl:onProperty rdf:resource="#hasParent" /> > <owl:hasValue rdf:resource="#Clinton" /> > <owl:hasValue rdf:resource="#Hillary" /> > </owl:Restriction> > > i.e. what to do when owl:hasValue has more than one possible outcome? In general malformed restrictions like the one above should be avoided. They are definitely not legal in OWL DL, and often have very strange meanings in OWL Full. > I hope someone can help me. Well, it is hard to determine exactly what you want to do here. > Regards, > Hans peter
Received on Tuesday, 17 January 2006 13:40:03 UTC