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

Subclass of Thing/Resource

From: Tim Berners-Lee <timbl@w3.org>
Date: Tue, 29 Feb 2000 17:07:57 -0500
Message-ID: <02ed01bf8301$6f9142e0$84001d12@politburo.w3.org>
To: <www-rdf-interest@w3.org>, "Stefan Decker" <stefan@db.stanford.edu>

From: Stefan Decker <stefan@db.stanford.edu>

>if an application  does not know protege:thing, it can ignore it.

Surely, if it does *not* know protege:thing it *cannot* ignore it without
throwing away information.
If it *does* know protege:thingthen it *can* ignore the statement as it
knows it contains no information.  Every class is a subclass of Thing.

>If a user defines a resource to be a subclass of protege:Thing, protege can
>not ignore this and we have to save that.

No, you can just hang all classes not defined as subclasses of anything else
off the "thing" hook in the UI.

>However,  i think there is a small missunderstanding: you probably meant
>that #Calendar is a subclass of rdfs:Resource.

In RDF, every class is a subclass of rdfs:Resource so surely that is just as
informationless too.
(I do wish RDF had used "thing" instead of "resource" which has a meaning in
URI already).



Received on Tuesday, 29 February 2000 17:08:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:44:22 UTC