--- a/test-suite/reports/index.html	Thu Aug 15 18:29:48 2013 -0400
+++ b/test-suite/reports/index.html	Fri Aug 16 12:12:13 2013 +0200
@@ -17,37 +17,37 @@
               "JSON-LD-API": "Markus Lanthaler, Gregg Kellogg, Manu Sporny, Editors. <cite><a href=\"http://json-ld.org/spec/latest/json-ld-api/\">JSON-LD 1.0 Processing Algorithms and API</a>.</cite> W3C Editor's Draft (work in progress). URL: <a href=\"http://json-ld.org/spec/latest/json-ld-api/\">http://json-ld.org/spec/latest/json-ld-api/</a>",
               "JSON-LD-TESTS": "<cite><a href=\"http://www.w3.org/2013/json-ld-tests/\">JSON-LD 1.0 Test Suite</a></cite>. W3C Test Suite (work in progress). URL: <a href=\"http://www.w3.org/2013/json-ld-tests/\">http://www.w3.org/2013/json-ld-tests/</a>",
           },
-        
+
             // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
             specStatus:           "unofficial",
             copyrightStart:       "2010",
             doRDFa:               "1.1",
-        
+
             // the specification's short name, as in http://www.w3.org/TR/short-name/
             shortName:            "json-ld-earl",
             //subtitle:             "JSON-LD Implementation Conformance Report",
             // if you wish the publication date to be other than today, set this
             publishDate:  "2013/08/06",
-        
+
             // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
             // and its maturity status
             //previousPublishDate:  "2011-10-23",
             //previousMaturity:     "ED",
             //previousDiffURI:      "http://json-ld.org/spec/ED/json-ld-syntax/20111023/index.html",
             //diffTool:             "http://www.aptest.com/standards/htmldiff/htmldiff.pl",
-        
+
             // if there a publicly available Editor's Draft, this is the link
             //edDraftURI:           "",
-        
+
             // if this is a LCWD, uncomment and set the end of its review period
             // lcEnd: "2009-08-05",
-        
+
             // if you want to have extra CSS, append them to this list
             // it is recommended that the respec.css stylesheet be kept
             extraCSS:             [
                 "http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"
             ],
-        
+
             // editors, add as many as you like
             // only "name" is required
             editors:  [
@@ -58,7 +58,7 @@
                 { name: "Manu Sporny", url: "http://manu.sporny.org/",
                   company: "Digital Bazaar", companyURL: "http://digitalbazaar.com/" }
             ],
-        
+
             // authors, add as many as you like.
             // This is optional, uncomment if you have authors as well as editors.
             // only "name" is required. Same format as editors.
@@ -73,16 +73,16 @@
                   company: "Graz University of Technology", companyURL: "http://www.tugraz.at/" },
                 { name: "Niklas Lindström", url: "http://neverspace.net/" }
             ],
-        
+
             // name of the WG
             wg:           "RDF Working Group",
-        
+
             // URI of the public WG page
             wgURI:        "http://www.w3.org/2011/rdf-wg/",
-        
+
             // name (with the @w3c.org) of the public mailing to which comments are due
             wgPublicList: "public-rdf-comments",
-        
+
             // URI of the patent status for this WG, for Rec-track documents
             // !!!! IMPORTANT !!!!
             // This is important for Rec-track documents, do not copy a patent URI from a random
@@ -154,32 +154,32 @@
     <section id='sodt'></section>
     <section>
       <h2>Instructions for submitting implementation reports</h2>
-      
-      <p>Tests should be run using the test manifests defined in the 
+
+      <p>Tests should be run using the test manifests defined in the
         <a href="#test-manifests">Test Manifests</a> Section.</p>
-      
+
       <p>Each test manifest MAY contain a <code>baseIri</code> property, indicating
         the base IRI to be used for running each test.</p>
-      
+
       <p>Reports should be submitted in Turtle format to <a href="mailto:public-rdf-comments@w3.org">public-rdf-comments@w3.org</a>
         and include an <code>earl:Assertion</code>
         for each test, referencing the test resource from the associated manifest
         and the test subject being reported upon. An example test entry is be the following:</p>
-      
+
       <pre><code>  [ a earl:Assertion;&#x000A;    earl:assertedBy &lt;http://greggkellogg.net/foaf#me&gt;;&#x000A;    earl:subject &lt;http://rubygems.org/gems/json-ld&gt;;&#x000A;    earl:test &lt;http://json-ld.org/test-suite/tests/flatten-manifest.jsonld#t0001&gt;;&#x000A;    earl:result [&#x000A;      a earl:TestResult;&#x000A;      earl:outcome earl:passed;&#x000A;      dc:date &quot;2013-02-22T15:12:30-08:00&quot;^^xsd:dateTime];&#x000A;    earl:mode earl:automatic ] .&#x000A;</code></pre>
-      
+
       <p>The Test Subject should be defined as a <code>doap:Project</code>, including the name,
         homepage and developer(s) of the software (see [[DOAP]]). Optionally, including the
         project description and programming language. An example test subject description is the following:</p>
-      
+
       <pre><code>  &lt;http://rubygems.org/gems/json-ld&gt; a doap:Project, earl:TestSubject, earl:Software ;&#x000A;    doap:name          &quot;JSON::LD&quot; ;&#x000A;    doap:homepage      &lt;http://gkellogg.github.com/json-ld&gt; ;&#x000A;    doap:license       &lt;http://creativecommons.org/licenses/publicdomain/&gt; ;&#x000A;    doap:description   &quot;JSON::LD parses and serializes JSON-LD into RDF and implements expansion, compaction and framing API interfaces.&quot;@en ;&#x000A;    doap:programming-language &quot;Ruby&quot; ;&#x000A;    doap:developer     &lt;http://greggkellogg.net/foaf#me&gt; ;&#x000A;    dc:title           &quot;JSON::LD&quot; ;&#x000A;    dc:date            &quot;2011-08-29&quot;^^xsd:date ;&#x000A;    dc:creator         &lt;http://greggkellogg.net/foaf#me&gt; ;&#x000A;</code></pre>
-      
+
       <p>The software developer, either an organization or one or more individuals SHOULD be
         referenced from <code>doap:developer</code> using [[FOAF]]. For example:</p>
-      
+
       <pre><code>  &lt;http://greggkellogg.net/foaf#me&gt; a foaf:Person, earl:Assertor;&#x000A;    foaf:name &quot;Gregg Kellogg&quot;;&#x000A;    foaf:title &quot;Implementor&quot;;&#x000A;    foaf:homepage &lt;http://greggkellogg.net/&gt; .&#x000A;</code></pre>
-      
-      <p>See <a href="http://json-ld.org/tests/">JSON-LD Test Description</a> for more information.</p>
+
+      <p>See <a href="http://json-ld.org/test-suite/">JSON-LD Test Description</a> for more information.</p>
     </section>
     <section>
       <h2>

--- a/test-suite/reports/template.haml	Thu Aug 15 18:29:48 2013 -0400
+++ b/test-suite/reports/template.haml	Fri Aug 16 12:12:13 2013 +0200
@@ -150,7 +150,7 @@
       :markdown
         ## Instructions for submitting implementation reports
 
-          Tests should be run using the test manifests defined in the 
+          Tests should be run using the test manifests defined in the
           [Test Manifests](#test-manifests) Section.
 
           Each test manifest MAY contain a <code>baseIri</code> property, indicating
@@ -194,7 +194,7 @@
                 foaf:title "Implementor";
                 foaf:homepage <http://greggkellogg.net/> .
 
-          See [JSON-LD Test Description](http://json-ld.org/tests/) for more information.
+          See [JSON-LD Test Description](http://json-ld.org/test-suite/) for more information.
     %section
       - test_info = {}
       - test_refs = {}