You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Eric Hauser <ew...@gmail.com> on 2010/07/02 16:02:04 UTC
Extending social data
Has anyone worked on/planning working on adding extension capabilities to
the social API? I need to ability to add arbitrary extensions to the social
API as defined in the 1.0 spec
http://opensocial-resources.googlecode.com/svn/spec/1.0/OpenSocial-Specification.xml#rfc.section.5.2
.
If not, I will probably begin working on a path. Is there an umbrella JIRA
ticket for 1.0 features?
Re: Extending social data
Posted by Paul Lindner <li...@inuus.com>.
I'd like to see something along these lines as well. At present an
extension (like the recently added activity streams extension) cannot add
data to the core models without touching the core code.
For simple json output you can subclass the existing implementation objects
and add your localized data. However this breaks down when you have
multiple contributors/extensions.
On Fri, Jul 2, 2010 at 7:50 AM, Eric Hauser <ew...@gmail.com> wrote:
> Kam,
>
> I think I'm ok from that perspective. MySpace has added well-defined
> fields
> to the social objects. I am looking for the ability to add extension
> fields
> to any object without explicitly adding the extensions in my concrete
> models.
>
> My questions were more around the technical implementation in Shindig.
> What
> I was thinking was something like:
>
> interface Extensible
> List<Extension> extensions
>
> class Extension
> String namespace
> Map<String, Object> extensions
>
> These would be added to the common solution and the JSON/ATOM converters
> would be altered to handle SerDe of classes that implemented Extensible.
> Then, concrete models that are open for extension could just implement the
> interface.
>
> --
> Eric Hauser
> http://erichauser.net/
>
>
> On Fri, Jul 2, 2010 at 10:29 AM, Kam Kasravi <kk...@yahoo-inc.com>
> wrote:
>
> > As far as I know, myspace has done this correctly - they've extended the
> > opensocial schema and
> > apis. Probably going thru their documentation would be the quickest way
> to
> > get an understanding of
> > how this is done from both the data model and javascript perspectives.
> >
> > kam
> >
> > On Jul 2, 2010, at 7:02 AM, Eric Hauser wrote:
> >
> > > Has anyone worked on/planning working on adding extension capabilities
> to
> > > the social API? I need to ability to add arbitrary extensions to the
> > social
> > > API as defined in the 1.0 spec
> > >
> >
> http://opensocial-resources.googlecode.com/svn/spec/1.0/OpenSocial-Specification.xml#rfc.section.5.2
> > > .
> > >
> > > If not, I will probably begin working on a path. Is there an umbrella
> > JIRA
> > > ticket for 1.0 features?
> >
> >
>
--
Paul Lindner -- lindner@inuus.com -- linkedin.com/in/plindner
Re: Extending social data
Posted by Eric Hauser <ew...@gmail.com>.
Kam,
I think I'm ok from that perspective. MySpace has added well-defined fields
to the social objects. I am looking for the ability to add extension fields
to any object without explicitly adding the extensions in my concrete
models.
My questions were more around the technical implementation in Shindig. What
I was thinking was something like:
interface Extensible
List<Extension> extensions
class Extension
String namespace
Map<String, Object> extensions
These would be added to the common solution and the JSON/ATOM converters
would be altered to handle SerDe of classes that implemented Extensible.
Then, concrete models that are open for extension could just implement the
interface.
--
Eric Hauser
http://erichauser.net/
On Fri, Jul 2, 2010 at 10:29 AM, Kam Kasravi <kk...@yahoo-inc.com> wrote:
> As far as I know, myspace has done this correctly - they've extended the
> opensocial schema and
> apis. Probably going thru their documentation would be the quickest way to
> get an understanding of
> how this is done from both the data model and javascript perspectives.
>
> kam
>
> On Jul 2, 2010, at 7:02 AM, Eric Hauser wrote:
>
> > Has anyone worked on/planning working on adding extension capabilities to
> > the social API? I need to ability to add arbitrary extensions to the
> social
> > API as defined in the 1.0 spec
> >
> http://opensocial-resources.googlecode.com/svn/spec/1.0/OpenSocial-Specification.xml#rfc.section.5.2
> > .
> >
> > If not, I will probably begin working on a path. Is there an umbrella
> JIRA
> > ticket for 1.0 features?
>
>
Re: Extending social data
Posted by Kam Kasravi <kk...@yahoo-inc.com>.
As far as I know, myspace has done this correctly - they've extended the opensocial schema and
apis. Probably going thru their documentation would be the quickest way to get an understanding of
how this is done from both the data model and javascript perspectives.
kam
On Jul 2, 2010, at 7:02 AM, Eric Hauser wrote:
> Has anyone worked on/planning working on adding extension capabilities to
> the social API? I need to ability to add arbitrary extensions to the social
> API as defined in the 1.0 spec
> http://opensocial-resources.googlecode.com/svn/spec/1.0/OpenSocial-Specification.xml#rfc.section.5.2
> .
>
> If not, I will probably begin working on a path. Is there an umbrella JIRA
> ticket for 1.0 features?