Activity Streams Updated to Support 1.0

[Eric Woods]

Hi All,

I've completed another iteration of Activity Streams support in OpenSocial. This patch supports Activity Streams 1.0, which is almost final. This iteration supports just the core Activity Streams 1.0 spec. It does not yet support arbitrary extensions or OpenSocial-specific extensions. Ideally, I'd like to get Shindig to support arbitrary extensions so that each extension does not need to be explicitly hardcoded (the AS spec also calls for supporting arbitrary extensions). At minimum, the next iteration will support the extensions necessary for OpenSocial to deprecate the Activities & Messaging APIs.

The OpenSocial spec patch has been uploaded for review here: http://code.google.com/p/opensocial-resources/issues/detail?id=1140

The Shindig reference implementation has been uploaded to JIRA and codereview:
https://issues.apache.org/jira/browse/SHINDIG-1536
http://codereview.appspot.com/3988041/

Comments are welcome.

- Eric W.

[Matthew Marum]

Patch has been applied.

[Mark W.]

One thing that I have not seen yet in the activity streams proposal is the addition of the opensocial extensions for "deliverTo:" and "actionLinks". We had talked about this a few weeks ago in RTP and I'd like to add these in.

[Mark W.]

Eric et at...

A couple of things that I wanted to get on the table before I can vote +1 on activity streams:

1) I wanted to circle back on the OpenSocial specific extensions that I mentioned above, specifically, deliverTo: (or to:) and actionLinks. I've created a patch, uploaded it to Issue 1140 and applied it.

2) I think we should add a bit more introductory text around the linkage between the activity streams work and OpenSocial spec. This is also in the patch. 

3) We added a media link data type, but nowhere do we tie this back to media items. I think this is a gap. We either need to add the fields to media items as well, so that a media item CAN BE a media link, or some how resolve this.

4) We wanted to deprecate the existing activity work. I suggest we remove it from 2.0, or at a minimum, clearly mark it as deprecated in the spec. 

Please let me know your thoughts...

-Mark W.

[James Snell]

On Mon, Jun 6, 2011 at 7:55 PM, Mark W. <weitze...@gmail.com> wrote:
> Eric et at...
> A couple of things that I wanted to get on the table before I can vote +1 on
> activity streams:
> 1) I wanted to circle back on the OpenSocial specific extensions that I
> mentioned above, specifically, deliverTo: (or to:) and actionLinks. I've
> created a patch, uploaded it to Issue 1140 and applied it.

+1 to "to".

> 2) I think we should add a bit more introductory text around the linkage
> between the activity streams work and OpenSocial spec. This is also in the
> patch.

Agreed. The extent of the linkage certainly is not clear and there are
a number of inconsistencies between the two data models that folks
need to be aware of.. specifically in the base object type
definitions.

> 3) We added a media link data type, but nowhere do we tie this back to media
> items. I think this is a gap. We either need to add the fields to media
> items as well, so that a media item CAN BE a media link, or some how resolve
> this.

+1... media item like should be made an extension of the activity
stream media link.

> 4) We wanted to deprecate the existing activity work. I suggest we remove it
> from 2.0, or at a minimum, clearly mark it as deprecated in the spec.

+1

- James

> Please let me know your thoughts...
> -Mark W.
>

> --
> 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/-/ulQZRyIgBA4J.
> To post to this group, send email to
> opensocial-an...@googlegroups.com.
> To unsubscribe from this group, send email to
> opensocial-and-gadg...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en.
>