Remove instructions from implementation report and some other minor tweaks
authorMarkus Lanthaler <>
Thu, 09 Jan 2014 18:56:55 +0100
changeset 2066 5d67441f1346
parent 2065 068d9c24c21b
child 2067 08125303bb03
Remove instructions from implementation report and some other minor tweaks

@gkellogg let me know if you are OK with this. I think it's a lot less intimidating (IMO the information how to run it is not needed in the report).

We can take care of the template separately if you think that's necessary.
--- a/test-suite/reports/index.html	Thu Jan 09 17:29:46 2014 +0100
+++ b/test-suite/reports/index.html	Thu Jan 09 18:56:55 2014 +0100
@@ -2,46 +2,41 @@
 <html prefix='earl: doap: mf:'>
     <meta content='text/html;charset=utf-8' http-equiv='Content-Type' />
-    <title>
-      JSON-LD
-      Implementation Report
-    </title>
+    <title>JSON-LD 1.0 Implementation Report</title>
     <script class='remove' src='' type='text/javascript'></script>
+    <script type="text/javascript" src="../../spec/latest/respec-w3c-extensions.js" class="remove"></script>
     <script type='text/javascript'>
         var respecConfig = {
             // extend the bibliography entries
-            localBiblio: {
-              DOAP: "Ed Dumbill. <cite><a href=\"\">Turtle: Terse RDF Triple Language.</a></cite> Community Specification. URL: <a href=\"\"></a>",
-              "JSON-LD": "Manu Sporny, Gregg Kellogg, Markus Lanthaler, Editors. <cite><a href=\"\">JSON-LD 1.0</a>.</cite> W3C Editor's Draft (work in progress). URL: <a href=\"\"></a>",
-              "JSON-LD-API": "Markus Lanthaler, Gregg Kellogg, Manu Sporny, Editors. <cite><a href=\"\">JSON-LD 1.0 Processing Algorithms and API</a>.</cite> W3C Editor's Draft (work in progress). URL: <a href=\"\"></a>",
-              "JSON-LD-TESTS": "<cite><a href=\"\">JSON-LD 1.0 Test Suite</a></cite>. W3C Test Suite (work in progress). URL: <a href=\"\"></a>",
-          },
+            localBiblio: localBibliography,
             // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
-            specStatus:           "unofficial",
+            specStatus:           "base",
             copyrightStart:       "2010",
             doRDFa:               "1.1",
             // the specification's short name, as in
             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/10/22",
+            publishDate:  "2013-10-22",
+            testSuiteURI:         "",
             // 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:      "",
             //diffTool:             "",
             // 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",
             // editors, add as many as you like
             // only "name" is required
             editors:  [
@@ -52,7 +47,7 @@
                 { name: "Manu Sporny", url: "",
                   company: "Digital Bazaar", companyURL: "" }
             // 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.
@@ -67,16 +62,16 @@
                   company: "Graz University of Technology", companyURL: "" },
                 { name: "Niklas Lindström", url: "" }
             // name of the WG
             wg:           "RDF Working Group",
             // URI of the public WG page
             wgURI:        "",
             // name (with the 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
@@ -128,51 +123,26 @@
   <body prefix='earl: doap: mf:'>
     <section about='' id='abstract' typeof='earl:Software doap:Project'>
-      <p>
-        This document report test subject conformance for and related specifications for
-        <span property='doap:name'>JSON-LD</span>
-        <span property='dc:bibliographicCitation'>[[JSON-LD-API]]</span>
-        according to the requirements of the Evaluation and Report Language (EARL) 1.0 Schema [[EARL10-SCHEMA]].
-      </p>
-      <p>
-        This report is also available in alternate formats:
-        <a href='earl.ttl'>
-          Turtle
-        </a>
-        and
-        <a href='earl.jsonld'>
-          JSON-LD
-        </a>
-      </p>
+      <p>This document reports on implementations of the
+        <span property="doap:name">JSON-LD&nbsp;1.0</span> specifications. The
+        main purpose of this document is to show that each feature of the
+        specifications has been implemented by demonstrating interoperable
+        implementations of each feature. To evaluate the coverage of an
+        implementation's features, the JSON-LD Test Suite is used as a point
+        of reference.</p>
     <section id='sodt'></section>
-      <h2>Instructions for submitting implementation reports</h2>
-      <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:[email protected]">[email protected]</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;;;&#x000A;    earl:subject &lt;;;&#x000A;    earl:test &lt;;;&#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;; a doap:Project, earl:TestSubject, earl:Software ;&#x000A;    doap:name          &quot;JSON::LD&quot; ;&#x000A;    doap:homepage      &lt;; ;&#x000A;    doap:license       &lt;; ;&#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;; ;&#x000A;    dc:title           &quot;JSON::LD&quot; ;&#x000A;    dc:date            &quot;2011-08-29&quot;^^xsd:date ;&#x000A;    dc:creator         &lt;; ;&#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;; a foaf:Person, earl:Assertor;&#x000A;    foaf:name &quot;Gregg Kellogg&quot;;&#x000A;    foaf:title &quot;Implementor&quot;;&#x000A;    foaf:homepage &lt;; .&#x000A;</code></pre>
+      <h2>Introduction</h2>
+      <p>The goal of this report is to verify whether the <cite>JSON-LD&nbsp;1.0</cite> [[JSON-LD]]
+        and <cite>JSON-LD&nbsp;1.0 Processing Algorithms and API</cite> [[JSON-LD-API]]
+        specifications are implementable.</p>
+      <p>To evaluate the coverage of an implementation's features, the
+        <cite>JSON-LD&nbsp;1.0 Test Suite</cite> [[JSON-LD-TESTS]] is used
+        as a point of reference.</p>
       <p>See <a href="">JSON-LD Test Description</a> for more information.</p>