SAC Paper – Application Scenario Thoughts

We discussed the application scenario in more detail and Martin pointed out that both, the creation and the execution of a Tweetflow happens in a mobile environment. Thus, a Tweetflow is created and executed in a mobile context. This gave Daniel and me the idea, to enrich the workflow during the design time with context data. In our case, this would be sensor data like pictures taken with the camera, location information, movement data or gestures. In doing so, we implicitly contextualize the creation of the Tweetflow. This has the very interesting consequence that we weave context information into the design phase of Tweetflows. For example, one could think of a Tweetflow that is created to solve an immediate problem like having insufficient power on a festival location (we discussed this in a previous post). Without having to specify the required context information a priori, we can enrich a Tweetflow (consisting of several (human) activities like connecting diesel generators to stages) with geo-location data and images from the actual location. The geo-location can help organizing the transport and images can be used to inform about peculiarities of the location (e.g., a narrow gate that prevents bigger trucks from entering the festival location or a people crowd gathered around a stage).
The inclusion of context in the design of a Tweetflow hinders its universal application. But, since ad hoc Tweetflows are not designed to be generic solutions in the first place, this should not pose a problem. Furthermore, the issue of context integration is actually a technical one, because we need to address how to “put” context data into the Tweetflow language and how to access it during the execution of the Tweetflow.

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>