<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>IKANGAI Solutions e.U. &#187; IKANGAI Blog</title>
	<atom:link href="http://www.ikangai.com/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ikangai.com</link>
	<description>Idea Factory For Mobile Design.</description>
	<lastBuildDate>Tue, 15 May 2012 11:39:30 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Building Interfaces for Human Provided Services</title>
		<link>http://www.ikangai.com/science/building-interfaces-for-human-provided-services/</link>
		<comments>http://www.ikangai.com/science/building-interfaces-for-human-provided-services/#comments</comments>
		<pubDate>Tue, 15 May 2012 10:36:26 +0000</pubDate>
		<dc:creator>Martin</dc:creator>
				<category><![CDATA[PhD]]></category>
		<category><![CDATA[Science]]></category>
		<category><![CDATA[GUI Considerations]]></category>
		<category><![CDATA[Tweetflows]]></category>
		<category><![CDATA[Twitter for Team Collaboration]]></category>

		<guid isPermaLink="false">http://www.ikangai.com/?p=2314</guid>
		<description><![CDATA[As discussed earlier, our concept of a Human Assisted Service Environment (HASE) encompasses the handling of the interaction between the human and the software on mobile devices. Mobile devices impose a set of constraints that need to be taken into account, like connectivity, screen size of the device, input capabilities or user interface limitations. For example, a SOAP messages like: &#160; &#60;?xml version=&#8221;1.0&#8243;?&#62; &#60;soap:Envelope xmlns:soap=&#8221;http://www.w3.org/2001/12/soap-envelope&#8221; soap:encodingStyle=&#8221;http://www.w3.org/2001/12/soap-encoding&#8221;&#62; &#60;soap:Body xmlns:m=&#8221;http://www.example.org/stock&#8221;&#62; &#60;m:GetStockPrice&#62; &#60;m:StockName&#62;IBM&#60;/m:StockName&#62; &#60;/m:GetStockPrice&#62; &#60;/soap:Body&#62; &#60;/soap:Envelope&#62; must be transformed (e.g., with XSLT) to remove the meta information, before presenting it to the human. Thus, the handling of SOAP requests requires the implementation of [...]]]></description>
		<wfw:commentRss>http://www.ikangai.com/science/building-interfaces-for-human-provided-services/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Motivating an Idea in a Scientific Paper</title>
		<link>http://www.ikangai.com/science/motivating-an-idea-in-a-scientific-paper/</link>
		<comments>http://www.ikangai.com/science/motivating-an-idea-in-a-scientific-paper/#comments</comments>
		<pubDate>Mon, 14 May 2012 07:15:42 +0000</pubDate>
		<dc:creator>Martin</dc:creator>
				<category><![CDATA[PhD]]></category>
		<category><![CDATA[Science]]></category>
		<category><![CDATA[Public Paper Writing]]></category>
		<category><![CDATA[Social Tuple Space]]></category>
		<category><![CDATA[Twitter for Team Collaboration]]></category>
		<category><![CDATA[Working Example]]></category>

		<guid isPermaLink="false">http://www.ikangai.com/?p=2303</guid>
		<description><![CDATA[When writing a paper, authors often struggle with the application of their ideas in real life. It is often the case that an idea is interesting, but fails to convince others because of the lack of immediate applicability or a difficulty to provide real world data. This problem is faced by many authors; for example, in 1989 when Tim Berners Lee proposed an information system that later became the WWW, there was no proof that this could work. So, in order to convince others, authors invent application scenarios that illustrate the application of their idea in a &#8220;realistic&#8221; setting. However, [...]]]></description>
		<wfw:commentRss>http://www.ikangai.com/science/motivating-an-idea-in-a-scientific-paper/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Installing a Twitter Testbed</title>
		<link>http://www.ikangai.com/science/installing-a-twitter-testbed/</link>
		<comments>http://www.ikangai.com/science/installing-a-twitter-testbed/#comments</comments>
		<pubDate>Fri, 11 May 2012 06:00:19 +0000</pubDate>
		<dc:creator>Martin</dc:creator>
				<category><![CDATA[PhD]]></category>
		<category><![CDATA[Science]]></category>
		<category><![CDATA[Installation]]></category>
		<category><![CDATA[Testbed]]></category>
		<category><![CDATA[Twitter for Team Collaboration]]></category>

		<guid isPermaLink="false">http://www.ikangai.com/?p=2300</guid>
		<description><![CDATA[Installing an open source Twitter Server (Status.net) can turn out to be a very time consuming task. It took me four days and dozens of &#8220;trial and error&#8221; to find the proper configuration for Status.net on our Server. One of the main problems was my lack of experience with being a Server admin: I&#8217;m a computer scientist, but I&#8217;ve never really administrated a Server. So I&#8217;m not used to cryptic error messages like &#8220;DB:Error&#8221; that frequently occurred during the installation of the current stable version of Status.net. One of the things that I tried, was to install the previous version [...]]]></description>
		<wfw:commentRss>http://www.ikangai.com/science/installing-a-twitter-testbed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Integrating People with Tweetflows</title>
		<link>http://www.ikangai.com/science/integrating-people-with-tweetflows/</link>
		<comments>http://www.ikangai.com/science/integrating-people-with-tweetflows/#comments</comments>
		<pubDate>Wed, 02 May 2012 06:43:04 +0000</pubDate>
		<dc:creator>Martin</dc:creator>
				<category><![CDATA[PhD]]></category>
		<category><![CDATA[Science]]></category>

		<guid isPermaLink="false">http://www.ikangai.com/?p=2284</guid>
		<description><![CDATA[One comment of the reviewers of the SOCA paper made us think about a very basic issue when invoking human provided services. The issue concerns the communication means that is used to communicate with the human behind the service interface. In particular, we noted that efforts are directed towards the software side of the service: it was considered important to provide a service (interface) that is software compatible. Examples for this approach include WS Human Task or Human Provided Services (HPS) which allow the integration of humans into existing (BPEL) workflows. This leads to a conceptual architecture of three layers: [...]]]></description>
		<wfw:commentRss>http://www.ikangai.com/science/integrating-people-with-tweetflows/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tweetflow Syntax Considerations</title>
		<link>http://www.ikangai.com/phd/tweetflow-syntax-considerations/</link>
		<comments>http://www.ikangai.com/phd/tweetflow-syntax-considerations/#comments</comments>
		<pubDate>Mon, 23 Apr 2012 08:40:13 +0000</pubDate>
		<dc:creator>Martin</dc:creator>
				<category><![CDATA[PhD]]></category>
		<category><![CDATA[Amazon Mechanical Turk]]></category>
		<category><![CDATA[Tweetflows]]></category>
		<category><![CDATA[Twitter for Team Collaboration]]></category>

		<guid isPermaLink="false">http://www.ikangai.com/?p=2277</guid>
		<description><![CDATA[After our Amamzon Mechanical Turk experiment, we took a closer look at the data. As discussed earlier, turkers had some troubles understanding the meaning of Tweetflows, due to the lack of an explanation. Omitting a detailed description was a deliberate choice: we wanted to know, if turkers were able to create Tweetflows with a minimal set of examples. We did not explain that Tweetflows are designed to be machine-readable and we did not discuss the structure of Tweetflow commands which can be separated into four distinct parts: prefix &#8211; defining the type of command (e.g., service request, service provision) command [...]]]></description>
		<wfw:commentRss>http://www.ikangai.com/phd/tweetflow-syntax-considerations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>First Results of Amazon Mechanical Turk Task</title>
		<link>http://www.ikangai.com/phd/first-results-of-amazon-mechanical-turk-task/</link>
		<comments>http://www.ikangai.com/phd/first-results-of-amazon-mechanical-turk-task/#comments</comments>
		<pubDate>Fri, 20 Apr 2012 07:26:17 +0000</pubDate>
		<dc:creator>Martin</dc:creator>
				<category><![CDATA[PhD]]></category>
		<category><![CDATA[Amazon Mechanical Turk]]></category>
		<category><![CDATA[Tweetflows]]></category>
		<category><![CDATA[Twitter for Team Collaboration]]></category>

		<guid isPermaLink="false">http://www.ikangai.com/?p=2267</guid>
		<description><![CDATA[Our Tweetflow experiment is completed: we&#8217;ve received results from all 40 turkers. At a first look, it seems that Tweetflows are indeed human readable &#8211; all workers completed their tasks and the resulting Tweetflows look good. However, some of the comments are very interesting, especially if we consider the setting in which the Tweetflows were translated into natural language. We only provided a small set of examples, so the turkers had a starting point, but we offered no further explanations. 24 out of 40 turkers had problems with the task, and we received comments like these: you get a general [...]]]></description>
		<wfw:commentRss>http://www.ikangai.com/phd/first-results-of-amazon-mechanical-turk-task/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

