comments on Section 8 of Reference

Suggested changes:

... unconstrained mixing of OWL and RDF.  The construct owl:Class ....
	to
... unconstrained use of RDF constructs.  The resource owl:Class ..., in
OWL Full

... not all RDF classes are OWL classes).
	to
... not all RDF classes are OWL classes in OWL DL and OWL Lite).

properties (note: ...).
	to
properties. (Note: ....)

sense (RDF ...).
	to
sense. (RDF ....)

[add a link to]
	(see below)

[fix formatting of note just before 8.2]

i.e.
	to
i.e.,

and built-in
	to
and the built-in

should be placed
	to
can be placed

Some RDF(S) vocabulary 
	to
Most RDF(S) vocabulary 

[remove]
	An OWL DL ontology that imports an OWL Full ontology becomes an
	OWL Full ontology.

Section 8.3 needs a complete rewrite.  Here is a suggestion:

OWL Lite abides by all the restrictions OWL DL puts on the use of the OWL
language constructs.  
In addition, OWL Lite forbids the use of 
owl:complementOf, 
owl:dataRange,
owl:disjointWith,
owl:hasValue,
owl:oneOf,
owl:Nothing,
and 
owl:unionOf.

OWL Lite also requires that
- the subject of owl:equivalentClass triples be named classes 
  and the object of owl:equivalentClass triples be named classes,
  restrictions, or subjects of owl:intersectionOf triples;
- the subject of rdfs:subClassOf triples be named classes 
  and the object of rdfs:subClassOf triples be named classes or
  restrictions;
- owl:intersectionOf be used only on lists of length greater than one that
  contain only named classes and restrictions; 
- the object of owl:allValuesFrom and owl:someValuesFrom triples be named
  classes or named datatypes;
- the object of rdf:type triples be named classes or restrictions;
- the object of rdf:domain triples be named classes;
and
- the object of rdf:range triples be named classes or datatypes.

Received on Wednesday, 26 March 2003 15:06:33 UTC