<?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: The footer element</title>
	<atom:link href="http://html5doctor.com/the-footer-element/feed/" rel="self" type="application/rss+xml" />
	<link>http://html5doctor.com/the-footer-element/</link>
	<description>helping you implement HTML5 today</description>
	<lastBuildDate>Mon, 06 Feb 2012 20:26:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: L&#8217;élément footer &#124; Docteur HTML5</title>
		<link>http://html5doctor.com/the-footer-element/#comment-10089</link>
		<dc:creator>L&#8217;élément footer &#124; Docteur HTML5</dc:creator>
		<pubDate>Thu, 12 Aug 2010 21:30:42 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=159#comment-10089</guid>
		<description>[...] Liens vers l&#8217;article L&#8217;élément footer en anglais [...]</description>
		<content:encoded><![CDATA[<p>[...] Liens vers l&#8217;article L&#8217;élément footer en anglais [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexander Simoes: Journal &#8211; New Obsession: HTML 5</title>
		<link>http://html5doctor.com/the-footer-element/#comment-3414</link>
		<dc:creator>Alexander Simoes: Journal &#8211; New Obsession: HTML 5</dc:creator>
		<pubDate>Sun, 02 May 2010 21:59:23 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=159#comment-3414</guid>
		<description>[...] http://html5doctor.com/the-footer-element/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://html5doctor.com/the-footer-element/" rel="nofollow">http://html5doctor.com/the-footer-element/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Loick</title>
		<link>http://html5doctor.com/the-footer-element/#comment-266</link>
		<dc:creator>Loick</dc:creator>
		<pubDate>Mon, 20 Jul 2009 18:14:23 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=159#comment-266</guid>
		<description>but I t hink XHML5 is the way to go

thank you</description>
		<content:encoded><![CDATA[<p>but I t hink XHML5 is the way to go</p>
<p>thank you</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carlos</title>
		<link>http://html5doctor.com/the-footer-element/#comment-265</link>
		<dc:creator>Carlos</dc:creator>
		<pubDate>Mon, 20 Jul 2009 17:38:52 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=159#comment-265</guid>
		<description>@Loick

If you use &#039;section&#039; for everything, in the future this may have consequences for the search engine relevance of your pages. For example, if I do a search for &#039;foo bar&#039; and your document has one section with a &#039;foo&#039; and then another with a &#039;bar&#039;, this is likely to be considered a less relevant match than another document where both &#039;foo&#039; and &#039;bar&#039; appear inside the same section (or even with no sections but inside the same &#039;div&#039;).

This is an over-simplified example, and I do not think that search engines do this yet, but these semantic elements are being introduced precisely with this intention. At present, writing XHTML does not harm, but in the future HTML5 markup may have slightly better search relevance, and then people will want HTML5 on their websites. As Jack mentions, this also depends on people using the markup correctly.</description>
		<content:encoded><![CDATA[<p>@Loick</p>
<p>If you use &#8216;section&#8217; for everything, in the future this may have consequences for the search engine relevance of your pages. For example, if I do a search for &#8216;foo bar&#8217; and your document has one section with a &#8216;foo&#8217; and then another with a &#8216;bar&#8217;, this is likely to be considered a less relevant match than another document where both &#8216;foo&#8217; and &#8216;bar&#8217; appear inside the same section (or even with no sections but inside the same &#8216;div&#8217;).</p>
<p>This is an over-simplified example, and I do not think that search engines do this yet, but these semantic elements are being introduced precisely with this intention. At present, writing XHTML does not harm, but in the future HTML5 markup may have slightly better search relevance, and then people will want HTML5 on their websites. As Jack mentions, this also depends on people using the markup correctly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Loick</title>
		<link>http://html5doctor.com/the-footer-element/#comment-264</link>
		<dc:creator>Loick</dc:creator>
		<pubDate>Mon, 20 Jul 2009 17:12:34 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=159#comment-264</guid>
		<description>ok Jack , I find it very interesting and I shall try it soon, but I keep coding XHTML   and not </description>
		<content:encoded><![CDATA[<p>ok Jack , I find it very interesting and I shall try it soon, but I keep coding XHTML   and not</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack Osborne</title>
		<link>http://html5doctor.com/the-footer-element/#comment-263</link>
		<dc:creator>Jack Osborne</dc:creator>
		<pubDate>Mon, 20 Jul 2009 17:10:09 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=159#comment-263</guid>
		<description>@Loick Please don&#039;t use &quot;section for everything&quot; what&#039;s the point in having all these elements if you&#039;re not going to utilise them correctly?</description>
		<content:encoded><![CDATA[<p>@Loick Please don&#8217;t use &#8220;section for everything&#8221; what&#8217;s the point in having all these elements if you&#8217;re not going to utilise them correctly?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Loick</title>
		<link>http://html5doctor.com/the-footer-element/#comment-262</link>
		<dc:creator>Loick</dc:creator>
		<pubDate>Mon, 20 Jul 2009 16:57:41 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=159#comment-262</guid>
		<description>anyway I can use section for everything 

thank you Carlos</description>
		<content:encoded><![CDATA[<p>anyway I can use section for everything </p>
<p>thank you Carlos</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carlos</title>
		<link>http://html5doctor.com/the-footer-element/#comment-261</link>
		<dc:creator>Carlos</dc:creator>
		<pubDate>Mon, 20 Jul 2009 14:43:32 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=159#comment-261</guid>
		<description>@Loick

The uses you mention seem to be for the &#039;nav&#039; element, and not for headers or footers. The new elements are semantic, not presentational.</description>
		<content:encoded><![CDATA[<p>@Loick</p>
<p>The uses you mention seem to be for the &#8216;nav&#8217; element, and not for headers or footers. The new elements are semantic, not presentational.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Loick</title>
		<link>http://html5doctor.com/the-footer-element/#comment-257</link>
		<dc:creator>Loick</dc:creator>
		<pubDate>Mon, 20 Jul 2009 05:23:26 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=159#comment-257</guid>
		<description>And If you want to do many skins

the menu on top or on the left  , the footer at the bottom but sometimes on the right  ?</description>
		<content:encoded><![CDATA[<p>And If you want to do many skins</p>
<p>the menu on top or on the left  , the footer at the bottom but sometimes on the right  ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Romy</title>
		<link>http://html5doctor.com/the-footer-element/#comment-246</link>
		<dc:creator>Romy</dc:creator>
		<pubDate>Sat, 18 Jul 2009 09:50:41 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=159#comment-246</guid>
		<description>Thank you for this tutorial that clarifies it!</description>
		<content:encoded><![CDATA[<p>Thank you for this tutorial that clarifies it!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

