Copyright © 2004-2023 World Wide Web Consortium. W3C® liability, trademark and permissive document license rules apply.
This page describes W3C RDF 1.1 Working Group's Entailment test suite. This test suite contains two kinds of tests:
rdft:PositiveEntailmentTest)These tests are also described in Turtle format in this directory for convenience. The manifest files in this directory lists all of the approved tests in the RDF WG's RDF Entailment test suite. All tests have a name (mf:name) and an input (mf:action).
Each test is one of the above kinds of tests. All tests have
mf:name),mf:action),mf:result),mf:entailmentRegime),mf:recognizedDatatypes),mf:unrecognizedDatatypes).An implementation passes a Positive (Negative) Entailment Test if, when configured to 1. perform entailment under the entailment regime of the test or some entailment regime that is stronger (weaker) than the entailment regime and 2. recognize all the datatypes in the list of recognized datatypes and none of the datatypes in the list of unrecognized datatypes, * for tests that have an output graph, determines that the input RDF graph entails (does not entail) the output RDF graph * for tests that have false as output, either determines that the input RDF graph entails (does not entail) an inconsistent RDF graph or that the input RDF graph is inconsistent (consistent).
An implementation also passes a test if when configured differently from a correct configuration as given above nonetheless produces the given result, and the result is correct in the configured entailment regime with the configured recognized datatypes.
Tests can be run from the web or by downloading either a tarball or zip file.
The home of the test suite is http://www.w3.org/2013/rdf-mt-tests/.
See http://www.w3.org/2011/rdf-wg/wiki/RDF_Test_Suites for more details. Per RFC 3986 section 5.1.3, the base IRI for parsing each file is the retrieval IRI for that file, but changing base IRIs should not affect any testing results.
The test manifests and entries are built automatically from manifest.ttl using a Rake task. Tests may be contributed via pull request to https://github.com/w3c/rdf-tests with suitable changes to the manifest.ttl and referenced files.
Distributed under both the W3C Test Suite License and the W3C 3-clause BSD License. To contribute to a W3C Test Suite, see the policies and contribution forms.
UNDER BOTH MUTUALLY EXCLUSIVE LICENSES, THIS DOCUMENT AND ALL DOCUMENTS, TESTS AND SOFTWARE THAT LINK THIS STATEMENT ARE PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, OR TITLE; THAT THE CONTENTS OF THE DOCUMENT ARE SUITABLE FOR ANY PURPOSE; NOR THAT THE IMPLEMENTATION OF SUCH CONTENTS WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS. COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE DOCUMENT OR THE PERFORMANCE OR IMPLEMENTATION OF THE CONTENTS THEREOF.
The claim that xsd:integer is a subClassOF xsd:decimal is not incompatible with using the intensional semantics for datatypes.
xsd:decimal
xsd:integer
none
Without datatype knowledge, a 'badly-formed' datatyped literal cannot be detected. Used to be a postitive test to itself.
none
xsd:integer
With appropriate datatype knowledge, a 'badly-formed' datatyped literal can be detected. Ill-formed datatyped literals now are inconsistent. Used to be negative entailment to <datatypes/test002b.nt>
xsd:integer
none
Demonstrating the semantic equivalence of two lexical forms of the same datatyped value.
xsd:integer
none
As semantic-equivalence-within-type-1; the entailment works both ways.
xsd:integer
none
Members of different datatypes may be semantically equivalent.
xsd:decimal
xsd:integer
none
Where sufficient DT knowledge is available, a range clash may be detected; the document then contains a contradiction.
xsd:integer
xsd:string
none
From decisions listed in http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2002Oct/0098.html
none
none
From decisions listed in http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2002Oct/0098.html
none
xsd:integer
From decisions listed in http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2002Oct/0098.html
xsd:integer
none
A plain literal denotes the same thing as its corresponding xsd:string, where one exists.
xsd:string
none
rdfs:subClassOf has intensional semantics, not extensional.
none
none
rdfs:subPropertyOf has intensional semantics, not extensional.
none
none
An international URI ref and its %-escaped form label different nodes in the graph. No model theoretic relationship holds between them.
none
none
An international URI ref and its %-escaped form label different nodes in the graph. No model theoretic relationship holds between them.
none
none
Statement of the MT closure rule.
none
none
Statement of the MT closure rule.
none
none
Statement of the MT closure rule.
none
none
Plain literals are distinguishable on the basis of language tags.
none
none
Plain literals are distinguishable on the basis of language tags.
none
none
Plain literals are distinguishable on the basis of language tags.
none
none
While it is a superproperty, _:a <rdfs:contains (@@member?)> _:b . does NOT entail _:a
none
none
RDF Semantics defines rdfs:range to have an intensional reading. However, semantic extensions may give an extensional reading to range. The premise/conclusion pair is a non-entailment for RDFS reasoning, but may hold in semantic extensions.
none
none
RDF Semantics defines rdfs:range to have an intensional reading of domain. However, semantic extensions may give an extensional reading to domain. The premise/conclusion pair is a non-entailment for RDFS reasoning, but may hold in semantic extensions.
none
none
Indicating a simple inconsistency drawn from RDFS. RDFS can only produce inconsistencies through badly-formed XMLLiteral datatypes. rdf:XMLLiteral support is no longer mandatory.
http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral
none
Datatype clashes can occur in RDFS entailment. Use to be from an inconsistent graph, any entailment can be drawn. This is an example.
xsd:string
http://www.w3.org/1999/02/22-rdf-syntax-ns#langString
none
Cycles are permitted in subClassOf; therefore, no error occurs and the following entailment holds trivially.
none
none
Cycles are permitted in subPropertyOf; therefore, no error occurs and the following entailment holds trivially.
none
none
an instance of the Property class may have an rdfs:subClassOf property. the meaning of such a property is defined by the model theory. The wording of the formal resolution is a bit bare, so let me add a few words of explanation. What this means is that a resource can be both a class and a property. This test is encoded as follows: a Property may have a subclass (that is, such an RDF graph is satisfiable)
none
none
The inheritance semantics of the subPropertyOf relationship needs to be clarified. => subProperties inherit conjunctively the domain and range of their superproperties
none
none
RDFCore WG RESOLVED that a reified statement was a stating, not a statement. The following entailment does not, therefore, hold.
none
none
RDFCore WG RESOLVED that a statement does NOT entail its reification. The following entailment does not, therefore, hold.
none
none
RDFCore WG RESOLVED that a reified statement was a stating, not a statement. The following entailment does not, therefore, hold. This is the same as test001, but using RDFS-entailment.
none
none
RDFCore WG RESOLVED that a statement does NOT entail its reification. The following entailment does not, therefore, hold. This is the same as test002, but using RDFS-entailment.
none
none
The case of the language tag is not significant.
none
none
The case of the language tag is not significant.
none
none
A well-formed typed literal is not related to an ill-formed literal. Even if they only differ by whitespace.
xsd:int
none
A well-formed typed literal is not related to an ill-formed literal. Even if they only differ by whitespace. Ill-formed datatyped literals now are inconsistent. Used to be negative entailment to <xmlsch-02/test001.ttl> .
xsd:int
none
An integer with whitespace is ill-formed. Ill-formed datatyped literals now are inconsistent. Used to be negative entailment.
xsd:int
none