<?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: Who owns &quot;open&quot;?</title>
	<atom:link href="http://redmonk.com/cote/2007/03/08/who-owns-open/feed/" rel="self" type="application/rss+xml" />
	<link>http://redmonk.com/cote/2007/03/08/who-owns-open/</link>
	<description>One foot in the muck, the other in utopia</description>
	<lastBuildDate>Tue, 29 May 2012 14:02:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=4.1</generator>
	<item>
		<title>By: Scott Mark</title>
		<link>http://redmonk.com/cote/2007/03/08/who-owns-open/#comment-1155</link>
		<dc:creator><![CDATA[Scott Mark]]></dc:creator>
		<pubDate>Fri, 09 Mar 2007 12:30:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/03/08/who-owns-open/#comment-1155</guid>
		<description><![CDATA[I think vendors need to be cautious about using &quot;open&quot;, exactly because there is not a common understanding of the term.  If they use it, they should be prepared to go the distance.

Vendors have been providing SPIs and pluggable architectures for a long time and that was always called &quot;published&quot; not &quot;open&quot;. ]]></description>
		<content:encoded><![CDATA[<p>I think vendors need to be cautious about using &quot;open&quot;, exactly because there is not a common understanding of the term.  If they use it, they should be prepared to go the distance.</p>
<p>Vendors have been providing SPIs and pluggable architectures for a long time and that was always called &quot;published&quot; not &quot;open&quot;. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://redmonk.com/cote/2007/03/08/who-owns-open/#comment-1154</link>
		<dc:creator><![CDATA[James]]></dc:creator>
		<pubDate>Fri, 09 Mar 2007 05:37:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/03/08/who-owns-open/#comment-1154</guid>
		<description><![CDATA[I am fine with vendors using the word open if it refers to the savage creation of industry standards or community participation by also providing source code with zero restrictions. Other than that, I think my expectations are that analysts will call vendors out so that customers don&#039;t get it twisted... ]]></description>
		<content:encoded><![CDATA[<p>I am fine with vendors using the word open if it refers to the savage creation of industry standards or community participation by also providing source code with zero restrictions. Other than that, I think my expectations are that analysts will call vendors out so that customers don&#039;t get it twisted&#8230; </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Governor</title>
		<link>http://redmonk.com/cote/2007/03/08/who-owns-open/#comment-1153</link>
		<dc:creator><![CDATA[James Governor]]></dc:creator>
		<pubDate>Fri, 09 Mar 2007 05:04:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/03/08/who-owns-open/#comment-1153</guid>
		<description><![CDATA[I am with Mark and Ed on this one. Conflating open and open source isn&#039;t entirely helpful. Stephen has done enough great definitional work around &quot;open standard&quot; and &quot;open format&quot; for us to be happy to use that term in the right context. As long as their is an open specification being met, ideally stewarded by a third party- a vendor can use the term open. ]]></description>
		<content:encoded><![CDATA[<p>I am with Mark and Ed on this one. Conflating open and open source isn&#039;t entirely helpful. Stephen has done enough great definitional work around &quot;open standard&quot; and &quot;open format&quot; for us to be happy to use that term in the right context. As long as their is an open specification being met, ideally stewarded by a third party- a vendor can use the term open. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ewH</title>
		<link>http://redmonk.com/cote/2007/03/08/who-owns-open/#comment-1152</link>
		<dc:creator><![CDATA[ewH]]></dc:creator>
		<pubDate>Thu, 08 Mar 2007 13:50:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/03/08/who-owns-open/#comment-1152</guid>
		<description><![CDATA[I agree with Mark on this one; it depends on what context the term is being applied.  As long as they don&#039;t claim open SOURCE, then they should be able to use the word to explain the areas which they are indeed open.
Cheers,
-ewH ]]></description>
		<content:encoded><![CDATA[<p>I agree with Mark on this one; it depends on what context the term is being applied.  As long as they don&#039;t claim open SOURCE, then they should be able to use the word to explain the areas which they are indeed open.<br />
Cheers,<br />
-ewH </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Wahl</title>
		<link>http://redmonk.com/cote/2007/03/08/who-owns-open/#comment-1151</link>
		<dc:creator><![CDATA[Mark Wahl]]></dc:creator>
		<pubDate>Thu, 08 Mar 2007 12:46:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/03/08/who-owns-open/#comment-1151</guid>
		<description><![CDATA[Vendors should be &quot;free&quot; to use the word &quot;open&quot; to describe aspects of their product besides the source code, so long as they define their terms and the implications are clear.  I see nothing wrong with an open platform, open APIs, open systems, open standards, open change control processes, for closed-source, restricted-source or both-closed-and-open-source products: these terms are valuable and AFAIK there is no good alternative term. ]]></description>
		<content:encoded><![CDATA[<p>Vendors should be &quot;free&quot; to use the word &quot;open&quot; to describe aspects of their product besides the source code, so long as they define their terms and the implications are clear.  I see nothing wrong with an open platform, open APIs, open systems, open standards, open change control processes, for closed-source, restricted-source or both-closed-and-open-source products: these terms are valuable and AFAIK there is no good alternative term. </p>
]]></content:encoded>
	</item>
</channel>
</rss>
