Re: Treating a class as both an individual and a class?

• From: Nikita Ogievetsky <nogievet@cogx.com>
• Date: Mon, 10 Mar 2003 07:24:08 -0800
• To: <costello@mitre.org>, "Peter F. Patel-Schneider" <pfps@research.bell-labs.com>
• Cc: <www-rdf-logic@w3.org>
• Message-ID: <OE22vUmmB61ZAe3NCnv00018de4@hotmail.com>

Peter F. Patel-Schneider wrote:
> No, this is not good modelling.  If you want to say that Davenport has a
> River, you should say so, via
> 
>      <City rdf:ID="Davenport">
>          <rdfs:subClassOf>
>     <owl:Restriction>
> <owl:onProperty rdf:resource="hasFeature" />
> <owl:someValuesFrom rdf:resource="http://geodesy.org#River"/>
>     </owl:Restriction>
>          </rdfs:subClassOf>
>          ....
>      </City>
> 

Hmmm.... 
Peter, in  your example an individual city is a class?
Should not it be something like:

<CityOnARiver rdf:ID="Davenport">
         ....
</CityOnARiver>

<owl:Class rdf:ID="CityOnARiver">
  <rdfs:subClassOf rdf:resource="#River">
  <rdfs:subClassOf>
    <owl:Restriction>
      <owl:onProperty rdf:resource="hasFeature" />
      <owl:someValuesFrom rdf:resource="http://geodesy.org#River"/>
    </owl:Restriction>
  </rdfs:subClassOf>
</owl:Class>

--Nikita

Nikita Ogievetsky, nogievet@cogx.com;
Cogitech Inc.        http://www.cogx.com   
Topic Maps Tutorials and Consulting. 
phone:  1 (917) 406 - 8734      


Nikita Ogievetsky, nogievet@cogx.com;
Cogitech Inc.        http://www.cogx.com   
Topic Maps Tutorials and Consulting. 
phone:  1 (917) 406 - 8734      

Received on Monday, 10 March 2003 10:24:22 UTC