<?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/"
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Patents, Microsoft, and the Future</title>
	<atom:link href="http://lewisshepherd.wordpress.com/2008/01/28/patents-microsoft-and-the-future/feed/" rel="self" type="application/rss+xml" />
	<link>http://lewisshepherd.wordpress.com/2008/01/28/patents-microsoft-and-the-future/</link>
	<description>A fuzzy technologist carves up facts &#38; figures</description>
	<lastBuildDate>Wed, 04 Nov 2009 08:01:33 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Required Reading on Innovation and Patents &#171; Shepherd&#8217;s Pi</title>
		<link>http://lewisshepherd.wordpress.com/2008/01/28/patents-microsoft-and-the-future/#comment-224</link>
		<dc:creator>Required Reading on Innovation and Patents &#171; Shepherd&#8217;s Pi</dc:creator>
		<pubDate>Tue, 20 May 2008 07:40:33 +0000</pubDate>
		<guid isPermaLink="false">http://lewisshepherd.wordpress.com/?p=103#comment-224</guid>
		<description>[...] fascinate me - reading them, counting them (as I watch others do each year), thinking about their implications.  They serve fundamentally as markers of the reach of [...]</description>
		<content:encoded><![CDATA[<p>[...] fascinate me &#8211; reading them, counting them (as I watch others do each year), thinking about their implications.  They serve fundamentally as markers of the reach of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Media Says, IBM is Good for Government. Ah, Strike That&#8230;. &#171; Shepherd&#8217;s Pi</title>
		<link>http://lewisshepherd.wordpress.com/2008/01/28/patents-microsoft-and-the-future/#comment-165</link>
		<dc:creator>Media Says, IBM is Good for Government. Ah, Strike That&#8230;. &#171; Shepherd&#8217;s Pi</dc:creator>
		<pubDate>Mon, 31 Mar 2008 21:40:05 +0000</pubDate>
		<guid isPermaLink="false">http://lewisshepherd.wordpress.com/?p=103#comment-165</guid>
		<description>[...] get me wrong: I like IBM, it&#8217;s a solid company with great technologies and great people. I&#8217;ve written before about my admiration for their research, labs, and focus on [...]</description>
		<content:encoded><![CDATA[<p>[...] get me wrong: I like IBM, it&#8217;s a solid company with great technologies and great people. I&#8217;ve written before about my admiration for their research, labs, and focus on [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Manny</title>
		<link>http://lewisshepherd.wordpress.com/2008/01/28/patents-microsoft-and-the-future/#comment-63</link>
		<dc:creator>Manny</dc:creator>
		<pubDate>Wed, 30 Jan 2008 07:58:20 +0000</pubDate>
		<guid isPermaLink="false">http://lewisshepherd.wordpress.com/?p=103#comment-63</guid>
		<description>Thye open source definition is here:
http://en.wikipedia.org/wiki/Open_Source_Definition

There are 10 requirements. Does the API in question meet these? If not, the it is NOT open source.

   1. Free Redistribution: the software can be freely given away or sold. (This was intended to expand sharing and use of the software on a legal basis.)
   2. Source Code: the source code must either be included or freely obtainable. (Without source code, making changes or modifications can be impossible.)
   3. Derived Works: redistribution of modifications must be allowed. (To allow legal sharing and to permit new features or repairs.)
   4. Integrity of The Author&#039;s Source Code: licenses may require that modifications are redistributed only as patches.
   5. No Discrimination Against Persons or Groups: no one can be locked out.
   6. No Discrimination Against Fields of Endeavor: commercial users cannot be excluded.
   7. Distribution of License: The rights attached to the program must apply to all to whom the program is redistributed without the need for execution of an additional license by those parties.
   8. License Must Not Be Specific to a Product: the program cannot be licensed only as part of a larger distribution.
   9. License Must Not Restrict Other Software: the license cannot insist that any other software it is distributed with must also be open source.
  10. License Must Be Technology-Neutral: no click-wrap licenses or other medium-specific ways of accepting the license must be required.</description>
		<content:encoded><![CDATA[<p>Thye open source definition is here:<br />
<a href="http://en.wikipedia.org/wiki/Open_Source_Definition" rel="nofollow">http://en.wikipedia.org/wiki/Open_Source_Definition</a></p>
<p>There are 10 requirements. Does the API in question meet these? If not, the it is NOT open source.</p>
<p>   1. Free Redistribution: the software can be freely given away or sold. (This was intended to expand sharing and use of the software on a legal basis.)<br />
   2. Source Code: the source code must either be included or freely obtainable. (Without source code, making changes or modifications can be impossible.)<br />
   3. Derived Works: redistribution of modifications must be allowed. (To allow legal sharing and to permit new features or repairs.)<br />
   4. Integrity of The Author&#8217;s Source Code: licenses may require that modifications are redistributed only as patches.<br />
   5. No Discrimination Against Persons or Groups: no one can be locked out.<br />
   6. No Discrimination Against Fields of Endeavor: commercial users cannot be excluded.<br />
   7. Distribution of License: The rights attached to the program must apply to all to whom the program is redistributed without the need for execution of an additional license by those parties.<br />
   8. License Must Not Be Specific to a Product: the program cannot be licensed only as part of a larger distribution.<br />
   9. License Must Not Restrict Other Software: the license cannot insist that any other software it is distributed with must also be open source.<br />
  10. License Must Be Technology-Neutral: no click-wrap licenses or other medium-specific ways of accepting the license must be required.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Boycott Novell &#187; Novell and Microsoft Amass Patents While Free Software Comes Under Fire</title>
		<link>http://lewisshepherd.wordpress.com/2008/01/28/patents-microsoft-and-the-future/#comment-62</link>
		<dc:creator>Boycott Novell &#187; Novell and Microsoft Amass Patents While Free Software Comes Under Fire</dc:creator>
		<pubDate>Wed, 30 Jan 2008 06:47:42 +0000</pubDate>
		<guid isPermaLink="false">http://lewisshepherd.wordpress.com/?p=103#comment-62</guid>
		<description>[...] like Novell, likes patents. But its loveraffair with patents has been reaching some worrisome peaks recently and it&#8217;s not hard to see why.  Fact: According to the latest annual report on patents [...]</description>
		<content:encoded><![CDATA[<p>[...] like Novell, likes patents. But its loveraffair with patents has been reaching some worrisome peaks recently and it&#8217;s not hard to see why.  Fact: According to the latest annual report on patents [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lewisshepherd</title>
		<link>http://lewisshepherd.wordpress.com/2008/01/28/patents-microsoft-and-the-future/#comment-57</link>
		<dc:creator>lewisshepherd</dc:creator>
		<pubDate>Mon, 28 Jan 2008 13:44:00 +0000</pubDate>
		<guid isPermaLink="false">http://lewisshepherd.wordpress.com/?p=103#comment-57</guid>
		<description>Not to be contrary, but au contraire. I know that for a lot of people, anything from MS is by definition proprietary and closed, but in this case that&#039;s not true. I did point out that this is an open source API, and I even put &quot;open source&quot; in quotes to highlight the API-ness. The API (not other MS apps themselves, but the API) is &quot;open source,&quot; in the very same sense that the Google Maps API is open source, leading to such breathless commentary as ZDNet&#039;s &quot;Google Maps API transforms the Web...We are getting a great demonstration right now of open source power, as applications using the Google Maps API begin to appear... It’s Google, using the open source process, that has blown the field apart. The code has only been out a few weeks but already we’re seeing several really great applications...Individuals were ready and able to use the API right away, and trust the results in ways even the BBC was reluctant to try. And remember, this is just the start. I guarantee that hundreds of programmers are now poring over the Google Map API documentation, thinking about applications that will drive both them, and Google, to new heights. All on the wings of open source.&quot;  (http://blogs.zdnet.com/open-source/?p=374)

All that about an API!

Now the Google Maps app itself - not the API - is not open source; it is proprietary, as everyone knows, and that&#039;s fine.  In fact, Google itself points out to the GMaps developer community that &quot;You are permitted to use Google Maps on an Intranet, or in a desktop application only if you buy Google Maps for Enterprise. Prices start at $10,000 per year and it is only available in a few countries.&quot;  (http://mapki.com/wiki/FAQs#Permissions)

Anyway, as Norm Hodne, the MS Windows accessibility lead says in the article I linked to in the post, &quot;We decided to donate the API we developed to make it open source and allow the AIA to take and port it to any platform they wanted to, Windows, Linux or Mac, to get consistency and accessibility&quot; (and pointed out that MS is already leveraging its alliance with Novell to get the UI Automation Spec over to the Linux platform).  He says, &quot;We think it&#039;s important this technology gets out there and companies don&#039;t see assistive technology as a competitive thing they have to control or do better than another company.&quot; To me, that&#039;s a refreshing attitude, and fits not only the spirit but the letter of the definition of &quot;open source.&quot; (http://en.wikipedia.org/wiki/Open_source)</description>
		<content:encoded><![CDATA[<p>Not to be contrary, but au contraire. I know that for a lot of people, anything from MS is by definition proprietary and closed, but in this case that&#8217;s not true. I did point out that this is an open source API, and I even put &#8220;open source&#8221; in quotes to highlight the API-ness. The API (not other MS apps themselves, but the API) is &#8220;open source,&#8221; in the very same sense that the Google Maps API is open source, leading to such breathless commentary as ZDNet&#8217;s &#8220;Google Maps API transforms the Web&#8230;We are getting a great demonstration right now of open source power, as applications using the Google Maps API begin to appear&#8230; It’s Google, using the open source process, that has blown the field apart. The code has only been out a few weeks but already we’re seeing several really great applications&#8230;Individuals were ready and able to use the API right away, and trust the results in ways even the BBC was reluctant to try. And remember, this is just the start. I guarantee that hundreds of programmers are now poring over the Google Map API documentation, thinking about applications that will drive both them, and Google, to new heights. All on the wings of open source.&#8221;  (<a href="http://blogs.zdnet.com/open-source/?p=374" rel="nofollow">http://blogs.zdnet.com/open-source/?p=374</a>)</p>
<p>All that about an API!</p>
<p>Now the Google Maps app itself &#8211; not the API &#8211; is not open source; it is proprietary, as everyone knows, and that&#8217;s fine.  In fact, Google itself points out to the GMaps developer community that &#8220;You are permitted to use Google Maps on an Intranet, or in a desktop application only if you buy Google Maps for Enterprise. Prices start at $10,000 per year and it is only available in a few countries.&#8221;  (<a href="http://mapki.com/wiki/FAQs#Permissions" rel="nofollow">http://mapki.com/wiki/FAQs#Permissions</a>)</p>
<p>Anyway, as Norm Hodne, the MS Windows accessibility lead says in the article I linked to in the post, &#8220;We decided to donate the API we developed to make it open source and allow the AIA to take and port it to any platform they wanted to, Windows, Linux or Mac, to get consistency and accessibility&#8221; (and pointed out that MS is already leveraging its alliance with Novell to get the UI Automation Spec over to the Linux platform).  He says, &#8220;We think it&#8217;s important this technology gets out there and companies don&#8217;t see assistive technology as a competitive thing they have to control or do better than another company.&#8221; To me, that&#8217;s a refreshing attitude, and fits not only the spirit but the letter of the definition of &#8220;open source.&#8221; (<a href="http://en.wikipedia.org/wiki/Open_source" rel="nofollow">http://en.wikipedia.org/wiki/Open_source</a>)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Manny</title>
		<link>http://lewisshepherd.wordpress.com/2008/01/28/patents-microsoft-and-the-future/#comment-56</link>
		<dc:creator>Manny</dc:creator>
		<pubDate>Mon, 28 Jan 2008 08:57:58 +0000</pubDate>
		<guid isPermaLink="false">http://lewisshepherd.wordpress.com/?p=103#comment-56</guid>
		<description>&quot;Yes - that’s Microsoft, making its API “open source” and allowing the AIA to port it to any platform (Windows, Linux, Mac), to promote accessibility.&quot;

That&#039;s NOT open source. It&#039;s just a royalty-free license  for a specific purpose. Open source means you open up the code and allow its use to create derivative software for any purpose. That&#039;s a BIG difference.</description>
		<content:encoded><![CDATA[<p>&#8220;Yes &#8211; that’s Microsoft, making its API “open source” and allowing the AIA to port it to any platform (Windows, Linux, Mac), to promote accessibility.&#8221;</p>
<p>That&#8217;s NOT open source. It&#8217;s just a royalty-free license  for a specific purpose. Open source means you open up the code and allow its use to create derivative software for any purpose. That&#8217;s a BIG difference.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
