I think, with some modifications to the REST API, you could accomplish a lot of use cases in a single request. For example, a request to a Person URI ought to be able to pull in not just profile data but data from that Person's activity stream, documents, etc. if they are available.

Something like.. GET /social/rest/people/user1?fields=displayName,thumbnailUrl,os:activitystream would return the display name, thumbnail URL from User1's profile along with data from User1's ActivityStream included inline with this request.

Similarly, a request like GET /social/rest/people?userId=user1,user2,user3&fields=displayName,thumbnailUrl,os:activitystream would return all the same data as the above request for users User1, User2, and User3.

You could also specify fields to be lined too.. GET /social/rest/people/user1?fields=displayName,thumbnailUrl,os:activitystream.title

could would be essentially equivalent to

GET /social/rest/people/user1?fields=displayName,thumbnailUrl & GET /social/rest/activitystreams/user1?fields=title

-- You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group. To view this discussion on the web visit https://groups.google.com/d/msg/opensocial-and-gadgets-spec/-/NHnc1sDJfnUJ .

To post to this group, send email to open...@googlegroups.com. To unsubscribe from this group, send email to opensocial-and-gadgets-spec+unsu...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en.