Re: Hydra+SHACL

Hello Michael

Thanks for the link. I was not aware of the WoT Think Description spec.

It does look like a packaged Hydra+SHACL solution indeed with a lot parallels. My main difference (and what I consider an issue) is that it seem based completely in JSON Schema and JSON-LD. SHACL is rooted in the graph model and does no concern itself with the representation serialisation. 

I would also expect SHACL to be more extensible. Since the Data Schema is also based in JSON-LD for the processing model, it could be a hurdle for implementors. I understand however how this is quite beneficial for the limited computational power of WoT applications.

In terms of form-building, there is definitely enough information in the WoT Data Schema to handle a subset of the possibilities of SHACL. Not sure if it would offer any advantage though, unless you want to run the builder on constrained machine. Otherwise maybe it would be easy to translate it to shapes and build a form from that?

Best,
Tom

On 28 December 2020 at 01:24:03, Michael Puckett (michaelcpuckett@gmail.com) wrote:
> Hi Tomasz,
>  
> Your form builder looks very promising!
>  
> I've been thinking about building something similar using Web of Things
> (WoT) Group's Actions/Data Schema validation mechanism:
>  
> https://www.w3.org/TR/wot-thing-description/#actionaffordance
>  
> https://www.w3.org/TR/wot-thing-description/#sec-data-schema-vocabulary-definition  
>  
> I don't know anything about it beyond the spec, so it might not be a good
> fit.
>  
> Any thoughts on building a full-fledged form builder with Hydra/SHACL vs
> WoT?
>  
> (Automatically fetching the wikipedia country data is really great, I'm not
> quite sure how that would be accomplished in WoT.)
>  
> Thanks,
> Michael Puckett
>  
> On Sat, Dec 26, 2020 at 10:33 AM Tomasz Pluskiewicz  
> wrote:
>  
> > Hello Group
> >
> > I’d like to share with my first post on using Hydra and SHACL together.
> >
> > https://t-code.pl/blog/2020/12/hydra-shacl-interoperability/
> >
> > I plan a bunch more to then gather these ideas in an auxiliary
> > specification to complement Hydra Core, probably resolving issues #214 [1]
> > and #215 [2]
> >
> > I will wholeheartedly welcome your feedback.
> >
> > Have a good day and Happy New Year,
> > Tom
> >
> > [1]: https://github.com/HydraCG/Specifications/issues/214
> > [2]: https://github.com/HydraCG/Specifications/issues/215
> >
> >
>

Received on Monday, 28 December 2020 10:20:51 UTC