<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Open Standards: Do Open Standards&#8217; implementations meet their specifications?</title>
	<link>http://robertogaloppini.net/2008/04/04/open-standards-do-open-standards-implementations-meet-their-specifications/</link>
	<description>Where Free Software meets Businessequally critical of proprietary and open source myths,advocating software choice beyondmarketing and romanticism</description>
	<pubDate>Fri, 04 Jul 2008 20:29:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Roberto Galoppini</title>
		<link>http://robertogaloppini.net/2008/04/04/open-standards-do-open-standards-implementations-meet-their-specifications/#comment-445594</link>
		<dc:creator>Roberto Galoppini</dc:creator>
		<pubDate>Mon, 16 Jun 2008 14:13:23 +0000</pubDate>
		<guid>http://robertogaloppini.net/2008/04/04/open-standards-do-open-standards-implementations-meet-their-specifications/#comment-445594</guid>
		<description>Hi Ken,

 I am glad to disseminate your message on open standards, is really important to let people know that standardization is a process, not a product. 

I always &lt;a href="http://robertogaloppini.net/2008/04/07/open-standards-standards-organizations-how-open-are-them-an-evaluation-methodology/" rel="nofollow"&gt;mention "open interface"&lt;/a&gt; in &lt;a href="http://robertogaloppini.net/2008/05/10/open-standards-conference-bob-sutor-at-the-ibm-conference-on-open-standards/" rel="nofollow"&gt;my speeches&lt;/a&gt;, explaining the importance of it. I also mention that "open interface" should go along with "open change", in order to avoid &lt;a href="http://perens.com/OpenStandards/Definition.html" rel="nofollow"&gt;predatory practices&lt;/a&gt;. I will try to cover these topics more extensively in the next future, thanks for your hint!</description>
		<content:encoded><![CDATA[<p>Hi Ken,</p>
<p> I am glad to disseminate your message on open standards, is really important to let people know that standardization is a process, not a product. </p>
<p>I always <a href="http://robertogaloppini.net/2008/04/07/open-standards-standards-organizations-how-open-are-them-an-evaluation-methodology/" rel="nofollow">mention &#8220;open interface&#8221;</a> in <a href="http://robertogaloppini.net/2008/05/10/open-standards-conference-bob-sutor-at-the-ibm-conference-on-open-standards/" rel="nofollow">my speeches</a>, explaining the importance of it. I also mention that &#8220;open interface&#8221; should go along with &#8220;open change&#8221;, in order to avoid <a href="http://perens.com/OpenStandards/Definition.html" rel="nofollow">predatory practices</a>. I will try to cover these topics more extensively in the next future, thanks for your hint!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Krechmer</title>
		<link>http://robertogaloppini.net/2008/04/04/open-standards-do-open-standards-implementations-meet-their-specifications/#comment-444879</link>
		<dc:creator>Ken Krechmer</dc:creator>
		<pubDate>Mon, 16 Jun 2008 03:25:46 +0000</pubDate>
		<guid>http://robertogaloppini.net/2008/04/04/open-standards-do-open-standards-implementations-meet-their-specifications/#comment-444879</guid>
		<description>Thank you for your very kind comments on my work. I think your suggestions about the need for specific aspects of openness are excellent. One aspect you did not mention, I think should be emphasized - open interface.  This is the most difficult aspect to understand, but perhaps the most useful today as it offers a means to support both public and proprietary features in a standard.  This provides a way around most of the intellectual property issues that bedevil standardization today.  The paper The Entrepreneur and Standards http://www.csrstds.com/IECChallenge2006.pdf given an introduction to this aspect and the paper The Fundamental Nature of Standards (http://www.csrstds.com/fundtec.html) under etiquettes gives a more technical description.</description>
		<content:encoded><![CDATA[<p>Thank you for your very kind comments on my work. I think your suggestions about the need for specific aspects of openness are excellent. One aspect you did not mention, I think should be emphasized - open interface.  This is the most difficult aspect to understand, but perhaps the most useful today as it offers a means to support both public and proprietary features in a standard.  This provides a way around most of the intellectual property issues that bedevil standardization today.  The paper The Entrepreneur and Standards <a href="http://www.csrstds.com/IECChallenge2006.pdf" rel="nofollow">http://www.csrstds.com/IECChallenge2006.pdf</a> given an introduction to this aspect and the paper The Fundamental Nature of Standards (http://www.csrstds.com/fundtec.html) under etiquettes gives a more technical description.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
