<?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: Interview with Per Andersen, Managing Director IDC Nordic &amp; Benelux</title>
	<atom:link href="http://www.talkstandards.com/interview-with-per-andersen-managing-director-idc-nordic-benelux/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.talkstandards.com/interview-with-per-andersen-managing-director-idc-nordic-benelux/</link>
	<description></description>
	<lastBuildDate>Tue, 18 Oct 2011 15:30:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Gramstad</title>
		<link>http://www.talkstandards.com/interview-with-per-andersen-managing-director-idc-nordic-benelux/comment-page-1/#comment-1913</link>
		<dc:creator>Gramstad</dc:creator>
		<pubDate>Fri, 04 Jun 2010 14:33:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.talkstandards.com/?p=3366#comment-1913</guid>
		<description>Ken and Per,
So nice to find you both at the same page and discussing our assessment of openness :)

I must admit that the question on online identification, negotiations and selection of capabilities was the most challenging one ;)

However looking at the answers, I suppose it all boils down to awareness. In an interconnected world it is almost impossible to avoid this kind of adaptability.

Ad. &quot;dictating the rules&quot; I suppose that was never among at least my objectives. To learn more about the good intentions, feel free to visit us at http://webtools.ec.europa.eu/wikis/idabc-camss/index.php/Main_Page

All the best
/Per-Olav</description>
		<content:encoded><![CDATA[<p>Ken and Per,<br />
So nice to find you both at the same page and discussing our assessment of openness :)</p>
<p>I must admit that the question on online identification, negotiations and selection of capabilities was the most challenging one ;)</p>
<p>However looking at the answers, I suppose it all boils down to awareness. In an interconnected world it is almost impossible to avoid this kind of adaptability.</p>
<p>Ad. &#8220;dictating the rules&#8221; I suppose that was never among at least my objectives. To learn more about the good intentions, feel free to visit us at <a href="http://webtools.ec.europa.eu/wikis/idabc-camss/index.php/Main_Page" rel="nofollow">http://webtools.ec.europa.eu/wikis/idabc-camss/index.php/Main_Page</a></p>
<p>All the best<br />
/Per-Olav</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: krechmer</title>
		<link>http://www.talkstandards.com/interview-with-per-andersen-managing-director-idc-nordic-benelux/comment-page-1/#comment-408</link>
		<dc:creator>krechmer</dc:creator>
		<pubDate>Mon, 01 Feb 2010 21:57:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.talkstandards.com/?p=3366#comment-408</guid>
		<description>I recognize that possible monetary gain makes intellectual property the most active topic about openness.  However the most &quot;important&quot; of the 10 criteria of open standards is (IMHO) adaptability.  Adaptability makes possible an on-line intellectual property negotiation (which has the ability to resolve the intellectual property issues) as well as addressing technical problems (maintaining backward compatibility) and rev level negotiation.</description>
		<content:encoded><![CDATA[<p>I recognize that possible monetary gain makes intellectual property the most active topic about openness.  However the most &#8220;important&#8221; of the 10 criteria of open standards is (IMHO) adaptability.  Adaptability makes possible an on-line intellectual property negotiation (which has the ability to resolve the intellectual property issues) as well as addressing technical problems (maintaining backward compatibility) and rev level negotiation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

