- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Wed, 12 Feb 2014 22:19:07 +0000
- To: Thomas Hoppe <thomas.hoppe@n-fuse.de>
- Cc: public-hydra@w3.org
(Changed subject for clarity.) > Slightly offensive question: > We are about to drop `hydra:CreateResourceOperation` and the like > (I don't repeat the pros/ cons here). > Isn't it inconsequent to keep hydra:search then?! > For me the same arguments for removing the aovementioned > operations apply equally to search or do I miss something? I see Hydra as the equivalent of HTML forms and as an evolved version of RDF Forms. An HTML search form has fields that allow humans to search a collection. hydra:search gives the same affordance to a machine client. Why would we want to drop something essential as that? (So yes, I think you do need to apply the pros/cons to hydra:search to discuss.) Best, Ruben PS I haven't joined the discussion on Operations because the arguments were to RESTy and technical. I think in itself, being able to explain the effect of an action on a _specific_ resource—which HTTP doesn't—is crucial.
Received on Wednesday, 12 February 2014 22:19:42 UTC