Hi All, I'm working on an RESTful OpenSocial implementation using Shindig and have run into a few questions. Sorry if any of these have been asked/ answered before, but I had trouble finding the answers in this group or in the spec.
1) I'm not entirely clear how Activity requests are supposed to handle an associated Person. I see that Activities can have a field "userId", but what if I want to include more information about the Person? Do I put it inside the field "templateParams" inside either the "person" field or the other fields in the ActivityTemplateParams type? 2) How am I supposed to handle fields that are specific to an Activity. For example, let's say I have a review activities that has an attribute "rating". Rating doesn't exist in Activity (it exists in MediaItem, but this is not a MediaItem). What is the desired way of dealing with this, is there a field that fits this situation? Should I create a special field for it, leave the information out entirely or possible overload the "body" field with more data? 3) For the @supportedfield request, how do should I deal with different Activities having different sets of fields returned. Ignoring the previous question, for example, one type of Activity may have a "url" associated with it while another may not. For @supportedfields, should it return the maximum set? or somehow specify a type -> field set mapping? Thanks for any and all of your help, Jason --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Implementing OpenSocial Containers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/opensocial-container?hl=en -~----------~----~----~----~------~----~------~--~---
