- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Mon, 5 Oct 2015 16:58:08 +0200
- To: pp.wasin@gmail.com
- Cc: public-hydra@w3.org
Hi Wasin, > This is my first email to HYDRA community. Welcome! > From what I known, hydra:filter [1] is the vocabulary that is used to query members of collection. > Linked Data Fragment (LDF) [2] is more general concept that used to query any triples depend on the resource that attract to. > Triple Pattern Fragment (TPF) [3] is implementation of LDF, which is based on HYDRA vocabulary. Correction to the last one: TPF defines a specific kind of LDFs, but it is not a concrete (= software) implementation. > In the example of TPF [3], it is used against dataset. > But I want to use TPF with hydra:Collection. > Therefore, i replace the hydra:search with hydra:filter and attract them to the collection (i.e., <http://example.org/collection>) > The details of my designed API show as below. I'm not sure I follow the reasoning. The difference between hydra:filter and hydra:search is not related to the difference between collection and dataset. Important remark: hydra:filter is not an official property yet. In fact, hydra:filter would be more appropriate than hydra:search for TPF, but we currently use hydra:search because hydra:filter is not official. > The question is whether this API is valid? Looks good to me. Just unsure of the need to differentiate from TPF, could you clarify? Best, Ruben
Received on Monday, 5 October 2015 14:58:39 UTC