mirror of
https://github.com/cookiengineer/audacity
synced 2025-07-31 16:09:28 +02:00
42 lines
1.6 KiB
Plaintext
42 lines
1.6 KiB
Plaintext
This README is for the W3C RDF Working Group's TriG test suite.
|
|
This test suite contains three kinds of tests:
|
|
|
|
Evaluation (rdft:TestTriGEval) - a pair of an input trig file
|
|
and reference ntriples file.
|
|
|
|
Positive syntax (rdft:TestTriGPositiveSyntax) - an input trig
|
|
file with no syntax errors.
|
|
|
|
Negative syntax (rdft:TestTriGNegativeSyntax) - an input trig
|
|
file with at least one syntax error.
|
|
|
|
The manifest.ttl file in this directory lists all of the tests in the
|
|
RDF WG's TriG test suite. Each test is one of the above tests. All
|
|
tests have a name (mf:name) and an input (mf:action). The Evaluation
|
|
tests have an expected result (mf:result).
|
|
|
|
• An implementation passes an Evaluation test if it parses the input
|
|
into a graph, parses the expecte result into another graph, and
|
|
those two graphs are isomorphic (see
|
|
<http://www.w3.org/TR/rdf11-concepts/#graph-isomorphism>).
|
|
|
|
• An implementation passes a positive syntax test if it parses the
|
|
input.
|
|
|
|
• An implementation passes a negative syntax test if it fails to parse
|
|
the input.
|
|
|
|
The home of the test suite is <http://www.w3.org/2013/TriGTests/>.
|
|
Per RFC 3986 section 5.1.3, the base IRI for parsing each file is the
|
|
retrieval IRI for that file. For example, the tests trig-subm-01 and
|
|
trig-subm-27 require relative IRI resolution against a base of
|
|
<http://www.w3.org/2013/TriGTests/trig-subm-01.trig> and
|
|
<http://www.w3.org/2013/TriGTests/trig-subm-27.trig> respectively.
|
|
|
|
|
|
See http://www.w3.org/2011/rdf-wg/wiki/TriG_Test_Suite for more details.
|
|
|
|
|
|
Eric Prud'hommeaux <eric+turtle@w3.org> - 11 June 2013.
|
|
Gregg Kellogg <gregg@greggkellogg.net> - 12 June 2013.
|