This normative version is a compound document.
Non-normative versions consisting of a single HTML file are available
in three sizes:
medium,
large,
and extra large.
The tests of this document are also available in these non-normative formats:
Zip archive of approved tests,
the test Web site.
This document contains and presents test cases for the Web Ontology Language (OWL)
approved by the
Web Ontology Working Group. Many of the test cases illustrate the correct usage
of the Web Ontology Language (OWL), and the formal
meaning of its constructs. Other test cases
illustrate the resolution of issues considered by the Working Group.
Conformance for OWL documents and OWL document checkers is specified.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
Publication as a Proposed Recommendation does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
The design of OWL expressed in earlier versions of these documents
has been widely reviewed and satisfies the Working Group's
technical requirements. The Working Group has addressed
all comments received, making changes as necessary.
During Candidate Recommendation,
many implementations
were reported, covering among them all features of the language.
Changes to
this document since the Candidate Recommendation version
are detailed in the change log.
W3C Advisory Committee Representatives are now invited to submit their
formal review via Web form, as described in the Call
for Review. Additional comments may be sent to a Team-only list, w3t-semweb-review@w3.org.
The public is invited to send comments to
public-webont-comments@w3.org
(archive)
and to participate in general discussion of related technology
at www-rdf-logic@w3.org (archive).
The review period extends until 19 January 2004.
As part of the definition of the Web Ontology Language (OWL)
the Web Ontology Working Group provides a
set of test cases. This document
presents those test cases.
They are intended to provide examples for, and clarification
of, the normative definition of OWL
found in
[OWL Semantics and Abstract Syntax]
to which this document is subsidiary.
This document is one component of the description of OWL, the Web Ontology
Language, being produced by the W3C Web Ontology Working Group.
The Document Roadmap section
of the
[OWL Overview] describes each of the different parts
and how they fit together.
This document describes the various types of test used
and the format in which the tests
are presented.
Alternative formats of the test collection are provided.
These are intended to be suitable
for use by OWL developers in test harnesses,
possibly as part of a test driven development process,
such as Extreme Programming [XP].
The format of the Manifest files
used as part of these alternative formats is described.
In the non-normative appendices, this document also
describes the
process for creation and approval of these tests.
However, the test cases do not constitute a conformance test
suite for OWL,
since they are silent
on several important issues. This document cannot be considered a
complete specification of OWL.
The tests illustrate issue resolutions, and illustrate the use and meaning
of
the terms in the OWL namespace.
There are
other miscellaneous tests:
some
arising in the literature, and in preexisting systems;
others intending to show the difficulty of
complete implementations of OWL Full.
Of the deliverables the only normative tests are
those included
in this document. All other deliverables
are informative. Moreover, the recommendation document is
informative except for the conformance statements, the
test data (specified in RDF/XML
[RDF/XML Syntax]), and the supporting documentation.
The
Web Ontology Working Group
has seen adequate implementation experience of
most of the tests in this document. Some, however, are particularly difficult
to implement efficiently. These are labelled as extra credit tests. Such
tests indicate the semantics of OWL, but may use features that are not
sufficiently widely implemented to provide good interoperability.
A general case of extra credit tests is that all OWL Full
nonentailments
and consistency tests are extra credit tests.
This is because typical OWL Full
implementations prove entailments but cannot prove nonentailments.
Extra credit tests are labelled with "EC" within this document and with
statusEXTRACREDIT in the manifest files.
The name indicates that there is no expectation that any implementation will
successfully run such tests and any that do gain extra credit.
Each test consists of one or more RDF/XML documents and a Manifest
file.
Tests of one document indicate some property of that document
when viewed as an OWL knowledge base.
Tests of two or more documents indicate a relationship between the two documents
when viewed as OWL knowledge bases.
The Manifest
file is named ManifestNNN.rdf (The NNN
is replaced by the test number).
It contains metadata (in RDF) indicating the test type,
and describing the test.
The metadata also indicates
the language levels appropriate for each test and each document in each test.
For each RDF/XML document, one language level is indicated, being OWL Lite, OWL DL or OWL Full,
as given by the syntactic rules in
[OWL Semantics and Abstract Syntax].
For semantic tests, one or two language levels are indicated.
If the language level OWL Full is indicated for a semantic test, then
the test holds according to the
RDF-Compatible Model-Theoretic Semantics
in [OWL Semantics and Abstract Syntax].
If the language level OWL Lite or OWL DL is indicated for a semantic test, then
the test holds according to the
Direct Model-Theoretic Semantics
in [OWL Semantics and Abstract Syntax].
If the language level OWL Lite is indicated for a semantic test, then the test only uses
features within the OWL Lite sublanguage.
These tests use one document.
It is named badNNN.rdf.
This document includes a use of the OWL namespace with a local name
that is not defined by the OWL recommendation. An OWL Syntax checker SHOULD
give a warning.
Note: These tests are intended to help migration
from DAML+OIL [DAML+OIL],
since the local names chosen are defined in the DAML+OIL namespace.
These tests use two documents.
One is named premisesNNN.rdf,
the other is named conclusionsNNN.rdf.
The conclusions are
entailed by the premises.
Such entailment is defined by the OWL semantics [OWL Semantics and Abstract Syntax],
(see also
OWL Full entailment).
These tests use two documents.
One is named premisesNNN.rdf,
the other is named nonconclusionsNNN.rdf.
The nonconclusions are not
entailed
by the premises.
Such entailment is defined by the OWL semantics [OWL Semantics and Abstract Syntax],
(see also
OWL Full entailment).
These tests use one document.
It is named conclusionsNNN.rdf.
The conclusions follow from the OWL semantics
[OWL Semantics and Abstract Syntax].
These tests are a special case of the entailment tests
in which the premises are empty.
These tests use one document.
It is named conclusionsNNN.rdf.
These are a special case of true tests.
The conclusions follow from the
OWL Full semantics[OWL Semantics and Abstract Syntax].
The tests are intended to illustrate how
OWL Full can be used to describe its own properties and
classes.
These tests use more than two documents.
One is named premisesNNN.rdf,
another is named conclusionsNNN.rdf, the rest have names
like supportNNN-A.rdf.
The support documents are in the
imports closure of the
premises document.
The conclusions are
entailed
by the
imports closure
of the premises.
Such entailment is defined by the OWL semantics [OWL Semantics and Abstract Syntax],
(see also
OWL Full entailment).
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.
In addition, an OWL Syntax Checker SHOULD report a warning if
the
RDF graph
[RDF Concepts]
corresponding to the document
uses any URI references
starting with the prefix http://www.w3.org/2002/07/owl#
except those found in the
[RDF Schema for OWL].
An OWL
syntax checker SHOULD report network errors occurring
during the computation of the imports closure.
An OWL
consistency checker MUST be sound:
it MUST
return Consistent only when the
input document is consistent and Inconsistent only when the input
document is not consistent, with respect to the datatype theory of the checker.
An OWL consistency checker is
complete and terminating,
if, given sufficient (but
finite) resources (CPU cycles and memory)
and the absence of
network errors, it will always return
either Consistent or Inconsistent. It has
been shown that for OWL Lite and DL it is possible to construct a
complete and terminating consistency checker
(the languages are decidable),
and that
for OWL full it is not possible to construct a complete and terminating
consistency
checker (the language is undecidable,
[Practical Reasoning]).
Note:
The usage of the word 'complete' in this section
follows the conventions of the description logic community.
In some other communities the word 'complete'
is used in a weaker sense, refering to the
detection
of inconsistency by logical inference systems.
An OWL consistency checker
can be tested using appropriate consistency
and inconsistency tests.
Appropriate tests are those
of an appropriate level and for which the checker has appropriate datatype support.
The level of the test indicates the semantic theory being used,
which may differ from the level of the file. For example, test Thing-004
contains an OWL DL file which is consistent as an OWL DL consistency test, but
inconsistent as an OWL Full consistency test.
If there are any datatypes that are required to be not supported by the test,
then they must not be supported by the
datatype theory of the checker (in some cases it may be sufficient
for only some of them to be not supported).
Where otest is bound to
http://www.w3.org/2002/03owlt/testOntology#
and rtest is bound to
http://www.w3.org/2000/10/rdf-tests/rdfcore/testSchema#.
The name of the original author of the test is shown using a
dc:creator property, see [Dublin Core].
A description of the test is given (using XHTML markup [XHTML])
as the value of the rtest:description property.
An issue, if any, from the OWL Issues list [OWL Issues], is
the value of a rtest:issue property.
An appropriate language feature, from the OWL namespace, if any, is
the value of the otest:feature property.
The input documents with the test data are found as the value of
the rtest:inputDocument property or
as the value of both the
rtest:premiseDocument and
the
rtest:conclusionDocument.
The support files for import entailment tests, import level tests
and test imports-002 are found
as the values of otest:importedPremiseDocument.
The conformance levels associated with both files and tests
are given with the otest:level property.
The value for each document is one of
otest:Full, otest:DL,
otest:Lite or otest:Other.
Each test is explicitly associated with one or two levels.
If it is associated with otest:Lite then it
is implicitly suitable for otest:DL.
The datatypes used in the test are given with the
otest:usedDatatype property or with one of its subproperties:
otest:supportedDatatype or otest:notSupportedDatatype.
These
indicate that
the test is only valid when the datatype is supported or not supported respectively
by the
datatype theory being used.
The rtest:status of the test
reflects the process of
appendix A.
It
is given as one of the following levels:
APPROVED
This indicates that the test has been approved by the Web Ontology Working Group,
and that implementors are expected to implement such functionality.
EXTRACREDIT
This indicates that the test has been approved by the Web Ontology Working Group,
but that implementors are
not expected to implement such functionality.
PROPOSED
This indicates that the test is awaiting approval.
OBSOLETED
The test, which was proposed or approved,
has ceased to be appropriate.
REJECTED
The Web Ontology Working Group rejected the test (not used).
These tests are ones that are either known from the literature
(for instance, from [Heinsohn et al.]),
or from test suites contributed by
Network Inference,
or developed by the Working Group.
The following additional namespace prefix is used in this section:
oiled
http://oiled.man.example.net/test#
In the N3 syntax [N3] used for namespace declarations,
this as as follows:
These tests
are ones that do not fit any other category.
Some are taken from the [OWL Guide];
others reflect various aspects of OWL, that
were not formal issues addressed by the Working Group.
There is no expectation that any implementation will successfully run
the tests in this section; any that do gain extra credit.
The intent is to illustrate the semantics of OWL, particularly OWL Full,
as specified by
[OWL Semantics and Abstract Syntax],
with the specific goal of showing that it is possible to say things
that it is not reasonable to expect an implementation to completely
understand.
Tests are created by members of the Working Group.
An (optional)
test editor is provided to facilitate this.
Tests are then placed
in the appropriate directory in the
test Web site.
This is done using CVS access to the W3C CVS server
[W3C CVS].
When created, tests are given a status of "PROPOSED".
The author of the test creates a Manifest file in the directory
of the new test, identifying:
The creator of the test.
The test type.
A description of the test.
The RDF/XML files used in the test.
The status as "PROPOSED".
At least one of:
An OWL feature that the test illustrates (by reference to the name of
some property or class in the OWL namespace).
An issue that the test case is related to (by reference to the issue URI
as specified in the OWL issues list [OWL Issues]).
At the chair's discretion, individual tests or groups of tests are put to the Working Group
in the weekly telecon or at a face-to-face meeting.
Tests are approved by Working Group decision,
with status 'APPROVED' or 'EXTRACREDIT'.
The Working Group may take account of favorable review
of the tests and/or implementation reports, as well as other factors.
If the Working Group approves a test, then it is included in the test case document.
The Working Group may reject a test, in which case its status is
changed to "REJECTED". This does not indicate that the
converse of the test has been accepted. There may be stylistic
or other grounds for rejecting technically correct tests.
The Working Group has complete discretion to approve or reject tests
independent of their conformance with this process or their conformance
with the OWL Working Drafts.
In the light of new information, and at the chairs' discretion, the Working Group
may review any previous decision regarding any test cases. The status of
"OBSOLETED" may be used where a test has ceased to be appropriate.
There is a preference for the following stylistic
rules.
None of these rules is obligatory, but test authors should be
minded that it will be easier to gain Working Group consensus
if they follow these rules.
Test and manifest files should have an xml:base attribute
[XMLBASE]
on
the document element. This should show the preferred URL
of the document, from which it is actually retrievable.
Files that contain no relative URIs may omit the xml:base attribute.
All URLs in the test and manifest files should be retrievable Web resources
except for those that use domain names with "example" as the penultimate
component (e.g. "http://www.example.org/ontology#prop").
The following copyright statement should be included as an XML
comment in every test file:
<!--
Copyright World Wide Web Consortium, (Massachusetts Institute of
Technology, European Research Consortium for Informatics and
Mathematics, Keio University).
All Rights Reserved.
Please see the full Copyright clause at
<http://www.w3.org/Consortium/Legal/copyright-software.html>
$Id: Overview.html,v 1.7 2018/10/09 13:18:40 denis Exp $
-->
Tests that relate principally
to some owl property or class, should be put in a directory
named using the local name of that property of class.
Otherwise, tests that relate to an issue should be put in a directory
named like I3.4 where the issue number is taken from the OWL issue list
[OWL Issues].
Both the approved and proposed tests
are shown both in RDF/XML, which is their normative
form, and in a triples format. This lists the triples
as subject, predicate and object, similar to the
N-triples format
described in [RDF Test Cases].
The following additional conventions are used:
Qnames
stand in for URI references.
Relative URLs are permitted and are with respect to:
http://www.w3.org/2002/03owlt/.
The following namespace prefixes are used throughout:
rdf
http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs
http://www.w3.org/2000/01/rdf-schema#
owl
http://www.w3.org/2002/07/owl#
xsd
http://www.w3.org/2001/XMLSchema#
first
The URL of the first file concatenated with #. The first file
is that named premisesNNN.rdf, badNNN.rdf, consistentNNN.rdf, inconsistentNNN.rdf
or importsNNN.rdf depending
on the
test type. (Not used for true tests or
OWL for OWL tests
).
second
The URL of the second file concatenated with #.
The second file is named conclusionsNNN.rdf, nonconclusionsNNN.rdf or mainNNN.rdf depending
on the
test type.
In the N3 syntax [N3] used for namespace declarations,
the first four appear as follows:
The following people have contributed tests to this document:
Sean Bechhofer,
Ian Horrocks,
Peter F. Patel-Schneider,
Jeff Heflin,
Dan Connolly,
the Guide editors,
Jonathan Borden,
Charles White,
Martin Drst, Masayasu Ishikawa,
Jim Hendler,
Herman ter Horst,
Dave Reynolds,
and the editors.
Ian Horrocks contributed to the conformance section of this document.
Sandro Hawke created the
tests results page,
that
has been a great help during the Candidate Recommendation phase.
We thank those who gave test reports and other feedback
during the Candidate Recommendation:
Ken Baclawski,
Sean Bechhofer,
Ian Dickinson,
Michael Grove,
Sandro Hawke,
Ian Horrocks,
Minsu Jang,
Gary Ng,
Mehrdad Omidvari,
Bijan Parsia,
Peter F. Patel-Schneider,
Dave Reynolds,
Rob Shearer,
Evren Sirin,
Charles White
and
Youyong Zou.
We also thank the many others who helped develop the systems which
produced these reports.
This document is the result of extensive discussions within the
Web Ontology Working Group
as a whole. The partipants in this Working Group included:
Yasser alSafadi, Jean-François Baget, James Barnette, Sean
Bechhofer, Jonathan Borden, Stephen Buswell, Jeremy Carroll, Dan
Connolly, Peter Crowther, Jonathan Dale, Jos De Roo, David De
Roure, Mike Dean, Larry Eshelman, Jérôme Euzenat, Tim
Finin, Nicholas Gibbins, Sandro Hawke, Patrick Hayes, Jeff Heflin,
Ziv Hellman, James Hendler, Bernard Horan, Masahiro Hori, Ian
Horrocks, Jane Hunter, Rüdiger Klein, Natasha Kravtsova, Ora
Lassila, Deborah McGuinness, Enrico Motta, Leo Obrst, Mehrdad
Omidvari, Martin Pike, Marwan Sabbouh, Guus Schreiber, Noboru
Shimizu, Michael K. Smith, John Stanton, Lynn Andrea Stein, Herman
ter Horst, David Trastour, Frank van Harmelen, Bernard Vatant,
Raphael Volz, Evan Wallace, Christopher Welty, Charles White,
Frederik Brysse, Francesco Iannuzzelli, Massimo Marchiori, Michael
Sintek and John Yanosy.
On
1st December,
the WG decided to change the status
of
6 tests
from APPROVED to EXTRACREDIT. These tests involved datatypes other than
xsd:integer and xsd:string.
Changed test
description-logic-208
in light of implementation experience
from
Bechhofer
,
Omidvari
,
Sirin
,
De Roo
.
Note that no other rationale for this change is provided - i.e.
no human intelligible justification is given.
Introduced non-entailment
description-logic-209
to capture the implementation feedback.
The tests mentioned here are associated with technical changes or nonchanges,
in [OWL Semantics and Abstract Syntax],
as agreed by the WG, in response to comments during the CR.
Many of the tests in the
Candidate Recommendation of 18th August were in fact incorrect,
when compared with the
mapping rules in the corresponding
Semantics and Abstract Syntax. Every Ontology
must include a triple with predicate rdf:type and object owl:Ontology.
This was not intended to impact OWL RDF/XML files, the fix has been to modify the
abstract syntax, as reported in the
change log of
OWL Semantics, dated [3 October 2003].
The new mapping rules still require such a triple
when the ontology uses an ontology property or annotation property.
This is exhibited in the tests
backwardCompatibleWith-001
and
backwardCompatibleWith-002.
Further, since there was
implementor comment concerning this
issue with respect to owl:imports,
we added imports-011 following suggestion of
Jim Hendler,
which includes the pertinent rdf:type owl:Ontology triple
from imports-001.
On 30th October 2003 the WG resolved that
URIs used only as objects of annotation properties do not
need to have an explicit type triple. Test
AnnotationProperty-003
has had its manifest information modified to reflect this (i.e. the test
data did not change but the correct behaviour of an OWL Syntax Checker is
now to return "Lite" on the premises file).
On 30th October 2003 the WG resolved that
URIs used for user defined datatypes
need to have an explicit type triple, tests
I5.8-013,
I5.8-014,
I5.8-015
and
I5.8-016 reflect this issue. The last one is the critical case,
which differs from the S&AS Candidate Recommendation.
ObjectProperty(ID ...
=>
ID rdf:type owl:ObjectProperty .
[opt if one of the last three triples is included]
...
Unfortunately, for ontologies that actually use a declared object property,
which was also an owl:InverseFunctionalProperty,
owl:SymmetricProperty or owl:TransitiveProperty,
the first rule took precedence over the intent of the second. This has been
changed.
The following new tests have been added including syntax which falls foul
of a strict reading of the August 18th rules, but now are in OWL Lite or OWL DL:
SymmeticProperty-002,
SymmeticProperty-003
and
TransitiveProperty-002.
They have also been chosen to exercise semantic features that were not
adequately covered by the
August 18th version of this document.
On 30th October 2003 the WG resolved
that owl:Thing must be non-empty. This only impacts DL tests and
the following tests were modified or added:
Thing-003,
Thing-004 and
Thing-005.
Test
Thing-001
was obsoleted as a result, and the text in the note in
section 4.2.2 that referred to that test as an example had to be updated, to refer to
Thing-004 and
Thing-005
There were continued
comments
concerning the problems of owl:Class
and rdfs:Class. The following tests were added in the hope of
clarifying the situation:
Class-001,
Class-002,
Class-003 and
Class-004,
All references to proposed tests have been deleted (except in appendices A and B).
The proposed test section has been deleted, since all tests have been approved or obsoleted.
The following sentence was deleted from the introduction since it was false:
This document describes the process for conflict
resolution and errata related to these tests.
RDF Test Cases, A. Barstow,
D. Beckett, J. Grant, Editors. W3C Proposed Recommendation 15 December 2003.
This version of the RDF Test Cases is http://www.w3.org/TR/2003/PR-rdf-testcases-20031215/.
The latest version of the RDF Test Cases is
at http://www.w3.org/TR/rdf-testcases/.
XML Base, J. Marsh, Editor,
W3C Recommendation. World Wide Web Consortium, 27 June 2001.
This version of XML Base is http://www.w3.org/TR/2001/REC-xmlbase-20010627/.
The latest version of XML Base is at
http://www.w3.org/TR/xmlbase/.