- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Tue, 3 Nov 2015 09:38:00 +0100
- To: Markus Lanthaler <markus.lanthaler@gmx.net>
- Cc: public-linked-data-fragments@w3.org
Hi Markus, > The client should have some safety measures to catch a case like this I > guess. The point is that this is not possible: there might just be a page which still has a triple, so the client is forced to keep on following "next" links. > Why not simply "the next link SHOULD NOT point to an empty fragment"? Agreed, with the change "empty page" (where we probably should define that then). > I used SHOULD NOT in because it could indeed happen from time to time if the > underlying dataset changes and shouldn't break a client. I could live with a > MUST NOT as well but I think a SHOULD NOT forces client developers to > program more defensively - which is a good thing. Fair enough. > Sure, but the concept is the same and we collect uses cases at > > https://www.w3.org/community/hydra/wiki/Client-initiated_pagination Okay, will add it there. Best, Ruben
Received on Tuesday, 3 November 2015 08:38:33 UTC