[Architecture] Update on project - Open Social Integration to GadgetServer using Apache Shindig

Thu May 13 22:21:58 EDT 2010

On Fri, May 14, 2010 at 7:27 AM, Umashanthi Pavalanathan <
umashanthi at wso2.com> wrote:

>
>
> On Thu, May 13, 2010 at 9:36 PM, Tyrell Perera <tyrell at wso2.com> wrote:
>
>>
>>
>> On Fri, May 14, 2010 at 6:32 AM, Sanjiva Weerawarana <sanjiva at wso2.com>wrote:
>>
>>> I don't understand why it should not be part of the registry. W talk
>>> about the registry having social features (comments, rating and tags) and to
>>> me opensocial significantly raises the validity of that claim! Why would we
>>> not do that natively?
>>>
>>> I would argue that even the storage should be contemplated natively ..
>>> not just use the representations we have now.
>>>
>>> Social computing is going to become front and center very soon. The
>>> registry (and hence all of our products) are well positioned to be effective
>>> in that setting with this work!
>>>
>>> To me the other APIs are different - that's basically to make storage and
>>> management of specific types of resources easier to do.
>>>
>>>
>> +1
>>
>> We spent a lot of time going through the core OpenSocial code and it's
>> handlers in order to come up with the model suggested in the document. The
>> main purpose of that was to have these APIs in the Registry core.
>>
>> We should think of these as our core Registry's social API, which means
>> it's implementation independent. If someone else comes up with an OpenSocial
>> impl (ie: PHP based Partuza), they should be able to use our Registry as the
>> repository. Of course this is just for starters. As Paul also mentioned in a
>> previous mail, these APIs will help make our whole carbon platform social
>> across products.
>>
>> I also think that the profile related APIs and Friending (which
>> initializes the social graph) should go into identity/usermanager.
>>
>
> I had a discussion with DimuthuL who handles identity/usermanagement.  She
> will be responding here with her ideas about Friending in the identity side.
>
>
>
Great. So.. about the OpenSocial profile additions such as "drinker",
"smoker" etc. I think we can have a basic profile with mandatory components
(which are already in identity) and leave the rest for the end application
to configure via its identity.xml as required.

Tyrell

> Thanks,
> Umashanthi
>
>
>
>
>>
>>
>> Tyrell
>>
>>
>>
>>> Sanjiva.
>>>
>>>
>>> On Fri, May 14, 2010 at 6:19 AM, Sumedha Rubasinghe <sumedha at wso2.com>wrote:
>>>
>>>> Uma & myself had several offline discussions on this. She came up with a
>>>> model(mentioned previously) of how the data is actually going to be stored
>>>> on Registry using available data structures (collection,resource,
>>>> properties, association, etc...).
>>>>
>>>> What I feel is, we should not have this as part of Core Registry API.
>>>> But rather as a separate API.
>>>> Eg: Social API backed by repository as the store.
>>>>
>>>> Similarly, we can have Document API, Multimedia API, Map API,etc based
>>>> on how & what's going to be stored on repository.
>>>>
>>>> /sumedha
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, May 13, 2010 at 3:14 PM, Umashanthi Pavalanathan <
>>>> umashanthi at wso2.com> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Thu, May 13, 2010 at 2:36 PM, Sanjiva Weerawarana <sanjiva at wso2.com
>>>>> > wrote:
>>>>>
>>>>>> Looks good to me .. in my reply yesterday (which bounced for some yet
>>>>>> unexplained reason) I suggested that you also review with the IS/user
>>>>>> manager team as they are the ones who do the user profile stuff (I think).
>>>>>> Clearly the friend info belongs there and I see that's where you store it
>>>>>> anyway.
>>>>>
>>>>>
>>>>> Ok, will do and give an update.
>>>>>
>>>>>
>>>>>>
>>>>>> OpenSocial has "Smoker" & "Drinker"??? Weird stuff!
>>>>>>
>>>>>
>>>>> Yeah, there are many more similar stuff...
>>>>>
>>>>>
>>>>> Thanks,
>>>>> Umashanthi
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> Sanjiva.
>>>>>>
>>>>>>
>>>>>> On Thu, May 13, 2010 at 1:48 PM, Umashanthi Pavalanathan <
>>>>>> umashanthi at wso2.com> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, May 13, 2010 at 1:06 PM, Umashanthi Pavalanathan <
>>>>>>> umashanthi at wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> Updated doc [1]. Added how the Shindig's data model can be mapped in
>>>>>>>> the registry.
>>>>>>>>
>>>>>>>> I forgot.. my earlier mail didn't get delivered yesterday..
>>>>>>>
>>>>>>> I had a discussion with Sumedha and he asked me to come up with this
>>>>>>> kind of mapping before start implementing (to get a clear idea...)
>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Umashanthi
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> Your suggestions please ...
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Umashanthi
>>>>>>>>
>>>>>>>> [1]
>>>>>>>> https://docs.google.com/a/wso2.com/Doc?docid=0AYn-LXhoFlx2ZGZybnp4dDdfNmd6Zmh0Mzli&hl=en
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, May 12, 2010 at 9:07 AM, Umashanthi Pavalanathan <
>>>>>>>> umashanthi at wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> Any comments on the doc [1]?
>>>>>>>>>
>>>>>>>>> I am planning to start the implementation. What about creating a
>>>>>>>>> new package under org.wso2.carbon.registry.core, called social (New package
>>>>>>>>> will be org.wso2.carbon.registry.core.social)?
>>>>>>>>>
>>>>>>>>> Please share your suggestions on both the doc and the package name.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Umashanthi
>>>>>>>>>
>>>>>>>>> [1]
>>>>>>>>> https://docs.google.com/a/wso2.com/Doc?docid=0AYn-LXhoFlx2ZGZybnp4dDdfNmd6Zmh0Mzli&hl=en
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, May 11, 2010 at 2:22 PM, Paul Fremantle <paul at wso2.com>wrote:
>>>>>>>>>
>>>>>>>>>> So I definitely agree with your analysis of where things sit:
>>>>>>>>>> * We need one component (back-end) that provides the services and
>>>>>>>>>> it relies on the registry core. It can be shipped with the registry and it
>>>>>>>>>> doesn't require the GS or front-end components.
>>>>>>>>>> * We need another component (front-end) that relies on the GS and
>>>>>>>>>> provides the gadget consumers of the OpenSocial API.
>>>>>>>>>>
>>>>>>>>>> I'm definitely +1 on melding these ideas with the registry
>>>>>>>>>> core..... we've talked for a long time about how our Registry is social -
>>>>>>>>>> this would significantly enhance that story. I think it also fits well into
>>>>>>>>>> our private cloud story. Imagine inviting your "friends" to help out with
>>>>>>>>>> your ESB config or your process flow!
>>>>>>>>>>
>>>>>>>>>> Paul
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 10 May 2010 12:15:16 UTC+1, Sanjiva Weerawarana <
>>>>>>>>>> sanjiva at wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> We're getting there! :-)
>>>>>>>>>>>
>>>>>>>>>>> So IMO we need to burn these models into the registry core ...
>>>>>>>>>>> which of course the registry team will love ;-). That is, we need to change
>>>>>>>>>>> the definition of Activity to be the more general form, or if that's not
>>>>>>>>>>> possible, introduce something like OpenSocialPerson, OpenSocialName etc..
>>>>>>>>>>> IMO that's ugly and its better if we can marry these concepts into the
>>>>>>>>>>> registry core.
>>>>>>>>>>>
>>>>>>>>>>> I'd love to hear what Sumedha, Paul, Dimuthu, Prabath and others
>>>>>>>>>>> too think about this! Its a very dangerous idea to execute based on my input
>>>>>>>>>>> only.
>>>>>>>>>>>
>>>>>>>>>>> Sanjiva.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, May 10, 2010 at 3:55 PM, Umashanthi Pavalanathan <
>>>>>>>>>>> umashanthi at wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> I have the some concerns regarding this new design:
>>>>>>>>>>>>
>>>>>>>>>>>> (1)
>>>>>>>>>>>> Shindig provides some OpenSocial models (eg: Person, Name,
>>>>>>>>>>>> Activity, Message... ) [1]
>>>>>>>>>>>>
>>>>>>>>>>>>  So, where can we have this models implemented : at the Registry
>>>>>>>>>>>> level or a particular product level?
>>>>>>>>>>>>
>>>>>>>>>>>> (2)
>>>>>>>>>>>> Currently registry has the 'Activity' concept which is related
>>>>>>>>>>>> to registry resources. But in the case of OpenSoical, activities have a
>>>>>>>>>>>> different scope. [2]
>>>>>>>>>>>>  eg: If Social App, Facebook activities.
>>>>>>>>>>>>        If an Enterprise app: say for eg : a project team reaches
>>>>>>>>>>>> a milestone or releases a product
>>>>>>>>>>>>
>>>>>>>>>>>> So, the existing 'Activity' concept in the GReg is not enough to
>>>>>>>>>>>> handle the whole OpenSocial Activities concept.
>>>>>>>>>>>> We have to think about an implementation for this.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Please give your thoughts on this...
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Umashanthi
>>>>>>>>>>>>
>>>>>>>>>>>> [1]
>>>>>>>>>>>> http://svn.apache.org/repos/asf/shindig/trunk/java/social-api/src/main/java/org/apache/shindig/social/opensocial/model/
>>>>>>>>>>>> [2]
>>>>>>>>>>>> http://wiki.opensocial.org/index.php?title=Opensocial.Activity_(v0.9)<http://wiki.opensocial.org/index.php?title=Opensocial.Activity_%28v0.9%29>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, May 10, 2010 at 3:06 PM, Umashanthi Pavalanathan <
>>>>>>>>>>>> umashanthi at wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>> The attached diagram shows the architecture design of what we
>>>>>>>>>>>>> have come up with after discussing about having OpenSoical at the platform
>>>>>>>>>>>>> level.
>>>>>>>>>>>>>
>>>>>>>>>>>>> The Plan:
>>>>>>>>>>>>> - Write an API in the registry to handle necessary storage and
>>>>>>>>>>>>> retrieval of OpenSocial data (eg: getPeople(), getActivities(),
>>>>>>>>>>>>> updatePersonData()..etc).
>>>>>>>>>>>>> - How the resources will be stored is shown in the diagram (
>>>>>>>>>>>>> resource paths)
>>>>>>>>>>>>> - Using Shindig's interfaces handle requests from GadgetServer
>>>>>>>>>>>>> - Write necessary REST or SOAP interfaces to handle calls from
>>>>>>>>>>>>> other applications.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Please give your suggestions on this.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> Umashanthi
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, May 10, 2010 at 11:27 AM, Sanjiva Weerawarana <
>>>>>>>>>>>>> sanjiva at wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, May 10, 2010 at 11:42 AM, Tyrell Perera <
>>>>>>>>>>>>>> tyrell at wso2.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I understood open social service offering was the plan :) And
>>>>>>>>>>>>>>> we can certainly move the data persistence/retrieval code into IS (which
>>>>>>>>>>>>>>> will eventually talk to the registry).
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> OK. Well its not just IS tho as the activity stuff is in the
>>>>>>>>>>>>>> registry and not IS. IS is only for user profiles, even friend relationships
>>>>>>>>>>>>>> will likely be stored in the registry. TBD.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> But, to expose/offer these services we have to either use
>>>>>>>>>>>>>>> Shindig's servlets or write a set of servlets ourselves. That's why I said
>>>>>>>>>>>>>>> that we have to either add Shindig to IS or write those services ourselves.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The problem (for me at least) is that Shindig is more about
>>>>>>>>>>>>>> gadget rendering than open social services. Even if we use take a dependency
>>>>>>>>>>>>>> on Shindig, those servlets would need to be changed to talk to G-Reg/IS to
>>>>>>>>>>>>>> get the underlying information. As such it makes more sense to me to copy
>>>>>>>>>>>>>> the servlets for the REST service side of it and hack the backend up. (I
>>>>>>>>>>>>>> can't imagine they are written with an "open social data provider" concept
>>>>>>>>>>>>>> already - if so then its easier to integrate of course.)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Shall we have a meeting on this?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Only if we need to :-).
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Sanjiva.
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>>>>> Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
>>>>>>>>>>>>>> email: sanjiva at wso2.com; phone: +1 408 754 7388 x51726; cell:
>>>>>>>>>>>>>> +94 77 787 6880 | +1 650 265 8311
>>>>>>>>>>>>>> blog: http://sanjiva.weerawarana.org/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Lean . Enterprise . Middleware
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>> Architecture mailing list
>>>>>>>>>>>>>> Architecture at wso2.org
>>>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> Architecture mailing list
>>>>>>>>>>>> Architecture at wso2.org
>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>> Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
>>>>>>>>>>> email: sanjiva at wso2.com; phone: +1 408 754 7388 x51726; cell:
>>>>>>>>>>> +94 77 787 6880 | +1 650 265 8311
>>>>>>>>>>> blog: http://sanjiva.weerawarana.org/
>>>>>>>>>>>
>>>>>>>>>>> Lean . Enterprise . Middleware
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> Architecture mailing list
>>>>>>>>>>> Architecture at wso2.org
>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Paul Fremantle
>>>>>>>>>> CTO and Co-Founder, WSO2
>>>>>>>>>> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>>>>>>>>>>
>>>>>>>>>> Office: +44 844 484 8143
>>>>>>>>>> Cell: +44 798 447 4618
>>>>>>>>>>
>>>>>>>>>> blog: http://pzf.fremantle.org
>>>>>>>>>> twitter.com/pzfreo
>>>>>>>>>> paul at wso2.com
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> wso2.com Lean Enterprise Middleware
>>>>>>>>>>
>>>>>>>>>> Disclaimer: This communication may contain privileged or other
>>>>>>>>>> confidential information and is intended exclusively for the addressee/s. If
>>>>>>>>>> you are not the intended recipient/s, or believe that you may have received
>>>>>>>>>> this communication in error, please reply to the sender indicating that fact
>>>>>>>>>> and delete the copy you received and in addition, you should not print,
>>>>>>>>>> copy, retransmit, disseminate, or otherwise use the information contained in
>>>>>>>>>> this communication. Internet communications cannot be guaranteed to be
>>>>>>>>>> timely, secure, error or virus-free. The sender does not accept liability
>>>>>>>>>> for any errors or omissions.
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Architecture mailing list
>>>>>>>>>> Architecture at wso2.org
>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Architecture mailing list
>>>>>>> Architecture at wso2.org
>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Sanjiva Weerawarana, Ph.D.
>>>>>> Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
>>>>>> email: sanjiva at wso2.com; phone: +1 408 754 7388 x51726; cell: +94 77
>>>>>> 787 6880 | +1 650 265 8311
>>>>>> blog: http://sanjiva.weerawarana.org/
>>>>>>
>>>>>> Lean . Enterprise . Middleware
>>>>>>
>>>>>> _______________________________________________
>>>>>> Architecture mailing list
>>>>>> Architecture at wso2.org
>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Architecture mailing list
>>>>> Architecture at wso2.org
>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Architecture mailing list
>>>> Architecture at wso2.org
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>>
>>>
>>>
>>> --
>>> Sanjiva Weerawarana, Ph.D.
>>> Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
>>> email: sanjiva at wso2.com; phone: +1 408 754 7388 x51726; cell: +94 77 787
>>> 6880 | +1 650 265 8311
>>> blog: http://sanjiva.weerawarana.org/
>>>
>>> Lean . Enterprise . Middleware
>>>
>>> _______________________________________________
>>> Architecture mailing list
>>> Architecture at wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Tyrell Perera
>> Technical Lead and Product Manager - WSO2 Mashup Server, WSO2 Gadget
>> Server
>>
>> WSO2, Inc.; http://www.wso2.com/
>> "Lean Enterprise Middleware"
>>
>> http://www.linkedin.com/in/tyrell
>> http://tyrellperera.blogspot.com
>> http://twitter.com/tyrellperera
>>
>>
>> _______________________________________________
>> Architecture mailing list
>> Architecture at wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
> _______________________________________________
> Architecture mailing list
> Architecture at wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>

-- 
Tyrell Perera
Technical Lead and Product Manager - WSO2 Mashup Server, WSO2 Gadget Server

WSO2, Inc.; http://www.wso2.com/
"Lean Enterprise Middleware"

http://www.linkedin.com/in/tyrell
http://tyrellperera.blogspot.com
http://twitter.com/tyrellperera
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.wso2.org/pipermail/architecture/attachments/20100514/80247be4/attachment.html>