GRDDL Tests

STATUS: These tests are in development; until a test is approved by WG decision, it is subject to change without notice.

Chime and JJC
$Revision: 1.45 $ of $Date: 2007/03/21 16:38:08 $

See editor's draft for details.

The test collection is separated into parts:

1. This part covers section 2 on using GRDDL with XML. These test don't involve namespace documents, so they're easy to run offline, and they work with other base URIs even though they have relative URI references.
2. For namespace/profile document tests, see part 2.
3. For tests of robustness of implementations in the face of anomalies, see part 3.

• P3P work-alike:
  input output

  approval: 2006-11-22

• Get RDF from a spreadsheet:
  input output

  approval: 2006-11-22

• Transformations may produce serializations other than RDF/XML
  input, output

  This test demonstrates an informative resolution to the issue-output-formats issue with an XSLT GRDDL transformation which outputs a [TURTLE] RDF graph serialization associated with an appropriate media-type (text/rdf+n3) via XSLT's output element.

  approval: 24 Jan discussion of #issue-output-formats

• RDFa example:
  input, output

• Inline transformation reference
  input, output

  This test case uses an inline GRDDL transformation reference (i.e. within an a element) instead of one within a link element. It also exercises the fact that the rel attribute can take multiple space-separated values, and only one of them needs to be equal to transformation to indicate that the resource is in fact a GRDDL transformation.

• Base URI: Same document reference
  input, output

  The base URI for the result document is the URI of the source document.

Pending tests:

• pending since 2006-08-30, re issue-base-param "I think I'll make a test case with the xslt2 function too."
• pending since 2006-09-05: running only some of the transforms for policy reasons
• pending since 2006-09-06: Passing an XSLT 2.0 transformation to an XSLT 1.0 engine
• pending since2006-09-06: multiple namespace transformations
• pending since 2006-10-25: "be robust in the face of unknown serializations" re issue-output-formats
• pending since 2006-10-25 discussion: "yes, you can use XProc to say to do xinclude and XSLT"
• pending since 2006-11-10 (spec.html v1.160): I think fn:tokenize(" a b ") includes "", the same-document URI reference. I think that's a bug.
• 5 names test: input
• #grddl_rdf for application/rdf+xml documents, the RDF/XML reading is a grddl result input, output.
• test use of grddl:transformation attribute in conjuction with namespace document(s), XHTML profile(s)
• the po-doc.xml XML Schema example
• 2007-01-20 a test for http://www.w3.org/2003/g/glean-profile. jjc noted it does more than the spec says; suggests simplifying. Better check with Dom. Any other "standard library" tests?
• @@see minutes 14 Feb for some more test ideas

$ python testft.py --run your_grddl_impl testlist1.rdf >earl_out.rdf
All tests were passed!

$ python testft.py \
  --tester 'dan.rdf#dwc' \
  --project 'grddlft.rdf#grddl_py' \
  --run your_grddl_impl \
  testlist1.rdf >earl_out.rdf
 All tests were passed!

 $ python tcpwatch.py -p 6543 &

 $ http_proxy=http://127.0.0.1:6543 python testft.py \
     --run your_grddl_impl testlist1.rdf