SAC Paper Ingredients

One of the problems with our current SAC paper is its positioning. We already discussed this in our last post and now we are going to elaborate on this topic by investigating some of the key “ingredients” of our proposed approach. We have four main ingredients that we wish to discuss:

Ingredient Number One:Social network. People are connected and know each other. What is that good for? Does it help us? If so, how? Can we use data like user profiles for our purpose?

Ingredient Number Two: Mobile Devices. Being permanently online appears to be the future. We are connected to the Web all the time. This can only be done with mobile devices, because we always have them with us. What is the impact of this for our work? One consequence is that we can build workflows anytime/anyplace, if we have the means to do so. This is the argument for needing a mobile workflow editor (which we fortunately already have:-))

Ingredient Number Three: Mobile Services. Mobile devices equals mobile Services. But how do Services “look” like? They aren’t SOAP Services, that is for sure. Are they Restful Services? Or can we think of a different abstraction to use? Again, we have an answer for this. In our previous work, we introduced the concept of App as a Service which can be employed to make use of Apps. However, Apps are self-contained, and do not come with public interfaces that can be addressed. Thus, we require a programming model that is able to plug into the social network directly from the App. Actually, this has been done to some extent by social platforms like Facebook/Twitter; they provide an API that allows to write “social” Applications that work on their platform.

Ingredient Number Four: Tweetflows. If we have mobile Services, we need to compose/orchestrate them in the context of the social network. How do we do this? This is related to the question of integrating Apps into social networks. In contrast to existing approaches which provide no communication means between different social Apps, we will investigate this aspect in extensive detail.

your ikangai science Team

, , ,
  • Delicious
  • Facebook
  • Digg
  • Reddit
  • StumbleUpon
  • Twitter

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>