- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Tue, 11 Feb 2014 22:45:09 +0000
- To: Markus Lanthaler <markus.lanthaler@gmx.net>
- Cc: public-hydra@w3.org
> I'm not sure whether there's a necessity to make this explicit respectively > how explicit we wanna make it. We can try to define the hydra:search > property in a fuzzy-enough way to not run into the complexities of generic > query languages. I'm don't know how feasible that's it, i.e., how much we > can improve the current description > > "A IRI template that can be used to query a collection" > > Do you have any ideas? Could the the following be added? "The items in the collection are filtered on whether they have the specified values for the specific properties.” That defines hydra:search really strictly, but makes it very useful. An alternative would be to keep hydra:search vague, but to define a subproperty such as hydra:propertySearch with that semantics. > You could provide a hint with "returns", couldn't you? Yes… but that'd probably remain a "hint" (i.e., not a strong expectation). > Talking about this stuff too abstractly doesn't bring us far I think. We > should try to come up with examples, define what the client knows and what > it doesn't know, define what information the server provides, and finally > check if the client can achieve its goal with that combined information. That's true. I hope to have something soon. Ruben
Received on Tuesday, 11 February 2014 22:45:44 UTC