Re: Some comments on the paging spec

> 1. Section 5.1 says " A server can offer links that support forward 
> and/or backward traversal of the pages, but it has to offer at least
> one."  So, it can support only backwards traversal.  But then 5.2.1 says 
"

5.1 (as of today, 6.1) is non-normative. The normative clauses (6.2.2.11) 
require forward links, and the 303/2NN patterns themselves mean that the 
only end of the sequence you're guaranteed access to is 'first'.  In 
effect, forward traversal is required and backward is optional, so the 
old-5.1 is downlevel.  I skimmed Issues to see if this changed recently, 
nothing jumped out; I suspect it's been that way for a long long time.  I 
also updated the definitions to try and clarify that the 303/2NN resource 
(Eric P's "expected resource in the 2NN draft") *is* the first in-sequence 
page resource, and everything else is relative to that starting point.

I have been working on the examples this week, so there is now a friendly 
green "under construction" sign on these non-normative bits.  If you 
pulled a copy earlier for later reading, I'd recommend a refresh.


> 2. Section 5.1 says " LDP Paging defines a mechanism for informing 
> clients that the paged resource has been changed ..."  but the 
> mechanism is not spelled out in any detail.

See if 6.2.2.7 grabs you (new).




Best Regards, John

Voice US 845-435-9470  BluePages
Cloud and Smarter Infrastructure OSLC Lead