- From: Pieter Colpaert via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Nov 2019 09:33:24 +0000
- To: public-hydra-logs@w3.org
> > I think order within the page is not interesting > > You really think so? Yes, and looking at how the Linked Data Platform is doing it, I’m not the only one with that opinion. I quote from their spec: >>> There are many cases where an ordering of the members of a container is important. LDP does not provide any particular support for server ordering of members in containers, __because any client can order the members in any way it chooses based on the value of any available property of the members__. [Read more](https://www.w3.org/TR/ldp-paging/#ldpc) > > 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. My use case is for Web APIs where supporting any kind of dynamic client-side ordering/filtering on the server-side would become too expensive (cfr. the Linked Data Fragments axis where we want to find a trade-off between server and client effort). In order to optimize caching, I want to minimize the amount of orderings I support, and describe these in-band. -- GitHub Notification of comment by pietercolpaert Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/172#issuecomment-555415536 using your GitHub account
Received on Tuesday, 19 November 2019 09:33:26 UTC