[Commentor] LC-2836 Tim Berners-Lee (archived comment) [Working Group decision] Given the time constraints under which the WG is it is deemed unpractical to depend on defining a new response code as suggested. However, based on input from several HTTP experts the WG decided to return the first page with 200 response code on initial GET which prevents the additional roundtrip you objected to. See http://www.w3.org/2013/meeting/ldp/2013-11-04#resolution_2 Move Paging information out of the RDF content into HTTP headers. See http://www.w3.org/2013/meeting/ldp/2013-09-30#resolution_2 [Commentor reply] tocheck [Comment] 
######################### 4.10.2.3 303 lis a basically very unsatisfactory design because of the round trip. As this is a new spec, suggest defined 20X code meaning like a 303 but containing the representation of the thing 303d to. This has been found to a problem in LD. LDP can avoid it now. Benefit: First page back to user in one less round trip. ######################### 4.10.2.4.3 This design puts the type and next links in the data. I prefer I think using HTTP headers here as elsewhere. Page control stuff is very meta, messy to have it in with actual data. Not a problem for containers, but for normal LDPRs IMHO.