- From: Gregg Kellogg <gregg@greggkellogg.net>
- Date: Sun, 29 Jan 2017 11:27:17 -0800
- To: Markus Lanthaler <markus.lanthaler@gmx.net>
- Cc: Hydra <public-hydra@w3.org>
- Message-Id: <0CA03313-D670-4778-A267-1FB800E4C0FA@greggkellogg.net>
> On Jan 29, 2017, at 9:42 AM, Markus Lanthaler <markus.lanthaler@gmx.net> wrote: > > On 27 Jan 2017 at 15:14, Asbjørn Ulsberg wrote: >> 2017-01-27 12:30 GMT+01:00 Antonio Garrote Hernández <antoniogarrote@gmail.com>: >> >>> I just wanted to let you know about a Clojure library for Hydra APIs I have >>> been working on: >>> >>> https://github.com/antoniogarrote/levanzo > > Fantastic work Antonio! Thanks for sharing > > >>> It also supports validation based on the declarative information in the API >>> and mock data generation. I hope to add additional support for SHACL so it >>> can offer more expressive validations. >> >> Sounds like a good plan. I think it has been discussed before that >> SHACL should become an integrated part of Hydra, so experience in how >> to combine Hydra and SHACL is very welcome. :) > > +1 Note that the ShEx [1] JSON variant (ShExJ) was just changed to JSON-LD, and there are a number of implementations. ShEx handles the same use cases as SHACL, but makes implementation much easier. There are a couple of places that shape matching could come in handy: * For validating the Hydra documentation * As a way to specify the expected shape of a Hydra Operation * Client-side to formulate the operation * Server-side to validate the operation * For performing before/after analysis of the target. (LD-Patch could also come in handy here). Gregg [1] https://shexspec.github.io/spec <https://shexspec.github.io/spec> >>> Demos are live here for the console: http://antoniogarrote.com:8080/ >> >> Great demo! It's even faster than Markus' version. ;-) > > Indeed :-) > > > -- > Markus Lanthaler > @markuslanthaler > >
Received on Sunday, 29 January 2017 19:27:53 UTC