<?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: 3 Reasons Apple&#8217;s New iPhone Promotes Better Markup</title>
	<atom:link href="http://www.agencybyte.com/2007/01/09/3-reasons-apples-new-iphone-promotes-better-markup/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.agencybyte.com/2007/01/09/3-reasons-apples-new-iphone-promotes-better-markup/</link>
	<description>Technology for creatives</description>
	<lastBuildDate>Sun, 17 Jan 2010 01:07:59 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Brett Derricott</title>
		<link>http://www.agencybyte.com/2007/01/09/3-reasons-apples-new-iphone-promotes-better-markup/comment-page-1/#comment-905</link>
		<dc:creator>Brett Derricott</dc:creator>
		<pubDate>Sat, 20 Jan 2007 21:17:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.agencybyte.com/2007/01/09/3-reasons-apples-new-iphone-promotes-better-markup/#comment-905</guid>
		<description>@Kris: I sure hope that doesn&#039;t happen...the last thing we need is a situation where we double the number of hacks we already have to use to work on multiple devices.

@Bill: Yes, with Safari on the iPhone you&#039;d think it&#039;d be possible to eliminate the requirement for a handheld-specific stylesheet. I can still see a desire for a separate stylesheet in some cases just to tailor the content to the smaller viewport.

@Michael: Very true, my friend. I did oversimplify a bit there! With semantic markup controlling the structure and CSS controlling the presentation, designers/developers can tailor the same content for different devices as you&#039;ve pointed out. Thanks.</description>
		<content:encoded><![CDATA[<p>@Kris: I sure hope that doesn&#8217;t happen&#8230;the last thing we need is a situation where we double the number of hacks we already have to use to work on multiple devices.</p>
<p>@Bill: Yes, with Safari on the iPhone you&#8217;d think it&#8217;d be possible to eliminate the requirement for a handheld-specific stylesheet. I can still see a desire for a separate stylesheet in some cases just to tailor the content to the smaller viewport.</p>
<p>@Michael: Very true, my friend. I did oversimplify a bit there! With semantic markup controlling the structure and CSS controlling the presentation, designers/developers can tailor the same content for different devices as you&#8217;ve pointed out. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Mulvey</title>
		<link>http://www.agencybyte.com/2007/01/09/3-reasons-apples-new-iphone-promotes-better-markup/comment-page-1/#comment-764</link>
		<dc:creator>Michael Mulvey</dc:creator>
		<pubDate>Fri, 12 Jan 2007 21:56:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.agencybyte.com/2007/01/09/3-reasons-apples-new-iphone-promotes-better-markup/#comment-764</guid>
		<description>Regarding your comment:

&quot;That means everyone will be making phones capable of a more robust handheld browsing experience, further increasing the desire of web designers and developers (and their clients) to make websites that look good on all devices.&quot;

You can&#039;t make a site that will look good on all devices. You can structure your HTML and CSS so that pages render well or adapt well, but if you&#039;ve ever visited Yahoo! or Google on a Treo, for example, you&#039;ll know that they feed a different version of their site to those devices.   

Again, it just goes back to the idea of separating structural markup from content.

... hopefully this is what you meant. In which case I agree.</description>
		<content:encoded><![CDATA[<p>Regarding your comment:</p>
<p>&#8220;That means everyone will be making phones capable of a more robust handheld browsing experience, further increasing the desire of web designers and developers (and their clients) to make websites that look good on all devices.&#8221;</p>
<p>You can&#8217;t make a site that will look good on all devices. You can structure your HTML and CSS so that pages render well or adapt well, but if you&#8217;ve ever visited Yahoo! or Google on a Treo, for example, you&#8217;ll know that they feed a different version of their site to those devices.   </p>
<p>Again, it just goes back to the idea of separating structural markup from content.</p>
<p>&#8230; hopefully this is what you meant. In which case I agree.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jbelkin</title>
		<link>http://www.agencybyte.com/2007/01/09/3-reasons-apples-new-iphone-promotes-better-markup/comment-page-1/#comment-716</link>
		<dc:creator>jbelkin</dc:creator>
		<pubDate>Thu, 11 Jan 2007 00:13:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.agencybyte.com/2007/01/09/3-reasons-apples-new-iphone-promotes-better-markup/#comment-716</guid>
		<description>find a place where the phone &quot;roams&quot; - make lots of calls, they will drop you :-)</description>
		<content:encoded><![CDATA[<p>find a place where the phone &#8220;roams&#8221; &#8211; make lots of calls, they will drop you <img src='http://www.agencybyte.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BIll W.</title>
		<link>http://www.agencybyte.com/2007/01/09/3-reasons-apples-new-iphone-promotes-better-markup/comment-page-1/#comment-705</link>
		<dc:creator>BIll W.</dc:creator>
		<pubDate>Wed, 10 Jan 2007 17:11:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.agencybyte.com/2007/01/09/3-reasons-apples-new-iphone-promotes-better-markup/#comment-705</guid>
		<description>I agree with everything you&#039;ve said, but doesn&#039;t the fact that the iPhone uses a fully functioning Safari browser sort of imply that media=&quot;handheld&quot; stylesheets aren&#039;t really necessary if other devices begin to implement real browsers into their devices?</description>
		<content:encoded><![CDATA[<p>I agree with everything you&#8217;ve said, but doesn&#8217;t the fact that the iPhone uses a fully functioning Safari browser sort of imply that media=&#8221;handheld&#8221; stylesheets aren&#8217;t really necessary if other devices begin to implement real browsers into their devices?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J-One</title>
		<link>http://www.agencybyte.com/2007/01/09/3-reasons-apples-new-iphone-promotes-better-markup/comment-page-1/#comment-704</link>
		<dc:creator>J-One</dc:creator>
		<pubDate>Wed, 10 Jan 2007 15:29:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.agencybyte.com/2007/01/09/3-reasons-apples-new-iphone-promotes-better-markup/#comment-704</guid>
		<description>Nokia phones allready come with opera9 browser which is also full featured. Its also aviable for Windows Mobile.</description>
		<content:encoded><![CDATA[<p>Nokia phones allready come with opera9 browser which is also full featured. Its also aviable for Windows Mobile.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kris Gosser</title>
		<link>http://www.agencybyte.com/2007/01/09/3-reasons-apples-new-iphone-promotes-better-markup/comment-page-1/#comment-684</link>
		<dc:creator>Kris Gosser</dc:creator>
		<pubDate>Wed, 10 Jan 2007 05:32:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.agencybyte.com/2007/01/09/3-reasons-apples-new-iphone-promotes-better-markup/#comment-684</guid>
		<description>Or, the knock-off competitor products will end up producing their own browsers (and not using Opera, Safari, Mobile FireFox, etc) which will throw yet MORE types of hacks needed to be used.

That&#039;s what I think will happen, and it saddens me.</description>
		<content:encoded><![CDATA[<p>Or, the knock-off competitor products will end up producing their own browsers (and not using Opera, Safari, Mobile FireFox, etc) which will throw yet MORE types of hacks needed to be used.</p>
<p>That&#8217;s what I think will happen, and it saddens me.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
