Audio plugin host https://kx.studio/carla
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

README 2.5KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465
  1. This README is for the W3C RDF Working Group's Turtle test suite.
  2. This test suite contains four kinds of tests:
  3. 132 Evaluation (rdft:TestTurtleEval) - a pair of an input turtle
  4. file and reference ntriples file.
  5. 77 Positive syntax (rdft:TestTurtlePositiveSyntax) - an input turtle
  6. file with no syntax errors.
  7. 78 Negative syntax (rdft:TestTurtleNegativeSyntax) - an input turtle
  8. file with at least one syntax error.
  9. 4 Negative Evaluation (rdft:TestTurtleNegativeEval) - a pair of an
  10. input turtle file and reference ntriples file. These tests have the
  11. same properties as rdft:TestTurtleNegativeSyntax.
  12. The manifest.ttl file in this directory lists all of the tests in the
  13. RDF WG's Turtle test suite. Each test is one of the above tests. All
  14. tests have a name (mf:name) and an input (mf:action). The Evaluation
  15. tests have an expected result (mf:result).
  16. • An implementation passes an Evaluation test if it parses the input
  17. into a graph, parses the expecte result into another graph, and
  18. those two graphs are isomorphic (see
  19. <http://www.w3.org/TR/rdf11-concepts/#graph-isomorphism>).
  20. • An implementation passes a positive syntax test if it parses the
  21. input.
  22. • An implementation passes a negative syntax test if it fails to parse
  23. the input.
  24. RELATIVE IRI RESOLUTION:
  25. The home of the test suite is <http://www.w3.org/2013/TurtleTests/>.
  26. Per RFC 3986 section 5.1.3, the base IRI for parsing each file is the
  27. retrieval IRI for that file. For example, the tests turtle-subm-01 and
  28. turtle-subm-27 require relative IRI resolution against a base of
  29. <http://www.w3.org/2013/TurtleTests/turtle-subm-01.ttl> and
  30. <http://www.w3.org/2013/TurtleTests/turtle-subm-27.ttl> respectively.
  31. CHARACTER ENCODING:
  32. The Turtle language uses UTF-8 encoding. The following tests include
  33. non-ascii characters:
  34. localName_with_assigned_nfc_bmp_PN_CHARS_BASE_character_boundaries
  35. localName_with_assigned_nfc_PN_CHARS_BASE_character_boundaries *
  36. localName_with_nfc_PN_CHARS_BASE_character_boundaries *
  37. labeled_blank_node_with_PN_CHARS_BASE_character_boundaries *
  38. LITERAL1_with_UTF8_boundaries *
  39. LITERAL_LONG1_with_UTF8_boundaries *
  40. LITERAL2_with_UTF8_boundaries *
  41. LITERAL_LONG2_with_UTF8_boundaries *
  42. Those marked with a * include characters with codepoints greater than
  43. U+FFFD and are thus expressed as a pair of surrogate characters when
  44. represented in UCS2.
  45. See http://www.w3.org/2011/rdf-wg/wiki/Turtle_Test_Suite for more details.
  46. Eric Prud'hommeaux <eric+turtle@w3.org> - 11 June 2013.