How should we standardize pagination? I’m a big fan of Content-Range + 206s

• They can be seamlessly interchanged by detecting status
• We can establish our own convention with the type identifier in the range header

They’re not popular, but we can make them 😉 And if anybody needs to not use them they can just define their own generic resource class. But we get the special syntax

We can do special codegen for the Standard Iterators

What other methods do standard collections have?

Other things to consider

• Cursors - I’ve warmed up to them; they’re good enough for AWS
• Links to collections may look different from normal links

Things we need

• Links - prev, next, first, last
• Metadata
  • Total number of results
  • Page number, total number of pages

Schema attempt

• content - [T]
• pagination - Optional object with the above - can be empty if the request is no longer paginated

This is nice but doesn’t allow for forwards compat like 206es do