This file specifies in RDF Schema format the built-in classes and properties that together form the basis of the RDF/XML syntax of OWL Full, OWL DL and OWL Lite. We do not expect people to import this file explicitly into their ontology. People that do import this file should expect their ontology to be an OWL Full ontology.
A member of this class is an issue in some issue list.
These tests use two documents. One is named importsNNN.rdf, the other is named mainNNN.rdf. These tests indicate the interaction between owl:imports and the sublanguage levels of the main document.
A consistent OWL document. (One that does not entail falsehood).
An inconsistent OWL document. (One that entails falsehood).
This is a positive entailment test according to the OWL entailment rules.
This is a negative entailment test according to the OWL entailment rules.
This is a negative test. The input document contains some use of the OWL namespace which is not a feature of OWL. These typically show DAML+OIL features that are not being carried forward into OWL.
Illustrative of the use of OWL to describe OWL Full.
The premise document, and its imports closure, entails the conclusion document.
The conclusions follow from the empty premises.
The object is a datatype that appears in one of the test files in the subject test.
The subject test is valid only when the object datatype is included in the datatype theory.
This property relates a test to a language feature. The language feature is usually indicated by a class or property.
A string valued property that gives a numeral (or some other quasi-numeric string) associated with an issue.
Indicates the conformance level of a document or test in the OWL test suite.
Structure sharing is not permitted in OWL DL, between two class descriptions.
If the owl:disjointWith edges in the graph form undirected complete subgraphs which share blank nodes then this is not within OWL DL.
This test shows a potential misapplication of OWL Full comprehension rules. It also shows optional type triples on an owl:Restriction.
If an OWL Lite document imports an OWL DL document then it becomes OWL DL.
This is a typical definition of range from description logic. It works both ways.
If prop belongs to owl:FunctionalProperty then an OWL individual has at most one value for prop.
The order of the instances in an owl:oneOf construct is unimportant.
DL Test: t5.1 Non-finite model example from paper The concept should be coherent but has no finite model
owl:sameAs is stronger than owl:equivalentClass.
This test illustrates the use of an undeclared user defined datatype. The document is hence in Full.
Despite the property URI, the document indicated by this property may or may not be imported into the test.
DL Test: heinsohn2.2 Tbox tests from [Heinsohn et al.] Tests incoherency caused by number restrictions
The union of two classes can be defined using OWL Lite restrictions, and owl:intersectionOf.
DL Test: k_branch ABox test from DL98 systems comparison.
DL Test: heinsohn1.4 Tbox tests from [Heinsohn et al.] Tests incoherency caused by disjoint concept
Comprehension does not build illformed lists.
The abstract syntax form of the conclusions is: EquivalentClasses( restriction( first:p, minCardinality(1) ) ) ObjectProperty( first:p ) This is trivially true given that first:p is an individualvaluedPropertyID.
A simple test for infinite loops in imports processing code.
Uniform treatment of literal data values
stateCode example using an inverseFunctionalProperty and literals
An owl:cardinality constraint is simply shorthand for a pair of owl:minCardinality and owl:maxCardinality constraints.
Classes can be the object of annotation properties in OWL Lite and DL.
DL Test: k_poly ABox test from DL98 systems comparison.
Two classes with the same partial description are not equivalent.
This test shows a relationship between integer addition and OWL Full.
In OWL Full, the triple in the premises is synonymous with the triple in the conclusions.
DL Test: k_path ABox test from DL98 systems comparison.
This entailment can be replicated for any three natural numbers i, j, k such that i+j >= k. In this example, they are chosen as 2, 3 and 5.
This test shows how user labels in a variety of languages can be used. Note the use of ruby annotation.
DL Test: fact1.1 If a, b and c are disjoint, then: (a and b) or (b and c) or (c and a) is unsatisfiable.
DatatypeProperty's may be used to related typed literals to typed literals, in OWL Full.
This test shows integer multiplication in OWL DL, interacting with infinity. N times infinity is 2 times infinity. M times infinity is 3 times infinity. N times M times infinity is 5 times infinity.
Structure sharing is not permitted in OWL DL, between an owl:equivalentClass triple and a type triple.
If the owl:disjointWith edges in the graph form unconnected undirected complete subgraphs then this may be within OWL DL.
DL Test: heinsohn4.2 Tbox tests from [Heinsohn et al.] Tests role restrictions
This test shows OWL Lite syntax for using two equivalent restrictions.
Importing OWL Full documents may change the level of OWL Lite or OWL DL documents.
This is a typical definition of range from description logic.
If the range of prop is a singleton set then it is necessarily functional, (i.e. every member of its domain has a single value) and so it is an owl:FunctionalProperty.
oneOf describes a class by enumerating its individuals.
In OWL Lite and DL the subject and object of a triple with predicate owl:backwardCompatibleWith must both be explicitly typed as owl:Ontology.
sameAs and sameIndividualAs are equivalent.
This test illustrates the use of a user defined datatype. The informal description has no formal semantics.
dc:creator may be declared as an annotation property.
The names used in a DAML+OIL qualified min cardinality constraint are not defined the OWL namespace.
DL Test: heinsohn1.3 Tbox tests from [Heinsohn et al.] Tests incoherency caused by disjoint concept
A reasoner can also deduce that hasLeader is a subProperty of hasHead and hasHead is a subProperty of hasLeader.
This test exhibits the effect of the comprehension principles in OWL Full.
Another simple example; contrast with owl:someValuesFrom.
Classes cannot be the object of regular properties in OWL DL.
The blank nodes in a individual description in OWL DL may not form a directed cycle.
DL Test: k_ph ABox test from DL98 systems comparison.
There are 128 different values of xsd:byte that are also xsd:unsignedInt.
hasLeader may be stated to be the owl:equivalentProperty of hasHead.
Two classes with the same partial description are not the same.
If the domain of prop is a singleton set then it is necessarily inverse functional, (i.e. every member of its range is the value of a single item) so it is an owl:InverseFunctionalProperty.
Two classes with the same complete description are equivalent.
In OWL Full every rdfs:Class is an owl:Class, in particular rdfs:Class is an owl:Class.
DL Test: k_lin ABox test from DL98 systems comparison.
This test shows integer multiplication in OWL DL. N is 200. M is 300. N times M is 60000.
Structure sharing is not permitted in OWL DL, between a class description and a type triple.
This example has owl:disjointWith edges in the graph which cannot be generated by the mapping rules for DisjointClasses. Consider the lack of owl:disjointWith edge between nodes C and D.
DL Test: heinsohn4.1 Tbox tests from [Heinsohn et al.] Tests role restrictions
This test shows syntax that is not permitted in OWL Lite or OWL DL for using the same restriction twice.
If a document imports a document which in turn imports a third document, then it entails anything which is entailed by the conjunction of the statements from the three documents. That is, imports is transitive.
OWL, unlike RDFS, uses iff semantics for range.
If prop is an owl:FunctionalProperty, then its inverse is an owl:InverseFunctionalProperty.
oneOf does not indicate that the named individuals are distinct. Thus a consistent interpretation of this file is when all the individual names denote the same individual.
This is a variation of equivalentClass-001, showing the use of two owl:Ontology triples in the premises.
There might be only 128 different values of xsd:byte that are also xsd:unsignedInt; but this does not follow from the datatype theory of this test. (cf. the similar inconsistency test).
The use of blank nodes in OWL DL and OWL Lite is restricted.
Annotations participate a little in the semantics.
owl:samePropertyAs is not an OWL property.
DL Test: t3a.3 There are 42,525 possible partitions in the satisfiable case
The names used in a DAML+OIL qualified max cardinality constraint are not defined the OWL namespace.
The complement of a class can be defined using OWL Lite restrictions.
hasLeader may be stated to be the samePropertyAs hasHead.
DL Test: heinsohn1.2 Tbox tests from [Heinsohn et al.] Tests incoherency caused by disjoint concept
rdf:nil cannot have an rdf:first property.
If the pair (x,y) is an instance of P, than the pair (y,x) is an instance of the named property.
Sets with appropriate extensions are related by unionOf.
AnnotationProperty's in OWL Lite and OWL DL, may not have range constraints.
This test specifies the domain and range for owl:imports.
DL Test: heinsohn3c.1 Tbox tests from [Heinsohn et al.] Tests incoherency caused by number restrictions and role hierarchy
There are precisely 128 different values of xsd:byte that are also xsd:unsignedInt.
If p and q have the same property extension then p owl:equivalentProperty q.
Two classes with the same complete description are the same.
If prop is an owl:InverseFunctionalProperty, then its inverse is an owl:FunctionalProperty.
Two classes may be different names for the same set of individuals
This is a different encoding of test 502.
DL Test: k_grz ABox test from DL98 systems comparison.
The extension of OWL Thing may not be a singleton in OWL Full.
using distinctMembers to derive differentFrom
The informal semantics indicated by comments concerning user defined classes are not respected by the formal machinery of OWL.
This test shows integer multiplication in OWL DL. N is 20. M is 30. N times M is 600.
If the owl:disjointWith edges in the graph form an undirected complete subgraph then this may be within OWL DL.
If a premise document uses a namespace but does not import the document corresponding to the namespace, then the premises do not necessarily entail anything that is entailed by the conjunction of the two documents.
This entailment is similar to one that does not hold in RDFS.
If prop belongs to owl:FunctionalProperty, and subject denotes a resource which is the subject of two prop triples, then the objects of these triples have the same denotation.Hence any assertion made using one of them can be transferred to the other.
The blank nodes in a class description in OWL DL may not form a directed cycle.
This is a variation of equivalentClass-001, showing the use of owl:Ontology triple only in the conclusions.
The empty graph entails that xsd:integer and xsd:string are a rdfs:Datatype
DL Test: t3a.2 There are 7,770 possible partitions in the unsatisfiable case
The names used in a DAML+OIL qualified cardinality constraint are not defined the OWL namespace.
using AllDistinct to derive differentFrom
DL Test: heinsohn1.1 Tbox tests from [Heinsohn et al.] Tests incoherency caused by disjoint concept
An example combining owl:oneOf and owl:inverseOf.
rdf:nil cannot have an rdf:rest property.
The owl:disjointWith loop is not in OWL DL. Classes that are disjoint with themselves are necessarily empty.
A union behaves quite like set theoretic union.
URI references used in annotations don't need to be typed.
DL Test: heinsohn3.2 Tbox tests from [Heinsohn et al.] Tests incoherency caused by number restrictions and role hierarchy
There are only 128 different values of xsd:byte that are also xsd:unsignedInt.
If p and q have the same property extension then p equivalentProperty q.
If prop belongs to owl:InverseFunctionalProperty, and object denotes a resource which is the object of two prop triples, then the subjects of these triples have the same denotation. Hence any assertion made using one of them can be transferred to the other.
This description cannot be expressed as a multicomponent restriction in the abstract syntax.
This is a different encoding of test 501.
This entailment does not hold under the RDF Semantics, but does under the RDFS Compatible Semantics for OWL.
Annotation properties refer to a class instance. sameAs, in OWL Full, also refers to the class instance.
An empty owl:Class has the same class extension as owl:Nothing.
The extension of OWL Thing may be a singleton in OWL DL.
DL Test: k_dum ABox test from DL98 systems comparison.
A possible mapping of the EquivalentClasses axiom, which is connected but without a Hamiltonian path.
This test shows a correct application of OWL Full comprehension rules. It also shows that use of rdfs:Class instead of owl:Class may make a file fall outside OWL DL.
Test illustrating extensional semantics of owl:TransitiveProperty.
The informal semantics for RDF container vocabulary, indicated by the comment, are not respected by the formal machinery of OWL.
This test shows integer multiplication in OWL DL. N is 2. M is 3. N times M is 6.
Disjoint classes have different members.
This test shows the syntax for using the same restriction twice in OWL Lite.
A test for the interaction of one-of and inverse using the idea of a spy point. Everything is related to the spy via the property p and we know that the spy has at most two invP successors, thus limiting the cardinality of the domain to being at most 2.
If a document imports another document, then it entails anything that is entailed by the conjunction of the two documents.
This shows that an OWL consistency checker which does not support the datatype rdf:XMLLiteral should not detect inconsistencies depending on it. This file is inconsistent with a datatype theory which supports rdf:XMLLiteral, but consistent in this test, which excludes such support.
If prop belongs to owl:FunctionalProperty, and subject denotes a resource which is the subject of two prop triples, then the objects of these triples have the same denotation.
If the owl:disjointWith edges in the graph form undirected complete subgraphs which share URIref nodes but do not share blank node then this may be within OWL DL.
It is often possible to import an ordinary RDFS document unchanged into an OWL Lite document. Aditional type declarations may be needed in the importing document.
0 is the only xsd:nonNegativeInteger which is also an xsd:nonPositiveInteger.
A simple infinite loop for implementors to avoid.
DL Test: t6f.1 Double blocking example. The concept should be incoherent but needs double blocking
owl:sameIndividualAs is not an OWL property.
This explores aliases of builtin datatypes.
DL Test: t3a.1 there are 1,701 possible partitions in the satisfiable case
A class like owl:Nothing can be defined using OWL Lite restrictions.
An example combinging owl:oneOf and owl:inverseOf.
Under the rdfs compatible semantics, the previous non-entailment is, in fact, an entailment.
A property with maximum cardinality of two cannot take three distinct values on some subject node. In this example, one of the three values is implicit.
DL Test: heinsohn3.1 Tbox tests from [Heinsohn et al.] Tests incoherency caused by number restrictions and role hierarchy
There are 256 different values for xsd:byte.
The order of the classes in an intersectionOf construct is unimportant.
The inverse entailment of test 002 also holds.
If prop belongs to owl:InverseFunctionalProperty, and object denotes a resource which is the object of two prop triples, then the subjects of these triples have the same denotation.
Two classes may have the same class extension.
Abstract syntax restrictions with multiple components are in OWL DL.
0 is the only xsd:nonNegativeInteger which is also an xsd:nonPositiveInteger. 0 is an xsd:short.
The triple asserts something of type owl:Nothing, however that is the empty class.
DL Test: k_d4 ABox test from DL98 systems comparison.
The extension of OWL Thing may not be empty.
Annotation properties refer to a class instance. equivalentClass refers to the class extension.
A more difficult prime factorization example.
This test shows a potential misapplication of OWL Full comprehension rules. It also shows optional type triples on an owl:Class.
DL Test: t3.2 There are 301 possible partitions in the unsatisfiable case
DL Test: k_poly ABox test from DL98 systems comparison. (Modified in light of implementation feedback, see test description-logic-208).
This non-entailment can be replicated for any three natural numbers i, j, k such that i+j < k. In this example, they are chosen as 200, 300 and 600.
Definitional Constraints on Conjunctive Types
This shows a simple inconsistency depending on the datatype rdf:XMLLiteral. This file is inconsistent with a datatype theory which supports rdf:XMLLiteral, and consistent otherwise.
Structure sharing is not permitted in OWL DL, between an owl:equivalentClass triple and an owl:disjointWith triple.
A further example that cannot be generated from the mapping rule for DisjointClasses.
This is a variation of equivalentClass-001, showing the use of owl:Ontology triples in the premises and conclusions.
The type declarations required by semantic layering can be imported into an OWL Lite or OWL DL file.
A simple example showing how owl:someValuesFrom differs from owl:allValuesFrom.
DL Test: t6.1 Double blocking example. The concept should be incoherent but needs double blocking
owl:equivalentClass is not related to annotations on classes.
The construct used here shows how to express mutual disjointness between classes with O(N) triples.
Range restrictions should not be separate URIs
The semantics of annotations in the direct semantics strictly distinguishes class valued annotations from individual valued annotations.
A property with maximum cardinality of two cannot take three distinct values on some subject node.
If p and q have the same property extension then they p samePropertyAs q.
Annotation properties refer to a class instance. sameIndividualAs, in OWL Full, also refers to the class instance.
There are only 256 different values for xsd:byte.
This document is OWL Lite according to the 3rd February working draft and to the 15th February editor's draft .
When importing a file that uses an xml:base declaration, if you use a different URL in an owl:imports triple, that URL may be without an explicit type.
Under the RDFS compatible semantics the entailment holds.
-1 is an xsd:short that is not an xsd:unsignedShort; 100000 is an xsd:unsignedInt that is not an xsd:unsignedShort; but there are no xsd:unsignedShort which are neither xsd:short nor xsd:unsignedInt
Test illustrating extensional semantics of owl:SymmetricProperty.
The extension of owl:Thing may not be emtpy in OWL Full.
The name UnambiguousProperty is not defined in the OWL namespace. daml:UnambiguousProperty corresponds to owl:InverseFunctionalProperty.
Prime factorization can be expressed in OWL Full.
Annotations about owl:Class are not related to those about rdfs:Class.
DL Test: t3.1 There are 90 possible partitions in the satisfiable case
This entailment can be replicated for any three natural numbers i, j, k such that i+j >= k. In this example, they are chosen as 200, 300 and 500.
This shows that initial whitespace in an rdf:XMLLiteral is significant within OWL.
Structure sharing is not permitted in OWL DL, between a class description and an owl:disjointWith triple.
This test shows a correct application of OWL Full comprehension rules. It also shows that optional type triples on an owl:Restriction do not replace the obligatory ones.
This test illustrates the use of dataRange in OWL DL. This test combines some of the ugliest features of XML, RDF and OWL.
There are 128 different bytes that are also unsigned integers; and hence also 127.
DL Test: t5f.1 Non-finite model example from paper The concept should be coherent but has no finite model
This test shows integer multiplication in OWL DL. N is 20. M is 30. N times M is not 601.
daml:disjointUnionOf did not make it into OWL.
This kind of pattern comes up a lot in more complex ontologies. Failure to cope with this kind of pattern is one of the reasons that many reasoners have been unable to cope with such ontologies.
DL Test: heinsohn2.1 Tbox tests from [Heinsohn et al.] Tests incoherency caused by number restrictions
An imported ontology must have type owl:Ontology to be in DL.
The name UniqueProperty is not defined in the OWL namespace. daml:UniqueProperty corresponds to owl:FunctionalProperty.
Class valued annotations are different from object valued annotations under the direct semantics.
-1 is an xsd:short that is not an xsd:unsignedByte.
Does OWL provide built in 'model checking' functionality
A simple illustration of symmetric properties.
The extension of OWL Thing may be emtpy.
This test shows a relationship between integer multiplication and OWL Full.
This non-entailment can be replicated for any three natural numbers i, j, k such that i+j < k. In this example, they are chosen as 2, 3 and 6.
This shows that insignificant whitespace in an rdf:XMLLiteral is not significant within OWL.
using oneOfDistinct to derive differentFrom
using AllDifferent to derive differentFrom
This test shows integer multiplication in OWL DL. For some finite K, N times K is 2 times K. M times K is 3 times K. N times M times K is not 5 times K.