On Fri, Apr 18, 2008 at 10:36 AM, John Panzer <[EMAIL PROTECTED]> wrote:
> The idea with the templates is that the pattern is usually:
>
> /{datatype}/{owner-uid}/...
>
Sorry for chiming in so late on this. I definitely like the
consistency of approach for the APIs.
My concern is mainly around the user-centric nature of this approach
-- though maybe this is out of scope given the focus on single user
interactions from the gadget side?
I'm coming from a very group-centric service, and for accessing the
user group information:
/groups/{uid}/
Seems to limit the future potential for group representations in the
rest api, especially with no unique ID for groups. I guess ideally, I
would like to see unique IDs for groups, so they can be first class
citizens, and a way of access group information directly, something
like:
/groups/{gid}/ - returns group information with access to member lists
for public groups
with a different way of accessing groups by user:
/groups/all/byuser/{uid}
But of course this doesn't square so well with the /<return
type>/<uid> approach. Does anyone else see this as an issue, or see
other potential approaches to group information here?
--gh
