W3C home > Mailing lists > Public > www-rdf-logic@w3.org > October 2000

Re: basic decisions underlying DAML-ONT (defined classes)

From: Peter F. Patel-Schneider <pfps@research.bell-labs.com>
Date: Thu, 12 Oct 2000 14:29:25 -0400
To: connolly@w3.org
Cc: www-rdf-logic@w3.org
Message-Id: <20001012142925A.pfps@research.bell-labs.com>
From: Dan Connolly <connolly@w3.org>
Subject: Re: basic decisions underlying DAML-ONT (defined classes)
Date: Thu, 12 Oct 2000 12:39:42 -0500

> "Peter F. Patel-Schneider" wrote:
> > 
> > Why not create a new kind of object, perhaps called a description, which
> > would ``contain'' restrictions and qualifications.   The meaning of a
> > description would be the intersection of these restrictions and
> > qualifications.  A class could then be defined as ``equivalentTo'' to a
> > description.
> 
> Yes, that's the basic idea. It's called reification
> in the RDF specs; it's called quoting elsewhere.

I don't think that I am asking for reification or quoting, just something like:

<Class ID="DAMLdescription">
       <comment> a DAMLdescription is defined to be precisely the intersection
       of its restrictions and qualifications</comment>
</Class>

<Property about="restrictedBy">
  <domain resource="#DAMLresource">
</Property>

then we can create defined classes via

<DAMLdescription ID="foo">
  <restrictedBy>
    <Restriction>
      <onProperty resource="#parent"/>
      <toClass resource="#Person"/>
    </Restriction>
</DAMLdescription>

<Class ID="objectsWithAllParentsPeople">
  <equivalentTo resource="#foo">
</Class>

Peter Patel-Schneider
Received on Thursday, 12 October 2000 14:30:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:52:37 GMT