- From: Karol Szczepański <karol.szczepanski@gmail.com>
- Date: Mon, 16 Nov 2015 22:32:33 +0100
- To: <public-hydra@w3.org>, "Thomas Hoppe" <thomas.hoppe@n-fuse.de>
Hi Thomas >Hmm, a property defining an operation does not sound straight forward to me >and with the current means of hydra this would not be possible to express. Well, I think it is doable right now. Hydra's SupportedProperty is a sub-class of hydra's Resource. There is an "interesting" property named hydra:operation that binds a Resource with an Operation, thus it won't do any harm to have something like this: my:Property a hydra:SupportedProperty; hydra:operation my:Operation . I can imagine a client that could check supported property's operations and choose an interesting one (i.e. that uses an IriTemplate mapping wiht hydra:freetextQuery) to do what's needed. As for the Dietrich's suggestion regarding allowed values - SHACL indeed touches that as far as I can remember. Best Karol
Received on Monday, 16 November 2015 21:32:57 UTC