- From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Feb 2019 20:58:39 +0000
- To: public-hydra-logs@w3.org
> As I wrote, you can express pageIndex/itemsPerPage with offset/limit, but not the opposite (limit can change on each request).
That is not the point. If I have an API which has collection URLs in the form of `/collection{?pageIndex,pageSize}` there is nothing to express differently. Because whose responsibility it would be to translate one form to the other? The generic client's?
The design is what it is and we must allow to describe both and possible any other, even if it's going to be specific to the given API (if it should use custom descriptions).
> For desktop views, your right. But for mobiles, not really.
We should not discuss desktop vs mobile. We are designing a generic API Description vocabulary. If it favours one solution (skip/take) over another (page index/page size) then we have failed.
> In streaming-line approach you'd favor skip/take as usually there is only `more` button [...]
This argument is moot as such "streaming" it's already easier done by following the `next` link. This PR will not change it.
--
GitHub Notification of comment by tpluscode
Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/184#issuecomment-463367658 using your GitHub account
Received on Wednesday, 13 February 2019 20:58:41 UTC