- From: Peter F. Patel-Schneider <pfps@research.bell-labs.com>
- Date: Wed, 23 Apr 2003 15:31:45 -0400 (EDT)
- To: mdean@bbn.com
- Cc: www-webont-wg@w3.org
From: Mike Dean <mdean@bbn.com> Subject: Re: Case for Reinstatement of Qualified Cardinality Restrictions Date: Wed, 23 Apr 2003 12:28:41 -0700 > > > Agreed. I normally use multiple Restrictions with the same > > > value for onProperty. > > > > If you are doing this in the RDF encoding you are going to be unpleasantly > > surprised. > > Perhaps I should clarify with an example > > <owl:Class rdf:ID="Person"> > <rdfs:subClassOf> > <owl:Restriction> > <owl:onProperty rdf:resource="#father"/> > <owl:allValuesFrom rdf:resource="#Person"/> > </owl:Restriction> > </rdfs:subClassOf> > <rdfs:subClassOf> > <owl:Restriction> > <owl:onProperty rdf:resource="#father"/> > <owl:cardinality>1</owl:cardinality> > </owl:Restriction> > </rdfs:subClassOf> > </owl:Class> > > Why is this a problem? > > Mike Sorry, I misread what you said. Your solution is fine. What doesn't work is <owl:Class rdf:ID="Person"> <rdfs:subClassOf> <owl:Restriction> <owl:onProperty rdf:resource="#father"/> <owl:allValuesFrom rdf:resource="#Person"/> <owl:cardinality>1</owl:cardinality> </owl:Restriction> </rdfs:subClassOf> </owl:Class> peter
Received on Wednesday, 23 April 2003 15:32:04 UTC