- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Mon, 5 Oct 2015 22:19:55 +0200
- To: pp.wasin@gmail.com
- Cc: public-hydra@w3.org
> From what i understand, hydra:search is used in more general case. What I remember is that hydra:filter is a subproperty of hydra:search. But _not_ in the sense that it changes the domain. Rather, hydra:search has a looser semantic coupling: it doesn't define _how_ the API uses the value to search data. On the other hand, hydra:filter has the specific semantics that it only returns data elements where the components match exactly. > It can attach to any resource. Both hydra:search and hydra:filter attach to a collection [1]. > On the other hand, hydra:filter is used only on hydra:Collection [1]. Same holds for hydra:search. > So, just use hydra:search. It is still OK, i think. Is okay (because hydra:filter would be a subproperty of it); but then I wonder what the difference is with TPF? Ruben [1] http://www.hydra-cg.com/spec/latest/core/#hydra:search
Received on Monday, 5 October 2015 20:20:28 UTC