index.html 91.8 KB

Raw Blame History Permalink

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html
  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

  <meta name="rcsid" content="$Id: Overview.html,v 1.10 2009/11/13 14:31:49 bertails Exp $" />

<title>OWL Web Ontology Language Test Cases</title>

  <style type="text/css" xml:space="preserve">

.Foo {
}

.TestTable {
  page-break-inside: avoid;
}
 .TestType {
    background-color: #d3d3d3;
    color: black;
 }
.TestNumber {
    background-color: #d3d3d3;
    color: black;
 }
.TestDescriptionHead {
    background-color: #e8e8e8;
    color: black;
 }
.TestErrorsHead {
    background-color: #e8e8e8;
    color: black;
 }
.TestNamespacesHead {
    background-color: #e8e8e8;
    color: black;
 }
.TestPartHead {
    background-color: #e8e8e8;
    color: black;
 }
 .TestDescription {
    background-color: #ffec8b;
    color: black;
 }
 .TestTriples {
    background-color: #c0e0e0;
    color: black;
 }
 .TestNamespaces {
    background-color: #c0e0e0;
    color: black;
 }
 .TestRDF {
    background-color: #c8c8f8;
    color: black;
 }

.TestErrors {
    background-color: #ffe8e8;
    color: red;
 }
  .TestRDF pre {
    margin-left: 0em;
    margin-top: 0em;
    margin-bottom: 0em;
    font-family: monospace;
  }
  .TestTriples pre {
    margin-left: 0em;
    margin-top: 0em;
    margin-bottom: 0em;
    font-family: monospace;
  }
  .TestNamespaces pre {
    margin-left: 0em;
    margin-top: 0em;
    margin-bottom: 0em;
    font-family: monospace;
  }


.note  { margin-left: 2em; }

*.todo {
  color: red;
  font-style: italic;
}

*.change {
  color: #33FF33;
}
*.delete {
  color: #FF9900;
  text-decoration: line-through;
}
*.conformance {
  color: #850021;
  font-weight: bold;
  font-style: italic;
}

*.smallcaps {
  font-size: smaller;
}
div.subtoc {padding: 1em; border: solid thin; margin: 1em 0;
    background: #ddd}

  </style>


<link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-REC" />

</head>
<body>
<div class="head"><a href="http://www.w3.org/" shape="rect">

<img height="48" width="72" alt="W3C" src="http://www.w3.org/Icons/w3c_home" />

</a>

<h1><a name="title" id="title" shape="rect">OWL Web Ontology Language <br clear="none" /> Test Cases</a></h1>

<h2><a name="WD" id="WD" shape="rect">W3C Recommendation
10 February 2004</a>
</h2>

      <div id="owl_2_notice" style="border: solid black 1px; padding: 0.5em; background: #FFB;">

	<p style="margin-top: 0; font-weight: bold;">New Version
        Available: OWL 2 <span style="padding-left: 2em;"></span>
        (Document Status Update, 12 November 2009)</p>

	<p style="margin-bottom: 0;">The OWL Working Group has produced
	a W3C Recommendation for a new version of OWL which adds
	features to this 2004 version, while remaining compatible.
	Please see <a href="http://www.w3.org/TR/owl2-overview">OWL 2
	Document Overview</a> for an introduction to OWL 2 and a guide
	to the OWL 2 document set.</p>

      </div>


<dl>


<dt>This version:</dt>


<dd><a href="http://www.w3.org/TR/2004/REC-owl-test-20040210/" shape="rect">http://www.w3.org/TR/2004/REC-owl-test-20040210/</a></dd>

<dt>Latest version:</dt>

<dd><a href="http://www.w3.org/TR/owl-test/" shape="rect">http://www.w3.org/TR/owl-test/</a></dd>

<dt>Previous version:</dt>

<dd><a href="http://www.w3.org/TR/2003/PR-owl-test-20031215/" shape="rect">http://www.w3.org/TR/2003/PR-owl-test-20031215/</a></dd>


<dt>Editors:</dt>

    <dd><a href="http://www-uk.hpl.hp.com/people/jjc/" shape="rect">Jeremy J. Carroll</a>, HP
      &lt;<a href="mailto:jjc@hpl.hp.com" shape="rect">jjc@hpl.hp.com</a>&gt;</dd>
    <dd>
<a href="http://www.agfa.com/w3c/jdroo/" shape="rect">Jos De Roo</a>, AGFA,&lt;<a href="mailto:jos.deroo@agfa.com" shape="rect">jos.deroo@agfa.com</a>&gt;</dd>
</dl>

<p>Please refer to the <a
href="http://www.w3.org/2001/sw/WebOnt/errata#owl-test"><strong>errata</strong></a>
for this document, which may include some normative corrections.</p>
  <p>

    This normative version is a compound document.

Non-normative versions consisting of a single HTML file are available
in three sizes:
<a href="M" shape="rect">medium</a>,
<a href="L" shape="rect">large</a>,
and <a href="XXL" shape="rect">extra large</a>.
The tests of this document are also available in these non-normative formats:
  <a href="approved.zip" shape="rect">Zip archive of approved tests</a>,

<a href="http://www.w3.org/2002/03owlt/" shape="rect">the test Web site</a>. </p>


<p>See also <a href="http://www.w3.org/2001/sw/RDFCore/translation/owl-test">translations</a>.</p>

<p class="copyright">
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright" shape="rect">
Copyright</a> © 2004 <a href="http://www.w3.org/" shape="rect">
<acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup>
(<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/" shape="rect"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/" shape="rect">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer" shape="rect">
liability</a>,
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks" shape="rect">
trademark</a>,
<a href="http://www.w3.org/Consortium/Legal/copyright-documents" shape="rect">document
use</a> and
<a href="http://www.w3.org/Consortium/Legal/copyright-software" shape="rect">software
licensing</a> rules apply.
</p>


<hr />
</div>

<h2><a id="abstract" name="abstract" shape="rect">Abstract</a></h2>
<p>
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.
</p>


<h2><a id="status" name="status" shape="rect">Status of this document</a></h2>


<!-- Start Status-Of-This-Document Text -->

<p>This document has been reviewed by W3C Members and other interested
parties, and it has been endorsed by the Director as a <a
href="http://www.w3.org/2003/06/Process-20030618/tr.html#RecsW3C">W3C
Recommendation</a>.  W3C's role in making the Recommendation is to
draw attention to the specification and to promote its widespread
deployment. This enhances the functionality and interoperability of
the Web.</p>

<p>This is one of <a
href="http://www.w3.org/TR/2004/REC-owl-features-20040210/#s1.1">six
parts</a> of the W3C Recommendation for OWL, the Web Ontology
Language.  It has been developed by the <a
href="http://www.w3.org/2001/sw/WebOnt/">Web Ontology Working
Group</a> as part of the <a href="http://www.w3.org/2001/sw/">W3C
Semantic Web Activity</a> (<a
href="http://www.w3.org/2001/sw/Activity">Activity Statement</a>, <a
href="http://www.w3.org/2001/sw/WebOnt/charter">Group Charter</a>) for
publication on 10 February 2004.  </p>

<p>The design of OWL expressed in earlier versions of these documents
has been widely reviewed and satisfies the Working Group's <a
href="http://www.w3.org/TR/webont-req/"> technical requirements</a>.
The Working Group has addressed <a
href="http://lists.w3.org/Archives/Public/public-webont-comments/">
all comments received</a>, making changes as necessary.  Changes to
this document since <a
href="http://www.w3.org/TR/2003/PR-owl-test-20031215/">the Proposed
Recommendation version</a> are detailed in the <a
href="./#changes-since-PR">change log</a>.</p>

<p>Comments are welcome at <a
href="mailto:public-webont-comments@w3.org">public-webont-comments@w3.org</a>
(<a
href="http://lists.w3.org/Archives/Public/public-webont-comments/">archive</a>)
and general discussion of related technology is welcome at <a
href="mailto:www-rdf-logic@w3.org">www-rdf-logic@w3.org</a> (<a
href="http://lists.w3.org/Archives/Public/www-rdf-logic/"
shape="rect">archive</a>).
</p>

<p>A list of <a href="http://www.w3.org/2001/sw/WebOnt/impls">
implementations</a> is available.</p>

<p>The W3C maintains a list of <a
href="http://www.w3.org/2001/sw/WebOnt/discl" rel="disclosure">any
patent disclosures related to this work</a>.
</p>

<p><em>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 <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p>

<!-- End Status-Of-This-Document Text -->


<hr />


<h2 class="notoc"><a id="toc" name="toc" shape="rect">Table of Contents</a></h2>

<div class="contents">


<ul class="toc">
<li class="tocline"><a href="./#introduction" shape="rect">1. Introduction</a>
<ul class="toc">
<li class="tocline"><a href="./#scope" shape="rect">1.1. Conformance and Scope</a></li></ul></li>
<li class="tocline"><a href="./#deliverables" shape="rect">2. Deliverables (Normative)</a>
<ul class="toc">
<li class="tocline"><a href="./#normativity" shape="rect">2.1. Normative Status</a></li>
<li class="tocline"><a href="./#extraCredit" shape="rect">2.2. Extra Credit Tests</a></li></ul></li>
<li class="tocline"><a href="./#testTypes" shape="rect">3. Test Types (Normative)</a>
<ul class="toc">
<li class="tocline"><a href="./#testBadOwl" shape="rect">3.1. Tests for Incorrect Use of OWL Namespace</a></li>
<li class="tocline"><a href="./#testEntailment" shape="rect">3.2. Entailment Tests</a></li>
<li class="tocline"><a href="./#testNonEntailment" shape="rect">3.3. Non-Entailment Tests</a></li>
<li class="tocline"><a href="./#testTrue" shape="rect">3.4. True Tests</a></li>
<li class="tocline"><a href="./#testOWLforOWL" shape="rect">3.5. OWL for OWL Tests</a></li>
<li class="tocline"><a href="./#testConsistency" shape="rect">3.6. Consistency Tests</a></li>
<li class="tocline"><a href="./#testInconsistency" shape="rect">3.7. Inconsistency Tests</a></li>
<li class="tocline"><a href="./#testImportEntailment" shape="rect">3.8. Import Entailment Tests</a></li>
<li class="tocline"><a href="./#testImportLevel" shape="rect">3.9. Import Level Tests</a></li></ul></li>
<li class="tocline"><a href="./#conformance" shape="rect">4. Conformance (Normative)</a>
<ul class="toc">
<li class="tocline"><a href="./#docConformance" shape="rect">4.1. Document Conformance</a>
<ul class="toc">
<li class="tocline"><a href="./#syntaxConformance" shape="rect">4.1.1. Syntactic Conformance</a></li>
<li class="tocline"><a href="./#consistencyConformance" shape="rect">4.1.2. Semantic Conformance</a></li></ul></li>
<li class="tocline"><a href="./#checkerConformance" shape="rect">4.2. Document Checker Conformance</a>
<ul class="toc">
<li class="tocline"><a href="./#syntaxChecker" shape="rect">4.2.1. Syntax Checker</a></li>
<li class="tocline"><a href="./#consistencyChecker" shape="rect">4.2.2. Consistency Checker</a></li></ul></li></ul></li>
<li class="tocline"><a href="./#running" shape="rect">5. Testing an OWL Implementation (Informative)</a>
<ul class="toc">
<li class="tocline"><a href="./#runningSyntaxChecker" shape="rect">5.1. OWL Syntax Checkers</a></li>
<li class="tocline"><a href="./#runningConsistencyChecker" shape="rect">5.2. OWL Consistency Checker</a></li></ul></li>
<li class="tocline"><a href="./#manifest" shape="rect">6. Manifest Files (Informative)</a></li>
<li class="tocline"><a href="./#approved" shape="rect">7. The OWL Tests (Normative)</a>
<ul class="toc">
<li class="tocline"><a href="byFunction#byFunction" shape="rect">7.1. By Function</a>
<ul class="toc">
<li class="tocline"><a href="byFunction#function-AllDifferent" shape="rect">7.1.1. <code>owl:AllDifferent</code></a></li>
<li class="tocline"><a href="byFunction#function-AnnotationProperty" shape="rect">7.1.2. <code>owl:AnnotationProperty</code></a></li>
<li class="tocline"><a href="byFunction#function-Class" shape="rect">7.1.3. <code>owl:Class</code></a></li>
<li class="tocline"><a href="byFunction#function-DatatypeProperty" shape="rect">7.1.4. <code>owl:DatatypeProperty</code></a></li>
<li class="tocline"><a href="byFunction#function-FunctionalProperty" shape="rect">7.1.5. <code>owl:FunctionalProperty</code></a></li>
<li class="tocline"><a href="byFunction#function-InverseFunctionalProperty" shape="rect">7.1.6. <code>owl:InverseFunctionalProperty</code></a></li>
<li class="tocline"><a href="byFunction#function-Nothing" shape="rect">7.1.7. <code>owl:Nothing</code></a></li>
<li class="tocline"><a href="byFunction#function-Ontology" shape="rect">7.1.8. <code>owl:Ontology</code></a></li>
<li class="tocline"><a href="byFunction#function-Restriction" shape="rect">7.1.9. <code>owl:Restriction</code></a></li>
<li class="tocline"><a href="byFunction#function-SymmetricProperty" shape="rect">7.1.10. <code>owl:SymmetricProperty</code></a></li>
<li class="tocline"><a href="byFunction#function-Thing" shape="rect">7.1.11. <code>owl:Thing</code></a></li>
<li class="tocline"><a href="byFunction#function-TransitiveProperty" shape="rect">7.1.12. <code>owl:TransitiveProperty</code></a></li>
<li class="tocline"><a href="byFunction#function-allValuesFrom" shape="rect">7.1.13. <code>owl:allValuesFrom</code></a></li>
<li class="tocline"><a href="byFunction#function-backwardCompatibleWith" shape="rect">7.1.14. <code>owl:backwardCompatibleWith</code></a></li>
<li class="tocline"><a href="byFunction#function-cardinality" shape="rect">7.1.15. <code>owl:cardinality</code></a></li>
<li class="tocline"><a href="byFunction#function-complementOf" shape="rect">7.1.16. <code>owl:complementOf</code></a></li>
<li class="tocline"><a href="byFunction#function-differentFrom" shape="rect">7.1.17. <code>owl:differentFrom</code></a></li>
<li class="tocline"><a href="byFunction#function-disjointWith" shape="rect">7.1.18. <code>owl:disjointWith</code></a></li>
<li class="tocline"><a href="byFunction#function-distinctMembers" shape="rect">7.1.19. <code>owl:distinctMembers</code></a></li>
<li class="tocline"><a href="byFunction#function-equivalentClass" shape="rect">7.1.20. <code>owl:equivalentClass</code></a></li>
<li class="tocline"><a href="byFunction#function-equivalentProperty" shape="rect">7.1.21. <code>owl:equivalentProperty</code></a></li>
<li class="tocline"><a href="byFunction#function-imports" shape="rect">7.1.22. <code>owl:imports</code></a></li>
<li class="tocline"><a href="byFunction#function-intersectionOf" shape="rect">7.1.23. <code>owl:intersectionOf</code></a></li>
<li class="tocline"><a href="byFunction#function-inverseOf" shape="rect">7.1.24. <code>owl:inverseOf</code></a></li>
<li class="tocline"><a href="byFunction#function-maxCardinality" shape="rect">7.1.25. <code>owl:maxCardinality</code></a></li>
<li class="tocline"><a href="byFunction#function-oneOf" shape="rect">7.1.26. <code>owl:oneOf</code></a></li>
<li class="tocline"><a href="byFunction#function-sameAs" shape="rect">7.1.27. <code>owl:sameAs</code></a></li>
<li class="tocline"><a href="byFunction#function-someValuesFrom" shape="rect">7.1.28. <code>owl:someValuesFrom</code></a></li>
<li class="tocline"><a href="byFunction#function-unionOf" shape="rect">7.1.29. <code>owl:unionOf</code></a></li></ul></li>
<li class="tocline"><a href="byIssue#byIssue" shape="rect">7.2. By Issue</a>
<ul class="toc">
<li class="tocline"><a href="byIssue#issue-I3.2-Qualified-Restrictions" shape="rect">7.2.1. Qualified Restrictions</a></li>
<li class="tocline"><a href="byIssue#issue-I3.4-UnambiguousProperty" shape="rect">7.2.2. UnambiguousProperty</a></li>
<li class="tocline"><a href="byIssue#issue-I4.1-UniqueProp-BadName" shape="rect">7.2.3. UniqueProp BadName</a></li>
<li class="tocline"><a href="byIssue#issue-I4.5-InverseOf" shape="rect">7.2.4. InverseOf</a></li>
<li class="tocline"><a href="byIssue#issue-I4.6-EquivalentTo" shape="rect">7.2.5. EquivalentTo</a></li>
<li class="tocline"><a href="byIssue#issue-I5.1-Uniform-treatment-of-literal-data-values" shape="rect">7.2.6. Uniform treatment of literal data values</a></li>
<li class="tocline"><a href="byIssue#issue-I5.2-Language-Compliance-Levels" shape="rect">7.2.7. Language Compliance Levels</a></li>
<li class="tocline"><a href="byIssue#issue-I5.21-drop-disjointUnionOf" shape="rect">7.2.8. drop-disjointUnionOf</a></li>
<li class="tocline"><a href="byIssue#issue-I5.24-IF-or-IFF-property-properties" shape="rect">7.2.9. IF-or-IFF-property-properties</a></li>
<li class="tocline"><a href="byIssue#issue-I5.26-OWLDLSyntax" shape="rect">7.2.10. OWL DL Sytntax</a></li>
<li class="tocline"><a href="byIssue#issue-I5.3-Semantic-Layering" shape="rect">7.2.11. Semantic-Layering</a></li>
<li class="tocline"><a href="byIssue#issue-I5.5-List-syntax-or-semantics" shape="rect">7.2.12. List syntax or semantics</a></li>
<li class="tocline"><a href="byIssue#issue-I5.8-Datatypes" shape="rect">7.2.13. Datatypes</a></li>
<li class="tocline"><a href="byIssue#issue-I6.1-UnnamedIndividualRestrictions" shape="rect">7.2.14. Unnamed Individual Restrictions</a></li></ul></li>
<li class="tocline"><a href="./#dL" shape="rect">7.3. Additional Description Logic Tests</a>
<ul class="toc">
<li class="tocline"><a href="dl-000-satisfiability#dl-000-satisfiability" shape="rect">7.3.1. Extended Satisfiability Tests</a></li>
<li class="tocline"><a href="dl-100-heinsohn#dl-100-heinsohn" shape="rect">7.3.2. Heinsohn's Tests</a></li>
<li class="tocline"><a href="dl-200-instance#dl-200-instance" shape="rect">7.3.3. DL 98 Instance Tests</a></li>
<li class="tocline"><a href="dl-500-SAT#dl-500-SAT" shape="rect">7.3.4. The 3 SAT Problem</a></li>
<li class="tocline"><a href="dl-600-harderlite#dl-600-harderlite" shape="rect">7.3.5. Difficult OWL Lite Tests</a></li>
<li class="tocline"><a href="dl-900-arith#dl-900-arith" shape="rect">7.3.6. Extended Cardinality Testing</a></li></ul></li>
<li class="tocline"><a href="./#misc" shape="rect">7.4. Miscellaneous Tests</a>
<ul class="toc">
<li class="tocline"><a href="misc-000-guide#misc-000-guide" shape="rect">7.4.1. Examples from the OWL Guide</a></li>
<li class="tocline"><a href="misc-100-syntax#misc-100-syntax" shape="rect">7.4.2. Detailed OWL Lite and OWL DL Syntax</a></li>
<li class="tocline"><a href="misc-200-xmlliteral#misc-200-xmlliteral" shape="rect">7.4.3. Concerning rdf:XMLLiteral</a></li>
<li class="tocline"><a href="misc-300-annotations#misc-300-annotations" shape="rect">7.4.4. Annotations</a></li></ul></li>
<li class="tocline"><a href="./#extraCreditTests" shape="rect">7.5. Extra Credit</a>
<ul class="toc">
<li class="tocline"><a href="extra-000-arithmetic#extra-000-arithmetic" shape="rect">7.5.1. Arithmetic in OWL</a></li></ul></li></ul></li>
<li class="tocline"><a href="./#testProcess" shape="rect">A. Test Creation, Approval and Modification (Historical, Informative)</a>
<ul class="toc">
<li class="tocline"><a href="./#creation" shape="rect">A.1. Creation</a></li>
<li class="tocline"><a href="./#approval" shape="rect">A.2. Approval</a></li>
<li class="tocline"><a href="./#change" shape="rect">A.3. Modification</a></li></ul></li>
<li class="tocline"><a href="./#style" shape="rect">B. Stylistic Preferences (Informative)</a>
<ul class="toc">
<li class="tocline"><a href="./#rdfxml" shape="rect">B.1. Use of RDF/XML</a></li>
<li class="tocline"><a href="./#xmlbase" shape="rect">B.2. Use of <code>xml:base</code></a></li>
<li class="tocline"><a href="./#rdfsuffix" shape="rect">B.3. Use of .rdf Suffix</a></li>
<li class="tocline"><a href="./#no404" shape="rect">B.4. Use of <code>example</code> Domains</a></li>
<li class="tocline"><a href="./#testCopyright" shape="rect">B.5. Copyright</a></li>
<li class="tocline"><a href="./#description" shape="rect">B.6. Description</a></li>
<li class="tocline"><a href="./#directory" shape="rect">B.7. Directory Structure</a></li>
<li class="tocline"><a href="./#numbering" shape="rect">B.8. Test Numbering</a></li>
<li class="tocline"><a href="./#n3format" shape="rect">B.9. Triple Format of Test Data</a></li></ul></li>
<li class="tocline"><a href="testIndex#testIndex" shape="rect">C. Index</a>
<ul class="toc">
<li class="tocline"><a href="testIndex#testIndexFunction" shape="rect">C.1. Index of OWL Feature Tests</a></li>
<li class="tocline"><a href="testIndex#testIndexIssue" shape="rect">C.2. Index of OWL Issue Tests</a></li>
<li class="tocline"><a href="testIndex#testIndexMisc" shape="rect">C.3. Index of Miscellaneous Tests</a></li>
<li class="tocline"><a href="testIndex#testIndexDL" shape="rect">C.4. Index of Description Logic Tests</a></li>
<li class="tocline"><a href="testIndex#testIndexExtra" shape="rect">C.5. Index of Extra Credit Tests</a></li></ul></li>
<li class="tocline"><a href="./#acknowledgments" shape="rect">D. Acknowledgments (Informative)</a></li>
<li class="tocline"><a href="./#changes-since-PR" shape="rect">E. Changes Since Proposed Recommendation</a></li>
<li class="tocline"><a href="./#references" shape="rect">F. References</a></li>


</ul>
</div>
<hr />


<h1><a id="introduction" name="introduction" shape="rect">1. Introduction</a></h1>

<p>
As part of the definition of the Web Ontology Language (OWL)
the Web Ontology Working Group provides  <em>a
set of  <strong>test cases</strong></em>. This document
presents those test cases.
They are intended to provide examples for, and clarification
of, the normative definition of OWL
 found in
<a href="./#ref-OWL_Semantics_and_Abstract_Syntax" shape="rect">[OWL Semantics and Abstract Syntax]</a>
to which this document is subsidiary.
</p>
<p>
This document is one component of the description of OWL, the Web Ontology
Language, being produced by the W3C Web Ontology Working Group.
The <a href="http://www.w3.org/TR/owl-features/#s1.1" shape="rect">Document Roadmap</a> section
of the
<a href="./#ref-OWL_Overview" shape="rect">[OWL Overview]</a> describes each of the different parts
and how they fit together.
</p>
<p>
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 <a href="./#ref-XP" shape="rect">[XP]</a>.
The format of the <code>Manifest</code> files
used as part of these alternative formats is described.
</p>

<p>In the non-normative appendices, this document also
describes the
process for creation and approval of these tests.
</p>

<h2><a id="scope" name="scope" shape="rect">1.1. Conformance and Scope</a></h2>
<p>
Various conformance levels are defined in <a href="./#conformance" shape="rect">this document</a>
in terms
of
<a href="./#ref-OWL_Semantics_and_Abstract_Syntax" shape="rect">[OWL Semantics and Abstract Syntax]</a>.
</p>
<p>
However, the test cases do <em>not</em> 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.
</p>
<p>
The tests illustrate issue resolutions, and illustrate the use and meaning
of
the terms in the OWL namespace.
</p>
<p>
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.

</p>

<h1><a id="deliverables" name="deliverables" shape="rect">2. Deliverables (Normative)</a></h1>
<p>
The deliverables included as part of the test cases are:
</p>
<ul>
<li>The <a href="./" shape="rect">recommendation track document</a>, which normatively includes the tests.</li>
<li>Additional alternative forms of the normative tests. These are also
included in informative appendices to this document.</li>
<li>A zip file including
<ul>
<li>The RDF/XML files that participate in the
tests </li>
<li>Manifest files indicating which tests should be applied to which
test files.</li>
<li>The non-normative alternative forms of the test files.</li>
</ul>
This zip file is a non-normative alternative format.
</li>
<li>
A
<a href="Manifest.rdf" shape="rect">Manifest</a>
file describing all the tests.
</li>
<li>A
<a href="http://www.w3.org/2002/03owlt/" shape="rect">Web site</a>
which includes the files in the zip file.
This also is a non-normative alternative format.</li>
</ul>
<p class="note">
<strong>Note:</strong> Other files can be found
under the top URL of the Web site which are not part
of the deliverable.
</p>
<h2><a id="normativity" name="normativity" shape="rect">2.1. Normative Status</a></h2>
<p>
Of the deliverables the only normative tests are
<a href="./#approved" shape="rect">those</a> 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
<a href="./#ref-RDF_Syntax" shape="rect">[RDF Syntax]</a>), and the supporting documentation.
</p>

<h2><a id="extraCredit" name="extraCredit" shape="rect">2.2. Extra Credit Tests</a></h2>
<p>
The
<a href="http://www.w3.org/2001/sw/WebOnt/" shape="rect">Web Ontology Working Group</a>
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.
</p>
<p>
A general case of extra credit tests is that all  OWL Full
<a href="./#testNonEntailment" shape="rect">nonentailments</a>
and <a href="./#testConsistency" shape="rect">consistency</a> tests are extra credit tests.
This is because typical OWL Full
implementations prove entailments but cannot prove nonentailments.
</p>
<p>
Extra credit tests are labelled with "EC" within this document and with
<a href="./#statusOfTests" shape="rect">status</a>
<span class="smallcaps">EXTRACREDIT</span> in the manifest files.
</p>
<p>
The name indicates that there is no expectation that any implementation will
successfully run such tests and any that do gain extra credit.
</p>

<h1><a id="testTypes" name="testTypes" shape="rect">3. Test Types (Normative)</a></h1>
<p>
Each test consists of one or more RDF/XML documents and a <code>Manifest</code>
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.
</p>
<p>
The <code>Manifest</code>
file is named <code>Manifest<em>NNN</em>.rdf</code> (The <code><em>NNN</em></code>
is replaced by the test number).
It contains metadata (in RDF) indicating the test type,
and describing the test.
</p>
<p>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
<a href="./#ref-OWL_Semantics_and_Abstract_Syntax" shape="rect">[OWL Semantics and Abstract Syntax]</a>.
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
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/rdfs" shape="rect">RDF-Compatible Model-Theoretic Semantics</a>
in <a href="./#ref-OWL_Semantics_and_Abstract_Syntax" shape="rect">[OWL Semantics and Abstract Syntax]</a>.
If the language level OWL Lite or OWL DL is indicated for a semantic test, then
the test holds according to the
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/direct" shape="rect">Direct Model-Theoretic Semantics </a>
in <a href="./#ref-OWL_Semantics_and_Abstract_Syntax" shape="rect">[OWL Semantics and Abstract Syntax]</a>.
If the language level OWL Lite is indicated for a semantic test, then the test only uses
features within the OWL Lite sublanguage.
</p>
<p>Some of the tests require that certain
datatypes are, or are not, supported in the
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/direct.html#datatype_theory" shape="rect">
datatype map</a>
<a href="./#ref-OWL_Semantics_and_Abstract_Syntax" shape="rect">[OWL Semantics and Abstract Syntax]</a>.
These are indicated with the test.
Other datatypes which are used in the test
  are also indicated: the test applies whether or not these are supported in the
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/direct.html#datatype_theory" shape="rect">
datatype map</a> .
The datatypes
<a href="http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#integer" shape="rect"><code>xsd:integer</code></a>, <a href="http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#string" shape="rect"><code>xsd:string</code></a>
from <a href="./#ref-XML_Schema_Datatypes" shape="rect">[XML Schema Datatypes]</a>
are not indicated, even when used or required, since they
<a href="./#minimal-datatype-support" shape="rect">must</a> be supported.
</p>

<h2><a id="testBadOwl" name="testBadOwl" shape="rect">3.1. Tests for Incorrect Use of OWL Namespace</a></h2>
<p>
These tests use one document.
It is named <code>bad<em>NNN</em>.rdf</code>.
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.
</p>
<p class="note">
<strong>Note:</strong> These tests are intended to help migration
from DAML+OIL <a href="./#ref-DAML_OIL" shape="rect">[DAML+OIL]</a>,
since the local names chosen are defined in the DAML+OIL namespace.
</p>
<h2><a id="testEntailment" name="testEntailment" shape="rect">3.2. Entailment Tests</a></h2>
<p>
These tests use two documents.
One is named <code>premises<em>NNN</em>.rdf</code>,
the other is named <code>conclusions<em>NNN</em>.rdf</code>.
The <code>conclusions</code> are
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/direct.html#direct_entails" shape="rect">entailed</a> by the <code>premises</code>.
Such entailment is defined by the OWL semantics <a href="./#ref-OWL_Semantics_and_Abstract_Syntax" shape="rect">[OWL Semantics and Abstract Syntax]</a>,
(see also
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/rdfs.html#rdfs_entails_Full" shape="rect">OWL Full entailment</a>).
</p>
<h2><a id="testNonEntailment" name="testNonEntailment" shape="rect">3.3. Non-Entailment Tests</a></h2>
<p>
These tests use two documents.
One is named <code>premises<em>NNN</em>.rdf</code>,
the other is named <code>nonconclusions<em>NNN</em>.rdf</code>.
The <code>nonconclusions</code> are not
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/direct.html#direct_entails" shape="rect">entailed</a>
 by the <code>premises</code>.
Such entailment is defined by the OWL semantics <a href="./#ref-OWL_Semantics_and_Abstract_Syntax" shape="rect">[OWL Semantics and Abstract Syntax]</a>,
(see also
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/rdfs.html#rdfs_entails_Full" shape="rect">OWL Full entailment</a>).</p>
<p>Exceptionally, <a href="byFunction#imports-002" shape="rect">test imports-002</a> includes a
<a href="http://www.w3.org/2002/03owlt/imports/support002-A" shape="rect">third document</a>.</p>
<h2><a id="testTrue" name="testTrue" shape="rect">3.4. True Tests</a></h2>
<p>
These tests use one document.
It is named <code>conclusions<em>NNN</em>.rdf</code>.
The <code>conclusions</code> follow from the OWL semantics
<a href="./#ref-OWL_Semantics_and_Abstract_Syntax" shape="rect">[OWL Semantics and Abstract Syntax]</a>.
These tests are a special case of the <a href="./#testEntailment" shape="rect">entailment tests</a>
in which the premises are empty.</p>
<h2><a id="testOWLforOWL" name="testOWLforOWL" shape="rect">3.5. OWL for OWL Tests</a></h2>
<p>
These tests use one document.
It is named <code>conclusions<em>NNN</em>.rdf</code>.
These are a special case of <a href="./#testTrue" shape="rect">true tests</a>.
The <code>conclusions</code> follow from the
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/rdfs.html#5.3" shape="rect">OWL Full semantics</a>
<a href="./#ref-OWL_Semantics_and_Abstract_Syntax" shape="rect">[OWL Semantics and Abstract Syntax]</a>.
The tests are intended to illustrate how
OWL Full can be used to describe its own properties and
classes.</p>
<h2><a id="testConsistency" name="testConsistency" shape="rect">3.6. Consistency Tests</a></h2>
<p>
These tests use one document.
It is named <code>consistent<em>NNN</em>.rdf</code>.
The document is
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/direct.html#direct_consistent" shape="rect">consistent</a>
as defined
by the  OWL Semantics <a href="./#ref-OWL_Semantics_and_Abstract_Syntax" shape="rect">[OWL Semantics and Abstract Syntax]</a>,
(see also
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/rdfs.html#rdfs_consistent_Full" shape="rect">OWL Full consistency</a>).
</p>
<h2><a id="testInconsistency" name="testInconsistency" shape="rect">3.7. Inconsistency Tests</a></h2>
<p>
These tests use one document.
It is named <code>inconsistent<em>NNN</em>.rdf</code>.
The document is not
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/direct.html#direct_consistent" shape="rect">consistent</a>
as defined
by the  OWL semantics <a href="./#ref-OWL_Semantics_and_Abstract_Syntax" shape="rect">[OWL Semantics and Abstract Syntax]</a>,
(see also
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/rdfs.html#rdfs_consistent_Full" shape="rect">OWL Full consistency</a>).
</p>
<h2><a id="testImportEntailment" name="testImportEntailment" shape="rect">3.8. Import Entailment Tests</a></h2>
<p>
These tests use more than two documents.
One is named <code>premises<em>NNN</em>.rdf</code>,
another is named <code>conclusions<em>NNN</em>.rdf</code>, the rest have names
like <code>support<em>NNN</em>-A.rdf</code>.
The <code>support</code> documents are in the <a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/rdfs.html#RDF_graph_imports_closure" shape="rect">
imports closure</a>  of the
 <code>premises</code> document.
The <code>conclusions</code> are
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/direct.html#direct_entails" shape="rect">entailed</a>
 by the <a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/rdfs.html#RDF_graph_imports_closure" shape="rect">
imports closure</a>
of the <code>premises</code>.
Such entailment is defined by the OWL semantics <a href="./#ref-OWL_Semantics_and_Abstract_Syntax" shape="rect">[OWL Semantics and Abstract Syntax]</a>,
(see also
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/rdfs.html#rdfs_entails_Full" shape="rect">OWL Full entailment</a>).</p>
<h2><a id="testImportLevel" name="testImportLevel" shape="rect">3.9. Import Level Tests</a></h2>
<p>
These tests use two documents.
One is named <code>imports<em>NNN</em>.rdf</code>,
the other is named <code>main<em>NNN</em>.rdf</code>.
These
 tests indicate the
interaction between <code>owl:imports</code>
and the sublanguage levels of the <code>main</code> document.</p>

<h1><a id="conformance" name="conformance" shape="rect">4. Conformance (Normative)</a></h1>
<h2><a id="docConformance" name="docConformance" shape="rect">4.1. Document Conformance</a></h2>

<h3><a id="syntaxConformance" name="syntaxConformance" shape="rect">4.1.1. Syntactic Conformance</a></h3>
<p>
An <a id="dfn-OWL-Full-document" name="dfn-OWL-Full-document" shape="rect"><dfn class="conformance">OWL Full
document</dfn></a>
is any
<a href="http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/" shape="rect">
RDF/XML document</a> <a href="./#ref-RDF_Syntax" shape="rect">[RDF Syntax]</a>.
</p>
<p>
An <a id="dfn-OWL-DL-document" name="dfn-OWL-DL-document" shape="rect"><dfn class="conformance">OWL DL
document</dfn></a> is an <a href="./#dfn-OWL-Full-document" shape="rect">OWL Full document</a>
such that the
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/rdfs.html#RDF_graph_imports_closure" shape="rect">imports closure</a>
<a href="./#ref-OWL_Semantics_and_Abstract_Syntax" shape="rect">[OWL Semantics and Abstract Syntax]</a>
of the corresponding
<a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-rdf-graph" shape="rect">
RDF graph
</a>
<a href="./#ref-RDF_Concepts" shape="rect">[RDF Concepts]</a>
is an
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/mapping.html#OWL_DL_RDF_graphs" shape="rect">OWL DL ontology in RDF
graph form</a>.
</p>
<p>
An <a id="dfn-OWL-Lite-document" name="dfn-OWL-Lite-document" shape="rect"><dfn class="conformance">OWL Lite
document</dfn></a> is an <a href="./#dfn-OWL-Full-document" shape="rect">OWL Full document</a>
such that the
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/rdfs.html#RDF_graph_imports_closure" shape="rect">imports closure</a>
<a href="./#ref-OWL_Semantics_and_Abstract_Syntax" shape="rect">[OWL Semantics and Abstract Syntax]</a>
of the corresponding
<a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-rdf-graph" shape="rect">
RDF graph
</a>
<a href="./#ref-RDF_Concepts" shape="rect">[RDF Concepts]</a>
is an
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/mapping.html#OWL_Lite_RDF_graphs" shape="rect">OWL Lite ontology in RDF
graph form</a>.
</p>

<h3><a id="consistencyConformance" name="consistencyConformance" shape="rect">4.1.2. Semantic Conformance</a></h3>


<p>
An <a href="./#dfn-OWL-Lite-document" shape="rect">OWL Lite</a> or
<a href="./#dfn-OWL-DL-document" shape="rect">OWL DL</a> document <em>D</em>
is
<a id="dfn-OWL-DL-consistent-document" name="dfn-OWL-DL-consistent-document" shape="rect"><dfn class="conformance">OWL DL consistent</dfn></a> with respect to
a <a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/direct.html#datatype_theory" shape="rect">datatype map</a>
 <em>T</em> if
and only if there is some
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/direct.html#3.1" shape="rect">
abstract OWL interpretation</a>
<em>I</em> with respect
to <em>T</em> such that <em>I</em>
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/direct.html#3.4" shape="rect">
satisfies</a>
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/syntax.html#2.1" shape="rect">
an abstract ontology <em>O</em></a>
corresponding to <em>D</em>,
in which <em>O</em> has a
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/mapping.html#separated_vocabulary" shape="rect">separated vocabulary</a>;
(see
<a href="./#ref-OWL_Semantics_and_Abstract_Syntax" shape="rect">[OWL Semantics and Abstract Syntax]</a>).
</p>
<p>
An
<a href="./#dfn-OWL-Full-document" shape="rect">OWL Full document</a>
<em>D</em> is
<a id="dfn-OWL-Full-consistent-document" name="dfn-OWL-Full-consistent-document" shape="rect"><dfn class="conformance">OWL Full consistent</dfn></a>
with respect to a
<a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210/#defDatatypeMap" shape="rect">datatype map</a>
 <em>T</em>, if and only if there is some
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/rdfs#5.2" shape="rect">
OWL Full interpretation</a> <em>I</em> with respect to <em>T</em> such that
<em>I</em> satisfies all
the RDF graphs in some
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/rdfs#RDF_graph_imports_closure" shape="rect">
imports closed collection</a> containing an RDF
graph corresponding to <em>D</em>.
</p>

<h2><a id="checkerConformance" name="checkerConformance" shape="rect">4.2. Document Checker Conformance</a></h2>
<p>
This section uses the words MUST, MUST NOT, SHOULD and MAY as in <a href="./#ref-RFC_2119" shape="rect">[RFC 2119]</a>.
</p>

<h3><a id="syntaxChecker" name="syntaxChecker" shape="rect">4.2.1. Syntax Checker</a></h3>

<p>
An <a name="dfn-OWL-syntax-checker" id="dfn-OWL-syntax-checker" shape="rect"><dfn class="conformance">OWL
syntax checker</dfn></a>
takes a document as input, and returns one word being one of <code>Lite</code>,
<code>DL</code>, <code>Full</code>, <code>Other</code>.
</p>
<p>
The return value MUST conform with the following:
</p>
<dl>
<dt>Lite</dt>
<dd>The input document is an <a href="./#dfn-OWL-Lite-document" shape="rect">OWL Lite document</a>.</dd>
<dt>DL</dt>
<dd>The input document is an <a href="./#dfn-OWL-DL-document" shape="rect">OWL DL document</a>
 but not an <a href="./#dfn-OWL-Lite-document" shape="rect">OWL Lite document</a>.</dd>
<dt>Full</dt>

<dd>The input document is an <a href="./#dfn-OWL-Full-document" shape="rect">OWL Full document</a>
 but not an <a href="./#dfn-OWL-DL-document" shape="rect">OWL DL document</a>.</dd>
<dt>Other</dt>
<dd>The input document is not an <a href="./#dfn-OWL-Full-document" shape="rect">OWL Full document</a>.</dd>
</dl>
<p>
In addition, an OWL Syntax Checker SHOULD report a warning if
 the
<a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-rdf-graph" shape="rect">
RDF graph
</a>
<a href="./#ref-RDF_Concepts" shape="rect">[RDF Concepts]</a>
corresponding to the document
uses any URI references
starting with the prefix <code>http://www.w3.org/2002/07/owl#</code>
except those found in the
<a href="./#ref-RDF_Schema_for_OWL" shape="rect">[RDF Schema for OWL]</a>.
</p>
<p>
<a name="network_errors" id="network_errors" shape="rect"> </a>
An <a href="./#dfn-OWL-syntax-checker" shape="rect">OWL
syntax checker</a> SHOULD report network errors occurring
during the computation of the imports closure.
</p>
<h3><a id="consistencyChecker" name="consistencyChecker" shape="rect">4.2.2. Consistency Checker</a></h3>
<p>
An <a name="dfn-OWL-consistency-checker" id="dfn-OWL-consistency-checker" shape="rect"><em>OWL consistency checker</em></a>
takes a document as input, and returns one word being <code>Consistent</code>,
<code>Inconsistent</code>, or <code>Unknown</code>.
</p>
<p>
An <a href="./#dfn-OWL-consistency-checker" shape="rect">OWL
consistency checker</a> SHOULD report network errors occurring
during the computation of the imports closure.
</p>
<p>
An <a href="./#dfn-OWL-consistency-checker" shape="rect">OWL
consistency checker</a> MUST provide a means to determine
the datatypes
supported by its
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/direct.html#datatype_theory" shape="rect">datatype map</a>,
<a href="./#ref-OWL_Semantics_and_Abstract_Syntax" shape="rect">[OWL Semantics and Abstract Syntax]</a>; for example, by listing them in its
supporting documentation.
</p>
<p>
An <a href="./#dfn-OWL-consistency-checker" shape="rect">OWL
consistency checker</a> MUST provide a means to determine
the model theory
<a href="./#ref-OWL_Semantics_and_Abstract_Syntax" shape="rect">[OWL Semantics and Abstract Syntax]</a>, it uses (either the
 <a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/direct.html" shape="rect">Direct Model-Theoretic Semantics</a>
or the
 <a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/rdfs.html" shape="rect">RDF-Compatible Model-Theoretic Semantics</a>);
for example, in its
supporting documentation.
</p>
<p>
An <a href="./#dfn-OWL-consistency-checker" shape="rect">OWL
consistency checker</a> MUST be <em>sound</em>:
it MUST
return <code>Consistent</code> only when the
input document is consistent and <code>Inconsistent</code> only when the input
document is not consistent, with respect to the <a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/direct.html#datatype_theory" shape="rect">datatype map</a> of the checker.
</p>
<p>
If an input
document uses datatypes that are not
supported by the <a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/direct.html#datatype_theory" shape="rect">datatype map</a> of
an <a href="./#dfn-OWL-consistency-checker" shape="rect">OWL
consistency checker</a> then it MAY report a warning.
</p>
<p>
An OWL consistency checker is
<a name="dfn-complete-and-terminating" id="dfn-complete-and-terminating" shape="rect"><em>complete and terminating</em></a>,
if, given sufficient (but
finite) resources (CPU cycles and memory)
and the absence of
<a href="./#network_errors" shape="rect">network errors</a>, it will always return
either <code>Consistent</code> or <code>Inconsistent</code>. It has
been shown that for OWL Lite and DL it is possible to construct a
<a href="./#dfn-complete-and-terminating" shape="rect">complete and terminating</a> consistency checker
(the languages are <em>decidable</em>),
and that
for OWL full it is not possible to construct a <a href="./#dfn-complete-and-terminating" shape="rect">complete and terminating</a>
consistency
checker (the language is <em>undecidable</em>,
<a href="./#ref-Practical_Reasoning" shape="rect">[Practical Reasoning]</a>).
</p>
<p>
<a name="minimal-datatype-support" id="minimal-datatype-support" shape="rect">
The </a>
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/direct.html#datatype_theory" shape="rect">
datatype map</a> of
an OWL consistency checker MUST minimally support at least
<a href="http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#integer" shape="rect"><code>xsd:integer</code></a>, <a href="http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#string" shape="rect"><code>xsd:string</code></a>
from <a href="./#ref-XML_Schema_Datatypes" shape="rect">[XML Schema Datatypes]</a>.
</p>
<p>
An <a href="./#dfn-OWL-consistency-checker" shape="rect">OWL consistency checker</a> SHOULD NOT return
<code>Unknown</code>.
<code>Unknown</code>, while sometimes needed, is not
a desired response.
</p>
<p>
Four different conformance classes of
<a href="./#dfn-OWL-consistency-checker" shape="rect">OWL consistency checker</a> are defined.
</p>
<p>
An <a name="dfn-OWL-Lite-consistency-checker" shape="rect"><dfn class="conformance">OWL Lite consistency checker</dfn></a>
is an <a href="./#dfn-OWL-consistency-checker" shape="rect">OWL consistency checker</a> that
takes an <a href="./#dfn-OWL-Lite-document" shape="rect">OWL Lite document</a> as input, and uses the

 <a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/direct.html" shape="rect">Direct Model-Theoretic Semantics</a>.</p>

<p>
An <a name="dfn-OWL-DL-consistency-checker" shape="rect"><dfn class="conformance">OWL DL consistency checker</dfn></a>
is an <a href="./#dfn-OWL-consistency-checker" shape="rect">OWL consistency checker</a> that
takes an <a href="./#dfn-OWL-DL-document" shape="rect">OWL DL document</a> as input and uses the
 <a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/direct.html" shape="rect">Direct Model-Theoretic Semantics</a>.
</p>
<p>
An <a name="dfn-OWL-Full-consistency-checker" shape="rect"><dfn class="conformance">OWL Full consistency checker</dfn></a>
is an <a href="./#dfn-OWL-consistency-checker" shape="rect">OWL consistency checker</a> that
takes an <a href="./#dfn-OWL-Full-document" shape="rect">OWL Full document</a> as input and uses the
 <a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/rdfs.html" shape="rect">RDF-Compatible Model-Theoretic Semantics</a>.
</p>
<p>
The
<a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210/#defDatatypeMap" shape="rect">
datatype map</a>  of an
<a href="./#dfn-OWL-Full-consistency-checker" shape="rect">OWL Full consistency checker</a>
MUST also support
<a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-rdf-XMLLiteral" shape="rect">
<code>rdf:XMLLiteral</code></a> from <a href="./#ref-RDF_Concepts" shape="rect">[RDF Concepts]</a>,
 see <a href="./#ref-RDF_Semantics" shape="rect">[RDF Semantics]</a>.
</p>
<p>
A <a name="dfn-complete-OWL-Lite-consistency-checker" shape="rect"><dfn class="conformance">complete OWL Lite consistency checker</dfn></a>
is an <a href="./#dfn-OWL-Lite-consistency-checker" shape="rect">OWL Lite consistency checker</a> that
is <a href="./#dfn-complete-and-terminating" shape="rect">complete and terminating</a>.
</p>
<div class="note">
<p><strong>Note:</strong>
An <a href="./#dfn-OWL-Full-consistency-checker" shape="rect">OWL Full consistency checker</a>
may indicate that an OWL DL document is inconsistent, while
an <a href="./#dfn-OWL-DL-consistency-checker" shape="rect">OWL DL consistency checker</a>
indicates that the same document is consistent, (for example: compare test
<a href="byFunction#Thing-005" shape="rect">Thing-005</a> with <a href="byFunction#Thing-004" shape="rect">Thing-004</a> or
compare <a href="byFunction#AnnotationProperty-001" shape="rect">AnnotationProperty-001</a> with <a href="byFunction#AnnotationProperty-002" shape="rect">AnnotationProperty-002</a>).
Every  <a href="./#dfn-OWL-DL-consistency-checker" shape="rect">OWL DL consistency checker</a>
is also an <a href="./#dfn-OWL-Lite-consistency-checker" shape="rect">OWL Lite consistency checker</a>.
</p>
</div>


<div class="note">
<p><strong>Note:</strong>

A
<a href="./#dfn-complete-OWL-Lite-consistency-checker" shape="rect">complete OWL Lite consistency checker</a>
MAY return <code>Unknown</code> for an  <a href="./#dfn-OWL-Lite-document" shape="rect">OWL Lite document</a> in the case where
a resource limit has been exceeded.
</p>
<p><strong>Note:</strong>
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.
</p>
</div>


<h1><a id="running" name="running" shape="rect">5. Testing an OWL Implementation (Informative)</a></h1>

<h2><a id="runningSyntaxChecker" name="runningSyntaxChecker" shape="rect">5.1. OWL Syntax Checkers</a></h2>
<p>
An <a href="./#dfn-OWL-syntax-checker" shape="rect">OWL syntax checker</a>
when presented with any of the test files
must return the indicated result.

This includes the
<a href="./#extraCredit" shape="rect">extra credit tests</a>.

</p>
<h2><a id="runningConsistencyChecker" name="runningConsistencyChecker" shape="rect">5.2. OWL Consistency Checker</a></h2>
<p>
An <a href="./#dfn-OWL-consistency-checker" shape="rect">OWL consistency checker</a>
can be tested using appropriate <a href="./#testConsistency" shape="rect">consistency</a>
and <a href="./#testInconsistency" shape="rect">inconsistency tests</a>.
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 <a href="byFunction#Thing-004" shape="rect">Thing-004</a>
contains an OWL DL file which is consistent as an OWL DL consistency test, but
inconsistent as an <a href="byFunction#Thing-005" shape="rect">OWL Full consistency test</a>.
</p>
<p>An <a href="./#dfn-OWL-consistency-checker" shape="rect">OWL consistency checker</a>
has
<a name="dfn-appropriate-datatypes" shape="rect">appropriate datatype support</a>
for a test if both:
</p>
<ul>
<li>Its
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/direct.html#datatype_theory" shape="rect">datatype map</a>,
<a href="./#ref-OWL_Semantics_and_Abstract_Syntax" shape="rect">[OWL Semantics and Abstract Syntax]</a>
supports all the datatypes that are required to be supported by the test.
</li>
<li>
If there are any datatypes that are required to be not supported by the test,
  then they must not be supported by the
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/direct.html#datatype_theory" shape="rect">datatype map</a> of the checker (in some cases it may be sufficient
for only some of them to be not supported).
</li>
</ul>
<p>
An <a href="./#dfn-OWL-Lite-consistency-checker" shape="rect">OWL Lite consistency checker</a>
with
<a href="./#dfn-appropriate-datatypes" shape="rect">appropriate datatype support</a>,
when presented with a file from
an OWL Lite <a href="./#testConsistency" shape="rect">consistency test</a>,
must return <code>Consistent</code>
or <code>Unknown</code>.
</p>
<p>
An <a href="./#dfn-OWL-DL-consistency-checker" shape="rect">OWL DL consistency checker</a>
with
<a href="./#dfn-appropriate-datatypes" shape="rect">appropriate datatype support</a>,
when presented with a file from
an OWL DL or OWL Lite <a href="./#testConsistency" shape="rect">consistency test</a>,
must return <code>Consistent</code>
or <code>Unknown</code>.
</p>
<p>
An <a href="./#dfn-OWL-Full-consistency-checker" shape="rect">OWL Full consistency checker</a>
with
<a href="./#dfn-appropriate-datatypes" shape="rect">appropriate datatype support</a>,
when presented with a file from
an OWL Full <a href="./#testConsistency" shape="rect">consistency test</a>,
must return <code>Consistent</code>
or <code>Unknown</code>.
</p>
<p>
The corresponding <a href="./#testInconsistency" shape="rect">inconsistency tests</a> must return
<code>Inconsistent</code> or <code>Unknown</code>.</p>
<p>
A <a href="./#dfn-complete-OWL-Lite-consistency-checker" shape="rect">complete OWL Lite consistency checker</a>
  should not return <code>Unknown</code> on the OWL Lite
<a href="./#testConsistency" shape="rect">consistency</a>
or <a href="./#testInconsistency" shape="rect">inconsistency</a> tests, regardless of the use of
unsupported datatypes.
</p>

<p>
The above constraints also apply to
<a href="./#extraCredit" shape="rect">extra credit tests</a>.
Consistency checkers that return the correct answer (i.e. not <code>Unknown</code>)
gain the extra credit.
</p>

<h1><a id="manifest" name="manifest" shape="rect">6. Manifest Files (Informative)</a></h1>
<p>
The <code>Manifest</code> file follows the RDF schema developed
for the RDF Test Cases <a href="./#ref-RDF_Tests" shape="rect">[RDF Tests]</a>.
</p>
<p>
This is augmented by a few new properties and types
which are declared in the OWL Test Ontology, found
at <a href="http://www.w3.org/2002/03owlt/testOntology" shape="rect">http://www.w3.org/2002/03owlt/testOntology</a>.
</p>
<p>
Specifically each test has its own <code>Manifest</code> file, and is identified from
the URI reference formed from the <code>Manifest</code> file's URL with a fragment <code>test</code>.
</p>
<p>
The test has one <code>rdf:type</code> explicit, and this is one of:
</p>
<dl>
<dt><code>otest:NotOwlFeatureTest</code></dt>
<dd><a href="./#testBadOwl" shape="rect">A test for the incorrect use of the OWL namespace name.</a></dd>

<dt><code>otest:PositiveEntailmentTest</code></dt>
<dd><a href="./#testEntailment" shape="rect">An entailment test.</a></dd>


<dt><code>otest:NegativeEntailmentTest</code></dt>
<dd><a href="./#testNonEntailment" shape="rect">A non-entailment test.</a></dd>


<dt><code>otest:TrueTest</code></dt>
<dd><a href="./#testTrue" shape="rect">A true test.</a></dd>


<dt><code>otest:OWLforOWLTest</code></dt>
<dd><a href="./#testOWLforOWL" shape="rect">An OWL for OWL test.</a></dd>

<dt><code>otest:ConsistencyTest</code></dt>
<dd><a href="./#testConsistency" shape="rect">A consistency test.</a></dd>

<dt><code>otest:InconsistencyTest</code></dt>
<dd><a href="./#testInconsistency" shape="rect">An inconsistency test.</a></dd>
<dt><code>otest:ImportEntailmentTest</code></dt>
<dd><a href="./#testImportEntailment" shape="rect">An import entailment test.</a></dd>
<dt><code>otest:ImportLevelTest</code></dt>
<dd><a href="./#testImportLevel" shape="rect">An import level test.</a></dd>

</dl>
<p>Where <code>otest</code> is bound to
<code>http://www.w3.org/2002/03owlt/testOntology#</code>
and <code>rtest</code> is bound to
<code>http://www.w3.org/2000/10/rdf-tests/rdfcore/testSchema#</code>.
</p>
<p>
The name of the original author of the test is shown using a
<code>dc:creator</code> property, see <a href="./#ref-Dublin_Core" shape="rect">[Dublin Core]</a>.
</p>
<p>
A description of the test is given (using XHTML markup <a href="./#ref-XHTML" shape="rect">[XHTML]</a>)
as the value of the <code>rtest:description</code> property.
</p>
<p>
An issue, if any, from the OWL Issues list <a href="./#ref-OWL_Issues" shape="rect">[OWL Issues]</a>, is
the value of a <code>rtest:issue</code> property.
</p>
<p>
An appropriate language feature, from the OWL namespace, if any, is
the value of the <code>otest:feature</code> property.
</p>
<p>
The input documents with the test data are found as the value of
the <code>rtest:inputDocument</code> property or
as the value of both the
<code>rtest:premiseDocument</code> and
the
<code>rtest:conclusionDocument</code>.
The support files for import entailment tests, import level tests
 and <a href="byFunction#imports-002" shape="rect">test imports-002</a> are found
as the values of <code>otest:importedPremiseDocument</code>.
</p>
<p>
The conformance levels associated with both files and tests
are given with the <code>otest:level</code> property.
The value for each document is one of
<code>otest:Full</code>, <code>otest:DL</code>,
<code>otest:Lite</code> or <code>otest:Other</code>.

Each test is explicitly associated with one or two levels.
If it is associated with <code>otest:Lite</code> then it
is implicitly suitable for <code>otest:DL</code>.
</p>
<p>The datatypes used in the test are given with the
<code>otest:usedDatatype</code> property or with one of its subproperties:
<code>otest:supportedDatatype</code> or <code>otest:notSupportedDatatype</code>.
These
indicate that
the test is only valid when the datatype is supported or not supported respectively
by the
<a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/direct.html#datatype_theory" shape="rect">
datatype map</a> being used.
</p>

<a name="statusOfTests" shape="rect"> </a>
<p>
The <code>rtest:status</code> of the test
reflects the process of
<a href="./#testProcess" shape="rect">appendix A</a>.
It
is given as one of the following levels:
</p>
<dl>
<dt class="smallcaps">APPROVED</dt>
<dd>
This indicates that the test has been approved by the Web Ontology Working Group,
and that implementors are expected to implement such functionality.
</dd>
<dt class="smallcaps">EXTRACREDIT</dt>
<dd>
This indicates that the test has been approved by the Web Ontology Working Group,
but that implementors are
<a href="./#extraCredit" shape="rect">not expected</a> to implement such functionality.
</dd>
<dt class="smallcaps">PROPOSED</dt>
<dd>This indicates that the test is awaiting approval.</dd>
<dt class="smallcaps">OBSOLETED</dt>
<dd>The test, which was proposed or approved,
has ceased to be appropriate.</dd>
<dt class="smallcaps">REJECTED</dt>
<dd>The Web Ontology Working Group rejected the test (not used).</dd>
</dl>


<h1><a id="approved" name="approved" shape="rect">7. The OWL Tests (Normative)</a></h1>


<div   class="subtoc"><p><strong>Contents</strong></p><ul class="toc"><li class="tocline"><a href="byFunction#byFunction" shape="rect">7.1. By Function</a>
<ul class="toc">
<li class="tocline"><a href="byFunction#function-AllDifferent" shape="rect">7.1.1. <code>owl:AllDifferent</code></a></li>
<li class="tocline"><a href="byFunction#function-AnnotationProperty" shape="rect">7.1.2. <code>owl:AnnotationProperty</code></a></li>
<li class="tocline"><a href="byFunction#function-Class" shape="rect">7.1.3. <code>owl:Class</code></a></li>
<li class="tocline"><a href="byFunction#function-DatatypeProperty" shape="rect">7.1.4. <code>owl:DatatypeProperty</code></a></li>
<li class="tocline"><a href="byFunction#function-FunctionalProperty" shape="rect">7.1.5. <code>owl:FunctionalProperty</code></a></li>
<li class="tocline"><a href="byFunction#function-InverseFunctionalProperty" shape="rect">7.1.6. <code>owl:InverseFunctionalProperty</code></a></li>
<li class="tocline"><a href="byFunction#function-Nothing" shape="rect">7.1.7. <code>owl:Nothing</code></a></li>
<li class="tocline"><a href="byFunction#function-Ontology" shape="rect">7.1.8. <code>owl:Ontology</code></a></li>
<li class="tocline"><a href="byFunction#function-Restriction" shape="rect">7.1.9. <code>owl:Restriction</code></a></li>
<li class="tocline"><a href="byFunction#function-SymmetricProperty" shape="rect">7.1.10. <code>owl:SymmetricProperty</code></a></li>
<li class="tocline"><a href="byFunction#function-Thing" shape="rect">7.1.11. <code>owl:Thing</code></a></li>
<li class="tocline"><a href="byFunction#function-TransitiveProperty" shape="rect">7.1.12. <code>owl:TransitiveProperty</code></a></li>
<li class="tocline"><a href="byFunction#function-allValuesFrom" shape="rect">7.1.13. <code>owl:allValuesFrom</code></a></li>
<li class="tocline"><a href="byFunction#function-backwardCompatibleWith" shape="rect">7.1.14. <code>owl:backwardCompatibleWith</code></a></li>
<li class="tocline"><a href="byFunction#function-cardinality" shape="rect">7.1.15. <code>owl:cardinality</code></a></li>
<li class="tocline"><a href="byFunction#function-complementOf" shape="rect">7.1.16. <code>owl:complementOf</code></a></li>
<li class="tocline"><a href="byFunction#function-differentFrom" shape="rect">7.1.17. <code>owl:differentFrom</code></a></li>
<li class="tocline"><a href="byFunction#function-disjointWith" shape="rect">7.1.18. <code>owl:disjointWith</code></a></li>
<li class="tocline"><a href="byFunction#function-distinctMembers" shape="rect">7.1.19. <code>owl:distinctMembers</code></a></li>
<li class="tocline"><a href="byFunction#function-equivalentClass" shape="rect">7.1.20. <code>owl:equivalentClass</code></a></li>
<li class="tocline"><a href="byFunction#function-equivalentProperty" shape="rect">7.1.21. <code>owl:equivalentProperty</code></a></li>
<li class="tocline"><a href="byFunction#function-imports" shape="rect">7.1.22. <code>owl:imports</code></a></li>
<li class="tocline"><a href="byFunction#function-intersectionOf" shape="rect">7.1.23. <code>owl:intersectionOf</code></a></li>
<li class="tocline"><a href="byFunction#function-inverseOf" shape="rect">7.1.24. <code>owl:inverseOf</code></a></li>
<li class="tocline"><a href="byFunction#function-maxCardinality" shape="rect">7.1.25. <code>owl:maxCardinality</code></a></li>
<li class="tocline"><a href="byFunction#function-oneOf" shape="rect">7.1.26. <code>owl:oneOf</code></a></li>
<li class="tocline"><a href="byFunction#function-sameAs" shape="rect">7.1.27. <code>owl:sameAs</code></a></li>
<li class="tocline"><a href="byFunction#function-someValuesFrom" shape="rect">7.1.28. <code>owl:someValuesFrom</code></a></li>
<li class="tocline"><a href="byFunction#function-unionOf" shape="rect">7.1.29. <code>owl:unionOf</code></a></li></ul></li></ul></div>
<div   class="subtoc"><p><strong>Contents</strong></p><ul class="toc"><li class="tocline"><a href="byIssue#byIssue" shape="rect">7.2. By Issue</a>
<ul class="toc">
<li class="tocline"><a href="byIssue#issue-I3.2-Qualified-Restrictions" shape="rect">7.2.1. Qualified Restrictions</a></li>
<li class="tocline"><a href="byIssue#issue-I3.4-UnambiguousProperty" shape="rect">7.2.2. UnambiguousProperty</a></li>
<li class="tocline"><a href="byIssue#issue-I4.1-UniqueProp-BadName" shape="rect">7.2.3. UniqueProp BadName</a></li>
<li class="tocline"><a href="byIssue#issue-I4.5-InverseOf" shape="rect">7.2.4. InverseOf</a></li>
<li class="tocline"><a href="byIssue#issue-I4.6-EquivalentTo" shape="rect">7.2.5. EquivalentTo</a></li>
<li class="tocline"><a href="byIssue#issue-I5.1-Uniform-treatment-of-literal-data-values" shape="rect">7.2.6. Uniform treatment of literal data values</a></li>
<li class="tocline"><a href="byIssue#issue-I5.2-Language-Compliance-Levels" shape="rect">7.2.7. Language Compliance Levels</a></li>
<li class="tocline"><a href="byIssue#issue-I5.21-drop-disjointUnionOf" shape="rect">7.2.8. drop-disjointUnionOf</a></li>
<li class="tocline"><a href="byIssue#issue-I5.24-IF-or-IFF-property-properties" shape="rect">7.2.9. IF-or-IFF-property-properties</a></li>
<li class="tocline"><a href="byIssue#issue-I5.26-OWLDLSyntax" shape="rect">7.2.10. OWL DL Sytntax</a></li>
<li class="tocline"><a href="byIssue#issue-I5.3-Semantic-Layering" shape="rect">7.2.11. Semantic-Layering</a></li>
<li class="tocline"><a href="byIssue#issue-I5.5-List-syntax-or-semantics" shape="rect">7.2.12. List syntax or semantics</a></li>
<li class="tocline"><a href="byIssue#issue-I5.8-Datatypes" shape="rect">7.2.13. Datatypes</a></li>
<li class="tocline"><a href="byIssue#issue-I6.1-UnnamedIndividualRestrictions" shape="rect">7.2.14. Unnamed Individual Restrictions</a></li></ul></li></ul></div>


<h2><a id="dL" name="dL" shape="rect">7.3. Additional Description Logic Tests</a></h2>
<p>
These tests are ones that are either known from the literature
(for instance, from <a href="./#ref-Heinsohn_et_al." shape="rect">[Heinsohn et al.]</a>),
or from test suites contributed by <!--DL implementors
(specifically from -->
<a href="http://www.networkinference.com/" shape="rect">Network Inference</a>,
or developed by the Working Group.
<!--and <span class="todo">maybe someone else still</span>)-->
</p>
<p>
The following additional namespace prefix is used in this section:
</p>
<dl>
<dt><code>oiled</code></dt><dd><code>http://oiled.man.example.net/test#</code></dd>
</dl>
<p>
In the N3 syntax <a href="./#ref-N3" shape="rect">[N3]</a> used for namespace declarations,
this as as follows:
</p>
     <table border="1" width="95%" summary="This table defines the rdf, rdfs, and owl namespace prefixes.">
     <tr><td class="TestNamespacesHead" colspan="1" rowspan="1"><strong>Namespaces:</strong></td></tr>
     <tr><td class="TestNamespaces" colspan="1" rowspan="1">
<pre xml:space="preserve">@prefix oiled: &lt;http://oiled.man.example.net/test#&gt; .
</pre></td></tr>
</table>


<div   class="subtoc"><p><strong>Contents</strong></p><ul class="toc"><li class="tocline"><a href="dl-000-satisfiability#dl-000-satisfiability" shape="rect">7.3.1. Extended Satisfiability Tests</a></li></ul></div>

<div   class="subtoc"><p><strong>Contents</strong></p><ul class="toc"><li class="tocline"><a href="dl-100-heinsohn#dl-100-heinsohn" shape="rect">7.3.2. Heinsohn's Tests</a></li></ul></div>

<div   class="subtoc"><p><strong>Contents</strong></p><ul class="toc"><li class="tocline"><a href="dl-200-instance#dl-200-instance" shape="rect">7.3.3. DL 98 Instance Tests</a></li></ul></div>

<div   class="subtoc"><p><strong>Contents</strong></p><ul class="toc"><li class="tocline"><a href="dl-500-SAT#dl-500-SAT" shape="rect">7.3.4. The 3 SAT Problem</a></li></ul></div>

<div   class="subtoc"><p><strong>Contents</strong></p><ul class="toc"><li class="tocline"><a href="dl-600-harderlite#dl-600-harderlite" shape="rect">7.3.5. Difficult OWL Lite Tests</a></li></ul></div>

<div   class="subtoc"><p><strong>Contents</strong></p><ul class="toc"><li class="tocline"><a href="dl-900-arith#dl-900-arith" shape="rect">7.3.6. Extended Cardinality Testing</a></li></ul></div>


<h2><a id="misc" name="misc" shape="rect">7.4. Miscellaneous Tests</a></h2>
<p>
These tests
are ones that do not fit any other category.
Some are taken from the <a href="./#ref-OWL_Guide" shape="rect">[OWL Guide]</a>;
others reflect various aspects of OWL, that
were not formal issues addressed by the Working Group.
</p>


<div   class="subtoc"><p><strong>Contents</strong></p><ul class="toc"><li class="tocline"><a href="misc-000-guide#misc-000-guide" shape="rect">7.4.1. Examples from the OWL Guide</a></li></ul></div>

<div   class="subtoc"><p><strong>Contents</strong></p><ul class="toc"><li class="tocline"><a href="misc-100-syntax#misc-100-syntax" shape="rect">7.4.2. Detailed OWL Lite and OWL DL Syntax</a></li></ul></div>

<div   class="subtoc"><p><strong>Contents</strong></p><ul class="toc"><li class="tocline"><a href="misc-200-xmlliteral#misc-200-xmlliteral" shape="rect">7.4.3. Concerning rdf:XMLLiteral</a></li></ul></div>

<div   class="subtoc"><p><strong>Contents</strong></p><ul class="toc"><li class="tocline"><a href="misc-300-annotations#misc-300-annotations" shape="rect">7.4.4. Annotations</a></li></ul></div>


<h2><a id="extraCreditTests" name="extraCreditTests" shape="rect">7.5. Extra Credit</a></h2>
<p>
There is no expectation that any implementation will successfully run
the tests in this section; any that do gain extra credit.
</p>
<p>
The intent is to illustrate the semantics of OWL, particularly OWL Full,
as specified by
<a href="./#ref-OWL_Semantics_and_Abstract_Syntax" shape="rect">[OWL Semantics and Abstract Syntax]</a>,
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.
</p>


<div   class="subtoc"><p><strong>Contents</strong></p><ul class="toc"><li class="tocline"><a href="extra-000-arithmetic#extra-000-arithmetic" shape="rect">7.5.1. Arithmetic in OWL</a></li></ul></div>


<h1><a id="testProcess" name="testProcess" shape="rect">A. Test Creation, Approval and Modification (Historical, Informative)</a></h1>
<p>
This appendix describes the process that was used during the development of this test suite.
</p>
<h2><a id="creation" name="creation" shape="rect">A.1. Creation</a></h2>
<p>
Tests are created by members of the Working Group.
An (optional)
<a href="http://www.w3.org/2002/03owlt/editors-draft/jsp/edit.jsp" shape="rect">
test editor</a> is provided to facilitate this.
Tests are then placed
in the appropriate directory in the
<a href="http://www.w3.org/2002/03owlt/" shape="rect">test Web site</a>.
This is done using CVS access to the W3C CVS server
<a href="./#ref-W3C_CVS" shape="rect">[W3C CVS]</a>.
</p>
<p>
When created, tests are given a status of <code>"PROPOSED"</code>.
The author of the test creates a Manifest file in the directory
of the new test, identifying:
</p>
<ul>
<li>The creator of the test.</li>
<li>The test type.</li>
<li>A description of the test.</li>
<li>The RDF/XML files used in the test.</li>
<li>The status as <code>"PROPOSED"</code>.</li>
<li>At least one of:
<ul>
<li>An OWL feature that the test illustrates (by reference to the name of
some property or class in the OWL namespace).</li>
<li>An issue that the test case is related to (by reference to the issue URI
as specified in the OWL issues list <a href="./#ref-OWL_Issues" shape="rect">[OWL Issues]</a>).</li>
<li>Some other rationale for the test.</li>
</ul>
</li>
</ul>
<h2><a id="approval" name="approval" shape="rect">A.2. Approval</a></h2>
<p>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.
</p>
<p>Tests are approved by Working Group decision,

with status 'APPROVED' or 'EXTRACREDIT'.

</p>
<p>The Working Group may take account of favorable review
 of the tests and/or implementation reports, as well as other factors.
</p>
<p>
If the Working Group approves a test, then it is included in the test case document.
</p>
<p>
The Working Group may reject a test, in which case its status is
 changed to <code>"REJECTED"</code>. 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.
</p>
<p>
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.
</p>
<p>
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
<code>"OBSOLETED"</code> may be used where a test has ceased to be appropriate.
</p>
<h2><a id="change" name="change" shape="rect">A.3. Modification</a></h2>
<p>The editors may
make editorial changes to approved and proposed tests.
This includes:
</p>
<ul>
<li>Editorial changes to text in the test descriptions.</li>
<li>Fixing of typos and trivial errors.</li>
<li>Moving tests to conform with document naming conventions.</li>
<li>Renaming and renumbering tests and test files.</li>
<li>Substantive changes resulting from other Working Group decisions.</li>
<li>Stylistic changes reflecting changes to the
<a href="./#style" shape="rect">preferences</a> expressed in this document. </li>
</ul>
<h1><a id="style" name="style" shape="rect">B. Stylistic Preferences (Informative)</a></h1>
<p>
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.
</p>
<h2><a id="rdfxml" name="rdfxml" shape="rect">B.1. Use of RDF/XML</a></h2>
<p>
Tests should normally be expressed in RDF/XML.
</p>
<p>
The following RDF/XML grammar rules <a href="./#ref-RDF_Syntax" shape="rect">[RDF Syntax]</a> are not used:
</p>
<ol>
<li>
<a href="http://www.w3.org/TR/rdf-syntax-grammar/#propertyAttr" shape="rect">Property attributes.</a>
</li>
<li>
<a href="http://www.w3.org/TR/rdf-syntax-grammar/#parseTypeResourcePropertyElt" shape="rect"><code>rdf:parseType="Resource"</code>.</a>
</li>
</ol>
<h2><a id="xmlbase" name="xmlbase" shape="rect">B.2. Use of <code>xml:base</code></a></h2>
<p>
Test and manifest files should have an <code>xml:base</code> attribute
<a href="./#ref-XMLBASE" shape="rect">[XMLBASE]</a>
on
the document element. This should show the preferred URL
of the document, from which it is actually retrievable.
</p>
<p>
Files that contain no relative URIs may omit the <code>xml:base</code> attribute.
</p>
<h2><a id="rdfsuffix" name="rdfsuffix" shape="rect">B.3. Use of .rdf Suffix</a></h2>
<p>
Test and manifest files should use the <code>".rdf"</code>
suffix. URIs should not. The URL used for <code>xml:base</code> declarations
does not have a suffix.
</p>

<h2><a id="no404" name="no404" shape="rect">B.4. Use of <code>example</code> Domains</a></h2>
<p>
All URLs in the test and manifest files should be retrievable Web resources
except for those that use domain names with <code>"example"</code> as the penultimate
component (e.g. <code>"http://www.example.org/ontology#prop"</code>).
</p>
<h2><a id="testCopyright" name="testCopyright" shape="rect">B.5. Copyright</a></h2>
<p>
The following copyright statement should be included as an XML
comment in every test file:
</p>

<pre xml:space="preserve">


&lt;!--
  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
  &lt;http://www.w3.org/Consortium/Legal/copyright-software.html&gt;

  $Id: Overview.html,v 1.10 2009/11/13 14:31:49 bertails Exp $
--&gt;
</pre>

<h2><a id="description" name="description" shape="rect">B.6. Description</a></h2>
<p>
The description should:
</p>
<ul>
<li>Link to relevant parts of of the OWL recommendations. </li>
<li>Clearly distinguish syntactic and semantic concerns. </li>
</ul>
<p>The description should be included as an XML comment
in each test file, and be included as RDF content in the Manifest file.
</p>
<h2><a id="directory" name="directory" shape="rect">B.7. Directory Structure</a></h2>
<p>
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.
</p>
<p>
Otherwise, tests that relate to an issue should be put in a directory
named like <code>I3.4</code> where the issue number is taken from the OWL issue list
<a href="./#ref-OWL_Issues" shape="rect">[OWL Issues]</a>.
</p>
<h2><a id="numbering" name="numbering" shape="rect">B.8. Test Numbering</a></h2>
<p>
Each directory should contain tests numbered consecutively from <code>001</code>.
</p>
<p>
No two tests in a single directory should have the same number.
</p>
<p>
Each file in a test should have the number of the test at the end of its name, before the suffix.
</p>
<p>
The rest of the file name should follow the conventions for the test type.
</p>
<p class="note"><strong>Note:</strong>
the approved tests in a directory will not necessarily be contiguously numbered.</p>
<p class="note"><strong>Note:</strong>
this differs from the RDF Core test case numbering conventions.</p>

<h2><a id="n3format" name="n3format" shape="rect">B.9. Triple Format of Test Data</a></h2>
<p>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
<a href="http://www.w3.org/TR/2003/WD-rdf-testcases-20030123/#ntriples" shape="rect">N-triples</a> format
described in <a href="./#ref-RDF_Tests" shape="rect">[RDF Tests]</a>.
The following additional conventions are used:
</p>
<ul>
<li>
Qnames
stand in for URI references.
</li>
<li>Relative URLs are permitted and are with respect to:
<code>http://www.w3.org/2002/03owlt/</code>.</li>
<li>The <a href="http://www.python.org/doc/1.5.1p1/tut/strings.html" shape="rect">triple quotes convention</a> from Python
is sometimes used.</li>
<li>No escaping of non-ASCII characters is required.</li>
</ul>
<p>
The following namespace prefixes are used throughout:
</p>
<dl>
<dt><code>rdf</code></dt><dd><code>http://www.w3.org/1999/02/22-rdf-syntax-ns#</code></dd>
<dt><code>rdfs</code></dt><dd><code>http://www.w3.org/2000/01/rdf-schema#</code></dd>
<dt><code>owl</code></dt><dd><code>http://www.w3.org/2002/07/owl#</code></dd>
<dt><code>xsd</code></dt><dd><code>http://www.w3.org/2001/XMLSchema#</code></dd>
<dt><code>first</code></dt><dd>The URL of the first file concatenated with <code>#</code>. The first file
is that named <code>premises<em>NNN</em>.rdf</code>, <code>bad<em>NNN</em>.rdf</code>, <code>consistent<em>NNN</em>.rdf</code>, <code>inconsistent<em>NNN</em>.rdf</code>
 or <code>imports<em>NNN</em>.rdf</code> depending
on the
<a href="./#testTypes" shape="rect">test type</a>. (Not used for <a href="./#testTrue" shape="rect">true tests</a> or
<a href="./#testOWLforOWL" shape="rect">OWL for OWL tests</a>
).</dd>
<dt><code>second</code></dt><dd>The URL of the second file concatenated with <code>#</code>.
The second file is named <code>conclusions<em>NNN</em>.rdf</code>, <code>nonconclusions<em>NNN</em>.rdf</code> or <code>main<em>NNN</em>.rdf</code> depending
on the
<a href="./#testTypes" shape="rect">test type</a>. </dd>
</dl>

<p>
In the N3 syntax <a href="./#ref-N3" shape="rect">[N3]</a> used for namespace declarations,
the first four appear as follows:
</p>
     <table border="1" width="95%" summary="This table defines the rdf, rdfs, and owl namespace prefixes.">
     <tr><td class="TestNamespacesHead" colspan="1" rowspan="1"><strong>Namespaces:</strong></td></tr>
     <tr><td class="TestNamespaces" colspan="1" rowspan="1">
<pre xml:space="preserve">@prefix rdf: &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt; .
@prefix rdfs: &lt;http://www.w3.org/2000/01/rdf-schema#&gt; .
@prefix owl: &lt;http://www.w3.org/2002/07/owl#&gt; .
@prefix xsd: &lt;http://www.w3.org/2001/XMLSchema#&gt; .
</pre></td></tr>
</table>
<p>
Other namespaces are explicitly listed with the test data.
</p>


<div   class="subtoc"><p><strong>Contents</strong></p><ul class="toc"><li class="tocline"><a href="testIndex#testIndex" shape="rect">C. Index</a>
<ul class="toc">
<li class="tocline"><a href="testIndex#testIndexFunction" shape="rect">C.1. Index of OWL Feature Tests</a></li>
<li class="tocline"><a href="testIndex#testIndexIssue" shape="rect">C.2. Index of OWL Issue Tests</a></li>
<li class="tocline"><a href="testIndex#testIndexMisc" shape="rect">C.3. Index of Miscellaneous Tests</a></li>
<li class="tocline"><a href="testIndex#testIndexDL" shape="rect">C.4. Index of Description Logic Tests</a></li>
<li class="tocline"><a href="testIndex#testIndexExtra" shape="rect">C.5. Index of Extra Credit Tests</a></li></ul></li></ul></div>


<hr />

<h1><a id="acknowledgments" name="acknowledgments" shape="rect">D. Acknowledgments (Informative)</a></h1>
<p>
Jeremy Carroll thanks <a href="mailto:oreste@w3.org" shape="rect">Oreste Signore</a>,
his host at
the <a href="http://www.w3c.it/" shape="rect">W3C Office in Italy</a> and
<a href="http://www.isti.cnr.it" shape="rect">Istituto di Scienza e Tecnologie dell'Informazione
"Alessandro Faedo"</a>, part of the
<a href="http://www.cnr.it" shape="rect">Consiglio Nazionale delle Ricerche</a>, where Jeremy is a
visiting researcher.
</p>
<p>
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 Dürst, Masayasu Ishikawa,

Jim Hendler,

Herman ter Horst,

Dave Reynolds,

and the editors.
</p>
<p>Ian Horrocks contributed to <a href="./#conformance" shape="rect">the conformance</a> section of this document.
</p>
<p>
Sandro Hawke created the
<a href="http://www.w3.org/2003/08/owl-systems/test-results-out" shape="rect">tests results</a> page,
that
has been a great help during the Candidate Recommendation phase.
</p>
<p>
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.
</p>
<p>
This document is the result of extensive discussions within the
<a href="http://www.w3.org/2001/sw/WebOnt/" shape="rect">Web Ontology Working Group
</a>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.
</p>
<h1><a id="changes-since-PR" name="changes-since-PR" shape="rect">E. Changes Since Proposed Recommendation</a></h1>
<p>This section gives the changes
between this document and the
<a href="http://www.w3.org/TR/2003/PR-owl-test-20031215/" shape="rect">
OWL Test Cases Proposed Recommendation</a>.</p>
<p>The term <em>datatype map</em> is used instead of
the term
<em>datatype theory</em>, for consistency with the OWL and RDF Semantics.
This occurred a number of times, including in the descriptions of tests
<a href="misc-200-xmlliteral#miscellaneous-204" shape="rect">miscellaneous-204</a>,
<a href="misc-200-xmlliteral#miscellaneous-205" shape="rect">miscellaneous-205</a>
and
<a href="byIssue#I5.8-012" shape="rect">I5.8-012</a>.
The last of these consequentially required other minor
rephrasing.
</p>
<p>Updated references to RDF and OWL documents.</p>
<p>
Added a paragraph near end of
<a href="./#consistencyChecker" shape="rect">section 4.2.2</a>, clarifying that a datatype map of
an OWL Full consistency checker, (being a datatype map from RDF Semantics)
"MUST" contain an entry for rdf:XMLLiteral.
This makes explicit a requirement that was already implicit in the PR
document. Also clarified that the datatype map in the definition
of <a href="#dfn-OWL-Full-consistent-document" shape="rect">an OWL Full consistent document</a>
is as defined in RDF Semantics, by changing the link.
</p>
<p>Consequentially, made explicit reference to RDF Semantics (this reference
was implicit in the OWL Test  Proposed Recommendation).
</p>
<p>
Corrected an error in the metadata of test <a href="misc-200-xmlliteral#miscellaneous-205" shape="rect">miscellaneous-205</a>
which is not
applicable for OWL Full, since rdf:XMLLiteral is a required datatype for OWL
Full. This change is visible as the deletion of the word "Full" from the
header of the test.
</p>
<p>
This error in the OWL Test
<a href="http://www.w3.org/TR/2003/CR-owl-test-20030818/proposed-misc-200-xmlliteral#miscellaneous-205" shape="rect">
Candidate</a>
and
<a href="http://www.w3.org/TR/2003/PR-owl-test-20031215/misc-200-xmlliteral#miscellaneous-205" shape="rect">
Proposed
</a>
Recommendation appears to
have been relatively benign:
</p>
<ul>
<li>
Test <a href="misc-200-xmlliteral#miscellaneous-205" shape="rect">miscellaneous-205</a> was passed by FOWL, Pellet, OWLP, Hoolet and failed
by  Consvisor.
</li>
<li>The related test <a href="misc-200-xmlliteral#miscellaneous-204" shape="rect">miscellaneous-204</a> was passed by Pellet,
Consvisor and Euler.
 </li>
<li>OWLP, Pellet and Hoolet being explicitly OWL DL
reasoners continue to pass test miscellaneous-205 appropriately.
 </li>
<li>Consvisor
being an OWL Full system which supports rdf:XMLLiteral already conforms with
this implicit constraint of the OWL PR.
</li>
</ul>


<h1><a id="references" name="references" shape="rect">F. References</a></h1>


    <h2><a name="normative" id="normative" shape="rect">Normative</a></h2>
<dl>
<dt><a name="ref-OWL_Semantics_and_Abstract_Syntax" id="ref-OWL_Semantics_and_Abstract_Syntax" shape="rect">[OWL Semantics and Abstract Syntax]</a></dt><dd>
<cite><a href="http://www.w3.org/TR/2004/REC-owl-semantics-20040210/" shape="rect">OWL Web Ontology Language Semantics and Abstract Syntax</a></cite>,
Peter F. Patel-Schneider, Patrick Hayes, and Ian Horrocks, Editors,
W3C Recommendation 10 February 2004,
http://www.w3.org/TR/2004/REC-owl-semantics-20040210/ .
<a href="http://www.w3.org/TR/owl-semantics/" shape="rect">Latest version</a> available at
http://www.w3.org/TR/owl-semantics/ .
</dd>
<dt><a name="ref-RDF_Concepts" id="ref-RDF_Concepts" shape="rect">[RDF Concepts]</a></dt><dd>
<cite><a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/" shape="rect">
RDF Concepts and Abstract Syntax</a></cite>,
Graham Klyne and Jeremy J. Carroll, Editors,
W3C Recommendation 10 February 2004,
http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/ .
<a href="http://www.w3.org/TR/rdf-concepts/" shape="rect">Latest version</a> available at
http://www.w3.org/TR/rdf-concepts/ .
</dd>
<dt><a name="ref-RDF_Syntax" id="ref-RDF_Syntax" shape="rect">[RDF Syntax]</a></dt><dd>
<cite><a href="http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/" shape="rect">
RDF/XML Syntax Specification (Revised)</a></cite>.
Dave Beckett, Editor,
W3C Recommendation 10 February 2004,
http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/ .
<a href="http://www.w3.org/TR/rdf-syntax-grammar/" shape="rect">Latest version</a> available at
http://www.w3.org/TR/rdf-syntax-grammar/ .
</dd>
<dt><a name="ref-RDF_Semantics" id="ref-RDF_Semantics" shape="rect">[RDF Semantics]</a></dt><dd>
<cite><a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210/" shape="rect">
RDF Semantics</a></cite>.
Patrick Hayes, Editor,
W3C Recommendation 10 February 2004,
http://www.w3.org/TR/2004/REC-rdf-mt-20040210/ .
<a href="http://www.w3.org/TR/rdf-mt/" shape="rect">Latest version</a> available at
http://www.w3.org/TR/rdf-mt/ .
</dd>
<dt><a name="ref-RFC_2119" id="ref-RFC_2119" shape="rect">[RFC 2119]</a></dt><dd>
<cite><a href="http://www.ietf.org/rfc/rfc2119.txt" shape="rect">
RFC 2119 - Key words for use in RFCs to Indicate Requirement Levels
</a></cite>. S. Bradner,
IETF. March 1997. This document is <tt>http://www.ietf.org/rfc/rfc2119.txt</tt>.
</dd>
<dt><a name="ref-RDF_Schema_for_OWL" id="ref-RDF_Schema_for_OWL" shape="rect">[RDF Schema for OWL]</a></dt><dd>
<cite><a href="http://www.w3.org/2002/07/owl" shape="rect">
<tt>http://www.w3.org/2002/07/owl</tt></a></cite>.
Mike Dean, ed.
World Wide Web Consortium.
</dd>
<dt><a name="ref-XML_Schema_Datatypes" id="ref-XML_Schema_Datatypes" shape="rect">[XML Schema Datatypes]</a></dt><dd>
<cite><a href="http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/" shape="rect">
XML Schema Part 2: Datatypes.</a></cite>.
Paul V. Biron and Ashok Malhotra, eds.
W3C Recommendation 02 May 2000.
Latest version is available at
<a href="http://www.w3.org/TR/xmlschema-2/" shape="rect">http://www.w3.org/TR/xmlschema-2/</a>.
</dd>
</dl>
    <h2><a name="informative" id="informative" shape="rect">Informative</a></h2>
<dl>
<dt><a name="ref-RDF_Tests" id="ref-RDF_Tests" shape="rect">[RDF Tests]</a></dt><dd>
<cite><a href="http://www.w3.org/TR/2004/REC-rdf-testcases-20040210/" shape="rect">RDF Test Cases</a></cite>,
Jan Grant and Dave Beckett, Editors, W3C Recommendation 10 February 2004,
http://www.w3.org/TR/2004/REC-rdf-testcases-20040210/ .
<a href="http://www.w3.org/TR/rdf-testcases/" shape="rect">Latest version</a> available
at http://www.w3.org/TR/rdf-testcases/ .
</dd>
<dt><a name="ref-OWL_Guide" id="ref-OWL_Guide" shape="rect">[OWL Guide]</a></dt><dd>
<cite><a href="http://www.w3.org/TR/2004/REC-owl-guide-20040210/" shape="rect">
OWL Web Ontology Language
 Guide</a></cite>.
Michael K. Smith, Chris Welty, Deborah L. McGuinness, Editors,
W3C Recommendation 10 February 2004,
http://www.w3.org/TR/2004/REC-owl-guide-20040210/ .
<a href="http://www.w3.org/TR/owl-guide/" shape="rect">Latest version</a> available
at http://www.w3.org/TR/owl-guide/ .
</dd>
<dt><a name="ref-OWL_Overview" id="ref-OWL_Overview" shape="rect">[OWL Overview]</a></dt><dd>
<cite><a href="http://www.w3.org/TR/2004/REC-owl-features-20040210/" shape="rect">
OWL Web Ontology Language
Overview </a></cite>.
Deborah L. McGuinness and
Frank van Harmelen, Editors,
W3C Recommendation 10 February 2004,
http://www.w3.org/TR/2004/REC-owl-features-20040210/ .
<a href="http://www.w3.org/TR/owl-features/" shape="rect">Latest version</a> available
at http://www.w3.org/TR/owl-features/ .
</dd>
<dt><a name="ref-DAML_OIL" id="ref-DAML_OIL" shape="rect">[DAML+OIL]</a></dt><dd>
<cite><a href="http://www.w3.org/TR/2001/NOTE-daml+oil-reference-20011218" shape="rect">
DAML+OIL (March 2001) Reference Description</a></cite>.
Dan Connolly, Frank van Harmelen, Ian Horrocks,
Deborah L. McGuinness, Peter F. Patel-Schneider, and Lynn Andrea Stein.
W3C Note 18 December 2001.
Latest version is available at
<a href="http://www.w3.org/TR/daml+oil-reference" shape="rect"><tt>http://www.w3.org/TR/daml+oil-reference</tt></a>.
</dd>
<dt><a name="ref-Dublin_Core" id="ref-Dublin_Core" shape="rect">[Dublin Core]</a></dt><dd>
<a href="http://dublincore.org/documents/" shape="rect"><tt>http://dublincore.org/documents/</tt></a>
</dd>
<dt><a name="ref-N3" id="ref-N3" shape="rect">[N3]</a></dt><dd>
<cite><a href="http://www.w3.org/2000/10/swap/Primer.html" shape="rect">Primer: Getting into RDF &amp; Semantic Web using N3</a></cite>
Tim Berners-Lee, Dan Connolly
</dd>
<dt><a name="ref-OWL_Issues" id="ref-OWL_Issues" shape="rect">[OWL Issues]</a></dt><dd>
<cite><a href="http://www.w3.org/2001/sw/WebOnt/webont-issues.html" shape="rect">
Web Ontology Issue Status</a></cite>.
Michael K. Smith, ed.
26 Feb 2003.
</dd>
<dt><a name="ref-W3C_CVS" id="ref-W3C_CVS" shape="rect">[W3C CVS]</a></dt><dd>
<cite><a href="http://www.w3.org/Project/CVSdoc/" shape="rect">
Use of CVS in W3C
</a>
</cite> (member-only link).
Henrik Frystyk Nielsen,
Gerald Oskoboiny.
2002.
</dd>
<dt><a name="ref-XHTML" id="ref-XHTML" shape="rect">[XHTML]</a></dt><dd>
<cite><a href="http://www.w3.org/TR/2000/REC-xhtml1-20000126/" shape="rect">XHTML 1.0: The Extensible HyperText Markup Language</a></cite>,
W3C Recommendation, S. Pemberton <i lang="la" xml:lang="la">et
al.</i>, 26 January 2000.<br clear="none" />
Available at: <tt>http://www.w3.org/TR/2000/REC-xhtml1-20000126</tt>
</dd>
<dt><a name="ref-XMLBASE" id="ref-XMLBASE" shape="rect">[XMLBASE]</a></dt><dd>
    <cite><a href="http://www.w3.org/TR/2001/REC-xmlbase-20010627/" shape="rect">XML Base</a></cite>, J. Marsh, Editor,
W3C Recommendation.  World Wide Web Consortium,  27 June 2001.
This version of XML Base is <tt>http://www.w3.org/TR/2001/REC-xmlbase-20010627/</tt>.
The <a href="http://www.w3.org/TR/xmlbase/" shape="rect">latest version of XML Base</a> is at
<tt>http://www.w3.org/TR/xmlbase/</tt>.
  </dd>
<dt><a name="ref-Practical_Reasoning" id="ref-Practical_Reasoning" shape="rect">[Practical Reasoning]</a></dt><dd>
<cite>Practical reasoning for expressive description logics</cite>,
 I. Horrocks, U. Sattler, and S. Tobies, 1999,
 in
Proc. of LPAR'99, vol. 1705 of LNAI.
</dd>

<dt><a name="ref-XP" id="ref-XP" shape="rect">[XP]</a></dt><dd>
<cite>
Extreme Programming Explained: Embrace Change</cite>,
Kent Beck.
5 Oct 1999.
Addison-Wesley. ISBN 0201616416.
</dd>
<dt><a name="ref-Heinsohn_et_al." id="ref-Heinsohn_et_al." shape="rect">[Heinsohn et al.]</a></dt><dd>
AI 68 (1994) pp367-397.
</dd>
<dt><a name="ref-DIMACS" id="ref-DIMACS" shape="rect">[DIMACS]</a></dt><dd>
<cite>Satisfiability Suggested Format</cite>
<code>challenge@dimacs.rutgers.edu</code>
Found at
<a href="ftp://dimacs.rutgers.edu/pub/challenge/satisfiability/doc/satformat.tex" shape="rect">
ftp://dimacs.rutgers.edu/pub/challenge/satisfiability/doc/satformat.tex</a>
May 8, 1993.
</dd>
<dt><a name="ref-DL_98_Systems_Comparison" id="ref-DL_98_Systems_Comparison" shape="rect">[DL 98 Systems Comparison]</a></dt><dd>
<a href="http://ceur-ws.org/Vol-11/Intro.ps" shape="rect"><cite>DL Systems Comparison</cite></a>
at
<a href="http://ceur-ws.org/Vol-11/" shape="rect">1998 International Workshop on
Description Logics (DL 98)</a>.
Peter F. Patel-Schneider, Ian Horrocks.
June, 1998.
</dd>
</dl>

</body>
</html>