test001
type: PositiveParserTest
status: APPROVED
approval: 0326.html
input document: test001.rdf
output document: test001.nt

test001
type: PositiveParserTest
status: APPROVED
approval: 0611.html
description: A simple datatype production; a language+datatype production. Simply duplicate the constructs under http://www.w3.org/2000/10/rdf-tests/rdfcore/ntriples/test.nt
input document: test001.rdf
output document: test001.nt

test002
type: PositiveParserTest
status: APPROVED
approval: 0611.html
description: A parser is not required to know about well-formed datatyped literals.
input document: test002.rdf
output document: test002.nt

non-well-formed-literal-1
type: PositiveEntailmentTest
status: APPROVED
approval: 0611.html
description: Without datatype knowledge, a "badly-formed" datatyped literal cannot be detected.
entailment rules: 22-rdf-syntax-ns#
entailment rules: rdf-schema#
premise document: test002.nt
conclusion document: test002.nt

non-well-formed-literal-2
type: NegativeEntailmentTest
status: APPROVED
approval: 0611.html
description: With appropriate datatype knowledge, a "badly-formed" datatyped literal can be detected.
entailment rules: 22-rdf-syntax-ns#
entailment rules: rdf-schema#
entailment rules: datatypes#
datatype support: integer
premise document: test002.nt
conclusion document: test002b.nt

semantic-equivalence-within-type-1
type: PositiveEntailmentTest
status: APPROVED
approval: 0611.html
description: Demonstrating the semantic equivalence of two lexical forms of the same datatyped value.
entailment rules: 22-rdf-syntax-ns#
entailment rules: datatypes#
datatype support: integer
premise document: test003a.nt
conclusion document: test003b.nt

semantic-equivalence-within-type-2
type: PositiveEntailmentTest
status: APPROVED
approval: 0611.html
description: As semantic-equivalence-within-type-1; the entailment works both ways.
entailment rules: 22-rdf-syntax-ns#
entailment rules: datatypes#
datatype support: integer
premise document: test003b.nt
conclusion document: test003a.nt

language-important-for-non-dt-entailment-1
type: NegativeEntailmentTest
status: APPROVED
approval: 0611.html
description: Language attributes on a datatyped literal make them distinct for the purposes of non-datatype-aware entailments.
entailment rules: 22-rdf-syntax-ns#
entailment rules: rdf-schema#
premise document: test004a.nt
conclusion document: test004b.nt

language-important-for-non-dt-entailment-2
type: NegativeEntailmentTest
status: APPROVED
approval: 0611.html
description: Language attributes on a datatyped literal make them distinct for the purposes of non-datatype-aware entailments.
entailment rules: 22-rdf-syntax-ns#
entailment rules: rdf-schema#
premise document: test004b.nt
conclusion document: test004c.nt

language-ignored-for-numeric-types-1
type: PositiveEntailmentTest
status: APPROVED
approval: 0611.html
description: Language doesn't affect the semantic equivalence of some datatypes, when doing a DT-entailment.
entailment rules: 22-rdf-syntax-ns#
entailment rules: datatypes#
datatype support: integer
premise document: test004a.nt
conclusion document: test004b.nt

language-ignored-for-numeric-types-2
type: PositiveEntailmentTest
status: APPROVED
approval: 0611.html
description: Language doesn't affect the semantic equivalence of some datatypes, when doing a DT-entailment.
entailment rules: 22-rdf-syntax-ns#
entailment rules: datatypes#
datatype support: integer
premise document: test004b.nt
conclusion document: test004c.nt

language-ignored-for-numeric-types-3
type: PositiveEntailmentTest
status: APPROVED
approval: 0611.html
description: Language doesn't affect the semantic equivalence of some datatypes, when doing a DT-entailment.
entailment rules: 22-rdf-syntax-ns#
entailment rules: datatypes#
datatype support: integer
premise document: test004c.nt
conclusion document: test004a.nt

semantic-equivalence-between-datatypes
type: PositiveEntailmentTest
status: PENDING
description: Members of different datatypes may be semantically equivalent.
entailment rules: 22-rdf-syntax-ns#
entailment rules: datatypes#
datatype support: integer
datatype support: decimal
premise document: test005a.nt
conclusion document: test005b.nt

range-clash
type: PositiveEntailmentTest
status: PENDING
description: Where sufficient DT knowledge is available, a range clash may be detected; the document then contains a contradiction.
entailment rules: 22-rdf-syntax-ns#
entailment rules: rdf-schema#
entailment rules: datatypes#
datatype support: decimal
datatype support: string
premise document: test006.nt
conclusion document: False-Document

language-and-xml-literal
type: NegativeEntailmentTest
status: PENDING
description: Language affects the denotation of rdf:XMLLiteral
entailment rules: 22-rdf-syntax-ns#
entailment rules: rdf-schema#
entailment rules: datatypes#
datatype support: XMLLiteral
premise document: test007a.nt
conclusion document: test007b.nt

test008
type: PositiveEntailmentTest
status: APPROVED
approval: 0131.html
description: From decisions listed in http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2002Oct/0098.html
premise document: test008a.nt
conclusion document: test008b.nt

test009
type: NegativeEntailmentTest
status: APPROVED
approval: 0131.html
description: From decisions listed in http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2002Oct/0098.html
premise document: test009a.nt
conclusion document: test009b.nt

test010
type: PositiveEntailmentTest
status: APPROVED
approval: 0131.html
description: From decisions listed in http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2002Oct/0098.html
entailment rules: 22-rdf-syntax-ns#
entailment rules: rdf-schema#
entailment rules: datatypes#
datatype support: XMLLiteral
premise document: test010.nt
conclusion document: False-Document

test001
type: PositiveParserTest
issue: rdf-charmod-literals
status: APPROVED
approval: 0056.html
discussion: 0016.html
description: Does the treatment of literals conform to charmod ? Test for success of legal Normal Form C literal
input document: test001.rdf
output document: test001.nt

error001
type: NegativeParserTest
issue: rdf-charmod-literals
status: APPROVED
approval: 0056.html
discussion: 0016.html
description: Does the treatment of literals conform to charmod ? Test for failure for literal not in Normal Form C
input document: error001.rdf

error002
type: NegativeParserTest
issue: rdf-charmod-literals
status: APPROVED
approval: 0056.html
discussion: 0016.html
description: Does the treatment of literals conform to charmod ? Test for failure for literal not in Normal Form C
input document: error002.rdf

test001
type: PositiveParserTest
issue: rdf-charmod-uris
status: APPROVED
approval: 0474.html
discussion: 0113.html
description: A uriref is allowed to match non-US ASCII forms conforming to Unicode Normal Form C. No escaping algorithm is applied.
input document: test001.rdf
output document: test001.nt

test002
type: PositiveParserTest
issue: rdf-charmod-uris
status: APPROVED
approval: 0474.html
discussion: 0113.html
description: A uriref which already has % escaping is permitted. No unescaping algorithm is applied.
input document: test002.rdf
output document: test002.nt

error001
type: NegativeParserTest
issue: rdf-charmod-uris
status: OBSOLETED
approval: 0474.html
discussion: 0113.html
description: Test for failure for uriref not in Normal Form C.
input document: error001.rdf

test003
type: NegativeEntailmentTest
issue: rdf-charmod-uris
status: APPROVED
approval: 0474.html
discussion: 0113.html
description: An international URI ref and its %-escaped form label different nodes in the graph. No model theoretic relationship holds between them.
entailment rules: 22-rdf-syntax-ns#
premise document: test001.rdf
conclusion document: test002.rdf

test004
type: NegativeEntailmentTest
issue: rdf-charmod-uris
status: APPROVED
approval: 0474.html
discussion: 0113.html
description: An international URI ref and its %-escaped form label different nodes in the graph. No model theoretic relationship holds between them.
entailment rules: 22-rdf-syntax-ns#
premise document: test002.rdf
conclusion document: test001.rdf

error001
type: NegativeParserTest
issue: rdf-containers-syntax-vs-schema
status: APPROVED
approval: 0000.html
input document: error001.rdf

error002
type: NegativeParserTest
issue: rdf-containers-syntax-vs-schema
status: APPROVED
approval: 0651.html
input document: error002.rdf

test001
type: PositiveParserTest
issue: rdf-containers-syntax-vs-schema
status: APPROVED
approval: 0000.html
input document: test001.rdf
output document: test001.nt

test002
type: PositiveParserTest
issue: rdf-containers-syntax-vs-schema
status: APPROVED
approval: 0000.html
input document: test002.rdf
output document: test002.nt

test003
type: PositiveParserTest
issue: rdf-containers-syntax-vs-schema
status: APPROVED
approval: 0000.html
input document: test003.rdf
output document: test003.nt

test004
type: PositiveParserTest
issue: rdf-containers-syntax-vs-schema
status: APPROVED
approval: 0000.html
input document: test004.rdf
output document: test004.nt

test005
type: PositiveParserTest
issue: rdf-containers-syntax-vs-schema
status: OBSOLETED
approval: 0651.html
input document: test005.rdf
output document: test005.nt

test006
type: PositiveParserTest
issue: rdf-containers-syntax-vs-schema
status: OBSOLETED
approval: 0000.html
input document: test006.rdf
output document: test006.nt

test007
type: PositiveParserTest
issue: rdf-containers-syntax-vs-schema
status: APPROVED
approval: 0000.html
input document: test007.rdf
output document: test007.nt

test008
type: PositiveParserTest
issue: rdf-containers-syntax-vs-schema
status: APPROVED
approval: 0000.html
input document: test008.rdf
output document: test008.nt

test0001
type: PositiveParserTest
issue: rdf-ns-prefix-confusion
status: APPROVED
approval: rdfc25May.html
input document: test0001.rdf
output document: test0001.nt

test0002
type: PositiveParserTest
issue: rdf-ns-prefix-confusion
status: OBSOLETED
approval: rdfc25May.html
input document: test0002.rdf
output document: test0002.nt

test0003
type: PositiveParserTest
issue: rdf-ns-prefix-confusion
status: APPROVED
approval: rdfc25May.html
input document: test0003.rdf
output document: test0003.nt

test0004
type: PositiveParserTest
issue: rdf-ns-prefix-confusion
status: APPROVED
approval: rdfc25May.html
input document: test0004.rdf
output document: test0004.nt

test0005
type: PositiveParserTest
issue: rdf-ns-prefix-confusion
status: APPROVED
approval: rdfc25May.html
input document: test0005.rdf
output document: test0005.nt

test0006
type: PositiveParserTest
issue: rdf-ns-prefix-confusion
status: APPROVED
approval: rdfc25May.html
input document: test0006.rdf
output document: test0006.nt

test0007
type: PositiveParserTest
issue: rdf-ns-prefix-confusion
status: APPROVED
approval: rdfc25May.html
input document: test0007.rdf
output document: test0007.nt

test0008
type: PositiveParserTest
issue: rdf-ns-prefix-confusion
status: OBSOLETE
approval: 0008.html
input document: test0008.rdf
output document: test0008.nt

test0009
type: PositiveParserTest
issue: rdf-ns-prefix-confusion
status: APPROVED
approval: rdfc25May.html
input document: test0009.rdf
output document: test0009.nt

test0010
type: PositiveParserTest
issue: rdf-ns-prefix-confusion
status: APPROVED
approval: rdfc25May.html
input document: test0010.rdf
output document: test0010.nt

test0011
type: PositiveParserTest
issue: rdf-ns-prefix-confusion
status: APPROVED
approval: rdfc25May.html
input document: test0011.rdf
output document: test0011.nt

test0012
type: PositiveParserTest
issue: rdf-ns-prefix-confusion
status: APPROVED
approval: rdfc25May.html
input document: test0012.rdf
output document: test0012.nt

test0013
type: PositiveParserTest
issue: rdf-ns-prefix-confusion
status: APPROVED
approval: rdfc25May.html
input document: test0013.rdf
output document: test0013.nt

test0014
type: PositiveParserTest
issue: rdf-ns-prefix-confusion
status: APPROVED
approval: rdfc25May.html
input document: test0014.rdf
output document: test0014.nt

error001
type: NegativeParserTest
status: PENDING
input document: error001.rdf

error002
type: NegativeParserTest
status: PENDING
input document: error002.rdf

error1
type: NegativeParserTest
issue: rdfms-difference-between-ID-and-about
status: APPROVED
approval: 0108.html
input document: error1.rdf

test1
type: PositiveParserTest
issue: rdfms-difference-between-ID-and-about
status: APPROVED
approval: 0108.html
input document: test1.rdf
output document: test1.nt

test2
type: PositiveParserTest
status: PENDING
issue: rdfms-difference-between-ID-and-about
description: This test shows the treatment of non-ASCII characters in the value of rdf:ID attribute.
input document: test2.rdf
output document: test2.nt

test3
type: PositiveParserTest
status: PENDING
issue: rdfms-difference-between-ID-and-about
description: This test shows the treatment of non-ASCII characters in the value of rdf:about attribute.
input document: test3.rdf
output document: test3.nt

test001
type: PositiveParserTest
issue: rdfms-duplicate-member-props
status: PENDING
approval: 0028.html
description: The question posed to the RDF WG was: should an RDF document containing multiple rdf:_n properties (with the same n) on an element be rejected as illegal? The WG decided that a parser should accept that case as legal RDF.
input document: test001.rdf
output document: test001.nt

error001
type: NegativeParserTest
issue: rdfms-empty-property-elements
status: APPROVED
approval: rdfc25May.html
input document: error001.rdf

error002
type: NegativeParserTest
issue: rdfms-empty-property-elements
status: APPROVED
approval: rdfc25May.html
input document: error002.rdf

error003
type: NegativeParserTest
issue: rdfms-empty-property-elements
status: APPROVED
approval: rdfc25May.html
input document: error003.rdf

test001
type: PositiveParserTest
issue: rdfms-empty-property-elements
status: APPROVED
approval: rdfc25May.html
input document: test001.rdf
output document: test001.nt

test002
type: PositiveParserTest
issue: rdfms-empty-property-elements
status: APPROVED
approval: rdfc25May.html
input document: test002.rdf
output document: test002.nt

test003
type: PositiveParserTest
issue: rdfms-empty-property-elements
status: APPROVED
approval: rdfc25May.html
input document: test003.rdf
output document: test003.nt

test004
type: PositiveParserTest
issue: rdfms-empty-property-elements
status: APPROVED
approval: rdfc25May.html
input document: test004.rdf
output document: test004.nt

test005
type: PositiveParserTest
issue: rdfms-empty-property-elements
status: APPROVED
approval: rdfc25May.html
input document: test005.rdf
output document: test005.nt

test006
type: PositiveParserTest
issue: rdfms-empty-property-elements
status: APPROVED
approval: rdfc25May.html
input document: test006.rdf
output document: test006.nt

test007
type: PositiveParserTest
issue: rdfms-empty-property-elements
status: APPROVED
approval: rdfc25May.html
input document: test007.rdf
output document: test007.nt

test008
type: PositiveParserTest
issue: rdfms-empty-property-elements
status: APPROVED
approval: rdfc25May.html
input document: test008.rdf
output document: test008.nt

test009
type: PositiveParserTest
issue: rdfms-empty-property-elements
status: APPROVED
approval: rdfc25May.html
input document: test009.rdf
output document: test009.nt

test010
type: PositiveParserTest
issue: rdfms-empty-property-elements
status: APPROVED
approval: rdfc25May.html
input document: test010.rdf
output document: test010.nt

test011
type: PositiveParserTest
issue: rdfms-empty-property-elements
status: APPROVED
approval: rdfc25May.html
input document: test011.rdf
output document: test011.nt

test012
type: PositiveParserTest
issue: rdfms-empty-property-elements
status: APPROVED
approval: rdfc25May.html
input document: test012.rdf
output document: test012.nt

test013
type: PositiveParserTest
issue: rdfms-empty-property-elements
status: APPROVED
approval: rdfc25May.html
input document: test013.rdf
output document: test013.nt

test014
type: PositiveParserTest
issue: rdfms-empty-property-elements
status: APPROVED
approval: rdfc25May.html
input document: test014.rdf
output document: test014.nt

test015
type: PositiveParserTest
issue: rdfms-empty-property-elements
status: APPROVED
approval: rdfc25May.html
input document: test015.rdf
output document: test015.nt

test016
type: PositiveParserTest
issue: rdfms-empty-property-elements
status: PENDING
description: Like rdfms-empty-property-elements/test001.rdf but with a processing instruction as the only content of the otherwise empty element.
input document: test016.rdf
output document: test016.nt

test017
type: PositiveParserTest
issue: rdfms-empty-property-elements
status: PENDING
description: Like rdfms-empty-property-elements/test001.rdf but with a comment as the only content of the otherwise empty element.
input document: test017.rdf
output document: test017.nt

test001
type: PositiveParserTest
issue: rdfms-identity-anon-resources
status: APPROVED
approval: 0405.html
input document: test001.rdf
output document: test001.nt

test002
type: PositiveParserTest
issue: rdfms-identity-anon-resources
status: APPROVED
approval: 0405.html
input document: test002.rdf
output document: test002.nt

test003
type: PositiveParserTest
issue: rdfms-identity-anon-resources
status: APPROVED
approval: 0405.html
input document: test003.rdf
output document: test003.nt

test004
type: PositiveParserTest
issue: rdfms-identity-anon-resources
status: APPROVED
approval: 0405.html
input document: test004.rdf
output document: test004.nt

test005
type: PositiveParserTest
issue: rdfms-identity-anon-resources
status: APPROVED
approval: 0405.html
input document: test005.rdf
output document: test005.nt

test001
type: PositiveParserTest
issue: rdfms-literal-is-xml-structure
status: NOT_APPROVED
input document: test001.rdf
output document: test001.nt

test002
type: PositiveParserTest
issue: rdfms-literal-is-xml-structure
status: NOT_APPROVED
input document: test002.rdf
output document: test002.nt

test003
type: PositiveParserTest
issue: rdfms-literal-is-xml-structure
status: NOT_APPROVED
input document: test003.rdf
output document: test003.nt

test004
type: PositiveParserTest
issue: rdfms-literal-is-xml-structure
status: NOT_APPROVED
input document: test004.rdf
output document: test004.nt

test005
type: PositiveParserTest
issue: rdfms-literal-is-xml-structure
status: NOT_APPROVED
input document: test005.rdf
output document: test005.nt

test001
type: PositiveParserTest
issue: rdfms-not-id-and-resource-attr
status: APPROVED
approval: 0235.html
input document: test001.rdf
output document: test001.nt

test002
type: PositiveParserTest
issue: rdfms-not-id-and-resource-attr
status: APPROVED
approval: 0235.html
input document: test002.rdf
output document: test002.nt

test003
type: PositiveParserTest
issue: rdfms-not-id-and-resource-attr
status: OBSOLETED
approval: 0235.html
input document: test003.rdf
output document: test003.nt

test004
type: PositiveParserTest
issue: rdfms-not-id-and-resource-attr
status: APPROVED
approval: 0235.html
input document: test004.rdf
output document: test004.nt

test005
type: PositiveParserTest
issue: rdfms-not-id-and-resource-attr
status: APPROVED
approval: 0235.html
input document: test005.rdf
output document: test005.nt

test001
type: PositiveParserTest
issue: rdfms-para196
status: APPROVED
approval: 0095.html
input document: test001.rdf
output document: test001.nt

error001
type: NegativeParserTest
status: NOT_APPROVED
input document: error001.rdf

error002
type: NegativeParserTest
status: NOT_APPROVED
input document: error002.rdf

error003
type: NegativeParserTest
status: NOT_APPROVED
input document: error003.rdf

error001
type: NegativeParserTest
status: PENDING
description: The value of rdf:ID must match the XML Name production, (as modified by XML Namespaces).
input document: error001.rdf

error002
type: NegativeParserTest
status: PENDING
description: The value of rdf:ID must match the XML Name production, (as modified by XML Namespaces).
input document: error002.rdf

error003
type: NegativeParserTest
status: PENDING
description: The value of rdf:ID must match the XML Name production, (as modified by XML Namespaces).
input document: error003.rdf

error004
type: NegativeParserTest
status: PENDING
description: The value of rdf:ID must match the XML Name production, (as modified by XML Namespaces).
input document: error004.rdf

error005
type: NegativeParserTest
status: PENDING
description: The value of rdf:ID must match the XML Name production, (as modified by XML Namespaces).
input document: error005.rdf

error006
type: NegativeParserTest
status: PENDING
description: The value of rdf:bagID must match the XML Name production, (as modified by XML Namespaces).
input document: error006.rdf

error007
type: NegativeParserTest
status: PENDING
description: The value of rdf:bagID must match the XML Name production, (as modified by XML Namespaces).
input document: error007.rdf

error-001
type: NegativeParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: error-001.rdf

error-002
type: NegativeParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: error-002.rdf

error-003
type: NegativeParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: error-003.rdf

error-004
type: NegativeParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: error-004.rdf

error-005
type: NegativeParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: error-005.rdf

error-006
type: NegativeParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: error-006.rdf

error-007
type: NegativeParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: error-007.rdf

error-008
type: NegativeParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: error-008.rdf

error-009
type: NegativeParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: error-009.rdf

error-010
type: NegativeParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: error-010.rdf

error-011
type: NegativeParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: error-011.rdf

error-012
type: NegativeParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: error-012.rdf

error-013
type: NegativeParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: error-013.rdf

error-014
type: NegativeParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: error-014.rdf

error-015
type: NegativeParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: error-015.rdf

error-016
type: NegativeParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: error-016.rdf

error-017
type: NegativeParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: error-017.rdf

error-018
type: NegativeParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: error-018.rdf

error-019
type: NegativeParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: error-019.rdf

error-020
type: NegativeParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: error-020.rdf

test-001
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-001.rdf
output document: test-001.nt

test-002
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-002.rdf
output document: test-002.nt

test-003
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-003.rdf
output document: test-003.nt

test-004
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-004.rdf
output document: test-004.nt

test-005
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-005.rdf
output document: test-005.nt

test-006
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-006.rdf
output document: test-006.nt

test-007
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-007.rdf
output document: test-007.nt

test-008
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-008.rdf
output document: test-008.nt

test-009
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-009.rdf
output document: test-009.nt

test-010
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-010.rdf
output document: test-010.nt

test-011
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-011.rdf
output document: test-011.nt

test-012
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-012.rdf
output document: test-012.nt

test-013
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-013.rdf
output document: test-013.nt

test-014
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-014.rdf
output document: test-014.nt

test-015
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-015.rdf
output document: test-015.nt

test-016
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-016.rdf
output document: test-016.nt

test-017
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-017.rdf
output document: test-017.nt

test-018
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-018.rdf
output document: test-018.nt

test-019
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-019.rdf
output document: test-019.nt

test-020
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-020.rdf
output document: test-020.nt

test-021
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-021.rdf
output document: test-021.nt

test-022
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-022.rdf
output document: test-022.nt

test-023
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-023.rdf
output document: test-023.nt

test-024
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-024.rdf
output document: test-024.nt

test-025
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-025.rdf
output document: test-025.nt

test-026
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-026.rdf
output document: test-026.nt

test-027
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-027.rdf
output document: test-027.nt

test-028
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-028.rdf
output document: test-028.nt

test-029
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-029.rdf
output document: test-029.nt

test-030
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-030.rdf
output document: test-030.nt

test-031
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-031.rdf
output document: test-031.nt

test-032
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-032.rdf
output document: test-032.nt

test-033
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-033.rdf
output document: test-033.nt

test-034
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-034.rdf
output document: test-034.nt

test-035
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-035.rdf
output document: test-035.nt

test-036
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-036.rdf
output document: test-036.nt

test-037
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: test-037.rdf
output document: test-037.nt

warn-001
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: warn-001.rdf
output document: warn-001.nt
warning: allowed with warnings

warn-002
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: warn-002.rdf
output document: warn-002.nt
warning: allowed with warnings

warn-003
type: PositiveParserTest
issue: rdfms-rdf-names-use
status: APPROVED
approval: 0651.html
input document: warn-003.rdf
output document: warn-003.nt
warning: allowed with warnings

test001
type: PositiveParserTest
status: PENDING
input document: test001.rdf
output document: test001.nt

test001
type: PositiveParserTest
issue: rdfms-seq-representation
status: APPROVED
approval: 0159.html
input document: test001.rdf
output document: test001.nt

test001
type: PositiveParserTest
issue: rdfms-syntax-incomplete
status: PENDING
description: rdf:nodeID can be used to label a blank node.
input document: test001.rdf
output document: test001.nt

test002
type: PositiveParserTest
issue: rdfms-syntax-incomplete
status: PENDING
description: rdf:nodeID can be used to label a blank node. These have file scope and are distinct from any unlabelled blank nodes.
input document: test002.rdf
output document: test002.nt

test003
type: PositiveParserTest
issue: rdfms-syntax-incomplete
status: OBSOLETED
description: On an rdf:Description or typed node rdf:nodeID behaves similarly to an rdf:about.
input document: test003.rdf
output document: test003.nt

test004
type: PositiveParserTest
issue: rdfms-syntax-incomplete
status: PENDING
description: On a property element rdf:nodeID behaves similarly to rdf:resource.
input document: test004.rdf
output document: test004.nt

error001
type: NegativeParserTest
issue: rdfms-syntax-incomplete
status: PENDING
description: The value of rdf:nodeID must match the XML Name production, (as modified by XML Namespaces).
input document: error001.rdf

error002
type: NegativeParserTest
issue: rdfms-syntax-incomplete
status: PENDING
description: The value of rdf:nodeID must match the XML Name production, (as modified by XML Namespaces).
input document: error002.rdf

error003
type: NegativeParserTest
issue: rdfms-syntax-incomplete
status: PENDING
description: The value of rdf:nodeID must match the XML Name production, (as modified by XML Namespaces).
input document: error003.rdf

error004
type: NegativeParserTest
issue: rdfms-syntax-incomplete
status: PENDING
description: Cannot have rdf:nodeID and rdf:ID.
input document: error004.rdf

error005
type: NegativeParserTest
issue: rdfms-syntax-incomplete
status: PENDING
description: Cannot have rdf:nodeID and rdf:about.
input document: error005.rdf

error006
type: NegativeParserTest
issue: rdfms-syntax-incomplete
status: PENDING
description: Cannot have rdf:nodeID and rdf:resource.
input document: error006.rdf

test001
type: PositiveParserTest
status: PENDING
input document: test001.rdf
output document: test001.nt

error001
type: MiscellaneousTest
status: PENDING
description: An RDF/XML serlializer is recommended to produce an exception if asked to serialize the following graph since there is no way to represent it in the RDF/XML syntax.
document: error001.nt
warning: An RDF/XML serlializer is recommended to produce an exception if asked to serialize the following graph since there is no way to represent it in the RDF/XML syntax.

test001
type: PositiveParserTest
issue: rdfms-xml-literal-namespaces
status: PENDING
input document: test001.rdf
output document: test001.nt

test002
type: PositiveParserTest
issue: rdfms-xml-literal-namespaces
status: PENDING
input document: test002.rdf
output document: test002.nt

test001
type: PositiveParserTest
status: APPROVED
approval: 0034.html
input document: test001.rdf
output document: test001.nt

test002
type: PositiveParserTest
status: APPROVED
approval: 0034.html
input document: test002.rdf
output document: test002.nt

test003
type: PositiveParserTest
status: APPROVED
approval: 0034.html
input document: test003.rdf
output document: test003.nt

test004
type: PositiveParserTest
status: APPROVED
approval: 0034.html
input document: test004.rdf
output document: test004.nt

test005
type: PositiveParserTest
status: APPROVED
approval: 0034.html
input document: test005.rdf
output document: test005.nt

test006
type: PositiveParserTest
status: PENDING
input document: test006.rdf
output document: test006.nt

test001
type: NegativeEntailmentTest
status: PENDING
description: While it is a superproperty, _:a <rdfs:contains (@@member?)> _:b . does NOT entail _:a <rdf:_n> _:b . for any _n.
entailment rules: 22-rdf-syntax-ns#
entailment rules: rdf-schema#
premise document: not1P.rdf
conclusion document: not1C.rdf

test001
type: PositiveParserTest
issue: rdfs-domain-and-range
status: APPROVED
approval: 0405.html
input document: test001.rdf
output document: test001.nt

test002
type: PositiveParserTest
issue: rdfs-domain-and-range
status: APPROVED
approval: 0405.html
input document: test002.rdf
output document: test002.nt

test003
type: PositiveParserTest
issue: rdfs-domain-and-range
status: NOT_APPROVED
input document: test003.rdf
output document: test003.nt

test004
type: PositiveParserTest
issue: rdfs-domain-and-range
status: NOT_APPROVED
input document: test004.rdf
output document: test004.nt

conjunction-test
type: PositiveEntailmentTest
issue: rdfs-domain-and-range
status: NOT_APPROVED
description: Should a property be allowed more than one rdfs:range property? What should the semantics of multiple domain and range properties be? -> Multiple domain and range constraints are permissable and will have conjunctive semantics. test001 describes a property with rdfs:domain the intersection of 2 domains test002 describes a property with rdfs:range the intersection of 2 ranges test003 sample statement test004 entailed description using test001, test002, test003 and the rules for RDF and RDFS entailment (see http://www.w3.org/2000/10/rdf-tests/rdfcore/entailment/ )
entailment rules: 22-rdf-syntax-ns#
entailment rules: rdf-schema#
premise document: test001.nt
premise document: test002.nt
premise document: test003.nt
conclusion document: test004.nt

intensionality-range
type: NegativeEntailmentTest
issue: rdfs-domain-and-range
issue: I5.24-IF-or-IFF-property-properties
status: PENDING
description: 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.
entailment rules: 22-rdf-syntax-ns#
entailment rules: rdf-schema#
premise document: premises005.rdf
conclusion document: nonconclusions005.rdf

intensionality-domain
type: NegativeEntailmentTest
issue: rdfs-domain-and-range
issue: I5.24-IF-or-IFF-property-properties
status: PENDING
description: 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.
entailment rules: 22-rdf-syntax-ns#
entailment rules: rdf-schema#
premise document: premises006.rdf
conclusion document: nonconclusions006.rdf

test001
type: PositiveEntailmentTest
issue: rdfs-no-cycles-in-subClassOf
status: APPROVED
approval: 0249.html
description: Cycles are permitted in subClassOf; therefore, no error occurs and the following entailment holds trivially.
entailment rules: 22-rdf-syntax-ns#
entailment rules: rdf-schema#
premise document: test001.rdf
conclusion document: test001.nt

test001
type: PositiveEntailmentTest
issue: rdfs-no-cycles-in-subPropertyOf
status: APPROVED
approval: 0249.html
description: Cycles are permitted in subPropertyOf; therefore, no error occurs and the following entailment holds trivially.
entailment rules: 22-rdf-syntax-ns#
entailment rules: rdf-schema#
premise document: test001.rdf
conclusion document: test001.nt

test001
type: PositiveEntailmentTest
issue: rdfs-subPropertyOf-semantics
status: PENDING
description: The inheritance semantics of the subPropertyOf relationship needs to be clarified. => subProperties inherit conjunctively the domain and range of their superproperties
entailment rules: 22-rdf-syntax-ns#
entailment rules: rdf-schema#
premise document: test001.nt
conclusion document: test002.nt

test001
type: NegativeEntailmentTest
status: APPROVED
approval: 0476.html
description: RDFCore WG RESOLVED that a reified statement was a stating, not a statement. The following entailment does not, therefore, hold.
entailment rules: 22-rdf-syntax-ns#
premise document: test001a.nt
conclusion document: test001b.nt

test002
type: NegativeEntailmentTest
status: APPROVED
approval: 0476.html
description: RDFCore WG RESOLVED that a statement does NOT entail its reification. The following entailment does not, therefore, hold.
entailment rules: 22-rdf-syntax-ns#
premise document: test002a.nt
conclusion document: test002b.nt

test003
type: NegativeEntailmentTest
status: APPROVED
approval: 0476.html
description: 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.
entailment rules: 22-rdf-syntax-ns#
entailment rules: rdf-schema#
premise document: test001a.nt
conclusion document: test001b.nt

test004
type: NegativeEntailmentTest
status: APPROVED
approval: 0476.html
description: 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.
entailment rules: 22-rdf-syntax-ns#
entailment rules: rdf-schema#
premise document: test002a.nt
conclusion document: test002b.nt

test001
type: PositiveParserTest
status: APPROVED
approval: 0152.html
input document: test001.rdf
output document: test001.nt

test002
type: PositiveParserTest
status: APPROVED
approval: 0152.html
input document: test002.rdf
output document: test002.nt

error001
type: NegativeParserTest
issue: rdfms-xml-base
status: NOT_APPROVED
description: This test case concerns URIs relative to a non-relative URI scheme base. It's beyond the scope of the WG to deal with this; it has therefore not been approved.
input document: error001.rdf

test001
type: PositiveParserTest
issue: rdfms-xml-base
status: APPROVED
approval: 0235.html
input document: test001.rdf
output document: test001.nt

test002
type: PositiveParserTest
issue: rdfms-xml-base
status: APPROVED
approval: 0235.html
input document: test002.rdf
output document: test002.nt

test003
type: PositiveParserTest
issue: rdfms-xml-base
status: APPROVED
approval: 0235.html
input document: test003.rdf
output document: test003.nt

test004
type: PositiveParserTest
issue: rdfms-xml-base
status: APPROVED
approval: 0235.html
input document: test004.rdf
output document: test004.nt

test005
type: PositiveParserTest
issue: rdfms-xml-base
status: APPROVED
approval: 0235.html
input document: test005.rdf
output document: test005.nt

test006
type: PositiveParserTest
issue: rdfms-xml-base
status: APPROVED
approval: 0235.html
input document: test006.rdf
output document: test006.nt

test007
type: PositiveParserTest
issue: rdfms-xml-base
status: APPROVED
approval: 0235.html
input document: test007.rdf
output document: test007.nt

test008
type: PositiveParserTest
issue: rdfms-xml-base
status: APPROVED
approval: 0235.html
input document: test008.rdf
output document: test008.nt

test009
type: PositiveParserTest
issue: rdfms-xml-base
status: APPROVED
approval: 0235.html
input document: test009.rdf
output document: test009.nt

test010
type: PositiveParserTest
issue: rdfms-xml-base
status: APPROVED
approval: 0235.html
input document: test010.rdf
output document: test010.nt

test011
type: PositiveParserTest
issue: rdfms-xml-base
status: APPROVED
approval: 0235.html
input document: test011.rdf
output document: test011.nt

test012
type: PositiveParserTest
issue: rdfms-xml-base
status: APPROVED
approval: 0235.html
input document: test012.rdf
output document: test012.nt

test013
type: PositiveParserTest
issue: rdfms-xml-base
status: APPROVED
approval: 0235.html
input document: test013.rdf
output document: test013.nt

test014
type: PositiveParserTest
issue: rdfms-xml-base
status: APPROVED
approval: 0235.html
description: Test output corrected to use correct base URL.
input document: test014.rdf
output document: test014.nt

test015
type: PositiveParserTest
issue: rdfms-xml-base
status: APPROVED
approval: 0235.html
input document: test015.rdf
output document: test015.nt

test016
type: PositiveParserTest
issue: rdfms-xml-base
status: APPROVED
approval: 0235.html
input document: test016.rdf
output document: test016.nt