- From: Jacopo Scazzosi <jacoposcazzosi@gmail.com>
- Date: Mon, 16 Feb 2015 09:17:04 +0000
- To: Ruben Verborgh <ruben.verborgh@ugent.be>
- Cc: Tomasz Pluskiewicz <tomasz@t-code.pl>, public-hydra@w3.org
Received on Monday, 16 February 2015 09:17:32 UTC
Hi Ruben. I see your point. I think it'd be nice for TPFs not to rely on hydra, but perhaps this is a consideration for another type of LDFs entirely. Thanks for your clarification. On Feb 16, 2015 8:29 AM, "Ruben Verborgh" <ruben.verborgh@ugent.be> wrote: > Hi Jacopo, > > > Assuming I correctly understand the purpose of TPF, it looks to me like > a decent amount of integration between TPF endpoints and subject pages > might result in APIs that do not need a dedicated pagination construct. > > Well, yes and no. > TPF itself relies on the Hydra Core Vocabulary to provide constructs for > paging, so we would need those in any case. > > But the combination you suggest might indeed be meaningful for some. > Instead of having to write a full API, you can direct clients to relevant > TPFs. Makes sense! > > Best, > > Ruben
Received on Monday, 16 February 2015 09:17:32 UTC