<?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: Semantic HTML 5? Pfft.</title>
	<atom:link href="http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/feed/" rel="self" type="application/rss+xml" />
	<link>http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/</link>
	<description>Adventures in web and graphic design</description>
	<lastBuildDate>Wed, 16 May 2012 19:14:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Steve</title>
		<link>http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/comment-page-1/#comment-92237</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Sun, 18 Jan 2009 16:39:37 +0000</pubDate>
		<guid isPermaLink="false">http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/#comment-92237</guid>
		<description>The whole idea is bad, somehow the concept from XHTML2 was ignored, were you can have an additional attribute &quot;role&quot;, separated from the class and it&#039;s association with the styling of the document.

(div class=&quot;tbrdr2&quot; role=&quot;Branding&quot;) ... (/div)

I still wish that HTML5 took more from XHTML2, which seems destined to be the great idea that has zero browser support, and were left with XHTML5 which seems to be just HTML5 with close tags.</description>
		<content:encoded><![CDATA[<p>The whole idea is bad, somehow the concept from XHTML2 was ignored, were you can have an additional attribute &#8220;role&#8221;, separated from the class and it&#8217;s association with the styling of the document.</p>
<p>(div class=&#8221;tbrdr2&#8243; role=&#8221;Branding&#8221;) &#8230; (/div)</p>
<p>I still wish that HTML5 took more from XHTML2, which seems destined to be the great idea that has zero browser support, and were left with XHTML5 which seems to be just HTML5 with close tags.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: blinds</title>
		<link>http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/comment-page-1/#comment-51862</link>
		<dc:creator>blinds</dc:creator>
		<pubDate>Sun, 13 Apr 2008 15:22:02 +0000</pubDate>
		<guid isPermaLink="false">http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/#comment-51862</guid>
		<description>oops, my markup dissappeared :-)

so again:
bad markup:

header
  h1
    logo
    SITE-title
  /h1
/header

content


good markup:

h1 PAGE title /h1

content

branding logo /branding</description>
		<content:encoded><![CDATA[<p>oops, my markup dissappeared <img src='http://f6design.com/journal/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>so again:<br />
bad markup:</p>
<p>header<br />
  h1<br />
    logo<br />
    SITE-title<br />
  /h1<br />
/header</p>
<p>content</p>
<p>good markup:</p>
<p>h1 PAGE title /h1</p>
<p>content</p>
<p>branding logo /branding</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: blinds</title>
		<link>http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/comment-page-1/#comment-51860</link>
		<dc:creator>blinds</dc:creator>
		<pubDate>Sun, 13 Apr 2008 15:18:56 +0000</pubDate>
		<guid isPermaLink="false">http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/#comment-51860</guid>
		<description>I totally agree with Jonathan. What if you decide not put your logo on top of your content, but right or left of it? You could put your branding markup, where ever you want:

Instead of doing stupid:


   
      
       
  




you could do:

page title



Thanks Jonathan. I was furious and dissapointed about the W3C&#039;s HTML5 proposal, too, but too busy and angry to write about it. Thanks for pointing it out.</description>
		<content:encoded><![CDATA[<p>I totally agree with Jonathan. What if you decide not put your logo on top of your content, but right or left of it? You could put your branding markup, where ever you want:</p>
<p>Instead of doing stupid:</p>
<p>you could do:</p>
<p>page title</p>
<p>Thanks Jonathan. I was furious and dissapointed about the W3C&#8217;s HTML5 proposal, too, but too busy and angry to write about it. Thanks for pointing it out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tedd</title>
		<link>http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/comment-page-1/#comment-35925</link>
		<dc:creator>tedd</dc:creator>
		<pubDate>Tue, 18 Dec 2007 06:33:11 +0000</pubDate>
		<guid isPermaLink="false">http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/#comment-35925</guid>
		<description>Hearing a different view is not giving up, but rather listening.

Cheers,

tedd</description>
		<content:encoded><![CDATA[<p>Hearing a different view is not giving up, but rather listening.</p>
<p>Cheers,</p>
<p>tedd</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jermayn Parker</title>
		<link>http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/comment-page-1/#comment-35873</link>
		<dc:creator>Jermayn Parker</dc:creator>
		<pubDate>Tue, 18 Dec 2007 00:07:57 +0000</pubDate>
		<guid isPermaLink="false">http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/#comment-35873</guid>
		<description>@Tedd - I dont mean a &#039;fight&#039; I mean is he going to give up on his point of view so easily. Sorry its an Australian saying, so sorry for any misunderstanding.</description>
		<content:encoded><![CDATA[<p>@Tedd &#8211; I dont mean a &#8216;fight&#8217; I mean is he going to give up on his point of view so easily. Sorry its an Australian saying, so sorry for any misunderstanding.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tedd</title>
		<link>http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/comment-page-1/#comment-35807</link>
		<dc:creator>tedd</dc:creator>
		<pubDate>Mon, 17 Dec 2007 14:06:25 +0000</pubDate>
		<guid isPermaLink="false">http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/#comment-35807</guid>
		<description>It&#039;s not a fight, but a discussion.

There&#039;s no &quot;right&quot; answer, but answers that fit the needs.

Semantic means different things to different people.</description>
		<content:encoded><![CDATA[<p>It&#8217;s not a fight, but a discussion.</p>
<p>There&#8217;s no &#8220;right&#8221; answer, but answers that fit the needs.</p>
<p>Semantic means different things to different people.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jermayn Parker</title>
		<link>http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/comment-page-1/#comment-35688</link>
		<dc:creator>Jermayn Parker</dc:creator>
		<pubDate>Sun, 16 Dec 2007 23:30:35 +0000</pubDate>
		<guid isPermaLink="false">http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/#comment-35688</guid>
		<description>You giving up without a fight Jonathan???</description>
		<content:encoded><![CDATA[<p>You giving up without a fight Jonathan???</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan</title>
		<link>http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/comment-page-1/#comment-35143</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Thu, 13 Dec 2007 19:56:02 +0000</pubDate>
		<guid isPermaLink="false">http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/#comment-35143</guid>
		<description>@Jermayn - It&#039;s a good point you make that markup re-usability be an important consideration. &lt;code&gt;header&lt;/code&gt; and &lt;code&gt;footer&lt;/code&gt; are two terms that are widely understood, so I realise I am playing the devils advocate by pointing out possible flaws with their semantic appropriateness. 

Judging from reader&#039;s comments I&#039;m in the minority on this one - long live &lt;code&gt;header&lt;/code&gt; and &lt;code&gt;footer&lt;/code&gt;!</description>
		<content:encoded><![CDATA[<p>@Jermayn &#8211; It&#8217;s a good point you make that markup re-usability be an important consideration. <code>header</code> and <code>footer</code> are two terms that are widely understood, so I realise I am playing the devils advocate by pointing out possible flaws with their semantic appropriateness. </p>
<p>Judging from reader&#8217;s comments I&#8217;m in the minority on this one &#8211; long live <code>header</code> and <code>footer</code>!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jermayn Parker</title>
		<link>http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/comment-page-1/#comment-34991</link>
		<dc:creator>Jermayn Parker</dc:creator>
		<pubDate>Thu, 13 Dec 2007 01:34:59 +0000</pubDate>
		<guid isPermaLink="false">http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/#comment-34991</guid>
		<description>I personally think its a good idea having &lt;code&gt;footer&lt;/code&gt; etc. While the Clarke idea is interesting, I think it fails in one area and that is if anyone has to rework your code. I hate having to read and rework other peoples code because of the confusing div naming and I think using &lt;em&gt;branding&lt;/em&gt; etc is too confusing.</description>
		<content:encoded><![CDATA[<p>I personally think its a good idea having <code>footer</code> etc. While the Clarke idea is interesting, I think it fails in one area and that is if anyone has to rework your code. I hate having to read and rework other peoples code because of the confusing div naming and I think using <em>branding</em> etc is too confusing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan</title>
		<link>http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/comment-page-1/#comment-34088</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Sat, 08 Dec 2007 01:51:05 +0000</pubDate>
		<guid isPermaLink="false">http://f6design.com/journal/2007/12/04/semantic-html-5-pfft/#comment-34088</guid>
		<description>@Tedd: I don&#039;t think the proposed naming convention is necessarily bad - I certainly wouldn&#039;t suggest my naming convention as an alternative! Like you say, my alternatives to header/footer make sense to me and the way I structure my pages, and wouldn&#039;t necessarily be as meaningful to someone else.

(I didn&#039;t actually make them up myself by the way - those are the names suggested by Andy Clarke in his book Transcending CSS)

What I find interesting is the to-and-fro of web design best practices. Andy Clarke and cohorts encourage us to make our markup semantic to the nth degree - advice I put to practice in my own work. While on the other hand the HTML 5 team seem to see no problem with describing content based on visual appearance (where it is likely to appear on the page).

I am curious to know if the new HTML elements will have a formatting bias as well. Will the new elements (header, footer, section, nav, aside) have some sort of default styles applied to them - will an aside be floated right, for instance, or will text in the footer be smaller than regular body copy?</description>
		<content:encoded><![CDATA[<p>@Tedd: I don&#8217;t think the proposed naming convention is necessarily bad &#8211; I certainly wouldn&#8217;t suggest my naming convention as an alternative! Like you say, my alternatives to header/footer make sense to me and the way I structure my pages, and wouldn&#8217;t necessarily be as meaningful to someone else.</p>
<p>(I didn&#8217;t actually make them up myself by the way &#8211; those are the names suggested by Andy Clarke in his book Transcending CSS)</p>
<p>What I find interesting is the to-and-fro of web design best practices. Andy Clarke and cohorts encourage us to make our markup semantic to the nth degree &#8211; advice I put to practice in my own work. While on the other hand the HTML 5 team seem to see no problem with describing content based on visual appearance (where it is likely to appear on the page).</p>
<p>I am curious to know if the new HTML elements will have a formatting bias as well. Will the new elements (header, footer, section, nav, aside) have some sort of default styles applied to them &#8211; will an aside be floated right, for instance, or will text in the footer be smaller than regular body copy?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

