RE: Triples from DAML

First of all thanks for your reply.

This first statement

>Actually DAML+OIL doesn't really care about either the XML/RDF encoding or
>the RDF triples.

highlighted some of the unsolved problems I still have.
Is there a difference between XML/RDF and RDF? Some ppl refer to the prior
rather than the latter.

And I am not sure I understood the second part

>What counts as far as DAML+OIL is concerned is the models of the above.

What is implied by " the models of the above": is it referring to how they
are structured?


-----Original Message-----
From: Peter F. Patel-Schneider []
Sent: Monday, November 26, 2001 8:55 PM
Subject: Re: Triples from DAML

Actually DAML+OIL doesn't really care about either the XML/RDF encoding or
the RDF triples.  What counts as far as DAML+OIL is concerned is the models
of the above.

In these models, some triples are interpreted as logical constructs
(e.g., equivalentTo John Susan) and others are interpreted as non-logical
constructs (e.g., parent John Susan).  Which is more important is, of
course, up to you, but generally both are needed to provide a coherent view
of a DAML+OIL knowlege base.

Peter F. Patel-Schneider
Bell Labs Research

From: "Charlie Abela" <>
Subject: Triples from DAML
Date: Fri, 23 Nov 2001 00:12:19 -0000

> Hi.
> Hopefully someone will dedicate some time to tell me if I'm on the right
> track or not.
> Since DAML is based on XML then one might consider using an XML parser to
> effectively parse a DAML file. Right?
> On the other hand a DAML parser is able to produce more information
> regarding a
> DAML since it would parse the DAML into triples.
> Which triples can be considered more useful than others when making a
> query?
> Example1: the following is an instance of a CS-Staff member
> IsAMemberOf(John,CS-Staff) =>
> CS-Staff is the Subject
> IsAMemberOf is the Predicate
> John is the Object
> So I would say that DatatypeProperties in a DAML file are important since
> from them one can get to the type of relations as above
> One can query for example: "Which are the staff members in the Computer
> Science department?"
> And this would return with all the values that the
sAMemberOf( x,CS-Staff)
> represents.
> Example 2:
> <daml:Class rdf:ID="Member">
>   <rdfs:label>Member</rdfs:label>
>   <rdfs:comment>represents a member of the lecturing staff</rdfs:comment>
>   <rdfs:subClassOf rdf:resource="
>" />
>   <rdfs:subClassOf rdf:resource="
>" />
>   <rdfs:subClassOf>
>      <daml:Restriction daml:maxCardinality="1">
>              <daml:onProperty rdf:resource="#hasOffice" />
>      </daml:Restriction>
>   </rdfs:subClassOf>
> </daml:Class>
> This block of daml code above represents a class Member which is a
> of a Person class and a Lecturing-Staff class and also a subclass of the
> abstract class where a Member has only one office(defined elsewhere).
> Such a number of statements when parsed with a DAML parser would result in
> number of triples, some being more useful than others when querying.
> Such triple as:
>       Subject :
>       Predicate:  subClassOf
>       Object :    Member
>       Subject :
>       Predicate:  subClassOf
>       Object :    Member
> Am I right in the above declarations of triples?
> Which other triples can be stated from the above code?
> Charlie

Received on Tuesday, 27 November 2001 14:08:05 UTC