Re: [ANN] Working drafts by SW Best Practices group -- request for comments

>>>> :AfricanLion
>>>>       a       :Animal;
>>>>       rdfs:subClassOf :Lion .
>>>>
>>>> :Animal
>>>>       a       owl:Class;
>>>>       rdfs:subClassOf owl:Class .

> AfricanLion will also be a subclass of owl:Class, which will mean that
> all its instances are classes. In most applications, this is probably
> not what you want.

I realize that this approach can be misleading. Let's say we have

:hasAnimal
  a :ObjectProperty
  rdfs:range :Animal

and

:Simba
  rdfs:subClassOf :AfricanLion;

then we can't say

:SanDiegoZoo
  :hasAnimal :Simba

until we also assert that

:Simba
  a :Animal;

Also, this will only work with OWL Full. Neverthless I think this is a
valid approach (let me know if it isn't), and no more awkward than some of
the other solutions you propose :-)

Received on Tuesday, 3 August 2004 04:52:37 UTC