<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Offerings as Commitments and Context: Service Systems from a Language Action Perspective</title>
	<atom:link href="http://coevolving.com/blogs/index.php/archive/offerings-as-commitments-and-context-service-systems-from-a-language-action-perspective/feed/" rel="self" type="application/rss+xml" />
	<link>http://coevolving.com/blogs/index.php/archive/offerings-as-commitments-and-context-service-systems-from-a-language-action-perspective/</link>
	<description>... in Business Organizations and Information Technologies</description>
	<lastBuildDate>Sat, 12 May 2012 11:24:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Coevolving Innovations &#124; Conversations: for action, for clarification, for possibilities, for orientation</title>
		<link>http://coevolving.com/blogs/index.php/archive/offerings-as-commitments-and-context-service-systems-from-a-language-action-perspective/comment-page-1/#comment-62160</link>
		<dc:creator>Coevolving Innovations &#124; Conversations: for action, for clarification, for possibilities, for orientation</dc:creator>
		<pubDate>Sat, 12 Dec 2009 20:14:09 +0000</pubDate>
		<guid isPermaLink="false">http://coevolving.com/blogs/index.php/archive/offerings-as-commitments-and-context-service-systems-from-a-language-action-perspective/#comment-62160</guid>
		<description>[...] primarily focused on conversations for action, towards a commitment action protocol. I extended, in 2008, those ideas into a research paper to recognize (at least) four types of [...]</description>
		<content:encoded><![CDATA[<p>[...] primarily focused on conversations for action, towards a commitment action protocol. I extended, in 2008, those ideas into a research paper to recognize (at least) four types of [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

