<?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: Configuring PR for the Mobile Internet</title>
	<atom:link href="http://www.bernaisesource.com/blog/2009/06/configuring-pr-for-the-mobile-internet/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bernaisesource.com/blog/2009/06/configuring-pr-for-the-mobile-internet/</link>
	<description>The official blog of Bernaise Source Media</description>
	<lastBuildDate>Thu, 04 Mar 2010 16:42:05 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Trusted Filter &#187; Blog Archive &#187; Mobile Meetings Abound</title>
		<link>http://www.bernaisesource.com/blog/2009/06/configuring-pr-for-the-mobile-internet/comment-page-1/#comment-240</link>
		<dc:creator>Trusted Filter &#187; Blog Archive &#187; Mobile Meetings Abound</dc:creator>
		<pubDate>Fri, 12 Jun 2009 03:08:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.bernaisesource.com/blog/?p=1187#comment-240</guid>
		<description>[...] apps through the approval process.  Dan Greenfield put together a little writeup over on his blog Bernaise Source and mentioned me.  Thanks [...]</description>
		<content:encoded><![CDATA[<p>[...] apps through the approval process.  Dan Greenfield put together a little writeup over on his blog Bernaise Source and mentioned me.  Thanks [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Emery</title>
		<link>http://www.bernaisesource.com/blog/2009/06/configuring-pr-for-the-mobile-internet/comment-page-1/#comment-235</link>
		<dc:creator>Mark Emery</dc:creator>
		<pubDate>Tue, 02 Jun 2009 15:27:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.bernaisesource.com/blog/?p=1187#comment-235</guid>
		<description>Also, a great first step for people interested in developing a mobile web presence would be to analyze traffic logs to see who is ALREADY accessing their site(s) on mobile devices. And then start developing for those devices.</description>
		<content:encoded><![CDATA[<p>Also, a great first step for people interested in developing a mobile web presence would be to analyze traffic logs to see who is ALREADY accessing their site(s) on mobile devices. And then start developing for those devices.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Emery</title>
		<link>http://www.bernaisesource.com/blog/2009/06/configuring-pr-for-the-mobile-internet/comment-page-1/#comment-234</link>
		<dc:creator>Mark Emery</dc:creator>
		<pubDate>Tue, 02 Jun 2009 15:25:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.bernaisesource.com/blog/?p=1187#comment-234</guid>
		<description>Great post Dan. 

I wonder about just how necessary it is for brands/marketers/pr people to care about .mobi URLs. Ultimately, most web servers should be able to detect what kind of device is requesting a web page, and serve up the most appropriately rendered content. The onus should be on web providers, not users, to be smart about how they deliver material to people requesting it.

Your larger point, however, is absolutely valid - companies who have a web presence ought to care about how that looks not just on Firefox/IE/Safari, but also on iPhone/RIM/Nokia/etc....</description>
		<content:encoded><![CDATA[<p>Great post Dan. </p>
<p>I wonder about just how necessary it is for brands/marketers/pr people to care about .mobi URLs. Ultimately, most web servers should be able to detect what kind of device is requesting a web page, and serve up the most appropriately rendered content. The onus should be on web providers, not users, to be smart about how they deliver material to people requesting it.</p>
<p>Your larger point, however, is absolutely valid &#8211; companies who have a web presence ought to care about how that looks not just on Firefox/IE/Safari, but also on iPhone/RIM/Nokia/etc&#8230;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
