W3C home > Mailing lists > Public > public-json-ld-wg@w3.org > March 2020

Re: Implementation report

From: Julien Lepiller <julien@lepiller.eu>
Date: Tue, 31 Mar 2020 16:22:10 -0400
To: Gregg Kellogg <gregg@greggkellogg.net>
CC: public-json-ld-wg@w3.org
Message-ID: <7AC692CD-AF18-4DBE-825A-FC3DB326012F@lepiller.eu>
Le 31 mars 2020 15:39:18 GMT-04:00, Gregg Kellogg <gregg@greggkellogg.net> a écrit :
>I created PR #441 (https://github.com/w3c/json-ld-api/pull/441
><https://github.com/w3c/json-ld-api/pull/441>, since merged) with your
>implementation report. Note that there were a number of errors that
>needed to be correct:
>* The base IRI for the manifests is set in the context file, and should
>be, for example,
><https://w3c.github.io/json-ld-api/tests/compact-manifest#t0001> not
>* It’s worth doing a syntax check on your generated turtle, there were
>some errors. An example Assertion could be the following:
>[ a earl:Assertion;
>  earl:assertedBy <https://lepiller.eu/#me>;
>  earl:subject <https://framagit.org/tyreunom/guile-jsonld>;
>  earl:result [
>    a earl:TestResult;
>    earl:outcome earl:passed;
>    dc:date "2020-03-30T03:33:09+0200"^^xsd:dateTime ];
>  earl:mode earl:automatic ] .
>(note that closing “]” after the dateTime).
>You can try using the “validate” command at
><http://rdf.greggkellogg.net/distiller>, for one.
>* Not that it’s significant, but the format of the timezone part of a
>dateTime should include a “:”, so 
>"2020-03-30T03:33:09+02:00"^^xsd:dateTime (see
><https://www.w3.org/TR/xmlschema-2/#dateTime-timezones>). It’s not used
>in the report, but a validator may/should mark it.
>* If you add a doap:programming-language entry to your software
>description, it will be added to your test-subject description
><https://w3c.github.io/json-ld-api/reports/#subj_0>), which would be
>useful for people looking for an appropriate implementation.
>You can see diffs to your source here
>for future reference if you end up re-generating the report.
>Anyway, congratulations for achieving such wide conformance, as you can
>see at https://w3c.github.io/json-ld-api/reports/
>(Note, we’ll freeze the test suite later this week, and you might find
>some additional tests).
>Gregg Kellogg
>> On Mar 29, 2020, at 7:11 PM, Julien Lepiller <julien@lepiller.eu>
>> Hi,
>> attached is an implementation report for guile-jsonld, an
>> implementation of the JsonLD API in the GNU Guile language.
>> I haven't yet released a version of that library, so this report is
>> the current master branch. If you need a release, then I'll make one
>> from that commit and give it a proper version number.
>> I haven't used or produced turtle documents before, but I tried to
>> produce a document that hopefully makes sense. I'm not sure if what I
>> did is correct, especially in the results, so please tell me if
>> anything is wrong, so i can correct it.
>> My library implements only JsonLD version 1.1, so I skiped tests
>> designed only for JsonLD 1.0. I still included them with a result of
>> earl:inapplicable. Is it correct, or should I simply not include
>> skiped tests?
>> I haven't implemented any of the features tested by the to RDF and
>> RDF test suites, and my implementation of features tested by the HTML
>> test suite is lacking (my main issue being that there doesn't seem to
>> be an HTML parser for Guile, I used an xml parser instead, but it's
>> enough). I haven't included any results from these three test suites.
>> Thanks in advance,
>> Julien Lepiller
>> <guile-jsonld-earl.ttl>

Thank you for your feedback! In the meantime I started writing a turtle parser in guile too, though it's not complete yet ^^. I'll correct my generator and re-submit when tests are frozen.
Received on Tuesday, 31 March 2020 20:22:38 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 31 March 2020 20:22:39 UTC