<?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: Apple Patents Multi-touch</title>
	<atom:link href="http://ux.buzzspree.com/apple-patents-multi-touch/feed/" rel="self" type="application/rss+xml" />
	<link>http://ux.buzzspree.com/apple-patents-multi-touch/</link>
	<description>User Experience blog</description>
	<lastBuildDate>Sun, 08 Feb 2009 02:06:41 -0800</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Skip Meetze</title>
		<link>http://ux.buzzspree.com/apple-patents-multi-touch/comment-page-1/#comment-11</link>
		<dc:creator>Skip Meetze</dc:creator>
		<pubDate>Sun, 08 Feb 2009 02:06:41 +0000</pubDate>
		<guid isPermaLink="false">http://ux.buzzspree.com/apple-patents-multi-touch/#comment-11</guid>
		<description>I’m no patent attorney either, but I would bet that the significant value of this patent to Apple is not in the offensive potential of the 20 claims in preventing others from making and selling products similar to the iPhone. To successfully challenge an imitator, Apple will have to defend these claims as new and not obvious in view of the work of Han and others.  

Whether Apple’s claims are valid (or are in fact in the public domain) may only be relevant if Apple chooses to seek remuneration from makers and sellers of iPhone imitators, and Apple may back down if rivals challenge the validity of their patent claims.  

However, the details of the patent’s 358 pages probably go a long way toward providing Apple with a legally defensive “right to use” all the features of the iPhone.  Without the comprehensive disclosure in this unusually lengthy patent specification, Apple might be more vulnerable to litigation in nuisance infringement suits based some competitor’s invalid patent claims.</description>
		<content:encoded><![CDATA[<p>I’m no patent attorney either, but I would bet that the significant value of this patent to Apple is not in the offensive potential of the 20 claims in preventing others from making and selling products similar to the iPhone. To successfully challenge an imitator, Apple will have to defend these claims as new and not obvious in view of the work of Han and others.  </p>
<p>Whether Apple’s claims are valid (or are in fact in the public domain) may only be relevant if Apple chooses to seek remuneration from makers and sellers of iPhone imitators, and Apple may back down if rivals challenge the validity of their patent claims.  </p>
<p>However, the details of the patent’s 358 pages probably go a long way toward providing Apple with a legally defensive “right to use” all the features of the iPhone.  Without the comprehensive disclosure in this unusually lengthy patent specification, Apple might be more vulnerable to litigation in nuisance infringement suits based some competitor’s invalid patent claims.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Bamford</title>
		<link>http://ux.buzzspree.com/apple-patents-multi-touch/comment-page-1/#comment-10</link>
		<dc:creator>David Bamford</dc:creator>
		<pubDate>Wed, 28 Jan 2009 13:55:55 +0000</pubDate>
		<guid isPermaLink="false">http://ux.buzzspree.com/apple-patents-multi-touch/#comment-10</guid>
		<description>Those of us at NYU in 2005 and even a bit earlier remember Jeff&#039;s work with multi-touch even before TED.

It&#039;s never who invents but the person or entity who develops and captures the majority of popular public opinion.</description>
		<content:encoded><![CDATA[<p>Those of us at NYU in 2005 and even a bit earlier remember Jeff&#8217;s work with multi-touch even before TED.</p>
<p>It&#8217;s never who invents but the person or entity who develops and captures the majority of popular public opinion.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
