<?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: Planet Mobile Web</title>
	<atom:link href="http://www.thisismobility.com/blog/2006/11/11/planet-mobile-web/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thisismobility.com/blog/2006/11/11/planet-mobile-web/</link>
	<description>Ripping mobility from the clutches of telecom</description>
	<pubDate>Tue, 16 Mar 2010 08:18:27 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Barnabas Kendall</title>
		<link>http://www.thisismobility.com/blog/2006/11/11/planet-mobile-web/comment-page-1/#comment-41503</link>
		<dc:creator>Barnabas Kendall</dc:creator>
		<pubDate>Wed, 22 Nov 2006 20:09:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.thisismobility.com/blog/?p=228#comment-41503</guid>
		<description>Hearty agreement on that last sentence. I think that making Skweezer's output validate at least 95% is an important goal. Mr. Passani's GAP is a fine effort on the mobile standards front as well, and I've been doing a lot of thinking and experimenting with the delta between the W3CBP and GAP.

Skweezer has for several years included stars at the bottom of web pages to indicate pre-processed mobile-readiness. In light of standards and validators like these however, a more standard/meaningful score is called for.

Excellent blog, Mike. Subscribed.

Barnabas Kendall, CTO
Greenlight Wireless</description>
		<content:encoded><![CDATA[<p>Hearty agreement on that last sentence. I think that making Skweezer&#8217;s output validate at least 95% is an important goal. Mr. Passani&#8217;s GAP is a fine effort on the mobile standards front as well, and I&#8217;ve been doing a lot of thinking and experimenting with the delta between the W3CBP and GAP.</p>
<p>Skweezer has for several years included stars at the bottom of web pages to indicate pre-processed mobile-readiness. In light of standards and validators like these however, a more standard/meaningful score is called for.</p>
<p>Excellent blog, Mike. Subscribed.</p>
<p>Barnabas Kendall, CTO<br />
Greenlight Wireless</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luca Passani</title>
		<link>http://www.thisismobility.com/blog/2006/11/11/planet-mobile-web/comment-page-1/#comment-40228</link>
		<dc:creator>Luca Passani</dc:creator>
		<pubDate>Thu, 16 Nov 2006 23:07:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.thisismobility.com/blog/?p=228#comment-40228</guid>
		<description>you may read what the creator of WALL (who is also a member of the W3C BPWG group) thinks of BP here:

http://www.passani.it/gap/intro.htm

WALL predates BP by two years. Anyway, I would say that WALL and BP are independent things: you can use WALL to create BP and non-BP sites alike.

Luca</description>
		<content:encoded><![CDATA[<p>you may read what the creator of WALL (who is also a member of the W3C BPWG group) thinks of BP here:</p>
<p><a href="http://www.passani.it/gap/intro.htm" rel="nofollow">http://www.passani.it/gap/intro.htm</a></p>
<p>WALL predates BP by two years. Anyway, I would say that WALL and BP are independent things: you can use WALL to create BP and non-BP sites alike.</p>
<p>Luca</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Prashanth</title>
		<link>http://www.thisismobility.com/blog/2006/11/11/planet-mobile-web/comment-page-1/#comment-39264</link>
		<dc:creator>Prashanth</dc:creator>
		<pubDate>Mon, 13 Nov 2006 06:25:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.thisismobility.com/blog/?p=228#comment-39264</guid>
		<description>mTLD has released their much awaited mobiReady report. http://mr.dev.mobi/

It tests the website for mobile readiness. The generated test report is very comprehensive. The tool is still in its Beta but  think its the best available test tool at this point of time.

Prashanth</description>
		<content:encoded><![CDATA[<p>mTLD has released their much awaited mobiReady report. <a href="http://mr.dev.mobi/" rel="nofollow">http://mr.dev.mobi/</a></p>
<p>It tests the website for mobile readiness. The generated test report is very comprehensive. The tool is still in its Beta but  think its the best available test tool at this point of time.</p>
<p>Prashanth</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Cranstone</title>
		<link>http://www.thisismobility.com/blog/2006/11/11/planet-mobile-web/comment-page-1/#comment-39245</link>
		<dc:creator>Peter Cranstone</dc:creator>
		<pubDate>Mon, 13 Nov 2006 03:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.thisismobility.com/blog/?p=228#comment-39245</guid>
		<description>Mike,

Well done for finding this link (the W3 tester site)! I just ran it on CNN - 1105 errors. 

Here's a thought for you on a solution to web site problem. What if the web servers themselves knew exactly what the terminal capabilities of the target device was? For instance - what if you could know in real time the current page size (320*240) screen resolution 144dpi, and number of colors 65,000, plus the connection speed. With that kind of information you have the web server generate a dynamic page which conformed exactly to the devices specs.

I think the real problem is figuring out the devices capabilities - until you can do that accurately, everything else is just a guess.

Thanks again for the link, definitely going in the bookmarks.

Peter</description>
		<content:encoded><![CDATA[<p>Mike,</p>
<p>Well done for finding this link (the W3 tester site)! I just ran it on CNN - 1105 errors. </p>
<p>Here&#8217;s a thought for you on a solution to web site problem. What if the web servers themselves knew exactly what the terminal capabilities of the target device was? For instance - what if you could know in real time the current page size (320*240) screen resolution 144dpi, and number of colors 65,000, plus the connection speed. With that kind of information you have the web server generate a dynamic page which conformed exactly to the devices specs.</p>
<p>I think the real problem is figuring out the devices capabilities - until you can do that accurately, everything else is just a guess.</p>
<p>Thanks again for the link, definitely going in the bookmarks.</p>
<p>Peter</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Micah Dubinko</title>
		<link>http://www.thisismobility.com/blog/2006/11/11/planet-mobile-web/comment-page-1/#comment-39242</link>
		<dc:creator>Micah Dubinko</dc:creator>
		<pubDate>Mon, 13 Nov 2006 03:36:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.thisismobility.com/blog/?p=228#comment-39242</guid>
		<description>The W3C Mobile Web Best Practices are particularly guilty of this--they are even referred to as "forward-looking best practices". Does anyone else find that a self-contradiction and just a little bit scary for a "Proposed Recommendation"? -m</description>
		<content:encoded><![CDATA[<p>The W3C Mobile Web Best Practices are particularly guilty of this&#8211;they are even referred to as &#8220;forward-looking best practices&#8221;. Does anyone else find that a self-contradiction and just a little bit scary for a &#8220;Proposed Recommendation&#8221;? -m</p>
]]></content:encoded>
	</item>
</channel>
</rss>
