<?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: Mobile Sitemap</title>
	<atom:link href="http://www.thisismobility.com/blog/2007/02/17/mobile-sitemap/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thisismobility.com/blog/2007/02/17/mobile-sitemap/</link>
	<description>Ripping mobility from the clutches of telecom</description>
	<pubDate>Fri, 09 Jan 2009 02:29:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Sean Owen</title>
		<link>http://www.thisismobility.com/blog/2007/02/17/mobile-sitemap/#comment-82004</link>
		<dc:creator>Sean Owen</dc:creator>
		<pubDate>Sun, 18 Feb 2007 07:49:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.thisismobility.com/blog/?p=287#comment-82004</guid>
		<description>I agree that getting the mobile web to show itself to a crawl is not necessarily easy. I'll point out that we (Google) send an Accept header which asks for mobile Internet media types too. While that's the right way to do it, it doesn't work everywhere. We also have to use yet another UA to get some cHTML content; many sites look for something like a "DoCoMo" UA.

(PS for the mobile webmasters, if you're going to write rules based on UA, do make sure you send your mobile content when you see "Googlebot-Mobile"!)

Even sites that are trying to look at Accept headers properly have trouble since text/html is the official type for both desktop-oriented HTML markup and cHTML.

I think this highlights how confused the whole MIME / Internet media type system has always been -- some document types have multiple media types (XHTML anyone?), some media types map to multiple document types (e.g. text/html for HTML, cHTML) -- but, that's another story.</description>
		<content:encoded><![CDATA[<p>I agree that getting the mobile web to show itself to a crawl is not necessarily easy. I&#8217;ll point out that we (Google) send an Accept header which asks for mobile Internet media types too. While that&#8217;s the right way to do it, it doesn&#8217;t work everywhere. We also have to use yet another UA to get some cHTML content; many sites look for something like a &#8220;DoCoMo&#8221; UA.</p>
<p>(PS for the mobile webmasters, if you&#8217;re going to write rules based on UA, do make sure you send your mobile content when you see &#8220;Googlebot-Mobile&#8221;!)</p>
<p>Even sites that are trying to look at Accept headers properly have trouble since text/html is the official type for both desktop-oriented HTML markup and cHTML.</p>
<p>I think this highlights how confused the whole MIME / Internet media type system has always been &#8212; some document types have multiple media types (XHTML anyone?), some media types map to multiple document types (e.g. text/html for HTML, cHTML) &#8212; but, that&#8217;s another story.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
