<?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"
	>
<channel>
	<title>Comments on: Q&#038;A: Novarra Responds to Mobile Web Issues</title>
	<atom:link href="http://www.mobilecrunch.com/2007/06/22/qa-novarra-responds-to-mobile-web-issues/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mobilecrunch.com/2007/06/22/qa-novarra-responds-to-mobile-web-issues/</link>
	<description>All About Mobile 2.0</description>
	<pubDate>Tue, 02 Dec 2008 05:23:53 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: angry developer</title>
		<link>http://www.mobilecrunch.com/2007/06/22/qa-novarra-responds-to-mobile-web-issues/#comment-421552</link>
		<dc:creator>angry developer</dc:creator>
		<pubDate>Sat, 20 Sep 2008 23:27:47 +0000</pubDate>
		<guid isPermaLink="false">http://mobilecrunch.com/2007/06/22/qa-novarra-responds-to-mobile-web-issues/#comment-421552</guid>
		<description>look at this and at the reaction the interview triggered:

http://www.mobilemarketingmagazine.co.uk/2008/05/talking-transco.html</description>
		<content:encoded><![CDATA[<p>look at this and at the reaction the interview triggered:</p>
<p><a href="http://www.mobilemarketingmagazine.co.uk/2008/05/talking-transco.html" rel="nofollow">http://www.mobilemarketingmagazine.co.uk/2008/05/talking-transco.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nadir</title>
		<link>http://www.mobilecrunch.com/2007/06/22/qa-novarra-responds-to-mobile-web-issues/#comment-189753</link>
		<dc:creator>Nadir</dc:creator>
		<pubDate>Mon, 25 Jun 2007 10:30:51 +0000</pubDate>
		<guid isPermaLink="false">http://mobilecrunch.com/2007/06/22/qa-novarra-responds-to-mobile-web-issues/#comment-189753</guid>
		<description>I agree with Brad, Novarra should have allowed mobile content providers to disallow the transcoding and explained them how to do so before their solution was launched on Voda, instead of finding workarounds after causing so much troubles.</description>
		<content:encoded><![CDATA[<p>I agree with Brad, Novarra should have allowed mobile content providers to disallow the transcoding and explained them how to do so before their solution was launched on Voda, instead of finding workarounds after causing so much troubles.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad</title>
		<link>http://www.mobilecrunch.com/2007/06/22/qa-novarra-responds-to-mobile-web-issues/#comment-186566</link>
		<dc:creator>Brad</dc:creator>
		<pubDate>Fri, 22 Jun 2007 22:05:09 +0000</pubDate>
		<guid isPermaLink="false">http://mobilecrunch.com/2007/06/22/qa-novarra-responds-to-mobile-web-issues/#comment-186566</guid>
		<description>Coming from a different angle, I understand the concerns of content owners.  Advertisers have very stringent requirements about how their ads are displayed - after all, that's their stock in trade.  Of course when you're dealing with a small screen and a network that makes it very difficult to get lots of content to the device in a reasonable amount of time, scraping and shaping solutions look attractive.  One good approach would be to put the decision in the hands of the content owners - let them decide what gets sent and how it looks on mobile, rather than an abstracted engine that makes the decisions for the content owner.  If you focus on the priority of content (I want this and this to be displayed first, then worry about the rest) rather than the transcoding of it (scrunch it up this way for this phone), or better yet combine the two, you put the content owner in charge of his content rather than the operator.</description>
		<content:encoded><![CDATA[<p>Coming from a different angle, I understand the concerns of content owners.  Advertisers have very stringent requirements about how their ads are displayed - after all, that&#8217;s their stock in trade.  Of course when you&#8217;re dealing with a small screen and a network that makes it very difficult to get lots of content to the device in a reasonable amount of time, scraping and shaping solutions look attractive.  One good approach would be to put the decision in the hands of the content owners - let them decide what gets sent and how it looks on mobile, rather than an abstracted engine that makes the decisions for the content owner.  If you focus on the priority of content (I want this and this to be displayed first, then worry about the rest) rather than the transcoding of it (scrunch it up this way for this phone), or better yet combine the two, you put the content owner in charge of his content rather than the operator.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blah</title>
		<link>http://www.mobilecrunch.com/2007/06/22/qa-novarra-responds-to-mobile-web-issues/#comment-186274</link>
		<dc:creator>Blah</dc:creator>
		<pubDate>Fri, 22 Jun 2007 17:12:05 +0000</pubDate>
		<guid isPermaLink="false">http://mobilecrunch.com/2007/06/22/qa-novarra-responds-to-mobile-web-issues/#comment-186274</guid>
		<description>1.0 launch of the Web? WTF!</description>
		<content:encoded><![CDATA[<p>1.0 launch of the Web? WTF!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
