- From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Nov 2019 08:51:17 +0000
- To: public-hydra-logs@w3.org
> I think order within the page is not interesting You really think so? It's not about runtime overhead but implementation complexity. The spec and a generic client will have to be very sophisticated to support a universal order description. Start adding paths and `castTo` and it's almost certainly going to become a nightmare. Not to mention that the particular field used to sort may not even be part of the response itself, which will prevent any kind of in-memory sorting. `rdf:List` is the easiest way to avoid all of those issues and simplify the order description. > I want a client to know that it will not find more items in the next pages, as it won’t match its filter any longer. Maybe it's not the best approach to try to standardise? Given the year example, the first design choice would be to filter and not have the client figure out the contents of further pages by analysing how the page got sorted and what are the contents. -- GitHub Notification of comment by tpluscode Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/172#issuecomment-555398538 using your GitHub account
Received on Tuesday, 19 November 2019 08:51:26 UTC