<?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: Joe Wilcox on HDTV and Microsoft DRM in Longhorn</title>
	<atom:link href="http://thomashawk.com/2005/07/joe-wilcox-on-hdtv-and-microsoft-drm.html/feed" rel="self" type="application/rss+xml" />
	<link>http://thomashawk.com/2005/07/joe-wilcox-on-hdtv-and-microsoft-drm.html</link>
	<description></description>
	<lastBuildDate>Fri, 25 May 2012 21:17:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Stephen Speicher</title>
		<link>http://thomashawk.com/2005/07/joe-wilcox-on-hdtv-and-microsoft-drm.html/comment-page-1#comment-19553</link>
		<dc:creator>Stephen Speicher</dc:creator>
		<pubDate>Mon, 18 Jul 2005 13:28:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/thomashawk/?p=3521#comment-19553</guid>
		<description>Interesting.... you could have just as easily said, &quot;For those of you waiting for HDTV MCE -- this is the technology that should allow Microsoft to convince CableLabs that their boxes are secure enough for CableCARDS.&quot;&lt;br /&gt;&lt;br /&gt;Everyone wants to assume that Microsoft is the 800lb guerilla.  However, I think that that&#039;s a simplistic view of it all.  When it comes to the cable industry, Microsoft is the weakling that gets sand kicked its eyes.&lt;br /&gt;&lt;br /&gt;Microsoft is trying to expand (and thus justify its numbers) further in to the CE and media market.  In order to do so, they must play nice with the content providers and (for the meantime) content distributors.&lt;br /&gt;&lt;br /&gt;While not the popular view, it’s fair to say that Microsoft will be using this technology to give you a choice.  It’s not like devices will be free of these restrictions.&lt;br /&gt;&lt;br /&gt;In any case, you can easily look at this news (and these technologies) as the cornerstone *for* HDTV MCE.&lt;br /&gt;&lt;br /&gt;It’s funny – I wrote the article (the Engadget one not the MicrosoftWatch one) to let people know about the technology and to make people aware that it should be part of their monitor buying decision process.  Very few people have said, “Wait HDCP is WELL established.  Why are the monitor companies pushing VERY high-end products without this?  Isn’t that a bit irresponsible?”  Oh well…</description>
		<content:encoded><![CDATA[<p>Interesting&#8230;. you could have just as easily said, &#8220;For those of you waiting for HDTV MCE &#8212; this is the technology that should allow Microsoft to convince CableLabs that their boxes are secure enough for CableCARDS.&#8221;</p>
<p>Everyone wants to assume that Microsoft is the 800lb guerilla.  However, I think that that&#8217;s a simplistic view of it all.  When it comes to the cable industry, Microsoft is the weakling that gets sand kicked its eyes.</p>
<p>Microsoft is trying to expand (and thus justify its numbers) further in to the CE and media market.  In order to do so, they must play nice with the content providers and (for the meantime) content distributors.</p>
<p>While not the popular view, it’s fair to say that Microsoft will be using this technology to give you a choice.  It’s not like devices will be free of these restrictions.</p>
<p>In any case, you can easily look at this news (and these technologies) as the cornerstone *for* HDTV MCE.</p>
<p>It’s funny – I wrote the article (the Engadget one not the MicrosoftWatch one) to let people know about the technology and to make people aware that it should be part of their monitor buying decision process.  Very few people have said, “Wait HDCP is WELL established.  Why are the monitor companies pushing VERY high-end products without this?  Isn’t that a bit irresponsible?”  Oh well…</p>
]]></content:encoded>
	</item>
</channel>
</rss>

