<?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: Presentational HTML &#8211; Semantically Useful or Wastefully Deprecated?</title>
	<atom:link href="http://nathanchase.com/2008/05/presentational-html-semantically-useful-or-wastefully-deprecated/feed/" rel="self" type="application/rss+xml" />
	<link>http://nathanchase.com/2008/05/presentational-html-semantically-useful-or-wastefully-deprecated/</link>
	<description>The portfolio, resume, and blog of Nathan Chase</description>
	<lastBuildDate>Fri, 20 May 2011 12:04:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Marcin</title>
		<link>http://nathanchase.com/2008/05/presentational-html-semantically-useful-or-wastefully-deprecated/comment-page-1/#comment-318</link>
		<dc:creator>Marcin</dc:creator>
		<pubDate>Tue, 15 Jul 2008 14:08:19 +0000</pubDate>
		<guid isPermaLink="false">http://nathanchase.com/?p=232#comment-318</guid>
		<description>nice portfolio - many good looking webs.. gratulations</description>
		<content:encoded><![CDATA[<p>nice portfolio &#8211; many good looking webs.. gratulations</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Travis Turner</title>
		<link>http://nathanchase.com/2008/05/presentational-html-semantically-useful-or-wastefully-deprecated/comment-page-1/#comment-314</link>
		<dc:creator>Travis Turner</dc:creator>
		<pubDate>Tue, 27 May 2008 14:50:08 +0000</pubDate>
		<guid isPermaLink="false">http://nathanchase.com/?p=232#comment-314</guid>
		<description>I have to admit, I&#039;ve almost completely abandoned inline styles except when quickly mashing something together, or for initial look and feel before I go back and move everything into a stylesheet.

I suppose, from an accessibility standpoint, this is probably frowned upon because it hinders a screen-reader&#039;s ability to place emphasis on certain parts of the text or what have you.  But to be completely honest, most of my styling seems to be for the presentation layer and NOT for semantics.</description>
		<content:encoded><![CDATA[<p>I have to admit, I&#8217;ve almost completely abandoned inline styles except when quickly mashing something together, or for initial look and feel before I go back and move everything into a stylesheet.</p>
<p>I suppose, from an accessibility standpoint, this is probably frowned upon because it hinders a screen-reader&#8217;s ability to place emphasis on certain parts of the text or what have you.  But to be completely honest, most of my styling seems to be for the presentation layer and NOT for semantics.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Coyier</title>
		<link>http://nathanchase.com/2008/05/presentational-html-semantically-useful-or-wastefully-deprecated/comment-page-1/#comment-313</link>
		<dc:creator>Chris Coyier</dc:creator>
		<pubDate>Tue, 27 May 2008 14:08:32 +0000</pubDate>
		<guid isPermaLink="false">http://nathanchase.com/?p=232#comment-313</guid>
		<description>The reasoning behind &lt;em&gt; replacing &lt;i&gt; is semantics. It&#039;s better to tags that generically describe the intent of the enclosed content than what it should look like. Emphasis might look like italic on one site, where on another it could mean 120% font size and bright red. If it&#039;s the latter, the &lt;i&gt; tag no longer makes sense... It&#039;s kind of like how class names like &quot;BigLeft&quot; are bad, since later that same class could be needed to apply a small and right formatting.

That being said... I still find myself using the small tag fairly often. Mostly because it&#039;s another INLINE element that does what it says on the box. Sometimes you need an extra hook within a p tag, and don&#039;t want to use strong or em, and small fits the bill nicely.</description>
		<content:encoded><![CDATA[<p>The reasoning behind &lt;em&gt; replacing &lt;i&gt; is semantics. It&#8217;s better to tags that generically describe the intent of the enclosed content than what it should look like. Emphasis might look like italic on one site, where on another it could mean 120% font size and bright red. If it&#8217;s the latter, the &lt;i&gt; tag no longer makes sense&#8230; It&#8217;s kind of like how class names like &#8220;BigLeft&#8221; are bad, since later that same class could be needed to apply a small and right formatting.</p>
<p>That being said&#8230; I still find myself using the small tag fairly often. Mostly because it&#8217;s another INLINE element that does what it says on the box. Sometimes you need an extra hook within a p tag, and don&#8217;t want to use strong or em, and small fits the bill nicely.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

