--- 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: http://www.w3.org/ns/earl# doap: http://usefulinc.com/ns/doap# mf: http://www.w3.org/2001/sw/DataAccess/tests/test-manifest#'>
<head>
<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='http://www.w3.org/Tools/respec/respec-w3c-common' type='text/javascript'></script>
+ <script type="text/javascript" src="../../spec/latest/respec-w3c-extensions.js" class="remove"></script>
<script type='text/javascript'>
//<![CDATA[
var respecConfig = {
// extend the bibliography entries
- localBiblio: {
- DOAP: "Ed Dumbill. <cite><a href=\"https://github.com/edumbill/doap/wiki\">Turtle: Terse RDF Triple Language.</a></cite> Community Specification. URL: <a href=\"https://github.com/edumbill/doap/wiki\">https://github.com/edumbill/doap/wiki</a>",
- "JSON-LD": "Manu Sporny, Gregg Kellogg, Markus Lanthaler, Editors. <cite><a href=\"http://json-ld.org/spec/latest/json-ld/\">JSON-LD 1.0</a>.</cite> W3C Editor's Draft (work in progress). URL: <a href=\"http://json-ld.org/spec/latest/json-ld/\">http://json-ld.org/spec/latest/json-ld/</a>",
- "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>",
- },
-
+ 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 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/10/22",
-
+ publishDate: "2013-10-22",
+
+ testSuiteURI: "http://www.w3.org/2013/json-ld-tests/",
+
// 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",
-
+
// editors, add as many as you like
// only "name" is required
editors: [
@@ -52,7 +47,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.
@@ -67,16 +62,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
@@ -128,51 +123,26 @@
</head>
<body prefix='earl: http://www.w3.org/ns/earl# doap: http://usefulinc.com/ns/doap# mf: http://www.w3.org/2001/sw/DataAccess/tests/test-manifest#'>
<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 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>
<section id='sodt'></section>
<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: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;
 earl:assertedBy <http://greggkellogg.net/foaf#me>;
 earl:subject <http://rubygems.org/gems/json-ld>;
 earl:test <http://json-ld.org/test-suite/tests/flatten-manifest.jsonld#t0001>;
 earl:result [
 a earl:TestResult;
 earl:outcome earl:passed;
 dc:date "2013-02-22T15:12:30-08:00"^^xsd:dateTime];
 earl:mode earl:automatic ] .
</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> <http://rubygems.org/gems/json-ld> a doap:Project, earl:TestSubject, earl:Software ;
 doap:name "JSON::LD" ;
 doap:homepage <http://gkellogg.github.com/json-ld> ;
 doap:license <http://creativecommons.org/licenses/publicdomain/> ;
 doap:description "JSON::LD parses and serializes JSON-LD into RDF and implements expansion, compaction and framing API interfaces."@en ;
 doap:programming-language "Ruby" ;
 doap:developer <http://greggkellogg.net/foaf#me> ;
 dc:title "JSON::LD" ;
 dc:date "2011-08-29"^^xsd:date ;
 dc:creator <http://greggkellogg.net/foaf#me> ;
</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> <http://greggkellogg.net/foaf#me> a foaf:Person, earl:Assertor;
 foaf:name "Gregg Kellogg";
 foaf:title "Implementor";
 foaf:homepage <http://greggkellogg.net/> .
</code></pre>
-
+ <h2>Introduction</h2>
+
+ <p>The goal of this report is to verify whether the <cite>JSON-LD 1.0</cite> [[JSON-LD]]
+ and <cite>JSON-LD 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 1.0 Test Suite</cite> [[JSON-LD-TESTS]] is used
+ as a point of reference.</p>
+
<p>See <a href="http://json-ld.org/test-suite/">JSON-LD Test Description</a> for more information.</p>
</section>
<section>