<?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: Mobile Web Kerfuffle</title>
	<atom:link href="http://www.torgo.com/blog/2006/09/mobile-web-kerfuffle.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.torgo.com/blog/2006/09/mobile-web-kerfuffle.html</link>
	<description>Musings on technology, the Web, mobility and beyond</description>
	<lastBuildDate>Mon, 10 Oct 2011 12:09:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Paul Anthony</title>
		<link>http://www.torgo.com/blog/2006/09/mobile-web-kerfuffle.html/comment-page-1#comment-93</link>
		<dc:creator>Paul Anthony</dc:creator>
		<pubDate>Mon, 18 Sep 2006 19:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://torgo.mobilemonday.org.uk/blog/?p=100#comment-93</guid>
		<description>I am completely for &lt;B&gt;One Web&lt;/B&gt;, there&#039;s just no other way, IMO.

The definition there is: &lt;I&gt;The Internet is the Internet, and sites should run well on all devices. Optimization should be based on CSS and device detection, but should not change site function or content beyond the necessary.&lt;/I&gt;

I couldn&#039;t have said it better myself. Dan, as you pointed out, pinppl exploits the BB browser&#039;s PIN number detection capability. And in terms of device detection, pinppl easily detects the BlackBerry series number, and it uses this to display, and not display information where absolutely necessary. (For instance, the BlackBerry browser cannot handle file uploads, so pinppl will not display this form element.)

The underlying XHTML markup remains unchanged regardless of which Web browser is being used, be it on the BlackBerry, or PC.

This is the beauty of well-structured markup, independent of visual elements - CSS handles that end, and does so wonderfully.

There are few mobile devices now that cannot handle basic XHTML. The reason for this being that users want to use, what they consider the &quot;real&quot; Internet - not mobile specific sites, of which there are very few in comparison.</description>
		<content:encoded><![CDATA[<p>I am completely for <b>One Web</b>, there&#8217;s just no other way, IMO.</p>
<p>The definition there is: <i>The Internet is the Internet, and sites should run well on all devices. Optimization should be based on CSS and device detection, but should not change site function or content beyond the necessary.</i></p>
<p>I couldn&#8217;t have said it better myself. Dan, as you pointed out, pinppl exploits the BB browser&#8217;s PIN number detection capability. And in terms of device detection, pinppl easily detects the BlackBerry series number, and it uses this to display, and not display information where absolutely necessary. (For instance, the BlackBerry browser cannot handle file uploads, so pinppl will not display this form element.)</p>
<p>The underlying XHTML markup remains unchanged regardless of which Web browser is being used, be it on the BlackBerry, or PC.</p>
<p>This is the beauty of well-structured markup, independent of visual elements &#8211; CSS handles that end, and does so wonderfully.</p>
<p>There are few mobile devices now that cannot handle basic XHTML. The reason for this being that users want to use, what they consider the &#8220;real&#8221; Internet &#8211; not mobile specific sites, of which there are very few in comparison.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

