- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Thu, 29 Oct 2015 21:45:28 +0100
- To: Karol Szczepański <karol.szczepanski@gmail.com>
- Cc: Hydra <public-hydra@w3.org>
Hi Karol, > While I'm somehow unhappy to rush with hydra changes to cover particular needs in any other specification, TPF in this case Well, TPF is part of the Hydra family of specs, and the previous change to the Core Vocabulary spec was breaking. TPF seems to be the most implemented and thus most affected, so several implementers need to be notified. To bundle all breaking changes, we need to prioritize this issue, which was already on the list anyway. I hope this clarifies the timing. > I'm not sure which fuzziness of the hydra:search you refer to. Note that these are Markus' words from the issue, not mine. But I agree: hydra:search is defined as selecting items using the given attributes in *some* way. It does not specify how to the server uses the attributes. Instead, hydra:filter states that members should be selected based on whether they have properties that match all attributes. These are stronger semantics than hydra:search. > Indeed, hydra:freetextQuery is fuzzy as it takes in theory an user's input, but doesn't bind that input with any particular property thus it might be not suitable in many situations. That's a different kind of fuzzy (string matching). > 1. Property of which value we want to filter on - from your example I assume that this is a case Yes. Best, Ruben
Received on Thursday, 29 October 2015 20:46:00 UTC