W3C home > Mailing lists > Public > public-earl10-comments@w3.org > May 2011

Bug 032: Requirements for JSON

From: Sean B. Palmer <sean@miscoranda.com>
Date: Wed, 11 May 2011 19:17:01 +0100
Message-ID: <BANLkTinGxwmh87VL+J62z74UJ7-noemG7Q@mail.gmail.com>
To: public-earl10-comments@w3.org
This is feedback on a Last Call Working Draft:

Developer Guide for Evaluation and Report Language (EARL) 1.0
W3C Working Draft 10 May 2011

Specifically § 5. Serializations of EARL Reports:


The body of which reads, in its entirety:

“Note: this section will be added to refer the reader to best
practices and existing references in RDF/XML serializations (possibly
providing a DTD or XML Schema for EARL); RDF->JSON conversion (in
particular if we do end up providing an XML Schema or DTD); binary RDF
(work in progress at W3C); or other formats that may be useful to tool

Does this mean that a JSON serialisation of EARL will only be
available if there is an XML Schema or a DTD for EARL? And is it at
all contingent on the binary RDF serialisation or will it be regarded
as a separate entity? In other words, would the group say “we can't
work on the JSON serialisation without working on the binary RDF
serialisation because that would be unfair”?

If there is a JSON serialisation, what will be its requirements? Would
it be possible for such a format to be 100% convertible to and from
EARL in its RDF guise? There does not appear to be anything about any
other serialisation in the EARL Requirements draft:

Requirements for the Evaluation and Report Language (EARL) 1.0
W3C Working Draft 29 October 2009

No results for “JSON” or “serial”.

If a JSON conversion is contingent in any way on XML Schema, DTD,
binary RDF, or any other technology other than EARL and JSON, then
this is a requirement bug. It would be easy to convert RDF to JSON and
back again, in some practical degree, without the use of, for example,
XML Schema. In fact, I'm not even sure why this should be connected at

Sean B. Palmer, http://inamidst.com/sbp/
Received on Wednesday, 11 May 2011 18:17:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:42:24 UTC