APPROVEDAPPROVED
The claim that xsd:integer is a subClassOF xsd:decimal is not
incompatible with using the intensional semantics for datatypes.
APPROVED
The claim that xsd:integer is a subClassOF xsd:string is
incompatible with using the intensional semantics for datatypes.
APPROVED
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
APPROVED
A parser is not required to know about well-formed datatyped literals.
APPROVED
Without datatype knowledge, a 'badly-formed' datatyped literal cannot be detected.
APPROVED
With appropriate datatype knowledge, a 'badly-formed' datatyped literal can be detected.
APPROVED
Demonstrating the semantic equivalence of two lexical forms of the same datatyped value.
APPROVED
As semantic-equivalence-within-type-1; the entailment works both ways.
OBSOLETE
This test used to claim:
Language attributes on a datatyped literal make them distinct for the purposes
of non-datatype-aware entailments.
There are no longer language tags on datatyped literals.
OBSOLETE
This test used to claim:
Language attributes on a datatyped literal make them distinct for the purposes
of non-datatype-aware entailments.
There are no longer language tags on datatyped literals.
OBSOLETE
Obsoleted: datatyped literals have no language tag.
OBSOLETE
Obsoleted: datatyped literals have no language tag.
OBSOLETE
Obsoleted: datatyped literals have no language tag.
APPROVED
Members of different datatypes may be semantically equivalent.
APPROVED
Where sufficient DT knowledge is available, a range clash may be detected; the document then
contains a contradiction.
OBSOLETE
Language does not affect the denotation of rdf:XMLLiteral. NOTE that this
is a change from previous versions of the spec.
Langauge tags do not live on XMLLiterals.
APPROVED
From decisions listed in http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2002Oct/0098.html
APPROVED
From decisions listed in http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2002Oct/0098.html
APPROVED
From decisions listed in http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2002Oct/0098.html
APPROVED
A plain literal denotes the same thing as its corresponding xsd:string,
where one exists.
APPROVED
rdfs:subClassOf has intensional semantics, not extensional.
APPROVED
rdfs:subPropertyOf has intensional semantics, not extensional.
APPROVED
Test that ICEXT(I(rdfs:Literal)) is a subset of LV.
APPROVED
Does the treatment of literals conform to charmod ?
Test for success of legal Normal Form C literal
WITHDRAWN
Does the treatment of literals conform to charmod ?
Test for failure for literal not in Normal Form C
This test case has been WITHDRAWN in light of changes to NFC handling
in concepts
WITHDRAWN
Does the treatment of literals conform to charmod ?
Test for failure for literal not in Normal Form C
This test case has been WITHDRAWN in light of changes to NFC handling
in concepts
APPROVED
A uriref is allowed to match non-US ASCII forms
conforming to Unicode Normal Form C.
No escaping algorithm is applied.
APPROVED
A uriref which already has % escaping is permitted.
No unescaping algorithm is applied.
OBSOLETE
Test for failure for uriref not in Normal Form C.
APPROVED
An international URI ref and its %-escaped form label
different nodes in the graph.
No model theoretic relationship holds between them.
APPROVED
An international URI ref and its %-escaped form label
different nodes in the graph.
No model theoretic relationship holds between them.
APPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDOBSOLETEDAPPROVEDAPPROVEDAPPROVEDAPPROVED
A surrounding rdf:RDF element is no longer mandatory.
OBSOLETE
This is again legal RDF
OBSOLETE
This is again legal RDF
OBSOLETE
This is again legal RDF
OBSOLETE
This is again legal RDF
OBSOLETE
This is again legal RDF
OBSOLETE
This is again legal RDF
OBSOLETE
This is again legal RDF
OBSOLETE
This is again legal RDF
OBSOLETE
This is again legal RDF
APPROVEDOBSOLETEAPPROVEDAPPROVEDAPPROVEDAPPROVEDOBSOLETE
rdf:aboutEach no longer valid.
OBSOLETEAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVED
This test shows the treatment of non-ASCII characters
in the value of rdf:ID attribute.
APPROVED
This test shows the treatment of non-ASCII characters
in the value of rdf:about attribute.
APPROVED
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.
APPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVED
Like rdfms-empty-property-elements/test001.rdf but with a processing instruction
as the only content of the otherwise empty element.
APPROVED
Like rdfms-empty-property-elements/test001.rdf but with a comment
as the only content of the otherwise empty element.
APPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDNOT_APPROVEDNOT_APPROVEDNOT_APPROVEDNOT_APPROVEDNOT_APPROVEDOBSOLETEOBSOLETEOBSOLETEOBSOLETEOBSOLETEOBSOLETEOBSOLETE
rdf:bagID is forbidden on property element prop with an rdf:resource or
rdf:parseType attribute: the following is in error.
OBSOLETEOBSOLETEOBSOLETE
Two property attributes and a property element on an rdf:Description.
Since the property attributes are not ordered under document
order, two different n-triples files corresponding to both
possible orderings are permitted.
One of test010a and test010b SHOULD pass, at least.
OBSOLETE
Two property attributes and a property element on an rdf:Description.
Since the property attributes are not ordered under document
order, two different n-triples files corresponding to both
possible orderings are permitted.
OBSOLETE
Two property attributes and a property element on an rdf:Description.
Since the property attributes are not ordered under document
order, two different n-triples files corresponding to both
possible orderings are permitted.
One of test011a and test011b SHOULD pass, at least.
OBSOLETE
Two property attributes and a property element on an rdf:Description.
Since the property attributes are not ordered under document
order, two different n-triples files corresponding to both
possible orderings are permitted.
OBSOLETE
Two property attributes and a property element on an rdf:Description.
Since the property attributes are not ordered under document
order, two different n-triples files corresponding to both
possible orderings are permitted.
One of test012a and test012b SHOULD pass, at least.
OBSOLETE
Two property attributes and a property element on an rdf:Description.
Since the property attributes are not ordered under document
order, two different n-triples files corresponding to both
possible orderings are permitted.
APPROVEDAPPROVEDOBSOLETEAPPROVEDAPPROVEDAPPROVEDNOT_APPROVEDNOT_APPROVEDNOT_APPROVEDAPPROVED
The value of rdf:ID must match the XML Name production,
(as modified by XML Namespaces).
APPROVED
The value of rdf:ID must match the XML Name production,
(as modified by XML Namespaces).
APPROVED
The value of rdf:ID must match the XML Name production,
(as modified by XML Namespaces).
APPROVED
The value of rdf:ID must match the XML Name production,
(as modified by XML Namespaces).
APPROVED
The value of rdf:ID must match the XML Name production,
(as modified by XML Namespaces).
APPROVED
The value of rdf:bagID must match the XML Name production,
(as modified by XML Namespaces).
APPROVED
The value of rdf:bagID must match the XML Name production,
(as modified by XML Namespaces).
APPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVED allowed with warnings APPROVED allowed with warnings APPROVED allowed with warnings APPROVEDAPPROVEDAPPROVED
Statement of the MT closure rule.
APPROVED
Statement of the MT closure rule.
APPROVED
Statement of the MT closure rule.
APPROVED
rdf:nodeID can be used to label a blank node.
APPROVED
rdf:nodeID can be used to label a blank node.
These have file scope and are distinct from any
unlabelled blank nodes.
APPROVED
On an rdf:Description or typed node rdf:nodeID behaves
similarly to an rdf:about.
APPROVED
On a property element rdf:nodeID behaves
similarly to rdf:resource.
APPROVED
The value of rdf:nodeID must match the XML Name production,
(as modified by XML Namespaces).
APPROVED
The value of rdf:nodeID must match the XML Name production,
(as modified by XML Namespaces).
APPROVED
The value of rdf:nodeID must match the XML Name production,
(as modified by XML Namespaces).
APPROVED
Cannot have rdf:nodeID and rdf:ID.
APPROVED
Cannot have rdf:nodeID and rdf:about.
APPROVED
Cannot have rdf:nodeID and rdf:resource.
APPROVEDAPPROVED
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.
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.
APPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVED
Plain literals are distinguishable on the basis of language tags.
APPROVED
Plain literals are distinguishable on the basis of language tags.
APPROVED
Plain literals are distinguishable on the basis of language tags.
APPROVED
While it is a superproperty,
_:a <rdfs:contains (@@member?)> _:b .
does NOT entail
_:a <rdf:_n> _:b .
for any _n.
APPROVEDAPPROVEDNOT_APPROVEDNOT_APPROVEDNOT_APPROVED
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/ )
APPROVED
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.
APPROVED
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.
APPROVED
Indicating a simple inconsistency drawn from RDFS. RDFS
can only produce inconsistencies through badly-formed XMLLiteral
datatypes.
APPROVED
From an inconsistent graph, any entailment can be drawn. This is an
example.
APPROVED
Cycles are permitted in subClassOf; therefore, no error occurs and the following entailment
holds trivially.
APPROVED
Cycles are permitted in subPropertyOf; therefore, no error occurs and the following entailment
holds trivially.
APPROVED
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)
APPROVED
The inheritance semantics of the subPropertyOf relationship needs to be clarified.
=> subProperties inherit conjunctively the domain and range of their superproperties
APPROVED
RDFCore WG RESOLVED that a reified statement was a stating, not a statement.
The following entailment does not, therefore, hold.
APPROVED
RDFCore WG RESOLVED that a statement does NOT entail its reification.
The following entailment does not, therefore, hold.
APPROVED
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.
APPROVED
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.
APPROVED
The case of the language tag is not significant.
APPROVED
The case of the language tag is not significant.
APPROVEDAPPROVEDAPPROVED
Demonstrating the canonicalisation of XMLLiterals.
NOT_APPROVED
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.
APPROVEDAPPROVEDAPPROVEDAPPROVEDOBSOLETE
This is not valid rdf/xml. The embedding of RDF/XML in other XML formats is
beyond the scope of these test cases. Test case withdrawn.
APPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDAPPROVEDWITHDRAWN
Test case WITHDRAWN in light of 2396bis
APPROVEDAPPROVED
Test output corrected to use correct base URL.
NOT_APPROVED
This test case is deprecated. The use of mailto: URIs with xml:base is not within the scope of
RDFCore's charter to sort out.
NOT_APPROVED
This test case is deprecated. The use of mailto: URIs with xml:base is not within the scope of
RDFCore's charter to sort out.
APPROVED
A well-formed typed literal is not related to an ill-formed literal.
Even if they only differ by whitespace.
APPROVED
A well-formed typed literal is not related to an ill-formed literal.
Even if they only differ by whitespace.
APPROVED
A simple test for well-formedness of a typed literal.
APPROVED
An integer with whitespace is ill-formed.