GRDDL Tests, Part 3

These tests help check for robusness of implementations in the face of various odd cases.

See part 1 for details on how GRDDL tests work.

• Namepace Loop
  input output

• XSLT Literal Result
  input output

• Testing GRDDL when XInclude processing is enabled
  input output

  In this test case, the input file uses XInclude to include xinclude2.xml, and that the output has only one triple unless the XML Processor of the GRDDL implementation implements XInclude. The output for this case assumes that the processor does resolve XIncludes. Note, however, that this test case subsumes the XInclude disabled test case, which assumes that the GRDDL implementation has disabled XInclude processing.

• Testing GRDDL when XInclude processing is disabled
  input output

  This test case is an alternative to the XInclude enabled test case. The output for this case assumes that the processor does not resolve XIncludes, which may lead to a different GRDDL result.

• Testing GRDDL attributes on RDF documents (1 of 3)
  input output

  Note that the input is a RDF document with a GRDDL transformation, and that according to the rules given by the GRDDL Specification, there are three distinct and equally valid output graphs for this test for this document. An implementation only has to produce one of these three. This output is the result of the transformation without merging it with the graph of the source document.

• Testing GRDDL attributes on RDF documents (2 of 3)
  input output

  This output is a graph that is identical with the graph given by the input document.

• Testing GRDDL attributes on RDF documents (3 of 3)
  input output

  This output is a graph that is merge of the graph given by the source document with the graph given by the result of the GRDDL transformation.

• Testing GRDDL attributes on RDF documents with XML media type(1 of 3)
  input output

  This test differs from the previous example of applying GRDDL to an RDF/XML document in that the RDF file is served (not best practice, but rather common) as media-type "application/xml". The output is the result of the transformation without merging it with the graph of the source document.

• Testing GRDDL attributes on RDF documents with XML media type(2 of 3)
  input output

  The output is a graph that is identical with the graph given by the input document.

• Testing GRDDL attributes on RDF documents with XML media type(3 of 3)
  input output

  The output is a graph that is merge of the graph given by the source document with the graph given by the result of the GRDDL transformation

• Content Negotiation with GRDDL (1 of 2)
  input output

  This test exists to bring attention to developers to issues of content negotiation, in particular, content negotiation over language as described and implemented by W3C QA. There are two valid resulting GRDDL results of running this GRDDL transformation depending on what language the GRDDL-aware agent uses, and an implementation of a GRDDL-aware agent only needs to retrieve the one that is appropriate for its HTTP header request. This result follows from retrieving a English version of the HTML representation and thus having the GRDDL result produce a result with English-language content.

• Content Negotiation with GRDDL (2 of 3)
  input output

  This result follows from retrieving a German version of the HTML representation and thus having the GRDDL result produce a result with German-language content.

• Content Negotiation with GRDDL (3 of 3)
  input output

  This result is the merge of the previous two GRDDL results.