Re: Comments on Feature Synopsis

Peter:
> If one wanted to provide a quick gloss, one could say something like:
> 
> - In OWL/DL a resource cannot be more than one of a class, a datatype, an
>   object property, a datatype property, or an individual.  OWL/DL requires
>   that inverse functional properties, symmetric properties, and transitive
>   properties be object properties, so they cannot be datatype properties.
> 
> - In OWL/DL an object property that participates in a cardinality
>   restriction cannot be specified as a transitive property nor can it have
>   a transitively-specified property as a descendant.
> 
> - In OWL/DL all descriptions must be well-formed, with no missing or extra
>   components, and must form tree-like structures.


A couple of days back Deb asked me:
> are you making a proposal that both the guide and the feature synopsis
> incorporate new proposed text?
> if so, could you suggest it?

I think Peter has more or less answered this for me.
I think it is more accurate to say for the first of the points:

"In OWL/DL every resource must be typed either explicitly as  a class or an 
individual, or possibly implicitly as one of a datatype, an object property 
or a datatype property."

(the key text in the mapping rules is still being polished, and the rules are 
changing a little still).

and then I would have the second sentence as another bullet point.

And later contrast this with

"OWL Full uses implicit typing in which each mention of a resource plays the 
apropriate role (class, datatype, property or individual). Moreover resources 
can play multiple roles)."

Jeremy

Received on Thursday, 2 January 2003 17:06:56 UTC