> 1. Should we use URI templates?
-1
In my desire to keep things simple, and because the first and primary
use case is "pagination" I am not sure this is necessary. And if it is
not necessary, I would advocate for dropping it.
> (the current draft only has
> {index}, and it seems unlikely that we could get consensus on
> anything more ambitious).
I would however like to have it open for an extension to provide a more
robust and complete implementation; one that provides date ranges, tags,
etc. For example, I would love to write an extension that enables
something like the following:
http://somedomian.com/atom/foo?{start=#date}&{tag=foo|bar|baz}&{end=#dat
e}
Or
http://somedomian.com/atom/foo?{to=#int}&{from=#int}
Something that gives more detail to the client so that it can surface
more intelligable forms to the user.
If we are going to provide a list template mechanism, let's do it right
and let's do it completely. But let's not make APP a dependency upon it.
> 2. Should we have prev/next pointers in collections to allow
> clients to page through?
+1
No doubt.
> On the face of it, it seems like all four possible outcomes
> are plausible.
> - No templates, no paging
-1
> - Templates but no paging
-1
> - Both templates and paging
-1
> - No templates but paging
+1
Byrne Reese
