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:
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.
This test case uses an inline GRDDL transformation reference (i.e.
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
indicate that the resource is in fact a GRDDL transformation.
The base URI for the result document is the URI of the source document.
The protocol trace discusses http://www.w3.org/2003/g/po-doc.xml, which should probably perhaps move to the WG test suite or sync with it somehow. http://www.w3.org/2003/g/embeddedRDF and http://www.w3.org/2003/g/glean-profile should get some testing too. The Jena GRDDL Reader test area, especially security4, security6 (as of jjc's comment), are noteworthy re security issues
An example homepage with Dublin Core, GeoURL, RSS, Creative Commons, etc. demonstrates several transformations and dialects.
These are potential primer chapters, too:
This test collection uses an RDF vocabulary for manifests developed for the RDF Test Cases Recommendation. The aboutTests transformation relates dialect in the HTML representation to an RDF graph (via RDF/XML).
$ python testft.py --run your_grddl_impl testlist1.rdf >earl_out.rdf All tests were passed!
It has options for --debug and such; invoke it with no arguments for details.
In addition to various diagnostics on stderr, the test harness writes to stdout some RDF data: an EARL assertion about each test it runs.
To tell it about the person running the tests and the software project being tested, point it at an ID in a foaf file and a DOAP file:
$ 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!
We find TCPWatch useful for debugging HTTP protocol interactions. If you start TCPWatch a la:
$ python tcpwatch.py -p 6543 &
then you can use it as a proxy:
$ http_proxy=http://127.0.0.1:6543 python testft.py \ --run your_grddl_impl testlist1.rdf
See also Dom's message Re: GRDDL test howto? of 23 Aug 2006.