W3C home > Mailing lists > Public > www-rdf-interest@w3.org > February 2003

RE: Type coercing a resource's type?

From: Patel, Chintan Odhavji (UMKC-Student) <copdk4@umkc.edu>
Date: Sat, 22 Feb 2003 16:25:29 -0600
Message-ID: <BAEA9E6C11AF064386D7C0D9EA7675D7258867@KC-MAIL3.kc.umkc.edu>
To: "Roger L. Costello" <costello@mitre.org>, <www-rdf-interest@w3.org>

I guess from the following construct (present somewhere), it could be
inferred that "EastChinaSea" is an instance of rdf:Type Sea.

<Sea rdf:ID="EastChinaSea"
           xmlns= http://www.china.org/geography#/>


-----Original Message-----
From: Roger L. Costello [mailto:costello@mitre.org] 
Sent: Saturday, February 22, 2003 3:06 PM
To: www-rdf-interest@w3.org
Subject: Type coercing a resource's type?

Hi Folks,

Consider this class hierarchy:

               |  |  |
        --------  |  --------
        |         |         |
        |         |         |
       Lake     Ocean      Sea

In my RDF Schema I have defined a property EmptiesInto to have a
rdfs:range value of BodyOfWater:

    <rdf:Property rdf:ID="EmptiesInto">
        <rdfs:range rdf:resource="#BodyOfWater"/>
        <rdfs:domain rdf:resource="#River"/>

Thus, when used in an RDF/XML instance the value for EmptiesInto can be
a Lake, Ocean, or Sea.

Here's a sample RDF/XML instance which shows that the Yangtze River
EmptiesInto the EastChinaSea:

    <?xml version="1.0"?>
    <River rdf:ID="Yangtze"
       <Length>6300 kilometers</Length>

From the RDF Schema I can infer that 


is a BodyOfWater.

However, I "should" be able to know more specifically that it is a Sea.

If this was a programming language I would do a type coercion to coerce
it to Sea.

My question is this: is there something that I can do in the RDF Schema
to indicate:

    "For the Yangtze River instance the property 
     EmptiesInto has the more specific type Sea"

That is, in an RDF Schema can I make statements about particular
instances?  /Roger
Received on Saturday, 22 February 2003 17:25:56 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:07:44 UTC