<?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: Rethinking Header Markup</title>
	<atom:link href="http://octidextro.us/2009/02/03/rethinking-header-markup/feed/" rel="self" type="application/rss+xml" />
	<link>http://octidextro.us/2009/02/03/rethinking-header-markup/</link>
	<description>i code in iambic pentameter</description>
	<lastBuildDate>Mon, 27 Jun 2011 20:49:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: M. Dave Auayan</title>
		<link>http://octidextro.us/2009/02/03/rethinking-header-markup/comment-page-1/#comment-6181</link>
		<dc:creator>M. Dave Auayan</dc:creator>
		<pubDate>Sun, 07 Feb 2010 02:16:56 +0000</pubDate>
		<guid isPermaLink="false">http://octidextro.us/?p=329#comment-6181</guid>
		<description>&lt;p&gt;thank disqus for the completely fucked handling of markup.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>thank disqus for the completely fucked handling of markup.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Myhrberg</title>
		<link>http://octidextro.us/2009/02/03/rethinking-header-markup/comment-page-1/#comment-6180</link>
		<dc:creator>Jim Myhrberg</dc:creator>
		<pubDate>Sun, 07 Feb 2010 02:11:41 +0000</pubDate>
		<guid isPermaLink="false">http://octidextro.us/?p=329#comment-6180</guid>
		<description>&lt;p&gt;Let&#039;s try some html in comments...&lt;br&gt;&lt;br&gt;&lt;/p&gt;

&lt;h1&gt;H1 Heading&lt;/h1&gt;

&lt;p&gt;&lt;br&gt;&lt;br&gt;&lt;/p&gt;

&lt;h2&gt;Unclosed H2 Heading&lt;br&gt;&lt;br&gt;&lt;div&gt;some other&lt;b&gt;&lt;code&gt; html goes&lt;/code&gt; here.&lt;/b&gt;&lt;/h2&gt;
</description>
		<content:encoded><![CDATA[<p>Let&#39;s try some html in comments&#8230;<br /><br /></p>

<h1>H1 Heading</h1>

<p><br /><br /></p>

<h2>Unclosed H2 Heading<br /><br />&lt;div&gt;some other<b><code> html goes</code> here.</b></h2>]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://octidextro.us/2009/02/03/rethinking-header-markup/comment-page-1/#comment-917</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Sat, 28 Mar 2009 20:29:44 +0000</pubDate>
		<guid isPermaLink="false">http://octidextro.us/?p=329#comment-917</guid>
		<description>&lt;p&gt;@Thomas Some people would argue using the &lt;code class=&#039;prettyprint&#039;&gt;&lt;dl&gt;&lt;/code&gt; for anything other than a definition list in the strictest sense would be abusing it (e.g., using it to mark up an image gallery with captions, credit, etc). More examples can be found here: http://www.maxdesign.com.au/presentation/definition/&lt;/p&gt;

&lt;p&gt;Personally, I think without the flexibility some have introduced to the tag, it should just be removed from the spec. The  could just be reintroduced if people miss the .&lt;/p&gt;

&lt;p&gt;@Dan Calling for things to be semantic is all well and good, but you have to allow for growth. If people find a better use for your product than the one you intended, you should learn to adapt to that rather than fight it. I don&#039;t agree with all or even most uses of the &lt;code class=&#039;prettyprint&#039;&gt;&lt;dl&gt;&lt;/code&gt; element, but I&#039;m all for experimentation so long as the page is well-structured.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@Thomas Some people would argue using the <code class='prettyprint'>&lt;dl&gt;</code> for anything other than a definition list in the strictest sense would be abusing it (e.g., using it to mark up an image gallery with captions, credit, etc). More examples can be found here: <a href="http://www.maxdesign.com.au/presentation/definition/" rel="nofollow">http://www.maxdesign.com.au/presentation/definition/</a></p>

<p>Personally, I think without the flexibility some have introduced to the tag, it should just be removed from the spec. The  could just be reintroduced if people miss the .</p>

<p>@Dan Calling for things to be semantic is all well and good, but you have to allow for growth. If people find a better use for your product than the one you intended, you should learn to adapt to that rather than fight it. I don&#8217;t agree with all or even most uses of the <code class='prettyprint'>&lt;dl&gt;</code> element, but I&#8217;m all for experimentation so long as the page is well-structured.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://octidextro.us/2009/02/03/rethinking-header-markup/comment-page-1/#comment-883</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Tue, 24 Mar 2009 23:55:50 +0000</pubDate>
		<guid isPermaLink="false">http://octidextro.us/?p=329#comment-883</guid>
		<description>&lt;p&gt;Which is why I wouldn&#039;t put the site name in an &lt;code class=&#039;prettyprint&#039;&gt;&lt;h1&gt;&lt;/code&gt; - sorry, I didn&#039;t explicitly state that in my previous comment.&lt;/p&gt;

&lt;p&gt;The page title is usually the most significant piece of information on the page, and so should go in an &lt;code class=&#039;prettyprint&#039;&gt;&lt;h1&gt;&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;I know this would then mean that a link to the home page on the &lt;code class=&#039;prettyprint&#039;&gt;&lt;h1&gt;&lt;/code&gt; would no longer make sense, but there&#039;s no reason why there couldn&#039;t be a link to the home page on the site logo (if you&#039;re not using it as a CSS background image on your &lt;code class=&#039;prettyprint&#039;&gt;&lt;h1&gt;&lt;/code&gt;), or as an item in the navigation, etc.&lt;/p&gt;

&lt;p&gt;Of course, the site name needs to be somewhere, which is why I tend to put it in the &lt;code class=&#039;prettyprint&#039;&gt;&lt;h1&gt;&lt;/code&gt; element, usually following the page title.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Which is why I wouldn&#8217;t put the site name in an <code class='prettyprint'>&lt;h1&gt;</code> &#8211; sorry, I didn&#8217;t explicitly state that in my previous comment.</p>

<p>The page title is usually the most significant piece of information on the page, and so should go in an <code class='prettyprint'>&lt;h1&gt;</code>.</p>

<p>I know this would then mean that a link to the home page on the <code class='prettyprint'>&lt;h1&gt;</code> would no longer make sense, but there&#8217;s no reason why there couldn&#8217;t be a link to the home page on the site logo (if you&#8217;re not using it as a CSS background image on your <code class='prettyprint'>&lt;h1&gt;</code>), or as an item in the navigation, etc.</p>

<p>Of course, the site name needs to be somewhere, which is why I tend to put it in the <code class='prettyprint'>&lt;h1&gt;</code> element, usually following the page title.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: M. Dave Auayan</title>
		<link>http://octidextro.us/2009/02/03/rethinking-header-markup/comment-page-1/#comment-882</link>
		<dc:creator>M. Dave Auayan</dc:creator>
		<pubDate>Tue, 24 Mar 2009 23:38:58 +0000</pubDate>
		<guid isPermaLink="false">http://octidextro.us/?p=329#comment-882</guid>
		<description>&lt;p&gt;Semantically speaking, an &lt;code class=&#039;prettyprint&#039;&gt;&lt;h1&gt;&lt;/code&gt; for the site name has even less to do with the content than an &#039;about&#039; link as a definition to the site name.&lt;/p&gt;

&lt;p&gt;You could also use:&lt;/p&gt;

&lt;p&gt;&lt;code class=&#039;prettyprint&#039;&gt;&lt;dl id=&quot;header&quot;&gt;
    &lt;dt&gt;&lt;a href=&quot;/&quot; title=&quot;Site Name - Home&quot;&gt;Site Name&lt;/a&gt;&lt;/dt&gt;
        &lt;dd&gt;This is my site. There are many like it, but this one is mine.&lt;/dd&gt;
&lt;/dl&gt;&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;As someone pointed out, have you tried navigating a page that used &lt;code class=&#039;prettyprint&#039;&gt;&lt;h1&gt;&lt;/code&gt; tags for the site name?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Semantically speaking, an <code class='prettyprint'>&lt;h1&gt;</code> for the site name has even less to do with the content than an &#8216;about&#8217; link as a definition to the site name.</p>

<p>You could also use:</p>

<p><code class='prettyprint'>&lt;dl id="header"&gt;
    &lt;dt&gt;&lt;a href="/" title="Site Name - Home"&gt;Site Name&lt;/a&gt;&lt;/dt&gt;
        &lt;dd&gt;This is my site. There are many like it, but this one is mine.&lt;/dd&gt;
&lt;/dl&gt;</code></p>

<p>As someone pointed out, have you tried navigating a page that used <code class='prettyprint'>&lt;h1&gt;</code> tags for the site name?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://octidextro.us/2009/02/03/rethinking-header-markup/comment-page-1/#comment-881</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Tue, 24 Mar 2009 23:30:32 +0000</pubDate>
		<guid isPermaLink="false">http://octidextro.us/?p=329#comment-881</guid>
		<description>&lt;p&gt;It&#039;s not a matter of being a &lt;code class=&#039;prettyprint&#039;&gt;&lt;dl&gt;&lt;/code&gt; purist as much as it is a matter of writing semantic markup.&lt;/p&gt;

&lt;p&gt;What the code here is describing is not a definition list. &#039;Site Name&#039; is not a definition title, nor are &#039;page name&#039; and &#039;page name 2&#039; definition descriptions for &#039;Site Name&#039;.&lt;/p&gt;

&lt;p&gt;We should use an &lt;code class=&#039;prettyprint&#039;&gt;&lt;h1&gt;&lt;/code&gt; for the most important heading on a page. Matt Cutts says it doesn&#039;t really matter if we have a couple or even three&lt;/p&gt;

&lt;p&gt;&lt;code class=&#039;prettyprint&#039;&gt;&lt;h1&gt;&lt;/code&gt; elements on the same page (as long as the content they markup is of equal importance); Google will only penalize us if we&#039;re obviously trying to abuse the &lt;code class=&#039;prettyprint&#039;&gt;&lt;h1&gt;&lt;/code&gt; element; i.e. not using them in an semantically correct fashion.&lt;/p&gt;

&lt;p&gt;The  element in the document  would usually contain the title of the current page, and often the site name. 
The first or only&lt;/p&gt;

&lt;p&gt;&lt;code class=&#039;prettyprint&#039;&gt;&lt;h1&gt;&lt;/code&gt; element on the page should contain the page title. If a logo is required, there&#039;s no reason why it can&#039;t be a CSS background image on the &lt;code class=&#039;prettyprint&#039;&gt;&lt;h1&gt;&lt;/code&gt; element.&lt;/p&gt;

&lt;p&gt;As far as I understand it, Google likes page headings to be unique, so putting the site name in the&lt;/p&gt;

&lt;p&gt;&lt;code class=&#039;prettyprint&#039;&gt;&lt;h1&gt;&lt;/code&gt; element on every page will reduce the uniqueness of the content and may do the site more harm than good.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>It&#8217;s not a matter of being a <code class='prettyprint'>&lt;dl&gt;</code> purist as much as it is a matter of writing semantic markup.</p>

<p>What the code here is describing is not a definition list. &#8216;Site Name&#8217; is not a definition title, nor are &#8216;page name&#8217; and &#8216;page name 2&#8242; definition descriptions for &#8216;Site Name&#8217;.</p>

<p>We should use an <code class='prettyprint'>&lt;h1&gt;</code> for the most important heading on a page. Matt Cutts says it doesn&#8217;t really matter if we have a couple or even three</p>

<p><code class='prettyprint'>&lt;h1&gt;</code> elements on the same page (as long as the content they markup is of equal importance); Google will only penalize us if we&#8217;re obviously trying to abuse the <code class='prettyprint'>&lt;h1&gt;</code> element; i.e. not using them in an semantically correct fashion.</p>

<p>The  element in the document  would usually contain the title of the current page, and often the site name. 
The first or only</p>

<p><code class='prettyprint'>&lt;h1&gt;</code> element on the page should contain the page title. If a logo is required, there&#8217;s no reason why it can&#8217;t be a CSS background image on the <code class='prettyprint'>&lt;h1&gt;</code> element.</p>

<p>As far as I understand it, Google likes page headings to be unique, so putting the site name in the</p>

<p><code class='prettyprint'>&lt;h1&gt;</code> element on every page will reduce the uniqueness of the content and may do the site more harm than good.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Thomassen</title>
		<link>http://octidextro.us/2009/02/03/rethinking-header-markup/comment-page-1/#comment-877</link>
		<dc:creator>Thomas Thomassen</dc:creator>
		<pubDate>Tue, 24 Mar 2009 16:07:34 +0000</pubDate>
		<guid isPermaLink="false">http://octidextro.us/?p=329#comment-877</guid>
		<description>&lt;p&gt;@Jason: dl elements are abused? I can&#039;t say I&#039;ve seen too many of that element around... Care to elaborate?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@Jason: dl elements are abused? I can&#8217;t say I&#8217;ve seen too many of that element around&#8230; Care to elaborate?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: M. Dave Auayan</title>
		<link>http://octidextro.us/2009/02/03/rethinking-header-markup/comment-page-1/#comment-466</link>
		<dc:creator>M. Dave Auayan</dc:creator>
		<pubDate>Wed, 04 Feb 2009 00:48:20 +0000</pubDate>
		<guid isPermaLink="false">http://octidextro.us/?p=329#comment-466</guid>
		<description>&lt;p&gt;There are &lt;code&gt;&lt;dl&gt;&lt;/code&gt; purists?!&lt;/p&gt;

&lt;p&gt;(I fixed that for you; I&#039;m using markdown so that might have been the problem.)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>There are <code>&lt;dl&gt;</code> purists?!</p>

<p>(I fixed that for you; I&#8217;m using markdown so that might have been the problem.)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://octidextro.us/2009/02/03/rethinking-header-markup/comment-page-1/#comment-465</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Wed, 04 Feb 2009 00:43:12 +0000</pubDate>
		<guid isPermaLink="false">http://octidextro.us/?p=329#comment-465</guid>
		<description>&lt;p&gt;Oh wow. That didn&#039;t come out quite right.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Oh wow. That didn&#8217;t come out quite right.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://octidextro.us/2009/02/03/rethinking-header-markup/comment-page-1/#comment-464</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Wed, 04 Feb 2009 00:41:53 +0000</pubDate>
		<guid isPermaLink="false">http://octidextro.us/?p=329#comment-464</guid>
		<description>&lt;p&gt;Interesting. I&#039;ve never used a &lt;code&gt;&lt;dl&gt;&lt;/code&gt; in the manner you mention – I generally use it for lists connected to pictures. I agree that using the &lt;code&gt;&lt;h1&gt;&lt;/code&gt; on the site link is a bit annoying, but I usually still do it. I wonder how SEO people would react to your suggestion, let alone the &lt;code&gt;&lt;dl&gt;&lt;/code&gt; purists who already think it&#039;s been abused.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Interesting. I&#8217;ve never used a <code>&lt;dl&gt;</code> in the manner you mention – I generally use it for lists connected to pictures. I agree that using the <code>&lt;h1&gt;</code> on the site link is a bit annoying, but I usually still do it. I wonder how SEO people would react to your suggestion, let alone the <code>&lt;dl&gt;</code> purists who already think it&#8217;s been abused.</p>]]></content:encoded>
	</item>
</channel>
</rss>

