OpenSocial ID. Beyond VIEWER and OWNER.
111 views
Skip to first unread message
Alejandro Rivero
May 5, 2008, 5:26:54 AM5/5/08
to OpenSocial and Gadgets Specification Discussion
Jason Cooper has raised a tutorial
http://code.google.com/apis/opensocial/articles/datarequests/datarequests-0.7.html
where
1) For FetchPerson, "The person to be fetched can be identified using
an OpenSocial ID or using one of two constants provided by the API"
2) For FetchPeople, "you can also pass an array of OpenSocial IDs to
retrieve specific persons"
But 0.7 says that SpecID for FetchPerson is
"The ID of the person to fetch; can be the standard person ID of
VIEWER or OWNER"
and for FetchPeople
" String idSpec - An ID, array of IDs, or a group reference used to
specify which people to fetch; the supported keys are VIEWER, OWNER,
VIEWER_FRIENDS, OWNER_FRIENDS, or a single ID within one of those
groups"
The opensource container, shindig, contains some code to follow
Cooper's suggestion, but it is buggy. I have no idea about the
deployed containers (Hi5, MySpace, Orkut). Should 0.7 be fixed, or
does it reflects the consensus?
Alejandro
http://code.google.com/apis/opensocial/articles/datarequests/datarequests-0.7.html
where
1) For FetchPerson, "The person to be fetched can be identified using
an OpenSocial ID or using one of two constants provided by the API"
2) For FetchPeople, "you can also pass an array of OpenSocial IDs to
retrieve specific persons"
But 0.7 says that SpecID for FetchPerson is
"The ID of the person to fetch; can be the standard person ID of
VIEWER or OWNER"
and for FetchPeople
" String idSpec - An ID, array of IDs, or a group reference used to
specify which people to fetch; the supported keys are VIEWER, OWNER,
VIEWER_FRIENDS, OWNER_FRIENDS, or a single ID within one of those
groups"
The opensource container, shindig, contains some code to follow
Cooper's suggestion, but it is buggy. I have no idea about the
deployed containers (Hi5, MySpace, Orkut). Should 0.7 be fixed, or
does it reflects the consensus?
Alejandro
Cassie
May 5, 2008, 5:32:19 AM5/5/08
to opensocial-an...@googlegroups.com
Alejandro - This is a Shindig specific issue and should be discussed on the shind...@incubator.apache.org mailing list. The spec is correct. To see an example of good behavior please try using one of the deployed containers.
Thanks.
- Cassie
Thanks.
- Cassie
Alejandro Rivero
May 5, 2008, 5:43:21 AM5/5/08
to OpenSocial and Gadgets Specification Discussion
Sorry Cassie; I raised the point in Shindig, but it seems that the
problem is more general, at least the description of OpenMySpaces also
tells that only VIEWER and OWNER are allowed SpecIDs.
So a consensus in the spec or the deployed containers seems needed
too. Particularly I understand that it should work as Cooper says,
because if we get a collection of activities we have the UserIDs but
we have not fetched yet specific user profiles, and we want to have
them if we want to present meaningful information.
On the contrary, if the spec is correct and Cooper is wrong, shindig
and myspaces are right. But the activities can not present meaningful
information.
Alejandro
On 5 mayo, 11:32, Cassie <d...@google.com> wrote:
> Alejandro - This is a Shindig specific issue and should be discussed on the
> shindig-...@incubator.apache.org mailing list. The spec is correct. To see
problem is more general, at least the description of OpenMySpaces also
tells that only VIEWER and OWNER are allowed SpecIDs.
So a consensus in the spec or the deployed containers seems needed
too. Particularly I understand that it should work as Cooper says,
because if we get a collection of activities we have the UserIDs but
we have not fetched yet specific user profiles, and we want to have
them if we want to present meaningful information.
On the contrary, if the spec is correct and Cooper is wrong, shindig
and myspaces are right. But the activities can not present meaningful
information.
Alejandro
On 5 mayo, 11:32, Cassie <d...@google.com> wrote:
> Alejandro - This is a Shindig specific issue and should be discussed on the
> an example of good behavior please try using one of the deployed containers.
> Thanks.
>
> - Cassie
>
> On Mon, May 5, 2008 at 11:26 AM, Alejandro Rivero <Al.Riv...@gmail.com>
> Thanks.
>
> - Cassie
>
> wrote:
>
>
>
> > Jason Cooper has raised a tutorial
>
> >http://code.google.com/apis/opensocial/articles/datarequests/datarequ...
>
>
>
> > Jason Cooper has raised a tutorial
>
Cassie
May 5, 2008, 5:49:09 AM5/5/08
to opensocial-an...@googlegroups.com
Alejandro - the spec is always right :)
For 0.7 you can pass in a single id, an array of ids, or VIEWER, OWNER, VIEWER_FRIENDS, or OWNER_FRIENDS. If a container does not allow this they are simply not compliant and we should work with that container to fix their implementation.
I wouldn't worry about it too much though because for 0.8 we have introduced a formal opensocial.IdSpec object. This will take the place of the long list of accepted parameters that you currently see. For more information on this change you can read this thread:
http://www.google.com/url?q=http://groups.google.com/group/opensocial-and-gadgets-spec/browse_thread/thread/6b2ba00f8a38cb45&sa=D&usg=ALhdy2-4SprwtQxPD3-SQqaMWqi_wDS7TA
Thanks.
- Cassie
For 0.7 you can pass in a single id, an array of ids, or VIEWER, OWNER, VIEWER_FRIENDS, or OWNER_FRIENDS. If a container does not allow this they are simply not compliant and we should work with that container to fix their implementation.
I wouldn't worry about it too much though because for 0.8 we have introduced a formal opensocial.IdSpec object. This will take the place of the long list of accepted parameters that you currently see. For more information on this change you can read this thread:
http://www.google.com/url?q=http://groups.google.com/group/opensocial-and-gadgets-spec/browse_thread/thread/6b2ba00f8a38cb45&sa=D&usg=ALhdy2-4SprwtQxPD3-SQqaMWqi_wDS7TA
Thanks.
- Cassie
Paul Walker
May 9, 2008, 4:11:36 AM5/9/08
to opensocial-an...@googlegroups.com
Myspace now supports the ability of apps to use an array of ids. We limit the # of ids to 10 and the id must be a friend of the viewer. We’re attempting to be careful with abuse and have not seen a large use of this.
What are your thoughts on this? We are adding app counters in order to measure, but I haven’t seen a clear use case for this yet….
Appreciate the feedback
~Paul
Paul Lindner
May 14, 2008, 6:46:57 AM5/14/08
to opensocial-an...@googlegroups.com
On Fri, May 09, 2008 at 01:11:36AM -0700, Paul Walker wrote:
> Myspace now supports the ability of apps to use an array of ids. We
> limit the # of ids to 10 and the id must be a friend of the viewer.
> We're attempting to be careful with abuse and have not seen a large use
> of this.
>
> What are your thoughts on this? We are adding app counters in order to
> measure, but I haven't seen a clear use case for this yet....> Myspace now supports the ability of apps to use an array of ids. We
> limit the # of ids to 10 and the id must be a friend of the viewer.
> We're attempting to be careful with abuse and have not seen a large use
> of this.
>
> What are your thoughts on this? We are adding app counters in order to
hi5 also supports fetching an array of ids as per spec.
--
Paul Lindner ||||| | | | | | | | | |
lin...@inuus.com
Reply all
Reply to author
Forward
0 new messages