OWL Test Cases

Not A W3C Working Draft, 27 Sep 2002

This version:

http://lists.w3.org/Archives/Public/www-archive/2002Sep/att-0223/01-owl-test-cases.html

Latest version:

http://sealpc09.cnuce.cnr.it:8080/wowg/jsp/main.jsp

Previous version:

none

Editors:

Jeremy Carroll, HP <jjc@hpl.hp.com>

Jos De Roo, AGFA,<jos.deroo.jd@belgium.agfa.com>

The tests of this document are also [[not yet]] available in these non-normative formats: Zip archive of approved tests, Zip archive of proposed tests, the test web site.

Copyright ©2002 W3C^® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply.

---

Abstract

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.

Status of this document

This section is largely untrue, and describes aspiration rather than fact. In fact, this document is merely the work of its authors for consideration by the Web Ontology Working Group.

This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C.

The approved test cases in this document represent the consensus of the Web Ontology Working Group as at 7th October 2002. In later versions of this document many of the proposed tests will have moved into the approved tests section, either positively or negatively, depending on the working group consensus on the underlying issues. This document is subsidiary to the other Web Ontology Language recommendation track documents ([OWL Language], [OWL Abstract Syntax], [OWL Formal Semantics]) that give the formal definition of the language. The test cases described in this document (both approved and proposed) may be updated, replaced, negated or obsoleted at any time; despite this the working group would value implementor feedback on them. For this first Working Draft, feedback is particularly sought on issues of test format, description, process and presentation.

Comments on this document should be sent to public-webont-comments@w3.org, a mailing list with a public archive. Alternatively, if you do not wish your comments to be made public, you can send your comments to mailto:w3t-semweb-review@w3.org. General discussion of related technology is welcome in www-rdf-logic.

There are no patent disclosures related to this work at the time of this writing.

This is a W3C Working Draft for review by W3C members and other interested parties. It is a draft document and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use W3C Working Drafts as reference materials or to cite them as other than "work in progress." A list of current W3C Recommendations and other technical documents can be found at http://www.w3.org/TR/.

This document has been produced as part of the W3C Semantic Web Activity (Activity Statement) following the procedures set out for the W3C Process. The document has been written by the Web Ontology Working Group. The goals of the Web Ontology working group are discussed in the Web Ontology Working Group charter.

Table of Contents

1. Introduction

As part of the definition of the Web Ontology Language (OWL) [OWL Language] the Web Ontology Working Group provides a set of test cases. This document contains those test cases. They are intended to provide examples for, and clarification of, the other recommendation track documents ([OWL Language], [OWL Abstract Syntax], [OWL Formal Semantics]) to which this document is subsiduary.

This document describes the various types of test used and the format in which the tests are presented. Alternative formats of the test collection are provided. These are intended to be suitable for use by OWL developers in test harnesses, possibly as part of a test driven development process, such as Extreme Programming [XP]. The format of the Manifest files used as part of these alternative formats is described.

This document describes the process for conflict resolution and errata related to these tests.

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

Further appendices show further proposed tests that are awaiting resolution by the working group.

1.1. Scope

The test cases do not constitute a conformance test suite for OWL.

The test illustrate issue resolutions, and illustrate the use and meaning of the terms in the OWL namespace.

There are other miscellaneous tests motivated individually [[none in this version]] .

2. Deliverables (Normative)

The deliverables included as part of the test cases are:

• This recommendation track document, which normatively includes the tests.
• Additional alternative forms of the normative tests. These are also included in informative appendices to this document.
• A zip file including
  • The RDF/XML files that participate in the tests
  • Manifest files indicating which tests should be apply to which test files.
  • The non-normative alternative forms of the test files.
  This zip file is a non-normative alternative format.
• A web-site which includes the files in the zip file. This also is a non-normative alternative format.

  Note: Other files can be found under the top URL of the web-site which are not part of the deliverable.

[[EDITORS' NOTE: Do we want index files for the web site that clarify which parts are part of the deliverable and which are not?]]

2.1. Normative Status

Of the deliverables the only normative tests are those included in this document. All other deliverables, are informative. Moreover, the recommendation document is informative except for the test data (specified in RDF/XML [RDF/XML Syntax]), and the supporting documentation.

2.2. Conflict Resolution

When the normative tests and the other normative OWL recommendations diverge the following process should be followed.

If the OWL working drafts are at or before last call then:

1. The conflict is reported to public-webont-comments@w3.org.
2. The working group makes appropriate modifications to remove the conflict.

If the OWL recommendation has passed last call then:

1. The conflict is reported to public-webont-comments@w3.org.
2. The working group, or its successors, considers the conflict
3. While this happens the other recommendation documents take precedence over the test case.
4. If there is working group consensus to retain the test case as normative and to publish an erratum against the other recommendation document(s) then this is done.
5. Otherwise an erratum is published which deletes the test case.

Note: this last step does not require consensus, or even a majority.

Note: the errata process over the tests is monotonic decreasing.

3. Test Types (Normative)

Each test consists of either one or two RDF/XML documents and a Manifest file. Tests of one document indicate some property of that document when viewed as an OWL knowledge base. Tests of two documents indicate a relationship between the two documents when viewed as OWL knowledge bases.

The Manifest file is named ManifestNNN.rdf (The NNN is replaced by the test number). It contains metadata (in RDF) indicating the test type, and describing the test.

3.1. Tests for Incorrect Use of OWL Namespace

These tests use one document. It is named badNNN.rdf. This document includes a use of the OWL namespace with a local name that is not defined by the OWL recommendation.

Note: These tests are intended to help migration from DAML+OIL [DAML+OIL], since the local names chosen are defined in the DAML+OIL namespace.

3.2. Entailment Tests

These tests use two documents. One is named premisesNNN.rdf, the other is named conclusionsNNN.rdf. The conclusions are entailed by the premises. Such entailment is defined by the OWL Formal Semantics [OWL Formal Semantics].

3.3. Non-Entailment Tests

These tests use two documents. One is named premisesNNN.rdf, the other is named nonconclusionsNNN.rdf. The nonconclusions are not entailed by the premises. Such entailment is defined by the OWL Formal Semantics [OWL Formal Semantics].

3.4. Consistency Tests

These tests use one document. It is named consistentNNN.rdf. The document is consistent as defined by the OWL Formal Semantics [OWL Formal Semantics].

3.5. Inconsistency Tests

These tests use one document. It is named inconsistentNNN.rdf. The document is inconsistent as defined by the OWL Formal Semantics [OWL Formal Semantics].

3.6. Miscellaneous Tests (Informative)

During development, tests that are not of one of the above types, are classified as miscellaneous while awaiting a new test type to be defined.

4. Testing an OWL Implementation (Informative)

This document does not define criteria for how any specific OWL system should respond to the test data. Appropriate use of these tests should be determined by the system developers.

The following guidelines are offered.

4.1. Any OWL System

Any OWL compliant system should be able to read and process all the test input files. Moreover, those files that show an incorrect use of the OWL namespace should result in the system issuing a diagnostic.

4.2. OWL Reasoners

OWL reasoners should be able to prove many of the relationships shown in these tests. However, incomplete reasoners may fail to find proofs of some truths illustrated by these test cases.

In detail, we may see that, a reasoner is unsound when:

• It shows an entailment between the two documents of a non-entailment test.
  Or:
• It shows the document from a consistency test as inconsistent.

A reasoner is incomplete if:

• It fails to prove an entailment between the two documents of an entailment test.
  Or:
• It fails to find the inconsistency in a document from an inconsistency test.

5. Manifest Files (Informative)

The Manifest file follows the RDF schema developed for the RDF Test Cases [RDF Test Cases].

This is augmented by a few new properties and types which are declared in the OWL Test Ontology, found at http://www.w3.org/2002/03owlt/testOntology.

Specifically each test has its own Manifest file, and is identified from the URI reference formed from the Manifest file's URL with a fragment test.

The test has one rdf:type explicit, and this is one of:

otest:NotOwlFeatureTest

A test for the incorrect us of OWL namespace.

otest:PositiveEntailmentTest

An entailment test.

otest:NegativeEntailmentTest

A non-entailment test.

otest:ConsistencyTest

A consistency test.

otest:InconsistencyTest

An inconsistency test.

rtest:MiscellaneousTest

Some other test.

Where otest is bound to http://www.w3.org/2002/03owlt/testOntology# and rtest is bound to http://www.w3.org/2000/10/rdf-tests/rdfcore/testSchema#.

The name of the original author of the test is shown using a dc:creator property, see [Dublin Core].

A description of the test is given (using Xhtml markup [XHTML]) as the value of the rtest:description property.

An issue, if any, from the OWL Issues list [OWL Issues], is the value of a rtest:issue property.

An appropriate language feature, from the OWL namespace, if any, is the value of the otest:feature property.

The input documents with the test data are found as the value of the rtest:inputDocument property or as the value of both the rtest:premiseDocument and the rtest:conclusionDocument.

6. The OWL Tests (Normative)

6.1. By Function

6.1.1. owl:FunctionalProperty

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:owl ="http://www.w3.org/2002/07/owl#"
  xmlns:first="http://www.w3.org/2002/03owlt/FunctionalProperty/premises001#" 
  xml:base="http://www.w3.org/2002/03owlt/FunctionalProperty/premises001" >
    <owl:FunctionalProperty rdf:ID="prop"/>
    <rdf:Description rdf:ID="subject">
      <first:prop rdf:resource="#object1" />
      <first:prop rdf:resource="#object2" />
    </rdf:Description>
</rdf:RDF>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:owl ="http://www.w3.org/2002/07/owl#"
  xml:base="http://www.w3.org/2002/03owlt/FunctionalProperty/conclusions001" >
    <rdf:Description rdf:about="premises001#object1">
      <owl:sameIndividualAs rdf:resource="premises001#object2" />
    </rdf:Description>
</rdf:RDF>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:owl ="http://www.w3.org/2002/07/owl#"
  xmlns:eg ="http://www.example.org/"
  xmlns:first="http://www.w3.org/2002/03owlt/FunctionalProperty/premises002#" 
  xml:base="http://www.w3.org/2002/03owlt/FunctionalProperty/premises002" >
    <owl:FunctionalProperty rdf:ID="prop"/>
    <rdf:Description rdf:ID="subject">
      <first:prop rdf:resource="#object1" eg:prop2="value" />
      <first:prop rdf:resource="#object2" />
    </rdf:Description>
</rdf:RDF>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:eg ="http://www.example.org/"
  xml:base="http://www.w3.org/2002/03owlt/FunctionalProperty/test002" >
    <rdf:Description rdf:about="premises002#object2" eg:prop2="value"/>
</rdf:RDF>

6.2. By Issue

A. Test Creation, Approval and Modification

A.1. Creation

Tests are created by members of the working group. An (optional) test editor is provided to facilitate this. Tests are then placed in the appropriate directory in the test web site. This is done using CVS access to the W3C CVS server [W3C CVS].

When created, tests are given a status of "PROPOSED". The author of the test creates a Manifest file in the directory of the new test, identifying:

• The creator of the test.
• The test type.
• A description of the test.
• The RDF/XML files used in the test.
• The status as "PROPOSED".
• At least one of:
  • An OWL feature that the test illustrates (by reference to the name of some property or class in the OWL namespace.
  • An issue that the test case is related to (by reference to the issue URI as specified in the OWL issues list [OWL Issues].
  • Some other rationale for the test.
  
  Optionally:
  
• Some part of the recommendation documents which are particularly relevant.

A.2. Approval

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.

The chair actions two members of the working group to review the tests a week before putting the test to the group.

If the Working Group approves a test, then it is included in the test case document.

The Working Group may reject a test, in which case its status is changed to "REJECTED". This does not indicate that the converse of the test has been accepted. There may be stylistic or other grounds for rejecting technically correct tests.

The Working Group has complete discretion to approve or reject tests independent of their conformance with this process or their conformance with the OWL working drafts.

In the light of new information, and at the chairs' discretion, the working group may review any previous decision regarding any test cases. The status of "OBSOLETED" may be used where a test has ceased to be appropriate.

A.3. Modification

Until this document reaches last call, the editors may make editorial changes to approved and proposed tests. This includes:

• Editorial changes to text in the test descriptions.
• Fixing of typos and trivial errors.
• Moving tests to conform with document naming conventions.
• Renaming and renumbering tests and test files.
• Small substantive changes resulting from other working group decisions.
• Larger substantive changes resulting from other working group decisions when actioned by the working group.
• Stylistic changes reflecting changes to the preferences expressed in this document.

B. Stylistic Preferences

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 gain group consensus if they follow these rules.

B.1. Use of RDF/XML

Tests should normally be expressed in RDF/XML.

Jeremy disagrees with the rest of this subsection and moves to strike the text. It is intended to reflect Peter's proposal to restrict RDF/XML to simple striped syntax.

The following RDF/XML grammar rules [RDF/XML Syntax] are not used:

1. Property attributes.
2. Bag ID.
3. rdf:parseType="Resource".
4. rdf:ID, both for reification and as an alternative to rdf:about.

Moreover, all URI references in rdf:about and rdf:resource attribute values are absolute.

B.2. Use of xml:base

Test and manifest files should have an xml:base attribute [XMLBASE] on the document element. This should show the preferred URL of the document, from which it is actually retrievable.

Files that contain no relative URIs may omit the xml:base attribute.

B.3. Use of .rdf Suffix

Test and manifest files should use the ".rdf" suffix. URIs should not. The URL used for xml:base declarations does not have a suffix.

B.4. Use of example Domains

All URLs in the test and manifest files should be retrievable web resources except for those that use domain names with "example" as the penultimate component (e.g. http://www.example.org/ontology#prop").

B.5. Copyright

The following copyright statement should be included as an XML comment in every test file:

<!--
  Copyright World Wide Web Consortium, (Massachusetts Institute of
  Technology, Institut National de Recherche en Informatique et en
  Automatique, Keio University).
 
  All Rights Reserved.
 
  Please see the full Copyright clause at
  <http://www.w3.org/Consortium/Legal/copyright-software.html>

  $Id: This string is updated by cvs. $
-->

B.6. Description

The description should:

• Link to relevant parts of of the OWL recommendations.
• Clearly distinguish syntactic and semantic concerns.

The description should be included as an XML comment in each test file, and be included as RDF content in the Manifest file.

B.7. Directory Structure

Tests that relate principally to some owl property or class, should be put in a directory named using the local name of that property of class.

Otherwise, tests that relate to an issue should be put in a directory named like I3.4 where the issue number is taken from the OWL issue list [OWL Issues].

B.8. Test Numbering

Each directory should contain tests numbered consecutively from 001.

No two tests in a single directory should have the same number.

Each file in a test should have the number of the test at the end of its name, before the suffix.

The rest of the file name should follow the conventions for the test type.

Note: the approved tests in a directory will not necessarily be contiguously numbered.

Note: this differs from the RDF Core test case numbering conventions.

C. The Tests as Triples (Informative)

This section repeats the normative tests.

This time the test data is shown in simple triples, using N-triple syntax [RDF Test Cases] with qnames. Qnames are used in place of URIs in the syntax with no delimiters. This syntax conforms with the usage in N3 [N3], the namespace prefices are also declared using N3 syntax [N3].

The following namespace prefixes are used throughout:

rdf

http://www.w3.org/1999/02/22-rdf-syntax-ns#

rdfs

http://www.w3.org/2000/01/rdf-schema#

owl

http://www.w3.org/2002/07/owl#

first

The URL of the first file concatenated with #

second

The URL of the second file concatenated with #

In the N3 syntax [N3] used for namespace declarations, the first three appear as follows:

@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .

Other namespaces are explicitly listed with the test data.

C.1. By Function

C.1.1. owl:FunctionalProperty

first:prop rdf:type owl:FunctionalProperty .
first:subject first:prop first:object1 .
first:subject first:prop first:object2 .

first:object1 owl:sameIndividualAs first:object2 .

@prefix eg: <http://www.example.org/> .

first:prop rdf:type owl:FunctionalProperty .
first:object1 eg:prop2 "value" .
first:subject first:prop first:object1 .
first:subject first:prop first:object2 .

first:object2 eg:prop2 "value" .

C.2. By Issue

D. Proposed Tests (Informative)

D.1. By Function

D.1.1. owl:FunctionalProperty

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:owl ="http://www.w3.org/2002/07/owl#"
  xml:base="http://www.w3.org/2002/03owlt/FunctionalProperty/premises003" >
    <owl:FunctionalProperty rdf:ID="prop">
      <owl:inverseOf rdf:resource="#inv"/>
    </owl:FunctionalProperty>
</rdf:RDF>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:owl ="http://www.w3.org/2002/07/owl#"
  xml:base="http://www.w3.org/2002/03owlt/FunctionalProperty/conclusions003" >
    <owl:InverseFunctionalProperty rdf:about="premises003#inv"/>
</rdf:RDF>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:owl ="http://www.w3.org/2002/07/owl#"  
  xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
  xml:base="http://www.w3.org/2002/03owlt/FunctionalProperty/premises004" >
    <owl:ObjectProperty rdf:ID="prop">
      <rdfs:range rdf:resource="#Singleton"/>
    </owl:ObjectProperty>
    <rdfs:Class rdf:ID="Singleton">
      <owl:oneOf rdf:parseType="Collection">
          <rdf:Description/>
      </owl:oneOf>
    </rdfs:Class>
</rdf:RDF>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:owl ="http://www.w3.org/2002/07/owl#"
  xml:base="http://www.w3.org/2002/03owlt/FunctionalProperty/conclusions004" >
    <owl:FunctionalProperty rdf:about="premises004#prop"/>
</rdf:RDF>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:owl ="http://www.w3.org/2002/07/owl#"
  xmlns:eg ="http://www.example.org/">
    <owl:FunctionalProperty rdf:about="http://www.example.org/foo#prop" />
    <owl:Thing rdf:about="http://www.example.org/foo#object" />
</rdf:RDF>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:owl ="http://www.w3.org/2002/07/owl#"
  xmlns:eg ="http://www.example.org/">
    <owl:Thing rdf:about="http://www.example.org/foo#object">
      <rdf:type>
        <owl:Restriction>
	  <owl:onProperty>
	    <owl:FunctionalProperty rdf:about="http://www.example.org/foo#prop" />
	  </owl:onProperty>
	  <owl:maxCardinality>1</owl:maxCardinality>
        </owl:Restriction>
      </rdf:type>
    </owl:Thing>
</rdf:RDF>

D.2. By Issue

D.2.1. UniqueProp BadName

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:owl ="http://www.w3.org/2002/07/owl#" >
    <owl:UniqueProperty rdf:ID="Name"/>
</rdf:RDF>

E. Proposed Tests as Triples (Informative)

This section repeats the tests of the previous section.

The following namespace prefixes are used throughout:

rdf

http://www.w3.org/1999/02/22-rdf-syntax-ns#

rdfs

http://www.w3.org/2000/01/rdf-schema#

owl

http://www.w3.org/2002/07/owl#

first

The URL of the first file concatenated with #

second

The URL of the second file concatenated with #

In the N3 syntax [N3] used for namespace declarations, the first three appear as follows:

@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .

Other namespaces are explicitly listed with the test data.

E.1. By Function

E.1.1. owl:FunctionalProperty

first:prop rdf:type owl:FunctionalProperty .
first:prop owl:inverseOf first:inv .

first:inv rdf:type owl:InverseFunctionalProperty .

@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .

first:prop rdf:type owl:ObjectProperty .
first:prop rdfs:range first:Singleton .
first:Singleton rdf:type rdfs:Class .
_:jARP679 rdf:first _:jARP680 .
_:jARP679 rdf:rest rdf:nil .
_:jARP679 rdf:type rdf:List .
first:Singleton owl:oneOf _:jARP679 .

first:prop rdf:type owl:FunctionalProperty .

@prefix eg: <http://www.example.org/> .

eg:foo#prop rdf:type owl:FunctionalProperty .
eg:foo#object rdf:type owl:Thing .

eg:foo#object rdf:type owl:Thing .
_:jARP685 rdf:type owl:Restriction .
eg:foo#prop rdf:type owl:FunctionalProperty .
_:jARP685 owl:onProperty eg:foo#prop .
_:jARP685 owl:maxCardinality "1" .
eg:foo#object rdf:type _:jARP685 .

E.2. By Issue

E.2.1. UniqueProp BadName

first:Name rdf:type owl:UniqueProperty .

F. Editorial Issues

F.1. Arising from Automated Checking

Some of these issues will be ignored.

Jtidy reported 5 warnings in TransitiveProperty/.
Jtidy reported 231 warnings in webont-issues.
Jtidy reported 1 warnings in I4.1/.
Jtidy reported 5 warnings in I3.4/.
Jtidy reported 5 warnings in oneOf/.
Jtidy reported 5 warnings in editors-draft/.
Jtidy reported 1 warnings in FunctionalProperty/.
Jtidy reported 1 warnings in umlp/.
Jtidy reported 5 warnings in InverseFunctionalProperty/.
Jtidy reported 5 warnings in Nothing/.
Jtidy reported 7 errors in webont-issues.
Jtidy reported 5 warnings in inverseOf/.
Jtidy reported 5 warnings in intersectionOf/.
Jtidy reported 5 warnings in unionOf/.
Jtidy reported 5 warnings in maxCardinality/.
Jtidy reported 1 warnings in 03owlt.
Jtidy reported 1 warnings in qualified-cardinality-constraints/.
Jtidy reported 5 warnings in I3.2/.

F.2. Other

Check descriptions of approved tests with respect to clarity of distinction between syntax and semantics.

Check descriptions for appropriate links to other OWL specs.

Add automatic checking of filenames. (4)

Page to choose which bits you want. (2)

Validate HTML.

Acknowledgments

Jeremy Carroll thanks Oreste Signore, his host at W3C Italia and Istituto di Scienza e Tecnologie dell'Informazione "Alessandro Faedo", part of the Consiglio Nazionale delle Ricerche, where Jeremy is a visiting researcher.

References

Normative

[OWL Abstract Syntax]

OWL Web Ontology Language 1.0 Abstract Syntax. Peter F. Patel-Schneider, Ian Horrocks, and Frank van Harmelen.. W3C Working Draft 29 July 2002. Latest version is available at http://www.w3.org/TR/owl-absyn/.

[OWL Formal Semantics]

In preparation.

[OWL Language]

OWL Web Ontology Language 1.0 Reference. Mike Dean, Dan Connolly, Frank van Harmelen, James Hendler, Ian Horrocks, Deborah L. McGuinness, Peter F. Patel-Schneider, and Lynn Andrea Stein. W3C Working Draft 29 July 2002. Latest version is available at http://www.w3.org/TR/owl-ref/.

[RDF/XML Syntax]

RDF/XML Syntax Specification (Revised). Dave Beckett, ed. W3C Working Draft 25 March 2002. Latest version is available at http://www.w3.org/TR/rdf-syntax-grammar/.

Informative

[DAML+OIL]

DAML+OIL (March 2001) Reference Description. 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 http://www.w3.org/TR/daml+oil-reference.

[Dublin Core]

http://dublincore.org/documents/

[N3]

Primer: Getting into RDF & Semantic Web using N3 Tim Berners-Lee, Dan Connolly

[OWL Issues]

Web Ontology Issue Status. Michael K. Smith, ed. 10 Jul 2002.

[RDF Test Cases]

RDF Test Cases, A. Barstow, D. Beckett, J. Grant, Editors. Work in progress. World Wide Web Consortium, 15 November 2001. This version of the RDF Test Cases is http://www.w3.org/TR/2001/WD-rdf-testcases-20011115/. The latest version of the RDF Test Cases is at http://www.w3.org/TR/rdf-testcases.

[W3C CVS]

Use of CVS in W3C (member-only link). Henrik Frystyk Nielsen, Gerald Oskoboiny. 2002.

[XHTML]

Missing ref.

[XMLBASE]

XML Base, J. Marsh, Editor, W3C Recommendation. World Wide Web Consortium, 27 June 2001. This version of XML Base is http://www.w3.org/TR/2001/REC-xmlbase-20010627/. The latest version of XML Base is at http://www.w3.org/TR/xmlbase/.

[XP]

Extreme Programming Explained: Embrace Change. . Kent Beck. 5 Oct 1999. Addison-Wesley. ISBN 0201616416.