W3C home > Mailing lists > Public > www-webont-wg@w3.org > January 2003

Re: ISSUE: owl:Class name misleading; try owl:Set?

From: Peter F. Patel-Schneider <pfps@research.bell-labs.com>
Date: Fri, 03 Jan 2003 06:34:55 -0500 (EST)
Message-Id: <20030103.063455.05326102.pfps@research.bell-labs.com>
To: connolly@w3.org
Cc: www-webont-wg@w3.org

From: Dan Connolly <connolly@w3.org>
Subject: Re: ISSUE: owl:Class name misleading; try owl:Set?
Date: 02 Jan 2003 23:51:25 -0600

> 
> On Thu, 2003-01-02 at 21:36, Jonathan Borden wrote:
> > Dan Connolly wrote:
> > ...
> > >
> > > Please provide an example of two owl classes that
> > > have the same members but differ in some other
> > > property ...
> > 
> > Hmmm....
> > 
> > ex:foo rdf:type owl:Class .
> > ex:bar rdf:type owl:Class .
> > 
> > ex:foo owl:sameClassAs ex:bar .
> > 
> > but they have different names ... that's a 'property' of a class that
> > differs from the extension eh?
> 
> But from what I understand, that's impossible for owl:Class's.
> i.e. if they have the same extension, they're identical,
> so they have the same properties. (this is not true
> for all rdfs:Classes; only for the owl:Class subclass)

As has been pointed out several times, this is not the case.  See, for
example,  http://lists.w3.org/Archives/Public/www-webont-wg/2003Jan/0018.html

If you believe otherwise, please point out some part of the semantics
document that you think would give rise to this.

[...]

peter
Received on Friday, 3 January 2003 06:35:08 GMT

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