Hi,
Using OpenSocial in your context is like opening a place in a shopping
mall rather then on the street.
The customers (users) are already there, but you still need to make
them enter your shop (install & use your new Gadget)
Use case1:
I can't see any way in Opensocial for the Gadget to "know" if a user
is part of "Mountain View Network" .
You can still do many things based on the "Person" object
http://opensocial-resources.googlecode.com/svn/spec/1.0/Social-Data.xml#Person
Use case 2:
Seems ok to me.
In both cases the challenge is to make user install your Gadget....
On Mar 26, 4:31 am, Elangovan Shanmugam
<
elangovan.shanmu...@gmail.com> wrote:
> Thanks Yuvi. I am thinking loud here. Here are some thoughts. Think about
> "social commerce".
>
> Use case 1:
> - Mr. John (Person/Cosnumer) lives in Mountain View, CA. By social, he could
> be part of "Mountain View Network" and "Bay Area Network".
> - All plumbing companies (Businesses) that run business in "Bay area" are
> part of the above mentioned networks.
> - Mr. John has to do some plumbing work in his house. Now he could either
> publish that "he is looking for plumbing quote".
> - Plumbing companies can subscribe to such messages and respond to Mr.
> John.
>
> *To generalize the above use case, "Plumbing" - may be replaced with any
> business. *