- From: Karol Szczepański <karol.szczepanski@gmail.com>
- Date: Mon, 28 Sep 2015 23:02:47 +0200
- To: Markus Lanthaler <markus.lanthaler@gmx.net>, "public-hydra@w3.org" <public-hydra@w3.org>
Received on Monday, 28 September 2015 21:03:11 UTC
Oh, I hope to have that fixed ASAP. Without the console working I cannot verify my solution and apply necessery ammendments to it so it generates an API doc that is compliant with Hydra as much as possible. Regards Karol Od: Markus Lanthaler Wysłano: poniedziałek, 28 września 2015 22:56 Do: public-hydra@w3.org Temat: RE: Yet another Hydra Console question On Thursday, September 24, 2015 7:41 PM, Karol Szczepański wrote: > I’ve investigated a bit deeper. I was able to craft a very tiny > example (I’ve added to the gist I’ve created earlier, see > https://gist.github.com/alien-mcl/bbe031342ed64e9a1e89). > > It seems that the hydra console doesn’t like explicitely typed > literals. In the example below: [...] > "http://www.w3.org/2000/01/rdf-schema#comment": { > "@type": "http://www.w3.org/2001/XMLSchema#string", > "@value": "Describes a person." > }, [...] > It causes a 400 JsonLdException, but when removing ‘"@type": > "http://www.w3.org/2001/XMLSchema#string",‘ it starts to work! > > Is it a bug? I’ve consulted JSON-LD spec on W3C and this construct is > pretty legal. This is completely valid JSON-LD. You uncovered a bug in my modified JSON-LD processor that powers the rendering of the JSON-LD responses in the Hydra Console. Thanks a lot for debugging this. I hope to get it fixed in the next couple of days. -- Markus Lanthaler @markuslanthaler
Received on Monday, 28 September 2015 21:03:11 UTC