Re: Call for consensus for the pagination design (ISSUE-42)

Am 21.10.2015 11:40 schrieb elf Pavlik <perpetual-tripper@wwelves.org>:
>

>
> We could also mention that this only applies to 'default paging', in 
> case of using some alternative paging mechanism. Response from: 
>
> GET /an-issue/comments 
>
> may include some other kind of view on that particular collection. For 
> example chat messages posted to this collection (ChatChannel) today with 
> prev control to show them day by day. Similar to what we can see on 
>
> http://socialwg.indiewebcamp.com/irc/social/2015-10-20

That is an interesting point. A microblog server may choose to respond with a view that represents the current day as the initial response, i.e. the last page is the first view the client receives. An event service might respond with current events as the first page and allow to go to the past and the future from there.

Proposal: "the client must not make assumptions which partial view it receives as initial response, it has to rely on available navigation controls".

But this poses a question. Currently we have only the page number to qualify the current view. Somehow I want to be able to recognize that I am back at the initial page. Can the initial page be No.  0, with positive and negative page numbers? Should the PartialCollectionView have an optional title which could give a human readable string like 'Today' , 'Yesterday' , 'Tomorrow' or so - or maybe even a predicate to say exactly which range I am looking at? The latter gets complicated fast ;) 

Cheers, 
Dietrich