- From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
- Date: Sun, 17 Feb 2019 20:10:49 +0000
- To: public-hydra-logs@w3.org
> Good point - skip/take approach is free of that issue as it relies only on number of items within the set (which will be always a natural number). This is irrelevant. Like I said, not every API will want to follow the skip/take design and I'm pretty sure that it's a less common approach in practice outside of implementations close to a query language, like OData. I find it harmful that Hydra should inadvertently favour one possible approach over another. This statement is also inaccurate. Just like with `pageReference` or any other alternative, it's not nearly enough to just tell the client > these are the `skip` and `take` variables, deal with them The server will most likely still impose restrictions, such as `Page size cannot be greater then 50`. If we take a step back and look at ways to extend the vocab around templates, we will be able to represent any design -- GitHub Notification of comment by tpluscode Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/184#issuecomment-464502828 using your GitHub account
Received on Sunday, 17 February 2019 20:10:53 UTC