W3C home > Mailing lists > Public > www-rdf-logic@w3.org > June 2004

Tbox quering

From: Dimitrios A. Koutsomitropoulos <kotsomit@hpclab.ceid.upatras.gr>
Date: Wed, 16 Jun 2004 20:10:51 +0300
To: "'rdf-logic'" <www-rdf-logic@w3.org>
Message-Id: <20040616171017.CCFBEA16EE@frink.w3.org>

Hello everyone,

Browsing through the DL-based matchmaking bibliography and also other
sources, I realized that one way to conduct querying in a OWL ontology is to
costruct a concept with preffered characteristics and then classify it in
the taxonomy. Its subconcepts would be then the answers to the query.

This method of quering requires only the presence of the Tbox in the
ontology. To a far extend, every instance in the ontology can be modeled as
a concept and queries can be conducted as mentioned before, thus using only
Tbox reasoning techniques.

For example consider the case that one would want to express the fact that
an artifact is made of iron:

<owl:Class rdf:ID="My_Artifact">
    <owl:onProperty rdf:resource="#isMadeOf"/>
    <owl:someValuesFrom rdf:resource="#Iron"/>

..given that Iron is Metal:

<owl:Class rdf:ID="Iron">
  <rdfs:subClassOf rdf:resource="#Metal" />

...one can now retieve every metal artifact:

   <owl:onProperty rdf:resource="#isMadeOf"/>
    <owl:someValuesFrom rdf:resource="#Metal"/>

This is perfect for that kind of queries. However consider the case where we
want to know the material that "My_Artifact" is made of.

Can this be achieved? (for example by using the inverse of "isMadeOf" and
some restriction on it?)

Thanks for your time!

Dimitrios Koutsomitropoulos
Received on Wednesday, 16 June 2004 13:10:19 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 2 March 2016 11:10:42 UTC