Re: Dealing with qualified expressions in DAML

• From: John Pacheco <pacheco@AI.SRI.COM>
• Date: Tue, 17 Sep 2002 12:14:07 -0700 (PDT)
• To: pfps@research.bell-labs.com
• Cc: www-rdf-logic@w3.org
• Message-Id: <200209171914.MAA11871@Lincoln.AI.SRI.COM>

> > <daml:Class rdf:ID="CartoonCharacter">
> >   <rdfs:subClassOf>
> >     <daml:Restriction>
> >       <daml:onProperty rdf:resource="#hasInPocket"/>
> >       <daml:hasClassQ rdf:resource="#Elephant"/>
> >       <daml:maxCardinalityQ>2</daml:maxCardinalityQ>
> >       <daml:hasClassQ rdf:resource="#Dynamite"/>
> >       <daml:maxCardinalityQ>4</daml:maxCardinalityQ>
> >       <daml:hasClassQ rdf:resource="#Anvil"/>
> >       <daml:maxCardinalityQ>1</daml:maxCardinalityQ>
> >     </daml:Restriction>
> >   </rdfs:subClassOf>
> > </daml:Class>
> 
> This is valid DAML+OIL, but it does not mean what you might think that it
> means. To get the standard meaning of this you need to create an
> intersectionOf multiple restrictions.

So what does this code mean then?  How is one to interpret multiple hasClassQ 
and cardinalityQ tags?

-John Pacheco

Received on Tuesday, 17 September 2002 15:14:15 UTC