Re: Close to final draft of "classes as values" note

Alan,

>  In Approach 1 under "Considerations" on pg 3 you have
>
>   
> vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv 
> vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
>  o The class BookAboutAnimals has AnimalClass as an allValuesFrom  
> range restriction for the dc:subject property:
>
>    :BookAboutAnimals
>            a       owl:Class ;
>          rdfs:subClassOf
>                  [a       owl:Restriction ;
>                           owl:allValuesFrom :AnimalClass ;
>                            owl:onProperty dc:subject              ] .
>
>   
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
> ^^^^^^^^^^^^^^^^^^^^
>
>  A footnote notes that if it could be about other things, then the  
> qualifier could be "SomeValuesFrom".
>
>  OWL's open world semantics require that a SomeValuesFrom restriction  
> be included in any case either in this class description or in some  
> superclass.   Otherwise, there is no requirement that  
> "BookAboutAnimals" be about anything.

You are right of course -- my mistake. Thanks a lot for spotting this.  
I'll change to someValuesFrom and leave it at that. We will probably  
have a different note to discuss the proper use of all and some and the  
patterns for closing roles. So, I'd rather leave the issue out of this  
note.

Natasha

Received on Wednesday, 19 May 2004 22:31:25 UTC