activitystrea.ms and OpenSocial

[NeilFred Picciotto]

Has anyone thought about (or better yet, worked on) unifying the
activity atom extensions spec with the OpenSocial spec for activity
data? I'm guessing the spec under discussion here is further along
than the OpenSocial one, but I haven't actually looked at the
OpenSocial spec since its initial launch.

Would be nice to just have one standard, obviously. :)

--
NeilFred Picciotto

[Martin Atkins]

Monica Keller from MySpace has noted that she is working with the
OpenSocial community to figure out how to unify the two. I'm looking
forward to seeing what they come up with.

[Chris Messina]

This has been a goal from the beginning, presuming that our work is successful and interesting, so that OpenSocial becomes a vector for seeing adoption of the Activity Streams format.

Until we have a few more drafts out and more implementations, I'm reluctant to push it to OpenSocial yet, though I'm more than happy to collaborate with folks on that project to move this forward!

Chris

--
Chris Messina
Citizen-Participant &
 Open Web Advocate

factoryjoe.com // diso-project.org // vidoop.com
This email is:   [ ] bloggable    [X] ask first   [ ] private

[Monica Keller]

I feel that we should promote collective concepts and thinking across
both standards and even with providers not supporting either standard
yet like FB. If the base concepts are the same then it will be easier
to migrate and we reduce the entry cost for developers.

OpenSocial has been thinking about generic representations of social
objects across providers for over a year so it was very useful for me
to review their latest 0.9 spec
http://opensocial-resources.googlecode.com/svn/spec/draft/REST-API.xml

Key concepts that we are missing in activitystrea.ms are: MediaItem as
a base object and our handling of Albums(collections) of objects needs
work.

Also our representation of person needs some work which Martin has
noted and Opensocial has an Address object but not the representation
for a Place or an Event which are key for myspace for example.

Opensocial is missing the verb concept and the object type concept and
in general indirect objects
but they do have a templating language

Where I am trying to get to is that:
Verb + object type should map to one template

For ex: If Opensocial developers say that this activity represents
Posting a Photo then we can provide the template and template
parameters they need to fill out.

Opensocial also needs to better clarify what template parameter types
are supported.

MySpace for example only handles Person and Literal. Supporting our
activity streams object types would provide a lot more value

Please circulate any more ideas you have.

We really need to get input from multiple providers to nail the specs
down.

congrats to PoCo becoming official btw

On Mar 24, 10:48 pm, Chris Messina <chris.mess...@gmail.com> wrote: