RDF Test Cases
RDF Test Cases
W3C Recommendation 10 February 2004
New Version
Available: "RDF 1.1 Test Cases"
(Document Status Update, 25 February 2014)
The RDF Working Group has produced
a W3C Recommendation for a new version of RDF which adds
features to this 2004 version, while remaining compatible.
Please see
"RDF 1.1
Test Cases"
for a new version of this document, and the
"What's New in RDF 1.1"
document for the differences between this
version of RDF and RDF 1.1.
This Version:
Latest Version:
Previous Version:
Editors:
Jan Grant, (ILRT, University of Bristol)
Dave Beckett
(ILRT, University of Bristol)
Series editor:
Brian
McBride
(Hewlett Packard Labs)
Please refer to the
errata
for this document, which may include some normative corrections.
See also
translations
W3C
MIT
ERCIM
Keio
),
liability
trademark
document
use
and
software
licensing
rules apply.
Abstract
This document describes the RDF Test Cases deliverable for the
RDF Core Working
Group
as defined in the Working Group's
Charter
Status of this Document
This document has been reviewed by W3C Members and other interested
parties, and it has been endorsed by the Director as a
W3C
Recommendation
. 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.
This is one document in a
set
of six
Primer
Concepts
Syntax
Semantics
Vocabulary
and
Test
Cases
) intended to jointly replace the original Resource
Description Framework specifications,
RDF Model and Syntax (1999
Recommendation)
and
RDF Schema
(2000 Candidate Recommendation)
. It has been developed by the
RDF Core Working Group
as part of the
W3C Semantic Web
Activity
Activity
Statement
Group
Charter
) for publication on 10 February 2004.
Changes to this document since the
Proposed Recommendation Working Draft
are detailed in
the
change log
The public is invited to send comments to
www-rdf-comments@w3.org
archive
and to participate in general discussion of related technology on
www-rdf-interest@w3.org
archive
).
A list of
implementations
is available.
The W3C maintains a list of
any patent disclosures related to this work
This section describes the status of this document at the time of its
publication. Other documents may supersede this document. A list of current W3C
publications and the latest revision of this technical report can be found in
the
W3C technical reports index
at
Table of Contents
1.
Introduction
1.1.
Scope
1.2.
RDF
Errata
2.
Test Cases
2.1.
Organization
2.2.
Approved Test
Cases
2.3.
Test Cases
Not Approved
2.4.
Running the
test cases
3.
N-Triples
3.1.
Extended Backus-Naur Form (EBNF)
Grammar
3.2.
Strings
3.3.
URI
References
3.4.
Example
3.5.
Tests
4.
References
Normative
References
Informative References
5.
Acknowledgments
(Informative)
A.
Change Log
(Informative)
B.
Open Issues
(Informative)
1.
Introduction
One of the deliverables specified in
Charter
of
the
RDF Core Working
Group
is:
a set of machine-processable
test
cases
corresponding to technical issues addressed by the
Working Group
. This document describes the test cases that fulfill that
deliverable but it does not contain the test cases themselves. The
test cases are available at
The
RDF Interest
Group
and other members of the RDF community have identified
issues/ambiguities in the [
RDFMS
] Specification and the [
RDF-SCHEMA
] Candidate Recommendation.
These issues have been collected and categorized in the
RDF Core Working Group Issue
Tracking
document. The RDF Core Working Group uses this issue
list to guide its work. The issues list is a working document; it
is updated as new issues are identified. It is updated as the
Working Group makes decisions as documented in the
Attention
Developers
section of the document.
The complete specification of RDF consists of a number of
documents:
RDF Primer
RDF-PRIMER
RDF Concepts and Abstract Syntax
RDF-CONCEPTS
RDF Semantics
RDF-SEMANTICS
RDF/XML Syntax
RDF-SYNTAX
RDF Vocabulary Description Language 1.0: RDF Schema
RDF-VOCABULARY
RDF Test Cases (this document)
1.1. Scope
A comprehensive and complete test suite for RDF should cover all
of the rules in the
Formal Grammar
for RDF
. The Working Group, however, is not chartered to
deliver such a test suite but rather to create test cases for the
issues the Working Group addresses (when applicable). Although the
Working Group will not create test cases for some grammar rules
(e.g. rule [6.1]), if such test cases are donated to the W3C the
Consortium may add such test cases to this set of test cases.
1.2. RDF
Errata
The
RDF
Errata
documents known errors in [
RDFMS
]. Since errata are considered
normative changes to a W3C Specification and Working Group
decisions are not normative until a specification is a W3C
Recommendation, none of the decisions made by the RDF Core Working
Group have (to date) been reflected in the errata.
2. Test Cases
The Test Case Repository
REPOSITORY
contains subdirectories, each containing test cases devoted to
a single issue. Each directory contains a manifest file
describing the tests in that directory. Where an issue originated
with the RDF Issue Tracking process
ISSUES
], the
manifest will indicate this fact.
The Test Case Repository contains ZIP files of all
Approved test
cases
APPROVED
] as well as
a ZIP archive of all Approved and Not Approved test cases
FULLTESTS
The Manifest file
MANIFEST
contains a machine-readable manifest of the test cases.
The format of this file is described below.
2.1. Organization
The manifest file
MANIFEST
contains a machine-readable description of the test cases in
RDF/XML. Care has been taken to ensure that this file
follows a simple format to assist in machine-processing the test
cases.
The file consists of a simple header
MANIFEST-HEAD
],
individual descriptions of the test cases, and a closing footer
MANIFEST-TAIL
].
The test cases are divided into the following categories:
Positive Parser Tests
These tests consist of one (or more) input documents in RDF/XML
as is revised in [
RDF-SYNTAX
]. The expected result
is defined using the
N-Triples syntax
(Section 3)
. A parser is considered to pass the test if it
produces a graph
equivalent to
the graph described by the N-triples output
document, according to
the definition of graph equivalence
given in [
RDF-CONCEPTS
]. Where the
input document(s) are legal RDF/XML, but a warning may be
generated, this is indicated in the test manifest.
This is a simple positive parser test example.
Negative Parser Tests
These tests consist of one input document. The document is not
legal RDF/XML. A parser is considered to pass the test if it
correctly holds the input document to be in error.
Positive Entailment Tests
These tests are specified by one or more premise documents (in
RDF/XML or N-Triples) together with a single conclusion
document. In addition, the rules used for determining
entailment are specified by test:entailmentRules elements. If
the following is present
then the test succeeds if the entailment holds according to the
rules of RDF-entailment as specified in [
RDF-SEMANTICS
]. If the following
two elements are present
then the test succeeds if the entailment holds according to the
rules of RDFS-entailment as specified in [
RDF-SEMANTICS
].
For test cases that use simple entailment, the following marker
is used:
This test demonstrates the conjunctive nature of range and domain.
According to [
RDF-SEMANTICS
], a premise document
that contains a semantic error with respect to any constraints
imposed by the entailment rules selected will be false in any
interpretation
(and hence entail anything).
Support for such situations is provided by the manifest
format by declaring an premise or conclusion pseudo-document as
follows:
By convention, such a pseudo-document is said to come out
false under any interpretation.
Negative Entailment Tests
These tests are specified using a similar structure to the
Positive Entailment Tests, with the
The test is
failed
if the conclusion can be drawn from the
premises using the rules of RDF- or RDFS-entailment. The test is
considered to be
passed
when it can be conclusively
demonstrated that the conclusion cannot be so drawn. In practice, the
test may be considered to be passed when a thorough attempt to fail
the test is unable to achieve failure.
RDF Core WG RESOLVED that a reified statement was a stating, not a statement.
The following entailment does not, therefore, hold.
Datatype-aware entailment tests
Entailment test cases may, in addition, require datatype
support. Such a requirement is indicated in the manifest by the
presence of the following
test:entailmentRules
element,
followed by zero or more
test:datatypeSupport
entries.
For the purposes of the test suite, if a test case requires
datatype support
for a set of datatypes, {
, ... } then the following three pieces of
machinery are required:
for any datatyped literal of the form
aaa
"^^<
where
is
a supported datatype, it must be possible to determine if
aaa
is a valid lexical form for that datatype;
and
for any two datatyped literals of the form
aaa
"^^<
and
bbb
"^^<
with
aaa
and
bbb
valid lexical forms of the supported
datatypes
and
respectively, it must be
possible to determine if those two literals denote the same
value. (Note that determining
what that value is
is
not explicitly required.)
for any datatyped literal of the form
aaa
"^^<
where
is
a supported datatype, and for some supported datatype
, it must be possible to determine if the value
denoted by the literal is or is not a member of the value
space of
. (This last condition is required to
support the checking of range clashes.) Finally,
For two supported datatypes
and
it must be possible to determine (possibly by simple fiat)
if
, considered as a class, is a subclass of
, considered as a class.
Miscellaneous Tests
This manifest entry is used to describe test cases that do not
fall into one of the earlier categories. It may have several
associated files, indicated in
A serializer asked to output the graph described in the test001
document should raise an exception since it cannot be described using
RDF/XML.
In addition, each test case description may have the following
common attributes:
The
test:issue
element contains a pointer to the
associated issue on the
RDF Core Working Group
Tracking
document. It may appear zero or more times.
The
test:status
element, if present, indicates the
status of the test according to RDF Core Working Group process. Only test
descriptions containing the following should be considered to
be approved by Working Group.
The
test:approval
element, if present, contains a
reference to the minutes of the RDF Core Working Group meeting where the
test case status was last changed.
The
test:discussion
element, if present, contains a
pointer to other discussion surrounding this test case or the
associated issue. This element may appear multiple times.
The
test:description
element, if present, contains a
human-readable summary of the test case.
Text describing the test case goes here.
The
test:warning
element, if present, indicates that
while the test should pass, it may generate a warning. The
contents of the element provide a human-readable description of
the warning.
2.2. Approved Test
Cases
The test cases in the following table have been approved.
There are 22 issues containing 157 approved test cases, and 57 test cases without an associated issue.
Relative URLs listed in this table should be resolved against the base URI http://www.w3.org/2000/10/rdf-tests/rdfcore/
Test cases without an issue: 57 tests
Positive parser tests (test cases: 15)
Input files
Output file
Warning?
Approved
amp-in-url/test001.rdf
amp-in-url/test001.nt
RDFCore Telecon 2001-09-21
datatypes/test001.rdf
datatypes/test001.nt
RDFCore Telecon 2002-11-22
datatypes/test002.rdf
datatypes/test002.nt
RDFCore Telecon 2002-11-22
rdf-element-not-mandatory/test001.rdf
rdf-element-not-mandatory/test001.nt
RDFCore Telecon 2003-10-03
rdfms-reification-required/test001.rdf
rdfms-reification-required/test001.nt
RDFCore Telecon 2003-01-10
rdfms-uri-substructure/test001.rdf
rdfms-uri-substructure/test001.nt
RDFCore Telecon 2003-01-10
rdfms-xmllang/test001.rdf
rdfms-xmllang/test001.nt
RDFCore Telecon 2002-06-07
rdfms-xmllang/test002.rdf
rdfms-xmllang/test002.nt
RDFCore Telecon 2002-06-07
rdfms-xmllang/test003.rdf
rdfms-xmllang/test003.nt
RDFCore Telecon 2002-06-07
rdfms-xmllang/test004.rdf
rdfms-xmllang/test004.nt
RDFCore Telecon 2002-06-07
rdfms-xmllang/test005.rdf
rdfms-xmllang/test005.nt
RDFCore Telecon 2002-06-07
rdfms-xmllang/test006.rdf
rdfms-xmllang/test006.nt
RDFCore Telecon 2003-01-10
unrecognised-xml-attributes/test001.rdf
unrecognised-xml-attributes/test001.nt
RDFCore Telecon 2002-01-18
unrecognised-xml-attributes/test002.rdf
unrecognised-xml-attributes/test002.nt
RDFCore Telecon 2002-01-18
xml-canon/test001.rdf
xml-canon/test001.nt
RDFCore Telecon 2003-08-08
Negative parser tests (test cases: 9)
Input file
Approved
rdfms-abouteach/error001.rdf
RDFCore Telecon 2003-01-10
rdfms-abouteach/error002.rdf
RDFCore Telecon 2003-01-10
rdfms-rdf-id/error001.rdf
RDFCore Telecon 2003-01-10
rdfms-rdf-id/error002.rdf
RDFCore Telecon 2003-01-10
rdfms-rdf-id/error003.rdf
RDFCore Telecon 2003-01-10
rdfms-rdf-id/error004.rdf
RDFCore Telecon 2003-01-10
rdfms-rdf-id/error005.rdf
RDFCore Telecon 2003-01-10
rdfms-rdf-id/error006.rdf
RDFCore Telecon 2003-01-10
rdfms-rdf-id/error007.rdf
RDFCore Telecon 2003-01-10
Positive Entailment tests (test cases: 16)
Rules
Premise files
Conclusion file
Warning?
Approved
RDF + RDFS + DT(xsd:integer, xsd:string)
datatypes-intensional/test002.nt
FALSE
RDFCore Telecon 2003-09-05
RDF + RDFS
datatypes/test002.nt
datatypes/test002.nt
RDFCore Telecon 2002-11-22
RDF + RDFS + DT(xsd:string)
datatypes/test011a.nt
datatypes/test011b.nt
RDFCore Telecon 2003-08-29
RDF + RDFS + DT(xsd:decimal, xsd:string)
datatypes/test006.nt
FALSE
RDFCore Telecon 2003-01-10
RDF + DT(xsd:decimal, xsd:integer)
datatypes/test005a.nt
datatypes/test005b.nt
RDFCore Telecon 2003-01-10
RDF + DT(xsd:integer)
datatypes/test003a.nt
datatypes/test003b.nt
RDFCore Telecon 2002-11-22
RDF + DT(xsd:integer)
datatypes/test003b.nt
datatypes/test003a.nt
RDFCore Telecon 2002-11-22
datatypes/test008a.nt
datatypes/test008b.nt
RDFCore Telecon 2002-10-11
RDF + RDFS + DT(rdf:XMLLiteral)
datatypes/test010.nt
FALSE
RDFCore Telecon 2002-10-11
RDF + RDFS
pfps-10/test001a.nt
pfps-10/test001b.nt
Editorial fix for issue PFPS-10
RDF + RDFS
rdfms-seq-representation/empty.nt
rdfms-seq-representation/test002.nt
RDFCore Telecon 2003-01-10
RDF + RDFS
rdfms-seq-representation/test003a.nt
rdfms-seq-representation/test003b.nt
RDFCore Telecon 2003-01-10
RDF + RDFS
rdfms-seq-representation/empty.nt
rdfms-seq-representation/test004.nt
RDFCore Telecon 2003-01-10
RDF
tex-01/test001.rdf
tex-01/test002.rdf
RDFCore Telecon 2003-07-18
RDF
tex-01/test002.rdf
tex-01/test001.rdf
RDFCore Telecon 2003-07-18
RDF + RDFS + DT(xsd:int)
xmlsch-02/test001.rdf
xmlsch-02/test003.rdf
RDFCore Telecon 2003-07-18
Negative Entailment tests (test cases: 16)
Rules
Premise files
Conclusion file
Warning?
Approved
RDF + RDFS + DT(xsd:decimal, xsd:integer)
datatypes-intensional/test001.nt
FALSE
RDFCore Telecon 2003-09-05
RDF + RDFS + DT(xsd:integer)
datatypes/test002.nt
datatypes/test002b.nt
RDFCore Telecon 2002-11-22
datatypes/test009a.nt
datatypes/test009b.nt
RDFCore Telecon 2002-10-11
RDF + RDFS
horst-01/test001.rdf
horst-01/test002.rdf
RDFCore Telecon 2003-07-18
RDF + RDFS
horst-01/test003.rdf
horst-01/test004.rdf
RDFCore Telecon 2003-07-18
rdfms-xmllang/test007a.nt
rdfms-xmllang/test007b.nt
RDFCore Telecon 2003-01-10
rdfms-xmllang/test007b.nt
rdfms-xmllang/test007c.nt
RDFCore Telecon 2003-01-10
rdfms-xmllang/test007c.nt
rdfms-xmllang/test007a.nt
RDFCore Telecon 2003-01-10
RDF + RDFS
rdfs-container-membership-superProperty/not1P.rdf
rdfs-container-membership-superProperty/not1C.rdf
RDFCore Telecon 2003-01-10
RDF
statement-entailment/test001a.nt
statement-entailment/test001b.nt
RDFCore Telecon 2002-02-15
RDF
statement-entailment/test002a.nt
statement-entailment/test002b.nt
RDFCore Telecon 2002-02-15
RDF + RDFS
statement-entailment/test001a.nt
statement-entailment/test001b.nt
RDFCore Telecon 2002-02-15
RDF + RDFS
statement-entailment/test002a.nt
statement-entailment/test002b.nt
RDFCore Telecon 2002-02-15
RDF + RDFS + DT(xsd:int)
xmlsch-02/test001.rdf
xmlsch-02/test002.rdf
RDFCore Telecon 2003-07-18
RDF + RDFS + DT(xsd:int)
xmlsch-02/test002.rdf
xmlsch-02/test001.rdf
RDFCore Telecon 2003-07-18
RDF + RDFS + DT(xsd:int)
xmlsch-02/test002.rdf
xmlsch-02/test003.rdf
RDFCore Telecon 2003-07-18
Miscellaneous tests (test cases: 1)
Related documents
Approved
rdfms-uri-substructure/error001.nt
RDFCore Telecon 2003-01-10
Issue:
rdf-charmod-literals
has 1 tests
Positive parser tests (test cases: 1)
Input files
Output file
Warning?
Approved
rdf-charmod-literals/test001.rdf
rdf-charmod-literals/test001.nt
RDFCore Telecon 2002-04-05
Issue:
rdf-charmod-uris
has 4 tests
Positive parser tests (test cases: 2)
Input files
Output file
Warning?
Approved
rdf-charmod-uris/test001.rdf
rdf-charmod-uris/test001.nt
RDFCore Telecon 2002-04-26
rdf-charmod-uris/test002.rdf
rdf-charmod-uris/test002.nt
RDFCore Telecon 2002-04-26
Negative Entailment tests (test cases: 2)
Rules
Premise files
Conclusion file
Warning?
Approved
RDF
rdf-charmod-uris/test001.rdf
rdf-charmod-uris/test002.rdf
RDFCore Telecon 2002-04-26
RDF
rdf-charmod-uris/test002.rdf
rdf-charmod-uris/test001.rdf
RDFCore Telecon 2002-04-26
Issue:
rdf-containers-syntax-vs-schema
has 9 tests
Positive parser tests (test cases: 7)
Input files
Output file
Warning?
Approved
rdf-containers-syntax-vs-schema/test001.rdf
rdf-containers-syntax-vs-schema/test001.nt
RDFCore Telecon 2001-06-29
rdf-containers-syntax-vs-schema/test002.rdf
rdf-containers-syntax-vs-schema/test002.nt
RDFCore Telecon 2001-06-29
rdf-containers-syntax-vs-schema/test003.rdf
rdf-containers-syntax-vs-schema/test003.nt
RDFCore Telecon 2001-06-29
rdf-containers-syntax-vs-schema/test004.rdf
rdf-containers-syntax-vs-schema/test004.nt
RDFCore Telecon 2001-06-29
rdf-containers-syntax-vs-schema/test006.rdf
rdf-containers-syntax-vs-schema/test006.nt
RDFCore Telecon 2001-06-29
rdf-containers-syntax-vs-schema/test007.rdf
rdf-containers-syntax-vs-schema/test007.nt
RDFCore Telecon 2001-06-29
rdf-containers-syntax-vs-schema/test008.rdf
rdf-containers-syntax-vs-schema/test008.nt
RDFCore Telecon 2001-06-29
Negative parser tests (test cases: 2)
Input file
Approved
rdf-containers-syntax-vs-schema/error001.rdf
RDFCore Telecon 2001-06-29
rdf-containers-syntax-vs-schema/error002.rdf
RDFCore Telecon 2001-11-30
Issue:
rdf-ns-prefix-confusion
has 11 tests
Positive parser tests (test cases: 11)
Input files
Output file
Warning?
Approved
rdf-ns-prefix-confusion/test0001.rdf
rdf-ns-prefix-confusion/test0001.nt
RDFCore Telecon 2001-05-25
rdf-ns-prefix-confusion/test0003.rdf
rdf-ns-prefix-confusion/test0003.nt
RDFCore Telecon 2001-05-25
rdf-ns-prefix-confusion/test0004.rdf
rdf-ns-prefix-confusion/test0004.nt
RDFCore Telecon 2001-05-25
rdf-ns-prefix-confusion/test0005.rdf
rdf-ns-prefix-confusion/test0005.nt
RDFCore Telecon 2001-05-25
rdf-ns-prefix-confusion/test0006.rdf
rdf-ns-prefix-confusion/test0006.nt
RDFCore Telecon 2001-05-25
rdf-ns-prefix-confusion/test0009.rdf
rdf-ns-prefix-confusion/test0009.nt
RDFCore Telecon 2001-05-25
rdf-ns-prefix-confusion/test0010.rdf
rdf-ns-prefix-confusion/test0010.nt
RDFCore Telecon 2001-05-25
rdf-ns-prefix-confusion/test0011.rdf
rdf-ns-prefix-confusion/test0011.nt
RDFCore Telecon 2001-05-25
rdf-ns-prefix-confusion/test0012.rdf
rdf-ns-prefix-confusion/test0012.nt
RDFCore Telecon 2001-05-25
rdf-ns-prefix-confusion/test0013.rdf
rdf-ns-prefix-confusion/test0013.nt
RDFCore Telecon 2001-05-25
rdf-ns-prefix-confusion/test0014.rdf
rdf-ns-prefix-confusion/test0014.nt
RDFCore Telecon 2001-05-25
Issue:
rdfms-difference-between-ID-and-about
has 4 tests
Positive parser tests (test cases: 3)
Input files
Output file
Warning?
Approved
rdfms-difference-between-ID-and-about/test1.rdf
rdfms-difference-between-ID-and-about/test1.nt
RDFCore Telecon 2001-12-14
rdfms-difference-between-ID-and-about/test2.rdf
rdfms-difference-between-ID-and-about/test2.nt
RDFCore Telecon 2003-01-10
rdfms-difference-between-ID-and-about/test3.rdf
rdfms-difference-between-ID-and-about/test3.nt
RDFCore Telecon 2003-01-10
Negative parser tests (test cases: 1)
Input file
Approved
rdfms-difference-between-ID-and-about/error1.rdf
RDFCore Telecon 2001-12-14
Issue:
rdfms-duplicate-member-props
has 1 tests
Positive parser tests (test cases: 1)
Input files
Output file
Warning?
Approved
rdfms-duplicate-member-props/test001.rdf
rdfms-duplicate-member-props/test001.nt
RDFCore Telecon 2002-05-03
Issue:
rdfms-empty-property-elements
has 20 tests
Positive parser tests (test cases: 17)
Input files
Output file
Warning?
Approved
rdfms-empty-property-elements/test001.rdf
rdfms-empty-property-elements/test001.nt
RDFCore Telecon 2001-05-25
rdfms-empty-property-elements/test002.rdf
rdfms-empty-property-elements/test002.nt
RDFCore Telecon 2001-05-25
rdfms-empty-property-elements/test003.rdf
rdfms-empty-property-elements/test003.nt
RDFCore Telecon 2001-05-25
rdfms-empty-property-elements/test004.rdf
rdfms-empty-property-elements/test004.nt
RDFCore Telecon 2001-05-25
rdfms-empty-property-elements/test005.rdf
rdfms-empty-property-elements/test005.nt
RDFCore Telecon 2001-05-25
rdfms-empty-property-elements/test006.rdf
rdfms-empty-property-elements/test006.nt
RDFCore Telecon 2001-05-25
rdfms-empty-property-elements/test007.rdf
rdfms-empty-property-elements/test007.nt
RDFCore Telecon 2001-05-25
rdfms-empty-property-elements/test008.rdf
rdfms-empty-property-elements/test008.nt
RDFCore Telecon 2001-05-25
rdfms-empty-property-elements/test009.rdf
rdfms-empty-property-elements/test009.nt
RDFCore Telecon 2001-05-25
rdfms-empty-property-elements/test010.rdf
rdfms-empty-property-elements/test010.nt
RDFCore Telecon 2001-05-25
rdfms-empty-property-elements/test011.rdf
rdfms-empty-property-elements/test011.nt
RDFCore Telecon 2001-05-25
rdfms-empty-property-elements/test012.rdf
rdfms-empty-property-elements/test012.nt
RDFCore Telecon 2001-05-25
rdfms-empty-property-elements/test013.rdf
rdfms-empty-property-elements/test013.nt
RDFCore Telecon 2001-05-25
rdfms-empty-property-elements/test014.rdf
rdfms-empty-property-elements/test014.nt
RDFCore Telecon 2001-05-25
rdfms-empty-property-elements/test015.rdf
rdfms-empty-property-elements/test015.nt
RDFCore Telecon 2001-05-25
rdfms-empty-property-elements/test016.rdf
rdfms-empty-property-elements/test016.nt
RDFCore Telecon 2003-01-10
rdfms-empty-property-elements/test017.rdf
rdfms-empty-property-elements/test017.nt
RDFCore Telecon 2003-01-10
Negative parser tests (test cases: 3)
Input file
Approved
rdfms-empty-property-elements/error001.rdf
RDFCore Telecon 2001-05-25
rdfms-empty-property-elements/error002.rdf
RDFCore Telecon 2001-05-25
rdfms-empty-property-elements/error003.rdf
RDFCore Telecon 2001-05-25
Issue:
rdfms-identity-anon-resources
has 5 tests
Positive parser tests (test cases: 5)
Input files
Output file
Warning?
Approved
rdfms-identity-anon-resources/test001.rdf
rdfms-identity-anon-resources/test001.nt
RDFCore Telecon 2001-10-19
rdfms-identity-anon-resources/test002.rdf
rdfms-identity-anon-resources/test002.nt
RDFCore Telecon 2001-10-19
rdfms-identity-anon-resources/test003.rdf
rdfms-identity-anon-resources/test003.nt
RDFCore Telecon 2001-10-19
rdfms-identity-anon-resources/test004.rdf
rdfms-identity-anon-resources/test004.nt
RDFCore Telecon 2001-10-19
rdfms-identity-anon-resources/test005.rdf
rdfms-identity-anon-resources/test005.nt
RDFCore Telecon 2001-10-19
Issue:
rdfms-not-id-and-resource-attr
has 4 tests
Positive parser tests (test cases: 4)
Input files
Output file
Warning?
Approved
rdfms-not-id-and-resource-attr/test001.rdf
rdfms-not-id-and-resource-attr/test001.nt
RDFCore Telecon 2002-03-15
rdfms-not-id-and-resource-attr/test002.rdf
rdfms-not-id-and-resource-attr/test002.nt
RDFCore Telecon 2002-03-15
rdfms-not-id-and-resource-attr/test004.rdf
rdfms-not-id-and-resource-attr/test004.nt
RDFCore Telecon 2002-03-15
rdfms-not-id-and-resource-attr/test005.rdf
rdfms-not-id-and-resource-attr/test005.nt
RDFCore Telecon 2002-03-15
Issue:
rdfms-para196
has 1 tests
Positive parser tests (test cases: 1)
Input files
Output file
Warning?
Approved
rdfms-para196/test001.rdf
rdfms-para196/test001.nt
RDFCore Telecon 2002-01-11
Issue:
rdfms-rdf-names-use
has 60 tests
Positive parser tests (test cases: 40)
Input files
Output file
Warning?
Approved
rdfms-rdf-names-use/test-001.rdf
rdfms-rdf-names-use/test-001.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-002.rdf
rdfms-rdf-names-use/test-002.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-003.rdf
rdfms-rdf-names-use/test-003.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-004.rdf
rdfms-rdf-names-use/test-004.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-005.rdf
rdfms-rdf-names-use/test-005.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-006.rdf
rdfms-rdf-names-use/test-006.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-007.rdf
rdfms-rdf-names-use/test-007.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-008.rdf
rdfms-rdf-names-use/test-008.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-009.rdf
rdfms-rdf-names-use/test-009.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-010.rdf
rdfms-rdf-names-use/test-010.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-011.rdf
rdfms-rdf-names-use/test-011.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-012.rdf
rdfms-rdf-names-use/test-012.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-013.rdf
rdfms-rdf-names-use/test-013.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-014.rdf
rdfms-rdf-names-use/test-014.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-015.rdf
rdfms-rdf-names-use/test-015.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-016.rdf
rdfms-rdf-names-use/test-016.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-017.rdf
rdfms-rdf-names-use/test-017.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-018.rdf
rdfms-rdf-names-use/test-018.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-019.rdf
rdfms-rdf-names-use/test-019.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-020.rdf
rdfms-rdf-names-use/test-020.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-021.rdf
rdfms-rdf-names-use/test-021.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-022.rdf
rdfms-rdf-names-use/test-022.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-023.rdf
rdfms-rdf-names-use/test-023.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-024.rdf
rdfms-rdf-names-use/test-024.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-025.rdf
rdfms-rdf-names-use/test-025.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-026.rdf
rdfms-rdf-names-use/test-026.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-027.rdf
rdfms-rdf-names-use/test-027.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-028.rdf
rdfms-rdf-names-use/test-028.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-029.rdf
rdfms-rdf-names-use/test-029.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-030.rdf
rdfms-rdf-names-use/test-030.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-031.rdf
rdfms-rdf-names-use/test-031.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-032.rdf
rdfms-rdf-names-use/test-032.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-033.rdf
rdfms-rdf-names-use/test-033.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-034.rdf
rdfms-rdf-names-use/test-034.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-035.rdf
rdfms-rdf-names-use/test-035.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-036.rdf
rdfms-rdf-names-use/test-036.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/test-037.rdf
rdfms-rdf-names-use/test-037.nt
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/warn-001.rdf
rdfms-rdf-names-use/warn-001.nt
allowed with warnings
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/warn-002.rdf
rdfms-rdf-names-use/warn-002.nt
allowed with warnings
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/warn-003.rdf
rdfms-rdf-names-use/warn-003.nt
allowed with warnings
RDFCore Telecon 2001-11-30
Negative parser tests (test cases: 20)
Input file
Approved
rdfms-rdf-names-use/error-001.rdf
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/error-002.rdf
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/error-003.rdf
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/error-004.rdf
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/error-005.rdf
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/error-006.rdf
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/error-007.rdf
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/error-008.rdf
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/error-009.rdf
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/error-010.rdf
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/error-011.rdf
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/error-012.rdf
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/error-013.rdf
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/error-014.rdf
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/error-015.rdf
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/error-016.rdf
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/error-017.rdf
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/error-018.rdf
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/error-019.rdf
RDFCore Telecon 2001-11-30
rdfms-rdf-names-use/error-020.rdf
RDFCore Telecon 2001-11-30
Issue:
rdfms-seq-representation
has 1 tests
Positive parser tests (test cases: 1)
Input files
Output file
Warning?
Approved
rdfms-seq-representation/test001.rdf
rdfms-seq-representation/test001.nt
RDFCore Telecon 2002-05-31
Issue:
rdfms-syntax-incomplete
has 10 tests
Positive parser tests (test cases: 4)
Input files
Output file
Warning?
Approved
rdfms-syntax-incomplete/test001.rdf
rdfms-syntax-incomplete/test001.nt
RDFCore Telecon 2003-01-10
rdfms-syntax-incomplete/test002.rdf
rdfms-syntax-incomplete/test002.nt
RDFCore Telecon 2003-01-10
rdfms-syntax-incomplete/test003.rdf
rdfms-syntax-incomplete/test003.nt
RDFCore Telecon 2003-01-10
rdfms-syntax-incomplete/test004.rdf
rdfms-syntax-incomplete/test004.nt
RDFCore Telecon 2003-01-10
Negative parser tests (test cases: 6)
Input file
Approved
rdfms-syntax-incomplete/error001.rdf
RDFCore Telecon 2003-01-10
rdfms-syntax-incomplete/error002.rdf
RDFCore Telecon 2003-01-10
rdfms-syntax-incomplete/error003.rdf
RDFCore Telecon 2003-01-10
rdfms-syntax-incomplete/error004.rdf
RDFCore Telecon 2003-01-10
rdfms-syntax-incomplete/error005.rdf
RDFCore Telecon 2003-01-10
rdfms-syntax-incomplete/error006.rdf
RDFCore Telecon 2003-01-10
Issue:
rdfms-xml-base
has 12 tests
Positive parser tests (test cases: 12)
Input files
Output file
Warning?
Approved
xmlbase/test001.rdf
xmlbase/test001.nt
RDFCore Telecon 2002-03-15
xmlbase/test002.rdf
xmlbase/test002.nt
RDFCore Telecon 2002-03-15
xmlbase/test003.rdf
xmlbase/test003.nt
RDFCore Telecon 2002-03-15
xmlbase/test004.rdf
xmlbase/test004.nt
RDFCore Telecon 2002-03-15
xmlbase/test006.rdf
xmlbase/test006.nt
RDFCore Telecon 2002-03-15
xmlbase/test007.rdf
xmlbase/test007.nt
RDFCore Telecon 2002-03-15
xmlbase/test008.rdf
xmlbase/test008.nt
RDFCore Telecon 2002-03-15
xmlbase/test009.rdf
xmlbase/test009.nt
RDFCore Telecon 2002-03-15
xmlbase/test010.rdf
xmlbase/test010.nt
RDFCore Telecon 2002-03-15
xmlbase/test011.rdf
xmlbase/test011.nt
RDFCore Telecon 2002-03-15
xmlbase/test013.rdf
xmlbase/test013.nt
RDFCore Telecon 2002-03-15
xmlbase/test014.rdf
xmlbase/test014.nt
RDFCore Telecon 2002-03-15
Issue:
rdfms-xml-literal-namespaces
has 2 tests
Positive parser tests (test cases: 2)
Input files
Output file
Warning?
Approved
rdfms-xml-literal-namespaces/test001.rdf
rdfms-xml-literal-namespaces/test001.nt
RDFCore Telecon 2003-01-10
rdfms-xml-literal-namespaces/test002.rdf
rdfms-xml-literal-namespaces/test002.nt
RDFCore Telecon 2003-01-10
Issue:
rdfs-domain-and-range
has 4 tests
Positive parser tests (test cases: 2)
Input files
Output file
Warning?
Approved
rdfs-domain-and-range/test001.rdf
rdfs-domain-and-range/test001.nt
RDFCore Telecon 2001-10-19
rdfs-domain-and-range/test002.rdf
rdfs-domain-and-range/test002.nt
RDFCore Telecon 2001-10-19
Negative Entailment tests (test cases: 2)
Rules
Premise files
Conclusion file
Warning?
Approved
RDF + RDFS
rdfs-domain-and-range/premises006.rdf
rdfs-domain-and-range/nonconclusions006.rdf
RDFCore Telecon 2003-01-10
RDF + RDFS
rdfs-domain-and-range/premises005.rdf
rdfs-domain-and-range/nonconclusions005.rdf
RDFCore Telecon 2003-01-10
Issue:
rdfs-no-cycles-in-subClassOf
has 1 tests
Positive Entailment tests (test cases: 1)
Rules
Premise files
Conclusion file
Warning?
Approved
RDF + RDFS
rdfs-no-cycles-in-subClassOf/test001.rdf
rdfs-no-cycles-in-subClassOf/test001.nt
RDFCore Telecon 2001-10-12
Issue:
rdfs-no-cycles-in-subPropertyOf
has 1 tests
Positive Entailment tests (test cases: 1)
Rules
Premise files
Conclusion file
Warning?
Approved
RDF + RDFS
rdfs-no-cycles-in-subPropertyOf/test001.rdf
rdfs-no-cycles-in-subPropertyOf/test001.nt
RDFCore Telecon 2001-10-12
Issue:
rdfs-subClassOf-a-Property
has 1 tests
Negative Entailment tests (test cases: 1)
Rules
Premise files
Conclusion file
Warning?
Approved
RDF + RDFS
rdfs-subClassOf-a-Property/test001.nt
FALSE
RDFCore Telecon 2003-01-10
Issue:
rdfs-subPropertyOf-semantics
has 1 tests
Positive Entailment tests (test cases: 1)
Rules
Premise files
Conclusion file
Warning?
Approved
RDF + RDFS
rdfs-subPropertyOf-semantics/test001.nt
rdfs-subPropertyOf-semantics/test002.nt
RDFCore Telecon 2003-01-10
Issue:
entailment-from-inconsistent-graph
has 2 tests
Positive Entailment tests (test cases: 2)
Rules
Premise files
Conclusion file
Warning?
Approved
RDF + RDFS
rdfs-entailment/test001.nt
FALSE
RDF + RDFS
FALSE
rdfs-entailment/test002.nt
Issue:
I5.24-IF-or-IFF-property-properties
has 2 tests
Negative Entailment tests (test cases: 2)
Rules
Premise files
Conclusion file
Warning?
Approved
RDF + RDFS
rdfs-domain-and-range/premises006.rdf
rdfs-domain-and-range/nonconclusions006.rdf
RDFCore Telecon 2003-01-10
RDF + RDFS
rdfs-domain-and-range/premises005.rdf
rdfs-domain-and-range/nonconclusions005.rdf
RDFCore Telecon 2003-01-10
2.3. Test Cases Not
Approved
The test case repository contains test cases that have not been
approved. Such test cases are not enumerated in this document but a
list of them is available at
2.4. Running the Test
Cases
The test case manifest format was deliberately chosen to be a
simple, declarative description of the test cases. Parser tests can
be run in conjunction with simple tools such as ntc[
NTC
]. A parser should pass all the
positive parser tests, and reject all the negative parser tests.
Tools like Euler
EULER
have been used to run the entailment tests.
Due to the rules of entailment tests, a positive or negative
entailment test case with an empty conclusion document can be used
to illustrate semantic constraints associated with sets of
entailment rules.
The test cases have been created to illustrate the resolution of
particular issues on the
RDF Issue
Tracking
list. Consequently, test case results should always be
interpreted in conjunction with the resolution of the associated
issue and the description (if any) attached to the test case in the
manifest.
3. N-Triples
N-Triples is a line-based, plain text format for encoding an RDF
graph. It was designed to be a fixed subset of N3[
N3
] [
N3-Primer
] and hence N3 tools such as
cwm [
CWM
],
n-triples2kif [
N-TRIPLES2KIF
],
and Euler [
EULER
can be used to read and process it.
cwm can output this format when invoked as
"cwm -ntriples".
It is recommended, but not required, that N-Triples content is
stored in files with an '.nt' suffix to distinguish them from
N3.
The Internet media type / MIME type of N-Triples is text/plain
and the character encoding is 7-bit US-ASCII.
NOTE
: N-Triples is an RDF syntax for
expressing RDF test cases and defining the correspondence
between RDF/XML and the RDF abstract syntax. RDF/XML
RDF-SYNTAX
is the recommended syntax for applications to exchange
RDF information.
3.1. Extended
Backus-Naur Form (EBNF) Grammar
An N-Triples document is a sequence of US-ASCII characters and
is defined by the
ntripleDoc
grammar term
below. Parsing it results in a sequence of
RDF triples
formed
from the
subject
predicate
and
object
productions.
This EBNF is
the notation used
in XML 1.0 second edition
ntripleDoc
::=
line
line
::=
ws
* (
comment
triple
)?
eoln
comment
::=
'#' (
character
- (
cr
lf
) )*
triple
::=
subject
ws
predicate
ws
object
ws
* '.'
ws
subject
::=
uriref
nodeID
predicate
::=
uriref
object
::=
uriref
nodeID
literal
uriref
::=
'<'
absoluteURI
'>'
nodeID
::=
'_:'
name
literal
::=
langString
datatypeString
langString
::=
'"'
string
'"' ( '@'
language
)?
datatypeString
::=
'"'
string
'"' '^^'
uriref
language
::=
[a-z]+ ('-' [a-z0-9]+ )*
encoding a
language tag
ws
::=
space
tab
eoln
::=
cr
lf
cr
lf
space
::=
#x20 /* US-ASCII space - decimal 32 */
cr
::=
#xD /* US-ASCII carriage return - decimal 13 */
lf
::=
#xA /* US-ASCII line feed - decimal 10 */
tab
::=
#x9 /* US-ASCII horizontal tab - decimal 9 */
string
::=
character
* with escapes as
defined in section
Strings
name
::=
[A-Za-z][A-Za-z0-9]*
absoluteURI
::=
character
+ with escapes as
defined in section
URI
References
character
::=
[#x20-#x7E] /* US-ASCII
space
to
decimal 126 */
These productions encode concepts defined in the
RDF Concepts and Abstract Syntax
RDF-CONCEPTS
] working draft as follows:
N-Triples production
RDF Concept encoded
triple
triple
subject
subject
predicate
predicate
object
object
absoluteURI
RDF URI reference
nodeID
Identifier for a
blank node
langString
plain literal
datatypeString
typed literal
3.2 Strings
N-Triples strings are sequences of US-ASCII
character
productions encoding [
UNICODE
character
strings
. The characters outside the US-ASCII range and some
other specific characters are made available by \-escape sequences
as follows:
Unicode character
(with code point
N-Triples encoding
[#x0-#x8]
\u
HHHH
4 required hexadecimal digits
HHHH
encoding Unicode character
#x9
\t
#xA
\n
[#xB-#xC]
\u
HHHH
4 required hexadecimal digits
HHHH
encoding Unicode character
#xD
\r
[#xE-#x1F]
\u
HHHH
4 required hexadecimal digits
HHHH
encoding Unicode character
[#x20-#x21]
the character
#x22
\"
[#x23-#x5B]
the character
#x5C
\\
[#x5D-#x7E]
the character
[#x7F-#xFFFF]
\u
HHHH
4 required hexadecimal digits
HHHH
encoding Unicode character
[#10000-#x10FFFF]
\U
HHHHHHHH
8 required hexadecimal digits
HHHHHHHH
encoding Unicode character
where
is a hexadecimal digit:
[#x30-#x39],[#x41-#x46] (0-9, uppercase A-F).
This escaping satisfies the [
CHARMOD
] section
Reference
Processing Model
on making the full Unicode character range U+0
to U+10FFFF available to applications and providing only one way to
escape any character.
3.3 URI
References
The
absoluteURI
production
encodes a Unicode string representing an
RDF URI references
as specified in
RDF-CONCEPTS
].
These are encoded in N-Triples using
the escapes described in section
Strings
3.4.
Example
The following N-Triples file:
_:a
_:a
represents the same RDF graph as the following RDF/XML:
3.5. N-Triples
Tests
The N-Triple test file at
contains multiple tests of legal N-Triples.
4 References
Normative
References
[APPROVED]
approved_20031114.zip
approved test cases at time of publication.
The
latest version
of this archive is available at
[FULLTESTS]
all_20031114.zip
Test case archive (including unapproved tests).
The
latest version
of this archive is available at
[MANIFEST]
Manifest.rdf
This file (available at
describes all the test cases within the repository.
[MANIFEST-HEAD]
Manifest header
A sample prefix which can be used to introduce a manifest file.
[MANIFEST-TAIL]
Manifest footer
A sample suffix which can be used to close a manifest file.
[CWM]
cwm
: T. Berners-Lee et al.
An RDF/N3 processing tool.
[N-TRIPLES2KIF]
n-triples2kif.pl
An RDF processing tool.
[EULER]
Euler
: Jos deRoo.
An RDF inference engine.
[ISSUES]
RDF Issue Tracking
, McBride et al.
[REPOSITORY]
Repository for
RDFCore Test Cases
hosted at the W3C.
[RDFMS]
Resource
Description Framework (RDF) Model and Syntax
Specification
, O. Lassila and R. Swick, Editors, World
Wide Web Consortium Recommendation. 22 February 1999. This
version is http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/.
The
latest version
of RDF M&S
is available at
[RDF-SCHEMA]
Resource
Description Framework (RDF) Schema Specification 1.0
Dan Brickley, R.V. Guha, Editors, World Wide Web Consortium
Candidate Recommendation, 27 March 2000. This version is
latest version
of RDF
Schema is http://www.w3.org/TR/rdf-schema/.
[UNICODE]
The Unicode Standard
Version
3.0
, Addison Wesley, Reading MA, 2000, ISBN: 0-201-61633-5.
This document is
[CHARMOD]
Character
Model for the World Wide Web 1.0
, M. Dürst, F.
Yergeau, R. Ishida, M. Wolf, T. Texin, Editors, World
Wide Web Consortium Working Draft, work in progress, 22 August
2003. This version of the Character Model is
latest version of the
Character Model
is at http://www.w3.org/TR/charmod/.
[RDF-CONCEPTS]
Resource
Description Framework (RDF): Concepts and Abstract
Syntax
, Klyne G., Carroll J. (Editors), W3C Recommendation, 10 February 2004.
This
version
is
latest version
is http://www.w3.org/TR/rdf-concepts/.
[RDF-SEMANTICS]
RDF
Semantics
, Hayes P. (Editor), W3C Recommendation, 10 February 2004.
This
version
is http://www.w3.org/TR/2004/REC-rdf-mt-20040210/.
The
latest version
is http://www.w3.org/TR/rdf-mt/.
[RDF-SYNTAX]
RDF/XML Syntax Specification (Revised)
, Beckett
D. (Editor), W3C Recommendation, 10 February 2004.
This version
is
The
latest
version
is
Informative
References
[RDF-PRIMER]
RDF
Primer
, Manola F., Miller E., Editors, W3C Recommendation, 10 February 2004.
This
version
is
latest version
is at
[RDF-VOCABULARY]
RDF
Vocabulary Description Language 1.0: RDF Schema
Brickley D., Guha R.V. (Editors), W3C Recommendation, 10 February 2004.
This
version
is
latest version
is http://www.w3.org/TR/rdf-schema/.
[N3]
Notation
, Tim Berners-Lee
[N3-Primer]
Primer: Getting
into RDF & Semantic Web using N3
, Tim
Berners-Lee
[NTC]
NTC:
A simple N-Triples isomorphism test utility
, Jan
Grant
5 Acknowledgments
(Informative)
Many thanks to Art Barstow (ex-W3C), former main editor of this
document, for his sterling work on editing and managing the RDF
test cases, which he had been doing well before the RDF Core WG
started.
The editors would also like to thank Jos DeRoo, of AGFA, for his
excellent work in the implementation of an RDF reasoner capable of
running the entailment test cases.
Thanks are also due to the RDF parser implementers who took the
time to run, and submit corrections to, our parser tests.
The following Working Group members have directly contributed to
this document and/or contributed test cases.
Art Barstow, ex-W3C Fellow
Jeremy Carroll, HP Labs Bristol
Dan Connolly, W3C
Jos DeRoo, AGFA
Graham Klyne, Clearswift and Nine by Nine
Brian McBride, HP Labs Bristol
Aaron Swartz, HWG
This document is a product of extended deliberations by the RDF
Core Working Group, whose members have included: Art Barstow (W3C)
Dave Beckett (ILRT), Dan Brickley (W3C/ILRT), Dan Connolly (W3C),
Jeremy Carroll (Hewlett Packard), Ron Daniel (Interwoven Inc), Bill
dehOra (InterX), Jos De Roo (AGFA), Jan Grant (ILRT), Graham Klyne
(Clearswift and Nine by Nine), Frank Manola (MITRE Corporation),
Brian McBride (Hewlett Packard), Eric Miller (W3C), Stephen
Petschulat (IBM), Patrick Stickler (Nokia), Aaron Swartz (HWG),
Mike Dean (BBN Technologies / Verizon), R. V. Guha (Alpiri Inc),
Pat Hayes (IHMC), Sergey Melnik (Stanford University), Martyn
Horner (Profium Ltd).
This specification also draws upon an earlier RDF Model and
Syntax document edited by Ora Lassilla and Ralph Swick, and RDF
Schema edited by Dan Brickley and R. V. Guha. RDF and RDF Schema
Working group members who contributed to this earlier work are:
Nick Arnett (Verity), Tim Berners-Lee (W3C), Tim Bray (Textuality),
Dan Brickley (ILRT / University of Bristol), Walter Chang (Adobe),
Sailesh Chutani (Oracle), Dan Connolly (W3C), Ron Daniel
(DATAFUSION), Charles Frankston (Microsoft), Patrick Gannon
(CommerceNet), RV Guha (Epinions, previously of Netscape
Communications), Tom Hill (Apple Computer), Arthur van Hoff
(Marimba), Renato Iannella (DSTC), Sandeep Jain (Oracle), Kevin
Jones, (InterMind), Emiko Kezuka (Digital Vision Laboratories), Joe
Lapp (webMethods Inc.), Ora Lassila (Nokia Research Center), Andrew
Layman (Microsoft), Ralph LeVan (OCLC), John McCarthy (Lawrence
Berkeley National Laboratory), Chris McConnell (Microsoft), Murray
Maloney (Grif), Michael Mealling (Network Solutions), Norbert
Mikula (DataChannel), Eric Miller (OCLC), Jim Miller (W3C,
emeritus), Frank Olken (Lawrence Berkeley National Laboratory),
Jean Paoli (Microsoft), Sri Raghavan (Digital/Compaq), Lisa Rein
(webMethods Inc.), Paul Resnick (University of Michigan), Bill
Roberts (KnowledgeCite), Tsuyoshi Sakata (Digital Vision
Laboratories), Bob Schloss (IBM), Leon Shklar (Pencom Web Works),
David Singer (IBM), Wei (William) Song (SISU), Neel Sundaresan
(IBM), Ralph Swick (W3C), Naohiko Uramoto (IBM), Charles Wicksteed
(Reuters Ltd.), Misha Wolf (Reuters Ltd.), Lauren Wood
(SoftQuad).
Appendix A: Change Log (Informative)
Changes since
Added explicit simple entailment marker to entailment tests.
Reworded the pass and failure criteria for negative entailment tests according
to suggested wording from Pat Hayes.
Added test case for RDF/XML without an enclosing rdf:RDF
element (rdf-element-not-mandatory/test001).
Removed N-Triples reference to language tags and RFC3066, use
the RDF concepts definition. A language tag cannot start with a
digit.
Changes since
Added test cases for intensional interpretation of datatypes.
Added test case: plain literals and xsd:string denotations overlap.
Editorial change. The caption on the test case table now makes
it clear that it refers only to the resolution of relative URLs
within the table
Editorial change. Updated section
3. N-Triples
NOTE on the purpose of N-Triples to say it is used to map abstract RDF
syntax and RDF/XML.
Terminological change. Updated section
2.1. Organization
To use the more acceptable term, "graph equivalence".
Substantive change. Updated section
2.1. Organization
to include fourth condition for datatype support when
describing datatype entailment tests.
Editorial change. Updated references throughout to remove URLs from prose;
additional changes as suggested by
Susan Lesch
Editorial change. Updated section
3.1. Extended Backus-Naur Form (EBNF) Grammar
to add
a new table showing how the N-Triples productions encode the respective
RDF concepts from [
RDF-CONCEPTS
].
Editorial change. Updated section
3.3 URI References
to say less about URI detail and defer to [
RDF-CONCEPTS
]. Removed reference to RFC2396 (URIs). Made after
comment by Duerst
, 2003-05-08
as
outlined
. Also addresses
comment by Patel-Schneider
, 2003-05-30.
Editorial change. Updated section
3.2 Strings
and the N-Triples escape sequence table to list the encodings
from Unicode character to N-Triples. Made after
comment by Patel-Schneider
, 2003-05-27
as
outlined
Substantive change. Updated
datatypeString
to use
string
rather than
langString
after removal of language tag from all typed literals as
approved
in RDF Core telcon 2003-05-09.
Changes since
Entailment test definitions changed to actually test proper
entailments, not pseudo-entailments.
Support for datatype-aware entailment tests in the manifest.
Pointer to RDF-CONCEPTS for the definition of graph isomorphism
/ equality.
Addition of the
always false
pseudo-document for
entailment tests.
Updated the test case list in this document.
Test case names changed to fragment references into individual
manifest documents.
Changes since
Production
language
. Changed to match
RFC 3066. Added [RFC 2396] to normative references.
3 N-Triples
NOTE reworded. Point to
RDF/XML as exchange syntax.
Production
character
: should be "to
126"
3.2 Strings
Removed suggestion to
use UTF-8 for apps.
Added
3.5. N-Triples Tests
pointing
at the
test file.
Use uppercase hexadecimal digits. Define
and use it for \uHHHH, \uHHHHHHHH.
Removed xmlString.
Changed the N-Triples language separator token to @ in
langString
Added RDF datatyping support using
datatypeString
using the form
^^
Changes since
Updated
3.3 URI References
to
allow Unicode characters in URIs
Merged
Future Work
into
Open Issues
Test case list expanded and reorganized to reflect additional
approved test cases
New
section 2
describing organization
of parser tests, the types of tests and examples of manifest format
that describes them.
Updated editors, added thanks to Art Barstow.
Changed literal to be
langString
xmlString (now gone)
N-Triples remains an ASCII format for now - closed issue on
UTF-8 encoding.
Update references to RDF Model Theory, Syntax WDs
Changes since
Changed the
Approved Test Cases
table so
that it includes links to related files and the Working Group
decision.
Removed the
Test Cases Not Approved
table and added a link to the repository's list of the not approved
test cases.
Added links to ZIP files of the repository's test cases.
Specify the
Future Work
and
Contributors
sections as Informative.
Renamed token bNode to nodeID.
Added RDF Model Theory reference.
Added URI Encoding section, pointing at Charmod rules and
updated absoluteURI grammar rule to use it.
Removed references to Python literals, reason for
\-escaping.
Added 4, 8 required digits for \u, \U string escapes.
Renamed section URIs to URI References.
Appendix B: Open Issues (Informative)
Complete the test cases